The dmp(s) point to
ntkrnlmp.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. You need to enable driver verifier to help pinpoint the faulty 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). Upload the new .dmp files as they occur.
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 1A, {41287, 7fef0b30000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
Followup: MachineOwner
--------- The following drivers are out dated and need to be updated or the associated program uninstalled..
How To Find Drivers:
Quote:
- 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 Code:
fffff880`067b9000 fffff880`067d1000 adfs adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)CF0)
fffff880`047b5000 fffff880`047c1f00 Alpham164 Alpham164.sys Mon Jul 23 03:57:03 2007 (46A45F4F)
fffff880`047c2000 fffff880`047c7500 Alpham264 Alpham264.sys Tue Mar 20 05:51:03 2007 (45FFAE87)
fffff880`043e1000 fffff880`043e9000 wacommousefilter wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)