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

godling · Feb 23, 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 Win7 install, so I just need to re-install. (Haven't done that much installing, yet.)

Thanks!
-Jon

ePeen · Feb 23, 2012

Don't see any attached dumps, unless you're working on that. Also, I don't know what you mean by "wonky screen"

, but ANY errors in Memtest are a no-no.

godling · Feb 23, 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 · Feb 23, 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 · Feb 24, 2012

bump?

mgorman87 · Feb 24, 2012

Almost everyone is memory corruption. Since you already ran memtest, I would like you to enable driver verifier - http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

godling · Feb 24, 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 · Feb 24, 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 · Feb 25, 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 · Feb 25, 2012

godling said:
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.

jcgriff2 · Feb 25, 2012

Hi -

Seeing bugchecks 0x109 (kernel corruption) + 0x24 (ntfs file system) + exception code 0xc0000005 (memory access violation), I would suggest you look at your Vertex 2 SSD - 60GB boot drive as the possible culprit here.

Check OCZ support site for firmware upgrade. Some OPs have reported success.

If BSODs persist, disconnect SSD; install Windows 7 onto HDD and see if BSODs persist. If not - RMA the SSD.

Also - if you were running memtest86+ one stick at a time, alternating the slots and one stick tested bad - it is likely bad regardless if you can replicate the failure or not. Remove the bad stick; RMA the RAM if possible.

Regards. . .

jcgriff2

godling · Feb 25, 2012

If it turns out to be the RAM, the easy part would be to swap it out. No need to pull disassemble, re-cable, all the time consuming stuff that comes with a new motherboard. Also no need to re-install the OS. Seems like a smart move.

On the other hand, I really wanted an Asus mobo instead of this Gigabyte, so the question would be: do I do the easy thing and swap the RAM, or do what I *really* want to do, and swap the mobo, even though that means another 3 hours or so of work? I'll probably swap the mobo.

But first, looking for any additional insight on those dmp files.

godling · Feb 25, 2012

That might be the ticket ... I borrowed a spare drive from work, and so far the install is going smooth and no blue screens. It's early yet, and i don't want to make any assumptions until I've set everything up (all updates, install Steam, play skyrim, run applications in the background, and all the other goodies.)

But I'm hopeful.

Best case scenario, I just need to re-install Windows, as the extra software Gigabyte gave me was problematic, and I think I even installed it before all the device drivers (bad on me).

Worst case scenario, it's my justification for going out and purchasing a 120GB Crucial m4.

-Jon

jcgriff2 · Feb 25, 2012

Hi -

Glad to hear install with different HDD (or SSD..?) is going well so far.

When you reach Desktop, allow Windows Updates to come in -

www.update.microsoft.com

Check Device Manager for red/ yellow flags; update video, audio, networking, other device drivers if needed. Install apps and use the system.

Run Driver Verifier - http://www.sysnative.com/0x1/Driver_Verifier.htm

If your BSODs are software related, Driver Verifier can help by subjecting 3rd party drivers to a variety of stresses and tests to find improper behavior. Driver Verifier monitors kernel-mode drivers to detect illegal actions that might corrupt the system.

If Driver Verifier detects a violation, it will flag (disable) the offending driver and force a BSOD.

Regards. . .

jcgriff2

godling · Feb 26, 2012

Thanks, folks. The HDD didn't have a problem at all, after about 12 hours or more of steady usage ... downloading, running video and audio loops, games running in the background, and all sort of other stuff. I even ran Prime95 for a couple hours. No issues.

So, I'm going to backup the couple of installs on my SSD and do a total disk wipe (OCZ has some specific software for that) and re-install the OS. I've already updated the firmware. I'm hopeful.

And, as I said earlier ... worst-case scenario is I go out and buy myself a new 120GB SSD.

Keeping this open until I'm certain the problem is solved, though.

Thanks again for all the help,

-Jon

godling · Feb 26, 2012

So, interestingly enough ... just attaching my SSD as a data drive (so I could secure wipe it) started causing BSOD's ... at least I think that was the cause. Still got error code 109, but it was literally within minutes of my connecting the drive.

I now highly suspect the SSD has a major issue. Here's the latest .dmp files, as well as perf mon report. Hoping someone can confirm.

-Jon

jcgriff2 · Feb 27, 2012

Hi -

2 dumps were bugcheck 0x109 = kernel corruption

The 3rd - 0x24 (0x1904fb,,,) naming ntfs.sys as probable cause

The 1st parm 0x1904fb translates to exception 0xc0000005 = memory access violation; could be referring to physical or virtual memory

Event Viewer logged:

Code:

[FONT=lucida console]Event[336]:[/FONT]
[FONT=lucida console]Log Name: System[/FONT]
[FONT=lucida console]Source: [COLOR=black][B]Ntfs[/B][/COLOR][/FONT]
[FONT=lucida console]Date: 2012-02-26T08:13:24.929[/FONT]
[FONT=lucida console]Level: Error[/FONT]
[FONT=lucida console]Description: [/FONT]
[FONT=lucida console][COLOR=navy]The file system structure on the disk is corrupt and unusable.[/COLOR] [/FONT]
[FONT=lucida console]Please run the chkdsk utility on the volume \Device\[COLOR=red]HarddiskVolumeShadowCopy24[/COLOR]. [/FONT]

That is a system restore point probably located on the SSD which still had the prior install of Windows on it.

I suggest that you keep the SSD away from the system for a while and see if it BSODs with just the SATA HDD. If it does - test the RAM.

Regards. . .

jcgriff2

BSOD SUMMARY

Code:

[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-25911-01.dmp][/FONT]
[FONT=lucida console]Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506[/FONT]
[FONT=lucida console]Debug session time: Sun Feb 26 08:35:49.074 2012 (GMT-5)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:15:33.933[/FONT]
[FONT=lucida console]Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+272 )[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0x24[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonClose+272[/FONT]
[FONT=lucida console]Bugcheck code 00000024[/FONT]
[FONT=lucida console]Arguments 00000000`001904fb fffff880`0339a798 fffff880`03399ff0 fffff880`012cf0b2[/FONT]
[FONT=lucida console]BiosVersion = FB[/FONT]
[FONT=lucida console]BiosReleaseDate = 10/12/2011[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = Z68AP-D3[/FONT]
[FONT=lucida console]MaxSpeed:     3300[/FONT]
[FONT=lucida console]CurrentSpeed: 3309[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-21902-01.dmp][/FONT]
[FONT=lucida console]Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506[/FONT]
[FONT=lucida console]Debug session time: Sun Feb 26 08:19:18.112 2012 (GMT-5)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:01:58.360[/FONT]
[FONT=lucida console]*** WARNING: Unable to verify timestamp for win32k.sys[/FONT]
[FONT=lucida console]*** ERROR: Module load completed but symbols could not be loaded for win32k.sys[/FONT]
[FONT=lucida console]Probably caused by : memory_corruption[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0x109[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  CODE_CORRUPTION[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT[/FONT]
[FONT=lucida console]Bugcheck code 00000109[/FONT]
[FONT=lucida console]Arguments a3a039d8`984217f5 b3b7465e`eabee75b fffff800`03013cee 00000000`00000001[/FONT]
[FONT=lucida console]BiosVersion = FB[/FONT]
[FONT=lucida console]BiosReleaseDate = 10/12/2011[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = Z68AP-D3[/FONT]
[FONT=lucida console]MaxSpeed:     3300[/FONT]
[FONT=lucida console]CurrentSpeed: 3309[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-18876-01.dmp][/FONT]
[FONT=lucida console]Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506[/FONT]
[FONT=lucida console]Debug session time: Sun Feb 26 08:03:44.021 2012 (GMT-5)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:01:58.880[/FONT]
[FONT=lucida console]*** WARNING: Unable to verify timestamp for win32k.sys[/FONT]
[FONT=lucida console]*** ERROR: Module load completed but symbols could not be loaded for win32k.sys[/FONT]
[FONT=lucida console]Probably caused by : memory_corruption[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0x109[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  CODE_CORRUPTION[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT[/FONT]
[FONT=lucida console]Bugcheck code 00000109[/FONT]
[FONT=lucida console]Arguments a3a039d8`98420820 b3b7465e`eabed776 fffff800`02e33b0e 00000000`00000001[/FONT]
[FONT=lucida console]BiosVersion = FB[/FONT]
[FONT=lucida console]BiosReleaseDate = 10/12/2011[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = Z68AP-D3[/FONT]
[FONT=lucida console]MaxSpeed:     3300[/FONT]
[FONT=lucida console]CurrentSpeed: 3309[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
 
 
 
 
[FONT=lucida console]     [COLOR=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/COLOR]   [/FONT]
 
[FONT=lucida console]         [URL="https://mvp.support.microsoft.com/profile/Griffith"][COLOR=#000055][U]https://mvp.support.microsoft.com/profile/Griffith[/U][/COLOR][/URL]   [/FONT]
 
[FONT=lucida console]         [URL="http://sysnative.com"][COLOR=#000033][U]www.sysnative.com[/U][/COLOR][/URL][/FONT]
 
[FONT=lucida console]         [URL="http://jcgriff2.com"][COLOR=#000055][U]www.jcgriff2.com[/U][/COLOR][/URL] [/FONT]
 
 
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/FONT]

godling · Feb 27, 2012

So, my dreams were dashed. I got a little more than a day out of the machine, and thought I was in the clear. Then about 30 minutes ago I had a small series of dumps. Looks like the same thing to me, but I can't be certain.

After I post this, I'm doing some serious memtest runs.

-Jon

godling · Feb 27, 2012

Okay! I think I've got proof that it's a RAM failure ... memtest is still running (it says) but after only 1 pass on the second stick (the first stick went 4+ hours untouched) I've got a lot of "\2u and a couple of weird symbols, and they repeat to cover most of the screen.

Now I have to go run the same tests in the other DIMM slots, to ensure it's not a bad board instead of bad memory ...

godling · Mar 1, 2012

Okay, marking this thing as fixed. Swapped the mobo and RAM for new pairs, and all seems to work fine. Even the SSD isn't failing.

Thanks for all the help, folks!

-Jon

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

New member

My Computer My Computer

At a glance

Banned

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Squad

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Banned

My Computer My Computer

At a glance

Account closed

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Account closed

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Account closed

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer