Random BSOD, x5 today; various error codes

[Rutinni]

I've been getting BSOD on my desktop for the last month. Sometimes it goes a few days without crashing, sometimes (like today) I get five in a day.

Tried getting help on the microsoft forums last week (suggestion was virus scan with Malwarebytes; found one virus, but follow-up scans were clean), but nothing helped.

Not all BSODs have resulted in .dmp files, but the fourteen I do have are attached.

Getting really frustrated, as I cannot rely on the computer to stay running.

Any suggestions?

 

[Arc]

Most of the BSODs are stop 0x109, which is a mystery bugcheck from the troubleshooting perspective. Here it is reporting a memory corruption.

BugCheck 109, {a3a039d89c24e51c, b3b7465eeea1b472, fffff80003413035, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

Followup: memory_corruption
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

 

[Rutinni]

Ran 9 passes last night... no errors.

 

[Arc]

Now let us search for any buggy driver that may cause memory corruption by sending bad info to it.

Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Rutinni]

Well, it definitely stressed the system... crashed on startup (immediately after login) every time.

[edit] DMP files in next post...

Thanks!

 

[Rutinni]

The new DMPs are attached here (.zip).

 

[Arc]

All them are pointing to some Gigabyte bloatware, which is too old, too. It is some bundled bloat of the motherboard's driver CD which should not be installed.

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

_____________________________________________________

BugCheck C4, {f6, 128, fffffa80079467d0, fffff88007fe1809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
[COLOR=Red]Probably caused by : gdrv.sys[/COLOR] ( gdrv+1809 )

Followup: MachineOwner
---------

    Image name: gdrv.sys
[COLOR=Red]    Timestamp:        Fri Mar 13 08:52:29 2009[/COLOR]

 

[Rutinni]

Went through and cleaned a bunch up... did not do a clean re-install however.

Things ran well for two days, and then another BSOD. DMP file attached...

 

[Arc]

BugCheck 109, {a3a039d89d26c9dc, b3b7465eefa39932, fffff80003413030, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

Followup: memory_corruption
---------

As your post #3 ensures that the RAM is free from error, you need to give Driver Verifier another go.

 

[Rutinni]

Ran Verifier for awhile... no BSOD.

Only issue was that Chrome would terminate (Snap error) constantly, but IE ran fine. Tracked this down to a pair of Google services that I'd turned off. Turned them back on this morning, and Chrome ran again. Got another BSOD this evening.

Not sure if it was related or not, but the correlation is worrying. The DMP is attached.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1)[COLOR=Red][B] A driver has inadvertently or deliberately modified critical kernel code
 or data. [/B][/COLOR]See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
[DEL]2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.[/DEL]
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:

If your RAM is tested to be free from error for sure, then it is some driver/software related issue only. Unfortunately verifier is not stressing it. In that case, a clean reinstall will solve the issue, as it is seen many a times.

And dont use any beta version of google chrome.