BSOD randomly occuring after +/- 40 to 45 minutes. Error 0x00000109

[arjanseb]

Hi,

I've been trying to fix my aunts malware infected pc. I've got to the point where all the malware has been removed. Programs used: F-Secure, malwarebytes and Hitman Pro. But now i'm trying to get these BSOD's solved. Ran memtest for over 7 passes to be sure that it isn't a RAM problem.

It's an custom build PC.

Windows Home Premium 64bit
Motherboard: Asus P5KPL-AM EPU
CPU: Pentium Dual-Core E5700
RAM: 4GB DDR2 800
HDD: Hitachi HDS721010CLA332 1TB
GPU: Intel onboard graphics.

Uploaded the info from the Seven Forums Diagnostics Tool.

 

[Arc]

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

[URL="http://www.carrona.org/bsodindx.html#0x00000109"]CRITICAL_STRUCTURE_CORRUPTION (109)[/URL]
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]A driver has inadvertently or deliberately modified critical kernel code[/COLOR]
 or data. See [url=http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx]Patching Policy for x64-Based Systems[/url]
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.
3) [COLOR=Red]A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/COLOR]
Arguments:
Arg1: a3a039d8958ef658, Reserved
Arg2: b3b7465ee80d329a, Reserved
Arg3: fffff80000b96bb0, Failure type dependent information
Arg4: 0000000000000006, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[arjanseb]

Thanks for the quick reply,

After turning on Driver Verifier i've almost got an instant bluescreen. Ran the Seven Forums Diagnostics tool again and uploaded the results.

 

[Arc]

It appears that the latest dump is not DV enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

If it is DV enabled, the ID would have been VERIFIER_ENABLED_VISTA_MINIDUMP.

I would suggest you to disable DV now, and then re-enable it. Dont check any driver provided by "microsoft" or "unknown" and run verifier again. Then let it run again.

 

[arjanseb]

Did the same thing again, now without the windows/unkown drivers selected.

 

[Arc]

Verifier is still not running, as far as I can see,

Use the command in an elevated command prompt ....

• verifier /query

To make it sure that verifier is actually running or not.

 

[arjanseb]

After I rebooted with driver verifier on, it just crashes windows before I can see the logon screen. Is there anything I can do about that?

 

[Arc]

Boot into http://www.sevenforums.com/tutorials/69585-safe-mode.html . Disable DV there.

Now boot back to normal mode. Enable DV again. Make it sure that you are not checking any driver provided by "microsoft" and "unknown". Let the computer run again with DV enabled.

Perform the most crash prone actions. Let the computer to crash a couple of times. Then post it following the Blue Screen of Death (BSOD) Posting Instructions.