blue screen with bbcode 109

[ghpink]

Computer was running fine and I haven't installed any hardware or really any software lately. All the sudden when I got home, I get this blue screen of death! It keeps happening about every 15 mins or so.

Did a drive sector scan and no problem so far. Changed the location of the /temp folder just in case there was something inside there causing problems. No problem with that.

Here is what the bbcode is

BCCode: 109
BCP1: A3A039D89E69378F
BCP2: B3B7465EF0E77851
BCP3: FFFFF80000B96BB0
BCP4: 0000000000000006


=================================================
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 109
BCP1: A3A039D89E69378F
BCP2: B3B7465EF0E77851
BCP3: FFFFF80000B96BB0
BCP4: 0000000000000006
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\080813-70013-01.dmp
d:\Temp\WER-76674-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


=======================================

Any ideas? I can send the two .DMP files if needed
C:\Windows\Minidump\080813-70013-01.dmp
d:\Temp\WER-76674-0.sysdata.xml

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[ghpink]

Okay here you go

Here is the zipped up SF diagnostics info.

 

[Arc]

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

[COLOR=Red]CRITICAL_STRUCTURE_CORRUPTION (109)[/COLOR]
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
 or data. [/COLOR]See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
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: a3a039d89e86e6a1, Reserved
Arg2: b3b7465ef1052763, 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

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.

Stress test the CPU.
Hardware - Stress Test With Prime95

If both the above tests 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.