The dmp(s) point to
ntkrnlmp.exe or
ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable driver verifier to isolate the faulting driver.
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything
EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers
NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and
wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then
let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1, 2, 0, fffff80002aa02b3}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002a7c80c, fffff8800453ed80, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
Followup: MachineOwner
---------
These drivers are out of date and should be updated...
Code:
e1y60x64.sys Mon Aug 18 17:45:05 2008 (48A9ED61) ... Intel(R) 82567LM Gigabit Network Connection ... [url]http://downloadcenter.intel.com/Default.aspx[/url]
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) ... GEARAspiWDM.sys ... [url=http://www.gearsoftware.com/]GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering[/url]
