The dmp(s) point to
ntkrpamp.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 run driver verifier to pinpoint 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).
Uninstall Zone Alarm ... it is known to cause BSOD issues in some Windows 7 machines, and having 2 competing anti-virus programs running at the same time is usually not recommended...
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80003051798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
The following drivers are out of date and need to be updated
Code:
fffff880`01060000 fffff880`0106be00 PxHlpa64 PxHlpa64.sys Fri May 15 17:43:06 2009 (4A0DE1EA)
fffff880`03fd6000 fffff880`03fee000 risdsne64 risdsne64.sys Wed Jul 01 00:50:14 2009 (4A4AEB06)
fffff880`0698f000 fffff880`0699a000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`03e00000 fffff880`03e02c80 SFEP SFEP.sys Fri Aug 03 01:35:53 2007 (46B2BEB9)
fffff880`04800000 fffff880`0484d000 SynTP SynTP.sys Thu Aug 27 22:00:37 2009 (4A973A45)
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
Driver Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads
