Daily Blue Screens

MustangCSA · 31 Aug 2010

OK so I decided I should follow post 4 again and enable driver verifier. I follow the instructions on the website then reboot. It would BSOD immediately after the windows boot splash. I let it do this twice then I booted into safe mode and did verifier /reset. Here is the dump after doing that. Anyway of testing if maybe my motherboard or video card could be dieing? A couple of the times I rebooted the comp wouldn't POST. It would either just keep acting like it was checking the DVD drive with no beeps or one time I got 1 long beep and 3 short beeps which is apparently a GPU error. It also doesn't detect one of my SATA drives anymore, although I have not opened the case yet to check the cable on that one. Any ideas?

**cluberti** · 31 Aug 2010

According to your data, driver verifier is pointing to the Logitech camera driver as the culprit, specifically passing an invalid IRP status during an I/O operation:

Code:

2: kd> lmvm lv302a64
start             end                 module name
fffff880`02b3d000 fffff880`02b3f400   lv302a64 T (no symbols)           
    Loaded symbol image file: lv302a64.sys
    Image path: \SystemRoot\system32\DRIVERS\lv302a64.sys
    Image name: lv302a64.sys
    Timestamp:        Thu Apr 30 18:41:07 2009 (49FA2903)
    CheckSum:         0000515F
    ImageSize:        00002400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That driver predates Win7, so I'd suggest updating it (or better, uninstalling the Logitech software and running for a bit to see if anything changes).

MustangCSA · 01 Sep 2010

OK so far so good. I uninstalled the Logitech webcam driver and software, and it made it all night without a BSOD. I hope this did it, now I just need to figure out the hard drive issue. Thanks for all the help and I'll post back again if anything changes for the worst.

MustangCSA · 02 Sep 2010

Worked great all day then like ten minutes ago it crashed again. I installed a couple games and a few programs then went into the kitchen and came back it had rebooted. Attached is the dump.

**cluberti** · 02 Sep 2010

This one is actually more forceful in trying to hint at a hardware problem, unlike most other bugcheck codes (STOP 0x50, 0x3B, etc) which only infer it very indirectly:

Code:

// CRITICAL_STRUCTURE_CORRUPTION (109) - only param 4 matters:
0: kd> .bugcheck
Bugcheck code 00000109
Arguments a3a039d8`98d11785 b3b7465e`eb4f2997 fffff880`00d3f600 00000000`00000001

Parameter 4 is 0x00000001, which means a *kernel* function in memory has been modified, causing the bugcheck. Since this is an x64 Win7 system with kernel protection, you aren't going to have the ability to hotpatch the Windows kernel (which is showing as the corrupted module holding the changed function as per the dump), so either this is a virus (not likely), or the function was corrupted because the memory holding it was corrupt. For what it's worth, the module that appears patched is win32k.sys, so you might want to consider it could be VirtualBox (I can't see any other driver on the system that would have any particular interest in win32k.sys, but VBox might).

This bugcheck will actually have Win7's problem troubleshooter point you to this URL:
Microsoft Windows Error Reporting

MustangCSA · 02 Sep 2010

OK so I went to the website that you linked and downloaded the Windows Memory Diagnostic tool. I let it run for one pass with no errors, but I will let it go overnight tonight and see what happens then. It says it can't map over 4g of memory, I have 6g in here, so I'm assuming it would be best to remove 2g and then test? I haven't run WMD before, how much do the tests differ from memtest? Any other tests I should run, cpu stress test, motherboard diagnostic or something of that nature? Any other suggestions? Thanks again for all the help so far.

**cluberti** · 02 Sep 2010

Memtest would be a better test - I was just pointing out that Windows thinks your RAM might be to blame. I'd follow the memtest guide here.

MustangCSA · 02 Sep 2010

OK I started running memtest I'll let it go all night and post back when it's done. I'm hopeing for no errors seeing as I ran memtest for 24 hours right before I installed Windows 7. If it passes without any errors what else can I try?

MustangCSA · 03 Sep 2010

OK so I ran memtest for a full 24 hours without any errors. What's next?

**cluberti** · 04 Sep 2010

If the hardware's ok, next is on to scanning the OS for any vulnerabilities - preferably offline. If that scan comes up clean, at that point it's down to drivers.