Jump to content

Memory Management BSOD

GER_T4IGA

My Laptop is not yet "dead" but suddenly "died" the second time now. Blue screen "MEMORY MANAGMENT" both times while watching twitch.tv.

Any ideas?

If you can help my I would also be happy to be redirected to any other forum if you know any.

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Update: boot up after crashes takes about twice as long(not kidding)

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Did you run MemTest86 to see if there is any problem with memory modules?

Intel Core i3 2100 @ 3.10GHz - Intel Stock Cooler - Zotac Geforce GT 610 2GB Synergy Edition

Intel DH61WW - Corsair® Value Select 4GBx1 DDR3 1600 MHz - Antec BP-300P PSU

WD Green 1TB - Seagate 2.5" HDD 1TB - Seagate Barracuda 500GB - Antec X1 E.

Link to comment
Share on other sites

Link to post
Share on other sites

Follow the instructions pinned in the top of this subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

I'm about to leave my home for the next hour or so, I'll take a look at the dump files when I get back. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Follow the instructions pinned in the top of this subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

I'm about to leave my home for the next hour or so, I'll take a look at the dump files when I get back. 

it kind of is stuck at waiting for syteminfo and that for awhile now? wait or do I have a problem?

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

it kind of is stuck at waiting for syteminfo and that for awhile now? wait or do I have a problem?

Follow Method B then. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Follow Method B then. 

ASUS K73SV-TY032V (laptop)

running Win7 x64 that came with it. never reinstalled.

system is pretty old... ~5 years or more

gt 540m

i5 2430m

... I guess you can check all that with the model number. If you need more: Ask.

https://drive.google.com/file/d/0B_EBxJIuS4fmVmdkb1NaZWRFUGM/view?usp=sharing

https://drive.google.com/file/d/0B_EBxJIuS4fmSlZXeTMzc3FwVkU/view?usp=sharing        files on google drive

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

ASUS K73SV-TY032V (laptop)

running Win7 x64 that came with it. never reinstalled.

system is pretty old... ~5 years or more

gt 540m

i5 2430m

... I guess you can check all that with the model number. If you need more: Ask.

https://drive.google.com/file/d/0B_EBxJIuS4fmVmdkb1NaZWRFUGM/view?usp=sharing

https://drive.google.com/file/d/0B_EBxJIuS4fmSlZXeTMzc3FwVkU/view?usp=sharing        files on google drive

I tried to request access?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

I tried to request access?

wait what?

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, you either have an GPU driver issue or an memory issues. Updating GPU drivers on dual graphics/Nvidia Optimus systems is kinda a pain.

 

So here we go:

 

First check that there is an option in the BIOS to disable the Nvidia (dedicated) GPU. If there is, do it, if not continue with the steps below:

Start by disabling the Nvidia GPU in device manager and then using DDU (Display Driver Uninstaller) to remove the NVIDIA drivers. Link to DDU: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Next restart, and check that the Nvidia card is still disabled. We'll now try to update the Intel iGPU driver.

Go download this driver from Intel's website: https://downloadcenter.intel.com/download/24971/Intel-HD-Graphics-Driver-for-Windows-7-8-64-bit

Start by trying to download and run the setup.EXE

Will it install this way? If not, you'll have to download the .ZIP and then manually update the driver via device manager by pointing it to the unzipped folder.

Next, restart and re-enable the Nvidia GPU in device manager and re-install the latest GPU driver from the Nvidia website.

Let me know once you have that done. Well do a memory test with instructions I give you.

BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000334aa40 to fffff800032d95c0STACK_TEXT:  fffff880`0e75cf68 fffff800`0334aa40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0e75cf70 fffff800`032c6a3f : fffffa80`00000000 00000000`486a9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0e75d130 fffff800`032d8853 : ffffffff`ffffffff fffff8a0`13e48b88 fffff8a0`13e48bb0 00000140`00008000 : nt!NtFreeVirtualMemory+0x61ffffff880`0e75d230 fffff800`032d4e10 : fffff880`06cf262e fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 : nt!KiSystemServiceCopyEnd+0x13fffff880`0e75d3c8 fffff880`06cf262e : fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 fffff8a0`13e48b80 : nt!KiServiceLinkagefffff880`0e75d3d0 fffff880`06cddc93 : 00000000`00000000 fffff8a0`01393f10 00000000`00000001 00000000`fffdb000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2fffff880`0e75d400 fffff880`06cd8637 : fffffa80`09ede650 00000000`00000001 fffff8a0`0c1f57a0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11bfffff880`0e75d4b0 fffff880`06cbeecc : 00000000`00000000 fffff800`00000000 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0e75d580 fffff880`08b20ccc : fffff8a0`0478d750 fffff8a0`0064b000 fffff8a0`0064b000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0e75d5b0 fffff880`08b213ac : fffff8a0`03b9a460 fffff8a0`03b9a460 00000000`00000001 fffff8a0`0064b000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0e75d6a0 fffff880`08b20651 : fffff8a0`0064b000 fffff8a0`0064b000 fffff8a0`0ee2cac0 5a5a5a5a`5a5a5a5a : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0e75d6d0 fffff880`08b208e1 : 00000000`00000000 fffff8a0`0064b000 00000000`00000001 fffff8a0`042ff9e0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0e75d720 fffff880`08b24739 : 00000000`00000000 fffff880`0e75db60 00000000`5518b000 fffff880`08aeb3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0e75d770 fffff880`08b27285 : fffff8a0`0064b000 fffff880`0e75d850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0e75d800 fffff960`001fb816 : 00000000`0011fd20 fffffa80`04342060 00000000`00000020 00000000`748d61b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0e75dab0 fffff800`032d8853 : fffffa80`04342060 fffff880`0e75db60 00000000`00000000 00000000`00000020 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0e75dae0 00000000`748f146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0011e1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748f146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2fffff880`06cf262e 488b0e          mov     rcx,qword ptr [rsi]SYMBOL_STACK_INDEX:  5SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_process_heap::free+a2FAILURE_ID_HASH:  {be43f1a4-3662-07ec-1c74-3b363fd9d97d}Followup: MachineOwner 
BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff800032e4a40 to fffff800032735c0STACK_TEXT:  fffff880`0c3a8058 fffff800`032e4a40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0c3a8060 fffff800`032a6f79 : 00000000`00000000 00000000`3dcc9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0c3a8220 fffff800`0358cbd1 : fffffa80`04d4e8c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9fffff880`0c3a8340 fffff880`06a20c28 : 00000000`00000000 fffffa80`04c9dcd0 00000000`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b1fffff880`0c3a8400 fffff880`06a1b637 : fffffa80`04c9dcd0 00000000`00000001 fffff8a0`04cbca40 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xb0fffff880`0c3a84b0 fffff880`06a01ecc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0c3a8580 fffff880`06afdccc : fffff8a0`0f1346d0 fffff8a0`052b1000 fffff8a0`052b1000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0c3a85b0 fffff880`06afe3ac : fffff8a0`0d399b40 fffff8a0`0d399b40 00000000`00000001 fffff8a0`052b1000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0c3a86a0 fffff880`06afd651 : fffff8a0`052b1000 fffff8a0`052b1000 fffff8a0`042bbb20 00000000`00000002 : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0c3a86d0 fffff880`06afd8e1 : fffffa80`0339ccf0 fffff8a0`052b1000 00000000`00000001 fffff8a0`0d1f9560 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0c3a8720 fffff880`06b01739 : 00000000`00000000 fffff880`0c3a8b60 00000000`00000000 fffff880`06ac83af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0c3a8770 fffff880`06b04285 : fffff8a0`052b1000 fffff880`0c3a8850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0c3a8800 fffff960`0024b816 : 00000000`00000000 fffffa80`06b84060 00000000`00000020 00000000`755261b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0c3a8ab0 fffff800`03272853 : fffffa80`06b84060 00000000`0c6bdd40 00000000`00000000 fffffa80`044bb730 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0c3a8ae0 00000000`7554146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0b2be328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7554146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0fffff880`06a20c28 eb7e            jmp     dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x130 (fffff880`06a20ca8)SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_global::closelocalallocation+b0FAILURE_ID_HASH:  {8ed2b5d5-1622-e0b9-6acb-b343a0817f54}Followup: MachineOwner 
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck AB, {1, 210, 0, 2}Probably caused by : memory_corruption ( nt!MiCheckSessionPoolAllocations+13f )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SESSION_HAS_VALID_POOL_ON_EXIT (ab)Caused by a session driver not freeing its pool allocations prior to asession unload.  This indicates a bug in win32k.sys, atmfd.dll,rdpdd.dll or a video driver.Arguments:Arg1: 0000000000000001, session IDArg2: 0000000000000210, number of paged pool bytes that are leakingArg3: 0000000000000000, number of nonpaged pool bytes that are leakingArg4: 0000000000000002, total number of paged and nonpaged allocations that are leaking.	nonpaged allocations are in the upper half of this word,	paged allocations are in the lower half of this word.Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xABPROCESS_NAME:  csrss.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000347a34f to fffff800030d7c40STACK_TEXT:  fffff880`08464988 fffff800`0347a34f : 00000000`000000ab 00000000`00000001 00000000`00000210 00000000`00000000 : nt!KeBugCheckExfffff880`08464990 fffff800`033178c7 : fffff880`05ff2b40 fffff880`05ff2000 fffff880`05ff2000 fffffa80`085fe060 : nt!MiCheckSessionPoolAllocations+0x13ffffff880`084649d0 fffff800`03415ab5 : fffff880`08464a68 fffffa80`085fe060 ffffffff`ffffffc9 fffff880`05ff2000 : nt!MiDereferenceSessionFinal+0x137fffff880`08464a70 fffff800`030a9b10 : fffff800`03260900 00000000`00000001 00000000`00000000 fffffa80`083c29f0 : nt! ?? ::NNGAKEGL::`string'+0x25025fffff880`08464aa0 fffff800`033adb1a : fffff8a0`01fbc630 00000000`00000000 00000000`00000000 fffffa80`085fe060 : nt!MmCleanProcessAddressSpace+0x610fffff880`08464af0 fffff800`033adeed : fffff880`00000000 fffff800`03372f01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x56afffff880`08464bf0 fffff800`030c95e6 : fffff880`009e9180 00000000`00000080 fffffa80`085fe060 fffff880`0144b384 : nt!PspTerminateThreadByPointer+0x4dfffff880`08464c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiCheckSessionPoolAllocations+13ffffff800`0347a34f cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiCheckSessionPoolAllocations+13fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3IMAGE_VERSION:  6.1.7601.17640IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fBUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xab_nt!michecksessionpoolallocations+13fFAILURE_ID_HASH:  {b8931bc3-cc7a-1f8b-2c00-6940a8b93fa1}Followup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, you either have an GPU driver issue or an memory issues. Updating GPU drivers on dual graphics/Nvidia Optimus systems is kinda a pain.

 

So here we go:

 

First check that there is an option in the BIOS to disable the Nvidia (dedicated) GPU. If there is, do it, if not continue with the steps below:

Start by disabling the Nvidia GPU in device manager and then using DDU (Display Driver Uninstaller) to remove the NVIDIA drivers. Link to DDU: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Next restart, and check that the Nvidia card is still disabled. We'll now try to update the Intel iGPU driver.

Go download this driver from Intel's website: https://downloadcenter.intel.com/download/24971/Intel-HD-Graphics-Driver-for-Windows-7-8-64-bit

Start by trying to download and run the setup.EXE

Will it install this way? If not, you'll have to download the .ZIP and then manually update the driver via device manager by pointing it to the unzipped folder.

Next, restart and re-enable the Nvidia GPU in device manager and re-install the latest GPU driver from the Nvidia website.

Let me know once you have that done. Well do a memory test with instructions I give you.

thx be right back

BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000334aa40 to fffff800032d95c0STACK_TEXT:  fffff880`0e75cf68 fffff800`0334aa40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0e75cf70 fffff800`032c6a3f : fffffa80`00000000 00000000`486a9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0e75d130 fffff800`032d8853 : ffffffff`ffffffff fffff8a0`13e48b88 fffff8a0`13e48bb0 00000140`00008000 : nt!NtFreeVirtualMemory+0x61ffffff880`0e75d230 fffff800`032d4e10 : fffff880`06cf262e fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 : nt!KiSystemServiceCopyEnd+0x13fffff880`0e75d3c8 fffff880`06cf262e : fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 fffff8a0`13e48b80 : nt!KiServiceLinkagefffff880`0e75d3d0 fffff880`06cddc93 : 00000000`00000000 fffff8a0`01393f10 00000000`00000001 00000000`fffdb000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2fffff880`0e75d400 fffff880`06cd8637 : fffffa80`09ede650 00000000`00000001 fffff8a0`0c1f57a0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11bfffff880`0e75d4b0 fffff880`06cbeecc : 00000000`00000000 fffff800`00000000 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0e75d580 fffff880`08b20ccc : fffff8a0`0478d750 fffff8a0`0064b000 fffff8a0`0064b000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0e75d5b0 fffff880`08b213ac : fffff8a0`03b9a460 fffff8a0`03b9a460 00000000`00000001 fffff8a0`0064b000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0e75d6a0 fffff880`08b20651 : fffff8a0`0064b000 fffff8a0`0064b000 fffff8a0`0ee2cac0 5a5a5a5a`5a5a5a5a : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0e75d6d0 fffff880`08b208e1 : 00000000`00000000 fffff8a0`0064b000 00000000`00000001 fffff8a0`042ff9e0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0e75d720 fffff880`08b24739 : 00000000`00000000 fffff880`0e75db60 00000000`5518b000 fffff880`08aeb3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0e75d770 fffff880`08b27285 : fffff8a0`0064b000 fffff880`0e75d850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0e75d800 fffff960`001fb816 : 00000000`0011fd20 fffffa80`04342060 00000000`00000020 00000000`748d61b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0e75dab0 fffff800`032d8853 : fffffa80`04342060 fffff880`0e75db60 00000000`00000000 00000000`00000020 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0e75dae0 00000000`748f146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0011e1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748f146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2fffff880`06cf262e 488b0e          mov     rcx,qword ptr [rsi]SYMBOL_STACK_INDEX:  5SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_process_heap::free+a2FAILURE_ID_HASH:  {be43f1a4-3662-07ec-1c74-3b363fd9d97d}Followup: MachineOwner 
BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff800032e4a40 to fffff800032735c0STACK_TEXT:  fffff880`0c3a8058 fffff800`032e4a40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0c3a8060 fffff800`032a6f79 : 00000000`00000000 00000000`3dcc9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0c3a8220 fffff800`0358cbd1 : fffffa80`04d4e8c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9fffff880`0c3a8340 fffff880`06a20c28 : 00000000`00000000 fffffa80`04c9dcd0 00000000`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b1fffff880`0c3a8400 fffff880`06a1b637 : fffffa80`04c9dcd0 00000000`00000001 fffff8a0`04cbca40 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xb0fffff880`0c3a84b0 fffff880`06a01ecc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0c3a8580 fffff880`06afdccc : fffff8a0`0f1346d0 fffff8a0`052b1000 fffff8a0`052b1000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0c3a85b0 fffff880`06afe3ac : fffff8a0`0d399b40 fffff8a0`0d399b40 00000000`00000001 fffff8a0`052b1000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0c3a86a0 fffff880`06afd651 : fffff8a0`052b1000 fffff8a0`052b1000 fffff8a0`042bbb20 00000000`00000002 : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0c3a86d0 fffff880`06afd8e1 : fffffa80`0339ccf0 fffff8a0`052b1000 00000000`00000001 fffff8a0`0d1f9560 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0c3a8720 fffff880`06b01739 : 00000000`00000000 fffff880`0c3a8b60 00000000`00000000 fffff880`06ac83af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0c3a8770 fffff880`06b04285 : fffff8a0`052b1000 fffff880`0c3a8850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0c3a8800 fffff960`0024b816 : 00000000`00000000 fffffa80`06b84060 00000000`00000020 00000000`755261b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0c3a8ab0 fffff800`03272853 : fffffa80`06b84060 00000000`0c6bdd40 00000000`00000000 fffffa80`044bb730 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0c3a8ae0 00000000`7554146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0b2be328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7554146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0fffff880`06a20c28 eb7e            jmp     dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x130 (fffff880`06a20ca8)SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_global::closelocalallocation+b0FAILURE_ID_HASH:  {8ed2b5d5-1622-e0b9-6acb-b343a0817f54}Followup: MachineOwner 
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck AB, {1, 210, 0, 2}Probably caused by : memory_corruption ( nt!MiCheckSessionPoolAllocations+13f )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SESSION_HAS_VALID_POOL_ON_EXIT (ab)Caused by a session driver not freeing its pool allocations prior to asession unload.  This indicates a bug in win32k.sys, atmfd.dll,rdpdd.dll or a video driver.Arguments:Arg1: 0000000000000001, session IDArg2: 0000000000000210, number of paged pool bytes that are leakingArg3: 0000000000000000, number of nonpaged pool bytes that are leakingArg4: 0000000000000002, total number of paged and nonpaged allocations that are leaking.	nonpaged allocations are in the upper half of this word,	paged allocations are in the lower half of this word.Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xABPROCESS_NAME:  csrss.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000347a34f to fffff800030d7c40STACK_TEXT:  fffff880`08464988 fffff800`0347a34f : 00000000`000000ab 00000000`00000001 00000000`00000210 00000000`00000000 : nt!KeBugCheckExfffff880`08464990 fffff800`033178c7 : fffff880`05ff2b40 fffff880`05ff2000 fffff880`05ff2000 fffffa80`085fe060 : nt!MiCheckSessionPoolAllocations+0x13ffffff880`084649d0 fffff800`03415ab5 : fffff880`08464a68 fffffa80`085fe060 ffffffff`ffffffc9 fffff880`05ff2000 : nt!MiDereferenceSessionFinal+0x137fffff880`08464a70 fffff800`030a9b10 : fffff800`03260900 00000000`00000001 00000000`00000000 fffffa80`083c29f0 : nt! ?? ::NNGAKEGL::`string'+0x25025fffff880`08464aa0 fffff800`033adb1a : fffff8a0`01fbc630 00000000`00000000 00000000`00000000 fffffa80`085fe060 : nt!MmCleanProcessAddressSpace+0x610fffff880`08464af0 fffff800`033adeed : fffff880`00000000 fffff800`03372f01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x56afffff880`08464bf0 fffff800`030c95e6 : fffff880`009e9180 00000000`00000080 fffffa80`085fe060 fffff880`0144b384 : nt!PspTerminateThreadByPointer+0x4dfffff880`08464c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiCheckSessionPoolAllocations+13ffffff800`0347a34f cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiCheckSessionPoolAllocations+13fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3IMAGE_VERSION:  6.1.7601.17640IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fBUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xab_nt!michecksessionpoolallocations+13fFAILURE_ID_HASH:  {b8931bc3-cc7a-1f8b-2c00-6940a8b93fa1}Followup: MachineOwner 

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, you either have an GPU driver issue or an memory issues. Updating GPU drivers on dual graphics/Nvidia Optimus systems is kinda a pain.

 

So here we go:

 

First check that there is an option in the BIOS to disable the Nvidia (dedicated) GPU. If there is, do it, if not continue with the steps below:

Start by disabling the Nvidia GPU in device manager and then using DDU (Display Driver Uninstaller) to remove the NVIDIA drivers. Link to DDU: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Next restart, and check that the Nvidia card is still disabled. We'll now try to update the Intel iGPU driver.

Go download this driver from Intel's website: https://downloadcenter.intel.com/download/24971/Intel-HD-Graphics-Driver-for-Windows-7-8-64-bit

Start by trying to download and run the setup.EXE

Will it install this way? If not, you'll have to download the .ZIP and then manually update the driver via device manager by pointing it to the unzipped folder.

Next, restart and re-enable the Nvidia GPU in device manager and re-install the latest GPU driver from the Nvidia website.

Let me know once you have that done. Well do a memory test with instructions I give you.

typing this for the 3rd time. So, short: I am until "GPU still disabled"

BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000334aa40 to fffff800032d95c0STACK_TEXT:  fffff880`0e75cf68 fffff800`0334aa40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0e75cf70 fffff800`032c6a3f : fffffa80`00000000 00000000`486a9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0e75d130 fffff800`032d8853 : ffffffff`ffffffff fffff8a0`13e48b88 fffff8a0`13e48bb0 00000140`00008000 : nt!NtFreeVirtualMemory+0x61ffffff880`0e75d230 fffff800`032d4e10 : fffff880`06cf262e fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 : nt!KiSystemServiceCopyEnd+0x13fffff880`0e75d3c8 fffff880`06cf262e : fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 fffff8a0`13e48b80 : nt!KiServiceLinkagefffff880`0e75d3d0 fffff880`06cddc93 : 00000000`00000000 fffff8a0`01393f10 00000000`00000001 00000000`fffdb000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2fffff880`0e75d400 fffff880`06cd8637 : fffffa80`09ede650 00000000`00000001 fffff8a0`0c1f57a0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11bfffff880`0e75d4b0 fffff880`06cbeecc : 00000000`00000000 fffff800`00000000 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0e75d580 fffff880`08b20ccc : fffff8a0`0478d750 fffff8a0`0064b000 fffff8a0`0064b000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0e75d5b0 fffff880`08b213ac : fffff8a0`03b9a460 fffff8a0`03b9a460 00000000`00000001 fffff8a0`0064b000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0e75d6a0 fffff880`08b20651 : fffff8a0`0064b000 fffff8a0`0064b000 fffff8a0`0ee2cac0 5a5a5a5a`5a5a5a5a : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0e75d6d0 fffff880`08b208e1 : 00000000`00000000 fffff8a0`0064b000 00000000`00000001 fffff8a0`042ff9e0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0e75d720 fffff880`08b24739 : 00000000`00000000 fffff880`0e75db60 00000000`5518b000 fffff880`08aeb3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0e75d770 fffff880`08b27285 : fffff8a0`0064b000 fffff880`0e75d850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0e75d800 fffff960`001fb816 : 00000000`0011fd20 fffffa80`04342060 00000000`00000020 00000000`748d61b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0e75dab0 fffff800`032d8853 : fffffa80`04342060 fffff880`0e75db60 00000000`00000000 00000000`00000020 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0e75dae0 00000000`748f146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0011e1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748f146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2fffff880`06cf262e 488b0e          mov     rcx,qword ptr [rsi]SYMBOL_STACK_INDEX:  5SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_process_heap::free+a2FAILURE_ID_HASH:  {be43f1a4-3662-07ec-1c74-3b363fd9d97d}Followup: MachineOwner 
BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff800032e4a40 to fffff800032735c0STACK_TEXT:  fffff880`0c3a8058 fffff800`032e4a40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0c3a8060 fffff800`032a6f79 : 00000000`00000000 00000000`3dcc9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0c3a8220 fffff800`0358cbd1 : fffffa80`04d4e8c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9fffff880`0c3a8340 fffff880`06a20c28 : 00000000`00000000 fffffa80`04c9dcd0 00000000`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b1fffff880`0c3a8400 fffff880`06a1b637 : fffffa80`04c9dcd0 00000000`00000001 fffff8a0`04cbca40 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xb0fffff880`0c3a84b0 fffff880`06a01ecc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0c3a8580 fffff880`06afdccc : fffff8a0`0f1346d0 fffff8a0`052b1000 fffff8a0`052b1000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0c3a85b0 fffff880`06afe3ac : fffff8a0`0d399b40 fffff8a0`0d399b40 00000000`00000001 fffff8a0`052b1000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0c3a86a0 fffff880`06afd651 : fffff8a0`052b1000 fffff8a0`052b1000 fffff8a0`042bbb20 00000000`00000002 : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0c3a86d0 fffff880`06afd8e1 : fffffa80`0339ccf0 fffff8a0`052b1000 00000000`00000001 fffff8a0`0d1f9560 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0c3a8720 fffff880`06b01739 : 00000000`00000000 fffff880`0c3a8b60 00000000`00000000 fffff880`06ac83af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0c3a8770 fffff880`06b04285 : fffff8a0`052b1000 fffff880`0c3a8850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0c3a8800 fffff960`0024b816 : 00000000`00000000 fffffa80`06b84060 00000000`00000020 00000000`755261b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0c3a8ab0 fffff800`03272853 : fffffa80`06b84060 00000000`0c6bdd40 00000000`00000000 fffffa80`044bb730 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0c3a8ae0 00000000`7554146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0b2be328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7554146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0fffff880`06a20c28 eb7e            jmp     dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x130 (fffff880`06a20ca8)SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_global::closelocalallocation+b0FAILURE_ID_HASH:  {8ed2b5d5-1622-e0b9-6acb-b343a0817f54}Followup: MachineOwner 
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck AB, {1, 210, 0, 2}Probably caused by : memory_corruption ( nt!MiCheckSessionPoolAllocations+13f )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SESSION_HAS_VALID_POOL_ON_EXIT (ab)Caused by a session driver not freeing its pool allocations prior to asession unload.  This indicates a bug in win32k.sys, atmfd.dll,rdpdd.dll or a video driver.Arguments:Arg1: 0000000000000001, session IDArg2: 0000000000000210, number of paged pool bytes that are leakingArg3: 0000000000000000, number of nonpaged pool bytes that are leakingArg4: 0000000000000002, total number of paged and nonpaged allocations that are leaking.	nonpaged allocations are in the upper half of this word,	paged allocations are in the lower half of this word.Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xABPROCESS_NAME:  csrss.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000347a34f to fffff800030d7c40STACK_TEXT:  fffff880`08464988 fffff800`0347a34f : 00000000`000000ab 00000000`00000001 00000000`00000210 00000000`00000000 : nt!KeBugCheckExfffff880`08464990 fffff800`033178c7 : fffff880`05ff2b40 fffff880`05ff2000 fffff880`05ff2000 fffffa80`085fe060 : nt!MiCheckSessionPoolAllocations+0x13ffffff880`084649d0 fffff800`03415ab5 : fffff880`08464a68 fffffa80`085fe060 ffffffff`ffffffc9 fffff880`05ff2000 : nt!MiDereferenceSessionFinal+0x137fffff880`08464a70 fffff800`030a9b10 : fffff800`03260900 00000000`00000001 00000000`00000000 fffffa80`083c29f0 : nt! ?? ::NNGAKEGL::`string'+0x25025fffff880`08464aa0 fffff800`033adb1a : fffff8a0`01fbc630 00000000`00000000 00000000`00000000 fffffa80`085fe060 : nt!MmCleanProcessAddressSpace+0x610fffff880`08464af0 fffff800`033adeed : fffff880`00000000 fffff800`03372f01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x56afffff880`08464bf0 fffff800`030c95e6 : fffff880`009e9180 00000000`00000080 fffffa80`085fe060 fffff880`0144b384 : nt!PspTerminateThreadByPointer+0x4dfffff880`08464c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiCheckSessionPoolAllocations+13ffffff800`0347a34f cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiCheckSessionPoolAllocations+13fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3IMAGE_VERSION:  6.1.7601.17640IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fBUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xab_nt!michecksessionpoolallocations+13fFAILURE_ID_HASH:  {b8931bc3-cc7a-1f8b-2c00-6940a8b93fa1}Followup: MachineOwner 

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

So i updated intel drivers. Went perfectly fine.

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

the Nvidia gpu however is not any more on the device manager.intsead it now says where the NVIDIA card was "Standart-VGA-Grafikkarte". it can not reanebled only disabled.just install NVIDIA driver from their site?

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

the Nvidia gpu however is not any more on the device manager.intsead it now says where the NVIDIA card was "Standart-VGA-Grafikkarte". it can not reanebled only disabled.just install NVIDIA driver from their site?

Yes you have to reinstall the nvidia driver from the website. It should re-enable by itself after the driver gets installed.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Yes you have to reinstall the nvidia driver from the website. It should re-enable by itself after the driver gets installed.

Did that. Fine so far. I will inform you if I keep getting an BSODs. Thx a lot

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, you either have an GPU driver issue or an memory issues. Updating GPU drivers on dual graphics/Nvidia Optimus systems is kinda a pain.

 

So here we go:

 

First check that there is an option in the BIOS to disable the Nvidia (dedicated) GPU. If there is, do it, if not continue with the steps below:

Start by disabling the Nvidia GPU in device manager and then using DDU (Display Driver Uninstaller) to remove the NVIDIA drivers. Link to DDU: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Next restart, and check that the Nvidia card is still disabled. We'll now try to update the Intel iGPU driver.

Go download this driver from Intel's website: https://downloadcenter.intel.com/download/24971/Intel-HD-Graphics-Driver-for-Windows-7-8-64-bit

Start by trying to download and run the setup.EXE

Will it install this way? If not, you'll have to download the .ZIP and then manually update the driver via device manager by pointing it to the unzipped folder.

Next, restart and re-enable the Nvidia GPU in device manager and re-install the latest GPU driver from the Nvidia website.

Let me know once you have that done. Well do a memory test with instructions I give you.

Let'S do the memory test?

BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000334aa40 to fffff800032d95c0STACK_TEXT:  fffff880`0e75cf68 fffff800`0334aa40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0e75cf70 fffff800`032c6a3f : fffffa80`00000000 00000000`486a9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0e75d130 fffff800`032d8853 : ffffffff`ffffffff fffff8a0`13e48b88 fffff8a0`13e48bb0 00000140`00008000 : nt!NtFreeVirtualMemory+0x61ffffff880`0e75d230 fffff800`032d4e10 : fffff880`06cf262e fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 : nt!KiSystemServiceCopyEnd+0x13fffff880`0e75d3c8 fffff880`06cf262e : fffff8a0`0c1f57a0 fffffa80`076a35b0 fffffa80`0471c4d0 fffff8a0`13e48b80 : nt!KiServiceLinkagefffff880`0e75d3d0 fffff880`06cddc93 : 00000000`00000000 fffff8a0`01393f10 00000000`00000001 00000000`fffdb000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2fffff880`0e75d400 fffff880`06cd8637 : fffffa80`09ede650 00000000`00000001 fffff8a0`0c1f57a0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11bfffff880`0e75d4b0 fffff880`06cbeecc : 00000000`00000000 fffff800`00000000 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0e75d580 fffff880`08b20ccc : fffff8a0`0478d750 fffff8a0`0064b000 fffff8a0`0064b000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0e75d5b0 fffff880`08b213ac : fffff8a0`03b9a460 fffff8a0`03b9a460 00000000`00000001 fffff8a0`0064b000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0e75d6a0 fffff880`08b20651 : fffff8a0`0064b000 fffff8a0`0064b000 fffff8a0`0ee2cac0 5a5a5a5a`5a5a5a5a : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0e75d6d0 fffff880`08b208e1 : 00000000`00000000 fffff8a0`0064b000 00000000`00000001 fffff8a0`042ff9e0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0e75d720 fffff880`08b24739 : 00000000`00000000 fffff880`0e75db60 00000000`5518b000 fffff880`08aeb3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0e75d770 fffff880`08b27285 : fffff8a0`0064b000 fffff880`0e75d850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0e75d800 fffff960`001fb816 : 00000000`0011fd20 fffffa80`04342060 00000000`00000020 00000000`748d61b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0e75dab0 fffff800`032d8853 : fffffa80`04342060 fffff880`0e75db60 00000000`00000000 00000000`00000020 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0e75dae0 00000000`748f146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0011e1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748f146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2fffff880`06cf262e 488b0e          mov     rcx,qword ptr [rsi]SYMBOL_STACK_INDEX:  5SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_process_heap::free+a2FAILURE_ID_HASH:  {be43f1a4-3662-07ec-1c74-3b363fd9d97d}Followup: MachineOwner 
BUGCHECK_STR:  0x1a_41790CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff800032e4a40 to fffff800032735c0STACK_TEXT:  fffff880`0c3a8058 fffff800`032e4a40 : 00000000`0000001a 00000000`00041790 fffffa80`00482dc0 00000000`0000ffff : nt!KeBugCheckExfffff880`0c3a8060 fffff800`032a6f79 : 00000000`00000000 00000000`3dcc9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4fffff880`0c3a8220 fffff800`0358cbd1 : fffffa80`04d4e8c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9fffff880`0c3a8340 fffff880`06a20c28 : 00000000`00000000 fffffa80`04c9dcd0 00000000`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b1fffff880`0c3a8400 fffff880`06a1b637 : fffffa80`04c9dcd0 00000000`00000001 fffff8a0`04cbca40 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xb0fffff880`0c3a84b0 fffff880`06a01ecc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19bfffff880`0c3a8580 fffff880`06afdccc : fffff8a0`0f1346d0 fffff8a0`052b1000 fffff8a0`052b1000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44fffff880`0c3a85b0 fffff880`06afe3ac : fffff8a0`0d399b40 fffff8a0`0d399b40 00000000`00000001 fffff8a0`052b1000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248fffff880`0c3a86a0 fffff880`06afd651 : fffff8a0`052b1000 fffff8a0`052b1000 fffff8a0`042bbb20 00000000`00000002 : dxgkrnl!DXGDEVICE::DestroyResource+0x84fffff880`0c3a86d0 fffff880`06afd8e1 : fffffa80`0339ccf0 fffff8a0`052b1000 00000000`00000001 fffff8a0`0d1f9560 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95fffff880`0c3a8720 fffff880`06b01739 : 00000000`00000000 fffff880`0c3a8b60 00000000`00000000 fffff880`06ac83af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9fffff880`0c3a8770 fffff880`06b04285 : fffff8a0`052b1000 fffff880`0c3a8850 00000000`00000000 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99fffff880`0c3a8800 fffff960`0024b816 : 00000000`00000000 fffffa80`06b84060 00000000`00000020 00000000`755261b8 : dxgkrnl!DxgkDestroyAllocation+0xa9dfffff880`0c3a8ab0 fffff800`03272853 : fffffa80`06b84060 00000000`0c6bdd40 00000000`00000000 fffffa80`044bb730 : win32k!NtGdiDdDDIDestroyAllocation+0x12fffff880`0c3a8ae0 00000000`7554146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0b2be328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7554146aSTACK_COMMAND:  kbFOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0fffff880`06a20c28 eb7e            jmp     dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x130 (fffff880`06a20ca8)SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13IMAGE_VERSION:  6.1.7601.18126FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_dxgmms1!vidmm_global::closelocalallocation+b0FAILURE_ID_HASH:  {8ed2b5d5-1622-e0b9-6acb-b343a0817f54}Followup: MachineOwner 
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck AB, {1, 210, 0, 2}Probably caused by : memory_corruption ( nt!MiCheckSessionPoolAllocations+13f )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SESSION_HAS_VALID_POOL_ON_EXIT (ab)Caused by a session driver not freeing its pool allocations prior to asession unload.  This indicates a bug in win32k.sys, atmfd.dll,rdpdd.dll or a video driver.Arguments:Arg1: 0000000000000001, session IDArg2: 0000000000000210, number of paged pool bytes that are leakingArg3: 0000000000000000, number of nonpaged pool bytes that are leakingArg4: 0000000000000002, total number of paged and nonpaged allocations that are leaking.	nonpaged allocations are in the upper half of this word,	paged allocations are in the lower half of this word.Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xABPROCESS_NAME:  csrss.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8000347a34f to fffff800030d7c40STACK_TEXT:  fffff880`08464988 fffff800`0347a34f : 00000000`000000ab 00000000`00000001 00000000`00000210 00000000`00000000 : nt!KeBugCheckExfffff880`08464990 fffff800`033178c7 : fffff880`05ff2b40 fffff880`05ff2000 fffff880`05ff2000 fffffa80`085fe060 : nt!MiCheckSessionPoolAllocations+0x13ffffff880`084649d0 fffff800`03415ab5 : fffff880`08464a68 fffffa80`085fe060 ffffffff`ffffffc9 fffff880`05ff2000 : nt!MiDereferenceSessionFinal+0x137fffff880`08464a70 fffff800`030a9b10 : fffff800`03260900 00000000`00000001 00000000`00000000 fffffa80`083c29f0 : nt! ?? ::NNGAKEGL::`string'+0x25025fffff880`08464aa0 fffff800`033adb1a : fffff8a0`01fbc630 00000000`00000000 00000000`00000000 fffffa80`085fe060 : nt!MmCleanProcessAddressSpace+0x610fffff880`08464af0 fffff800`033adeed : fffff880`00000000 fffff800`03372f01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x56afffff880`08464bf0 fffff800`030c95e6 : fffff880`009e9180 00000000`00000080 fffffa80`085fe060 fffff880`0144b384 : nt!PspTerminateThreadByPointer+0x4dfffff880`08464c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiCheckSessionPoolAllocations+13ffffff800`0347a34f cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiCheckSessionPoolAllocations+13fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3IMAGE_VERSION:  6.1.7601.17640IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fBUCKET_ID:  X64_0xAB_nt!MiCheckSessionPoolAllocations+13fANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xab_nt!michecksessionpoolallocations+13fFAILURE_ID_HASH:  {b8931bc3-cc7a-1f8b-2c00-6940a8b93fa1}Followup: MachineOwner 

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Let'S do the memory test?

Ok, follow the instructions here:http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for at least 3 hours.

 

If you've gotten any new BSODs, please post the dump files so I can take a look at them.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, follow the instructions here:http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for at least 3 hours.

 

If you've gotten any new BSODs, please post the dump files so I can take a look at them.

I've got more BSODs, .zip file is upsoon; will run memtest tomorrow. What does it do? you say run it 3 hours? Does it crash in between if my RAM is not OK?

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, follow the instructions here:http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for at least 3 hours.

 

If you've gotten any new BSODs, please post the dump files so I can take a look at them.

https://drive.google.com/file/d/0B_EBxJIuS4fmS1BOVW0taUl0VkE/view?usp=sharing

I hope it is ot a problem that some of it is in german :o

Laptop keyboard ==> lots of typos sry

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, follow the instructions here:http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for at least 3 hours.

 

If you've gotten any new BSODs, please post the dump files so I can take a look at them.

I neither have a USB stick nor a burnable CD (I think my laptop doesn't even have a burner). I am currently on holiday. any ideas. Can I use an android phone as a USB stick and boot from it?(I have seen my friend do it with his Xperia Z at school booting Linux)

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

I neither have a USB stick nor a burnable CD (I think my laptop doesn't even have a burner). I am currently on holiday. any ideas. Can I use an android phone as a USB stick and boot from it?(I have seen my friend do it with his Xperia Z at school booting Linux)

If your phone is rooted, I believe you can use: https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en

Run Memtest86+ for 3 to 6 hours.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

After you run Memtest86+ and no errors are found, the I'd suggest repair instaling Windows: http://www.sevenforums.com/tutorials/3413-repair-install.html

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

If your phone is rooted, I believe you can use: https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en

Run Memtest86+ for 3 to 6 hours.

It is not rooted and I can't since it is my fathers buisiness-phone. Any other ideas?

http://linustechtips.com/main/topic/334934-unofficial-ltt-beginners-guide/ (by Minibois) and a few things that will make our community interaction more pleasent:
1. FOLLOW your own topics                                                                                2.Try to QUOTE people so we can read through things easier
3.Use
PCPARTPICKER.COM - easy and most importantly approved here        4.Mark your topics SOLVED if they are                                
Don't change a running system

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×