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 help 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).A
Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp,
sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
DuplexSecure - Downloads
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
These drivers are out of date and should be updated, or the associated program uninstalled for troubleshooting purposes...
How to find drivers -
- 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 manufacturer links are on this page: Drivers and Downloads[/
Code:
fffff880`09504000 fffff880`0950d000 BCM42RLY BCM42RLY.sys Tue Jul 07 20:34:55 2009 (4A53E9AF)
fffff880`080a1000 fffff880`08349000 bcmwl664 bcmwl664.sys Tue Jul 07 20:45:04 2009 (4A53EC10)
fffff880`08069000 fffff880`08076000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff880`01214000 fffff880`0121fe00 PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
fffff880`0242d000 fffff880`02467000 RtsUStor RtsUStor.sys Fri May 08 04:15:18 2009 (4A03EA16)
fffff880`09493000 fffff880`09504000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`01002000 fffff880`01128000 sptd sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
