On December 27, 2009 you had 5 STOP 0x124 BSOD's (usually hardware or compatibility issues)
Then you were BSOD free until yesterday (January 9, 2010) when you had a STOP 0xD1- a period of 13 days.
Info on the STOP 0x124: BSOD Index
Info on the STOP 0xD1: BSOD Index
What did you do to the system after the December BSOD's? This is probably more important than the analysis of the dump file(s).
The last dump file points to the Windows kernel, which isn't usually a factor (if it was, you'd have a lot more problems than just an occasional BSOD). So, let's see what was done to the system and if we can't find anything, then we'll try running Driver Verifier.
Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:
How To Find Updated 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.
Here's the older drivers:
Code:
ctac32k.sys Wed Jul 02 04:38:22 2008 - Creative Audio driver
dadder.sys Thu Aug 02 05:33:03 2007 - DeathAdder Mouse driver
Summary of the BSOD's:
Code:
BugCheck 124, {0, fffffa80073ac028, be000000, 300136}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 124, {0, fffffa8009269028, fa000000, 400405}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 124, {0, fffffa800878f028, b2000000, 10005}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 124, {0, fffffa80086bf028, be000000, 800400}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 124, {0, fffffa800928c028, fa000000, 400405}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {38, 2, 1, fffff88006a99de9}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )