Windows 7: BSOD, stop 109 code, various times, can't seem to nail it down.

godling · 23 Feb 2012

Hi guys ... great to be on the show today ... long-time reader, first-time poster ...

Just built a new (partially) system. Bought a new mobo / cpu / RAM. Clean install of Win7x64. Started getting BSODs almost immediately. Ran ALL windows updates. Memtest86+ (no errors on passes -- did get a wonky screen after about 6 hours on one of my sticks, but I heard that happens on occasion. Haven't tried to repeat, yet.)

Been trying to resolve this for about 36 hours now, to no effect. Lots of research on the internet and these forums but so far no luck.

I could be playing a game (Steam - Skyrim) or just browsing, or running a system check. Generally comes up Stop 109.

Brand new mobo / CPU / RAM, running Win7x64 ultimate

System specs:
Mobo: GA-z68AP-D3
Intel i2500k
8GB (2x4GB) Vengence RAM
Vertex 2 SSD - 60GB boot drive
Western Digital 750GB data drive

Attaching latest .dmp files.

thanks in advance for all the help. Would live to find out it's an easy swap out (like CPU or RAM) or even something went wonky in the Windows 7 install, so I just need to re-install. (Haven't done that much installing, yet.)

Thanks!
-Jon

ePeen · 23 Feb 2012

Don't see any attached dumps, unless you're working on that. Also, I don't know what you mean by "wonky screen" :P, but ANY errors in Memtest are a no-no.

godling · 23 Feb 2012

My mistake ... I didn't follow the steps for posting the .dmp files properly. I'll update this evening when I'm home from work.

godling · 23 Feb 2012

Okay, dump files and Perf Mon results zipped up and attached. Also attaching sfcdetails.txt file.

Thanks again for the help, folks!

-Jon

godling · 24 Feb 2012

bump?

mgorman87 · 24 Feb 2012

Almost everyone is memory corruption. Since you already ran memtest, I would like you to enable driver verifier - Driver Verifier - Enable and Disable

But first, do these things:

Code:

gdrv.sys     Thu Mar 12 23:22:29 2009 (49B9D175)

Gigabyte Easy Saver. Known BSOD maker. Please remove any Gigabyte software from your computer

Code:

nvlddmkm.sys Sat Oct 15 02:07:55 2011 (4E99233B)

Update video card - NVIDIA DRIVERS 295.73 WHQL

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 23 08:46:43.405 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:10.826
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 20:26:48.484 2012 (UTC - 5:00)
System Uptime: 0 days 0:05:09.904
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+45 )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFullDeleteLcb+45
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 20:20:39.374 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:22.794
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+114 )
PROCESS_NAME:  mscorsvw.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 20:12:19.580 2012 (UTC - 5:00)
System Uptime: 0 days 0:10:00.610
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 12:40:19.751 2012 (UTC - 5:00)
System Uptime: 0 days 5:08:00.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 07:31:24.952 2012 (UTC - 5:00)
System Uptime: 0 days 8:50:01.201
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 21:20:13.395 2012 (UTC - 5:00)
System Uptime: 0 days 2:03:43.722
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 16:34:02.085 2012 (UTC - 5:00)
System Uptime: 0 days 0:12:10.037
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 16:21:27.904 2012 (UTC - 5:00)
System Uptime: 0 days 0:05:57.856
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 14:23:38.174 2012 (UTC - 5:00)
System Uptime: 0 days 0:09:58.500
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 14:13:15.236 2012 (UTC - 5:00)
System Uptime: 0 days 0:04:02.563
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 14:08:19.007 2012 (UTC - 5:00)
System Uptime: 0 days 4:27:18.334
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+fd2c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+fd2c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 08:44:38.166 2012 (UTC - 5:00)
System Uptime: 0 days 0:03:45.118
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 21 08:40:27.106 2012 (UTC - 5:00)
System Uptime: 0 days 0:09:50.433
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

godling · 24 Feb 2012

Thanks, mgorman87. I updated the video driver last night, when I realized it was out of date. Still BSOD this morning. Just uninstalled all the Gigabyte software, and now using DriverVerifier as instructed.

Testing it all out to see how it goes.

-J

godling · 24 Feb 2012

Okay, setup everything as requested, got another BSOD, reports attached.

Ran driver verifier, never had a response from it ... not sure what I was supposed to see?

Thanks again for all your help, guys!

-J

godling · 25 Feb 2012

I just ran memtest for another 3 hours, 5 passes, with both sticks in, and not a bit of error anywhere. Wondering if I should leave it running over night tonight.

Next question: could it be an incompatibility between the memory modules and the motherboard? The Vengeance RAM is made for the Sandy Bridge chipset, but it's not on the motherboard's qualified memory list.

-J

ePeen · 25 Feb 2012

Quote: Originally Posted by godling

I just ran memtest for another 3 hours, 5 passes, with both sticks in, and not a bit of error anywhere. Wondering if I should leave it running over night tonight.

Next question: could it be an incompatibility between the memory modules and the motherboard? The Vengeance RAM is made for the Sandy Bridge chipset, but it's not on the motherboard's qualified memory list.

-J

Funny you mention that, I have Vengeance memory as well. Wondering the same thing myself.

Windows 7: BSOD, stop 109 code, various times, can't seem to nail it down.

BSOD, stop 109 code, various times, can't seem to nail it down. problems?