BSOD, Seems to be when i'm playing WoW/Listening to music...

dakers89 · Jan 6, 2012

I've been having BSOD's on and off for the past 6 months or so.
I know a fair bit about computers so I took the liberty of trying to fix it myself.

The computer is a little over a year old, and has only had the RAM upgraded since i purchased it.

Recently I've been getting a LOT of bluescreens, but annoyingly so, the errors have not been consistent. The computer would crash and I would research into it, it would crash again and a different error would appear!

Using the guide on BSOD posting i've compressed the crash folder down

If someone could take a look at it and suggest why the errors are occurring it would be greatly appreciated.

- Windows 7 Professional x64
- Full retail version
- Has been re-installed within the past 2 months

usasma · Jan 6, 2012

SP1 is not installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates

MSINFO32 reports problems with this device:

Not Available ROOT\SYSTEM\0002 The drivers for this device are not installed.

Please zip up and upload the perfmon report. If unable to do this, please post back and we'll see what else we can do. This device will most likely be fixed by the updates, but otherwise I'll need the report to help identify it.

11 memory dumps (14 Nov 2011 to 05 Jan 2012)
9 different BSOD error codes
4 different causes blamed
This is either a:
- hardware problem
- compatibility issue
- low-level driver problem (to include missing Windows Updates and the 2005 version of ASACPI.sys)
- malware

ASACPI.sys:

You have the 2005 version of ASACPI.sys installed on your system. This is a known cause of BSOD's with Win7.

If your motherboard supports Windows 7, go to ASUSTeK Computer Inc. -Support- Drivers and Download and download the latest version of the Asus ATK0110 ACPI Utility (in the Utilities or ATK section).

