Originally Posted by KhaoticKomputing
Sorry. The holiday's have been long, and work has been crazy! Here are the files you requested.
BSOD Info.zip 1468k .zip file
And the full system spec's of the PC:
AMD Phenom II x6 1045t CPU
ASRock 880GM-LE FX mobo
2x4(8gb) MicroCenter/ADATA 1333 RAM
Inland Gold ILG Power Supply, I think its a 500w but cannot remember.
DiabloTek EVO Mid tower
No GPU, use's on board video, soon to have a 460GTX
Windows 7 Home Premium 64-Bit (OEM)
Ignore the stuff about the Virtual machine Ethernet ports. Its not an issue and has nothing to do with the BSOD. Thank's for your time.
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) A driver has inadvertently or deliberately modified critical kernel code
or data. 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) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arg1: a3a039d8989d754a, Reserved
Arg2: b3b7465eeb1a44a0, Reserved
Arg3: fffff80003055070, Failure type dependent information
Arg4: 0000000000000001, 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
Definitely memory corruption going on here.
I'd suspect a faulty driver if the memtest results were OK. We can track this down fairly easily. See below:
You may wish to print out these instructions in order to refer to recovery steps if your computer fails to restart after enabling the Driver Verifier (thus rendering this page inaccessible)
The Driver Verifier is a component of Windows starting with Windows Server 2003 (8, 7, Vista, XP, 2008/R2) which is used to promote stability and reliability. Drivers are kernel-mode components that if do not behave correctly can cause system corruption, failures and other crashes.
If a non-Microsoft driver is running around in bad territory and causing your computer to blue-screen, turning on the Driver Verifier will help to pinpoint which driver is at fault, after which it then can be updated or removed from the system.How to enable the Driver VerifierCreate a System Restore pointThis section does NOT apply to Windows XP, Windows Server 2003 or 2008/R2
1. Click Start
2. In the search box, type sysdm.cpl
and then press ENTER.
3. Verify that the system disk is selected and click the Create
4. Type a description for the restore point.
5. Click the Create
button. A status bar will appear as Vista saves your files. When the process is complete, a message box will appear indicating that the restore point was created.Configure Driver Verifier
1. Click Start
2. In the search box, type verifier
and then press ENTER.
3. Ensure that Create custom settings (for code developers)
is selected and then click Next
4. Select Select individual settings from a full list
and then click Next
5. Place a check mark next to the following boxes:
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 and Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
6. Click Next
and then choose Select driver names from a list
7. Click the Provider
column to sort drivers by their provider.
8. Place a check mark next to each item that is NOT
provided by Microsoft or Microsoft Corporation.
9. Click Finish
and restart your computer.What you should know about the Driver VerifierThe Driver Verifier works by monitoring the drivers you selected and then if a violation is detected, it will immediately cause a blue-screen
Sometimes after the Driver Verifier is enabled and you restart your computer, you may blue-screen before being able to log on to Windows. This happens when the Driver Verifier detects a violation from a driver that is set to load at boot time. This is no cause for concern - to resume normal operation, follow the below steps:
1. Restart the computer in Safe Mode by selecting it from the F8 boot menu (press F8 repeatedly after the system restarts).
2. Once in Safe Mode, do the following:If you created a restore point and are NOT running Windows XP, Windows Server 2003 or 2008/R2:
If you are running Windows XP, Windows Server 2003 or 2008/R2, or could not create a restore point beforehand:
- Click Start, type system restore in the search box, and then press ENTER.
- Restore your computer to the point you created beforehand.
How long do I leave the Driver Verifier enabled?
- Click Start, type cmd in the search box, and then press ENTER.
- At the command prompt, type verifier /reset and then press ENTER.
- Restart your computer
Keep the Driver Verifier enabled for around 24-48 hours - don't worry too much about getting the timing perfect. If your computer does not blue-screen during that time, you can disable the Driver Verifier by following the steps above.A blue-screen occurred, what should I do?
The minidumps generated by your blue-screen will now have more information in them due to Driver Verifier being enabled. They will be located at %windir%\Minidump
. Save these and attach them to your next reply for analysis.