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

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

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.

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

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

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

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

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:

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

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:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-25911-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 26 08:35:49.074 2012 (GMT-5)
System Uptime: 0 days 0:15:33.933
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+272 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonClose+272
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0339a798 fffff880`03399ff0 fffff880`012cf0b2
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-21902-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 26 08:19:18.112 2012 (GMT-5)
System Uptime: 0 days 0:01:58.360
*** 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
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`984217f5 b3b7465e`eabee75b fffff800`03013cee 00000000`00000001
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022612-18876-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 26 08:03:44.021 2012 (GMT-5)
System Uptime: 0 days 0:01:58.880
*** 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
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`98420820 b3b7465e`eabed776 fffff800`02e33b0e 00000000`00000001
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
 
 
 
     J. C. Griffith, Microsoft MVP (jcgriff2)   
 
         https://mvp.support.microsoft.com/profile/Griffith   
 
         www.sysnative.com
 
         www.jcgriff2.com 
 
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

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

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 ...

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