If your motherboard doesn't support Windows 7, you'll have to choose which of the following to do:
1 - Remove the 2005 version of ASACPI.sys (some people report this as working - but I haven't verified it).
2 - Install a Win7 version of the driver manually - inserting it into C:\Windows\System32\drivers.
-- 64 bit here: http://www.carrona.org/64bitAsacpi.zip
-- 32 bit here: http://www.carrona.org/32bitAsAcpi.zip
If you do, be sure to scan the download with your antivirus BEFORE opening it.
3 - Download the Vista version of the Asus ATK0110 ACPI Utility for your motherboard and attempt to install it using Compatibility Mode (I don't have experience with this either).
4 - Download the Win7 version of the Asus ATK0110 ACPI Utility driver for another motherboard (I have the P6T Deluxe with a Core i7) and attempt to install that (I don't have experience with this either).
64 bit: ASUSTeK Computer Inc. -Support- The URL you are looking for does not exist.
32 bit: ASUSTeK Computer Inc. -Support- The URL you are looking for does not exist.

If your motherboard doesn't support Windows 7, there's no guarantee that any of this will work. But it's worth a try since the alternative is purchasing a new motherboard.

Your Wacom mouse driver dates from 2007, please update your Wacom software ASAP

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-22510-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jan  4 16:36:17.395 2012 (UTC - 5:00)
System Uptime: 1 days 5:18:19.330
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`032ce93d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-18813-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Jan  3 08:48:15.168 2012 (UTC - 5:00)
System Uptime: 0 days 1:00:11.849
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+5fe1 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CurseClient.ex
FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+5fe1
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff683`ff8004b0 58400001`6695d8c6 fffff8a0`0a647ea9
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121811-24866-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Dec 17 19:29:44.592 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:58.153
Probably caused by : ntkrnlmp.exe ( nt!RtlSidHashLookup+31 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlSidHashLookup+31
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cc4ec1 fffff880`0a55a950 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121811-34226-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Dec 17 19:13:48.245 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:48.180
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : hardware ( nt!KeWaitForSingleObject+35c )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cd5d5c 00000000`00000001 00000001`54ebefd7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121611-15225-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 16 12:11:59.534 2011 (UTC - 5:00)
System Uptime: 0 days 3:35:49.470
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+367fc )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+367fc
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00009368 0000936b`000126d8
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121311-18049-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Dec 13 13:53:37.468 2011 (UTC - 5:00)
System Uptime: 0 days 0:26:30.029
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`05778cee fffff880`03cfe6a8 fffff880`03cfdf10
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112611-16021-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Nov 26 09:57:58.339 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:36.274
BugCheck D1, {ffffffffffffffff, 2, 8, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  LowerP.EXE
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Bugcheck code 000000D1
Arguments ffffffff`ffffffff 00000000`00000002 00000000`00000008 ffffffff`ffffffff
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112611-16707-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Nov 26 09:49:33.741 2011 (UTC - 5:00)
System Uptime: 0 days 20:48:25.677
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72
Bugcheck code 0000000A
Arguments 00000000`01000000 00000000`00000002 00000000`00000000 fffff800`02ae1c22
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112411-14024-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Nov 24 12:29:36.943 2011 (UTC - 5:00)
System Uptime: 1 days 23:34:34.878
Probably caused by : hardware ( nt!KiSetTimerEx+1ec )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02a7dd5c 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112111-16645-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Nov 21 14:30:11.350 2011 (UTC - 5:00)
System Uptime: 0 days 3:46:36.911
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fc8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fc8
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`053a0a5c fffff880`05c9f6d8 fffff880`05c9ef40
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112111-23790-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Nov 21 10:41:35.073 2011 (UTC - 5:00)
System Uptime: 1 days 1:58:26.008
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
BUGCHECK_STR:  0x10e_1f
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
Bugcheck code 0000010E
Arguments 00000000`0000001f fffff8a0`149a3680 00000000`00000000 00000000`0152a694
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111611-16177-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov 16 08:36:57.669 2011 (UTC - 5:00)
System Uptime: 0 days 0:16:01.604
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02a8293d
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111511-30388-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Nov 15 04:28:23.445 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:44.380
Probably caused by : hardware ( nt!KiSetTimerEx+1ec )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02a8dd5c 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111411-18283-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Nov 13 20:38:29.553 2011 (UTC - 5:00)
System Uptime: 2 days 17:28:32.115
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

dakers89 · Jan 6, 2012

Hello usasma

Thank you for looking in to this for me.

I'm in the process of downloading the SP1 .iso from Microsoft now but it's 1.9gb (taking it's time!)

However looking at the next part i'm having no joy finding Asus ATK0110 ACPI Utility under my motherboard downloads section.

I have the ASUS M4N68T and there doesn't appear to be anything of the sort on the page

Also the two downloads for the x32 and x64 you posted aren't working properly.

Could you shine any light on this situation?

usasma · Jan 6, 2012

Sorry about the links, it's an old "canned" speech that I use and I haven't updated the links since Asus changed their web pages around (about 6 months ago).

Go to the Downloads section for your mobo at the Asus support website ( ASUSTeK Computer Inc. - Motherboards- ASUS M4N68T-M LE )
Enter your OS (Win7 64 bit) and then expand the Utilities section.
The second (2nd) item is the ASUS AI Suite V1.06.16 for 32/64bit Windows XP & 32/64bit Vista & 32/64bit Windows 7. The ASACPI.sys driver is contained in this and will be installed when you install the program.

dakers89 · Jan 6, 2012

Thanks for directing me to the AI suite, I've installed that so hopefully that faulty driver is now functioning.
I'm installing SP1 as we speak so hopefully this should resolve my problem

I'm looking into the unknown usb device. I only have my mouse, keyboard and Headset power plugged in at the moment but i'll get to the bottom of it

Will report back to you wether it's been successful or not and bump the thread

You've been most helpful up to now
Many thanks!

dakers89 · Jan 10, 2012

New error

Hi again

Well all was fine til a couple of days ago
It started just black screening, no dmp files so i thought it could be gfx related.
so i've installed a spare GPU (same model) and updated to the newest driver for it via ati downloads.
I've updated drivers and updated to SP1 but i've clearly missed something
today whilst on a game (chrome in background) I got the error Reference_by_pointer and it's created a dmp file luckily so if you could take a look the attached files that'd be great

Edit: I've uninstalled the said Wacom driver completely as it isn't needed anymore

Editedit: The computer has just blue screened again without error, whilst trying to run the WINDOWS_NT6 software. it's hanging on a black screen now without a restart

dakers89 · Jan 10, 2012

attached file with the latest .dmp file

managed to get windows_nt6 to finish it's process

usasma · Jan 10, 2012

Daemon Tools rears it's ugly head!!!
(in 2 of the last 5 memory dumps)
Uninstall it, then use this free tool to ensure that the sptd.sys driver is also removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Your Death Adder mouse driver dates from 2007, this is also likely to cause BSOD's. Please uninstall it and then install the latest version from the Razer website

Wacommousefilter.sys (from 2007) is still installed on the system. Please uninstall it.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011012-21918-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 08:55:11.486 2012 (UTC - 5:00)
System Uptime: 0 days 0:32:54.156
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011012-32073-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 08:13:08.704 2012 (UTC - 5:00)
System Uptime: 1 days 0:04:16.374
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49d71 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+49d71
Bugcheck code 00000018
Arguments 00000000`00000000 fffffa80`09f9f7f0 00000000`00000002 fffffa80`09e0700f
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-67111-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan  6 11:30:31.383 2012 (UTC - 5:00)
System Uptime: 0 days 1:32:52.350
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1300 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1300
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`04081300 fffff980`1cb44e10 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-23649-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan  6 09:56:05.086 2012 (UTC - 5:00)
System Uptime: 0 days 0:02:32.678
Probably caused by : hardware ( nt!KeWaitForSingleObject+35c )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032dbd5c 00000000`00000001 00000000`1aec321d
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-26286-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan  6 09:51:29.704 2012 (UTC - 5:00)
System Uptime: 0 days 1:27:08.296
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1300 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1300
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`079b4300 fffff980`3a06ee10 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-22666-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan  6 08:22:34.347 2012 (UTC - 5:00)
System Uptime: 0 days 0:14:54.939
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dxdiag.exe
FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffffa80`0a067e01 fffff880`063637f0 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

dakers89 · Jan 11, 2012

Hi usasma

I had no joy removing the Wacom drivers so figured a fresh install would be best.
(I've a seperate data partition but all my drivers and windows installation are on C

Upon a fresh install, I installed SP1 immediately along with the ASUS drivers and latest GPU driver.
I've only installed the driver for my Razer Naga which is the most up to date (not even plugged the dreaded deathadder in yet) Also stayed away from the old wacom tablet in fear of getting a driver i couldn't remove!!

At least your post helped me be proactive about this install as i've gone so long without having the service pack

Thankyou for your help it's greatly appreciated.
At least now if the computer does crash again, drivers can be pretty much crossed off the list and i can focus on hardware

Kind regards!

usasma · Jan 11, 2012

Thanks for letting us know!
Good Luck!

dakers89 · Jan 11, 2012

Thought that'd be the best way to reply

I Got the blue screen error PFN_LIST_CORRUPT whilst playing warcraft

I reinstalled windows 7, sp1, new gpu drivers etc. even updated Directx

the 2 dump files attached are from the fresh install

The second blue screen was DRIVER_IRQL.....

Edit: I'm currently typing this from my laptop, i decided to shut down my pc to spare myself from the impending crashes awaiting instruction!
It's installing updates automatically now... 4 of 58 since it's fresh install.
I'm not sure if this is a bad thing or not in terms of resolving the problem
as i've got the latest driver for Mobo, GPU, mouse, etc from their respective websites and hope that windows doesn't overwrite anyof these.

Arg heads hurting now.

EDIT: after updates, resumed to play, and got System Service Exception blue screen.
the computer is staying off until i have a solution

usasma · Jan 12, 2012

Remember the ASACPI.sys driver from before - it's back to the 2005 version (which causes BSOD's) Please update it with the AISuite software

Please uninstall the AMD OverDrive driver ( AODDriver2.sys ). You'll have to remove the AMD Vision Control Center using the AMD uninstall manager in order to get rid of it.

The networking driver from your chipset drivers ( nvm62x64.sys ) dates from 2008. Please update the chipset drivers from the nVidia website ( NVIDIA DRIVERS 15.49 WHQL )

So, so far we've discovered that the BSOD's are either hardware related, or are related to an unknown driver. The unknown driver issue is less likely than the hardware issue - but is easier to troubleshoot.

So, if you keep getting BSOD's, try running Driver Verifier according to these directions. If it doesn't reveal a particular driver, then we'll start looking into the hardware problems:

Code:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- 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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-28860-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jan 11 20:23:12.833 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:11.503
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck D1, {7fefb6b15b2, 2, 0, fffff88001b6124a}
Probably caused by : rdyboost.sys ( rdyboost!SmdMdlCopy+16 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_rdyboost!SmdMdlCopy+16
Bugcheck code 000000D1
Arguments 000007fe`fb6b15b2 00000000`00000002 00000000`00000000 fffff880`01b6124a
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-37393-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jan 11 20:15:24.140 2012 (UTC - 5:00)
System Uptime: 0 days 2:00:11.889
Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x4E_9a_nt!MiBadRefCount+4f
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`00005138 00000000`00000002 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

dakers89 · Jan 12, 2012

Hi again

so i did what was asked, installed all the relevant drivers. and ran verifier

Began playing, all fine, no blue screen whilst playing...

After about a couple hours i logged off. literally as soon as the game closed i received blue screen without a general reason.

managed to upload the dump files.

This is becoming a vicious circle, probably going to result in me launching this machine out of the window and putting my hand in my pocket for a new one!

usasma · Jan 12, 2012

The first BSOD is a Driver Verifier memory dump and it blames mcdbus.sys - a component of Magic ISO
Uninstall it please.

It still shows ASACPI.sys as being from 2005.
Download the attachment that I attached
Unzip it (Extract all files)
Open the folder
Double click on the AsAcpiIns.exe file.
That should install the ASACPI.sys driver from 2009

Go to C:\Windows\System32\drivers and check the date on it there.

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-20716-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 14:55:48.898 2012 (UTC - 5:00)
System Uptime: 0 days 0:05:49.614
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`5000e5d8 8bf00001`ce8c6882 fffff6fc`5000f5d9
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-25194-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 14:48:33.027 2012 (UTC - 5:00)
System Uptime: 0 days 5:39:15.353
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`0a356de0 00000000`0000008a 00000000`00000000
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-24133-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 08:49:13.170 2012 (UTC - 5:00)
System Uptime: 0 days 0:03:26.840
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`070dc7b0 fffffa80`070dc7b0 fffffa80`070dd7b0
BiosVersion = 1102   
BiosReleaseDate = 02/28/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-31278-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 21:08:29.617 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:38.912
*** WARNING: Unable to verify timestamp for $MftMirr
Probably caused by : ntkrnlmp.exe ( nt!RtlCompareUnicodeStrings+44 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlCompareUnicodeStrings+44
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d6d344 fffff880`07d4c6b0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

dakers89 · Jan 12, 2012

Ah it would seem that running the AI suite alone didn't install the 2009 driver

Located the .exe within the folder and checked in system32/drivers and found it to be updated to 2009 now.

No BSOD yet. fingers crossed!

BSOD, Seems to be when i'm playing WoW/Listening to music...

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer