The dmp(s) point to
ntkrplmp.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).
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff8000516e145, fffff8800897bac0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+ea )
Followup: MachineOwner
---------
The following drivers are outdated and should be updated ...
Code:
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401) ... Wacom(tablet) Mouse Filter ... [url=http://www.wacom.com/downloads/drivers.php]Wacom Hardware Drivers[/url]
