BSOD

Koboldstatus · 22 Nov 2010

Hi!

I have some problems with some crashes. I have windows 7 64-bit. Full retail version. My system is about 1 year old and has reinstalled window for about a week ago. I thought the crashes would disapear but no.

Thanks!

usasma · 23 Nov 2010

13 memory dumps, 8 different BSOD error codes, 8 different causes blamed.
This is the beginning of a pattern that says there is a hardware/compatibility problem.

Please uninstall Daemon Tools, it is known to cause BSOD's on some Win7 systems. Also, once it's uninstalled, please use this free program to remove the offending sptd.sys file: DuplexSecure - FAQ - Remove 64 bit sptd.sys

One of the memory dumps points at your wired networking driver. Please visit the manufacturer's website and download the latest copy of the Win7 compatible drivers for your device. Uninstall the current drivers, and install the freshly downloaded one's.

Another points to your Avast antivirus, please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the antivirus software from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of the antivirus software using one of these free tools: Antivirus Uninstallers
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 15:14:47.071 2010 (UTC - 5:00)
System Uptime: 0 days 6:40:00.897
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  wmplayer.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000004A
Arguments 00000000`75362dd9 00000000`00000002 00000000`00000000 fffff880`0c697c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 08:33:59.959 2010 (UTC - 5:00)
System Uptime: 0 days 1:28:09.785
Probably caused by : aswTdi.SYS ( aswTdi+7caa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`02cb2caa fffff880`0baf19b0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 07:04:39.700 2010 (UTC - 5:00)
System Uptime: 0 days 2:56:24.527
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+202 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0288fcdc fffff880`07c597d0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 04:07:24.032 2010 (UTC - 5:00)
System Uptime: 0 days 19:13:33.498
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 21 08:53:10.814 2010 (UTC - 5:00)
System Uptime: 2 days 2:09:23.640
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+11af7 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 06:43:04.908 2010 (UTC - 5:00)
System Uptime: 0 days 15:40:41.359
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9c8e1601 b3b7465e`ef0ae7f7 fffff800`02bb8a0b 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 18 15:01:03.661 2010 (UTC - 5:00)
System Uptime: 1 days 0:16:56.487
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BB.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0288c995 fffff880`0b9010e0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 17 14:30:59.419 2010 (UTC - 5:00)
System Uptime: 0 days 1:41:00.245
Probably caused by : afd.sys ( afd! ?? ::GFJBLGFE::`string'+39e6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`02d537e3 fffff880`031a8938 fffff880`031a81a0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 17 12:48:45.183 2010 (UTC - 5:00)
System Uptime: 0 days 2:20:25.009
BugCheck D1, {30, 2, 1, fffff88000fbb123}
Probably caused by : cdrom.sys ( cdrom!DeviceMainTimerTickHandler+ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00000030 00000000`00000002 00000000`00000001 fffff880`00fbb123
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 17 06:40:10.044 2010 (UTC - 5:00)
System Uptime: 0 days 4:10:08.496
BugCheck D1, {fffff7ffe38ca210, 2, 8, fffff7ffe38ca210}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iexplore.exe
Bugcheck code 000000D1
Arguments fffff7ff`e38ca210 00000000`00000002 00000000`00000008 fffff7ff`e38ca210
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 17 02:25:47.463 2010 (UTC - 5:00)
System Uptime: 0 days 18:38:31.915
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+637cd )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff960`000c37cd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 15 06:27:27.362 2010 (UTC - 5:00)
System Uptime: 0 days 4:55:04.813
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+74 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`028a141c fffff880`0afcfdc0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 14 14:44:41.180 2010 (UTC - 5:00)
System Uptime: 0 days 4:45:01.006
Probably caused by : memory_corruption ( nt!MiProcessWorkingSets+c6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffffa01`08f79418 00000000`00000002 00000000`00000001 fffff800`028e0086
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Koboldstatus · 24 Nov 2010

Any idea on what hardware that is the problem. RAM-memory maybe?

usasma · 24 Nov 2010

That's the problem with this sort of analysis - it doesn't tell us what exactly the problem is.
If it's a driver problem, normally the BSOD errors and causes will remain the same throughout several memory dump crashes. But if the errors start spitting out all over the place (as yours are tending to), then it's typically a problem that's caused by hardware (and, since the error comes whenever it feels like it, it will catch the system at different times/places, so it'll generate different errors).

There is also an error that sort of "bridges" the difference between software and hardware issues - and that is the compatibility problem. They have symptoms that vary, and can resemble either one.

So, let's start by getting rid of Daemon Tools (which is a compatibility issue), update your networking drivers, and reset your antivirus (this also has some symptoms of both hardware and software - because of the low level that the antivirus drivers work at).

Then if it continues, we'll start ripping things apart! :)