BSOD - Help please

JusMu · 02 Nov 2010

My computer is about 6 months old and i have changed my motherboard already one time. In past few days i have starting to ger BSOD while working in windows. When im playing BSOD doesn't appear. Could somebody help me ? I have already runned memtest and it didn't give any error.

Windows 7 . . .
- x86 (32-bit) or x64 ?- x64
- the original installed OS on the system? - Yes
- an OEM or full retail version? - Full Retail
- What is the age of system (hardware)? - 6 moths, but my graphics card and hard disks are about 3-4 years old.
- What is the age of OS installation - I formated my OS yesterday

I ran the Windows_NT6_BSOD_jcgriff2 program and a system health report. Here are the files. Thanks in advance.

richc46 · 02 Nov 2010

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Documents[1].zip\Windows_NT6_BSOD_jcgriff2\110210-23805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Tue Nov  2 07:52:04.229 2010 (GMT-4)
System Uptime: 0 days 0:02:50.275
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\drivers\habu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for habu.sys
*** ERROR: Module load completed but symbols could not be loaded for habu.sys
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : habu.sys ( habu+718 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+0
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002a8746e to fffff80002a8f710
STACK_TEXT:  
fffff800`04258be8 fffff800`02a8746e : fffffa80`0376e650 fffff800`04258c68 fffff800`042593f0 fffff800`02abc668 : nt!KeBugCheck
fffff800`04258bf0 fffff800`02ab540d : fffff800`02c9db7c fffff800`02bd7e84 fffff800`02a1f000 fffff800`04259350 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04258c20 fffff800`02abca90 : fffff800`02bdeb14 fffff800`04258c98 fffff800`04259350 fffff800`02a1f000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`04258c50 fffff800`02abe06a : fffff800`04259350 fffff800`042593f0 fffffa80`00000001 00000000`00000005 : nt!RtlDispatchException+0x410
fffff800`04259330 fffff800`02aea112 : fffffa80`05af7050 fffff880`04612ba2 fffffa80`03920010 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff800`042598d0 fffff880`059ba718 : fffffa80`066ae301 fffff880`00000000 fffffa80`06733300 fffffa80`062ff800 : nt! ?? ::FNODOBFM::`string'+0xf5fc
fffff800`04259950 fffffa80`066ae301 : fffff880`00000000 fffffa80`06733300 fffffa80`062ff800 fffffa80`066d1250 : habu+0x718
fffff800`04259958 fffff880`00000000 : fffffa80`06733300 fffffa80`062ff800 fffffa80`066d1250 fffff880`0462dd70 : 0xfffffa80`066ae301
fffff800`04259960 fffffa80`06733300 : fffffa80`062ff800 fffffa80`066d1250 fffff880`0462dd70 fffffa80`0666ec00 : 0xfffff880`00000000
fffff800`04259968 fffffa80`062ff800 : fffffa80`066d1250 fffff880`0462dd70 fffffa80`0666ec00 fffffa80`067333d0 : 0xfffffa80`06733300
fffff800`04259970 fffffa80`066d1250 : fffff880`0462dd70 fffffa80`0666ec00 fffffa80`067333d0 fffffa80`066ae300 : 0xfffffa80`062ff800
fffff800`04259978 fffff880`0462dd70 : fffffa80`0666ec00 fffffa80`067333d0 fffffa80`066ae300 fffff800`02a91d26 : 0xfffffa80`066d1250
fffff800`04259980 fffff880`047e5300 : 00000000`000007ff 00000000`00000050 fffffa80`07349cc0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xac
fffff800`042599c0 fffffa80`066d1010 : fffffa80`0666eca0 fffffa80`038b0210 00000000`00000002 fffffa80`03920010 : usbehci!EHCI_sMode_PollEndpointSlot+0x388
fffff800`04259a50 fffffa80`0666eca0 : fffffa80`038b0210 00000000`00000002 fffffa80`03920010 fffffa80`05af7050 : 0xfffffa80`066d1010
fffff800`04259a58 fffffa80`038b0210 : 00000000`00000002 fffffa80`03920010 fffffa80`05af7050 fffff880`046135d9 : 0xfffffa80`0666eca0
fffff800`04259a60 00000000`00000002 : fffffa80`03920010 fffffa80`05af7050 fffff880`046135d9 fffffa80`05af7050 : 0xfffffa80`038b0210
fffff800`04259a68 fffffa80`03920010 : fffffa80`05af7050 fffff880`046135d9 fffffa80`05af7050 fffffa80`072fb200 : 0x2
fffff800`04259a70 fffffa80`05af7050 : fffff880`046135d9 fffffa80`05af7050 fffffa80`072fb200 00000000`00000000 : 0xfffffa80`03920010
fffff800`04259a78 fffff880`046135d9 : fffffa80`05af7050 fffffa80`072fb200 00000000`00000000 00000000`00000000 : 0xfffffa80`05af7050
fffff800`04259a80 fffff880`04613ab7 : fffffa80`03920002 fffffa80`067333d0 00000000`ffffffff fffffa80`05af7ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`04259b60 fffff880`0461164f : fffffa80`05af7ea8 fffffa80`05af71a0 fffffa80`05af8040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`04259bc0 fffff880`04602f89 : fffffa80`05af7050 00000000`00000000 fffffa80`0588c702 fffffa80`05af7ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`04259c00 fffff880`00f124ce : fffffa80`0588c000 fffffa80`05af7ea8 fffffa80`0588c750 fffffa80`05af7ec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`04259c30 fffffa80`0588c000 : fffffa80`05af7ea8 fffffa80`0588c750 fffffa80`05af7ec0 fffff880`045b99ec : sptd+0x424ce
fffff800`04259c38 fffffa80`05af7ea8 : fffffa80`0588c750 fffffa80`05af7ec0 fffff880`045b99ec 01cb7a84`5e096d5a : 0xfffffa80`0588c000
fffff800`04259c40 fffffa80`0588c750 : fffffa80`05af7ec0 fffff880`045b99ec 01cb7a84`5e096d5a fffff800`04253080 : 0xfffffa80`05af7ea8
fffff800`04259c48 fffffa80`05af7ec0 : fffff880`045b99ec 01cb7a84`5e096d5a fffff800`04253080 00000000`00000022 : 0xfffffa80`0588c750
fffff800`04259c50 fffff880`045b99ec : 01cb7a84`5e096d5a fffff800`04253080 00000000`00000022 00000000`00000000 : 0xfffffa80`05af7ec0
fffff800`04259c58 01cb7a84`5e096d5a : fffff800`04253080 00000000`00000022 00000000`00000000 00000000`00000000 : Rt64win7+0x449ec
fffff800`04259c60 fffff800`04253080 : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1cb7a84`5e096d5a
fffff800`04259c68 00000000`00000022 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05af7ec0 : 0xfffff800`04253080
fffff800`04259c70 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`05af7ec0 fffffa80`05af7ea8 : 0x22

Please remove 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:
http://www.duplexsecure.com/en/faq

Update Habu.sys
Habu.sys with description Diamondback USB Optical Mouse Driver is a driver file from company Razer (Asia-Pacific) Pte Ltd belonging to product Diamondback USB Optical Mouse.
In total there are 1 launchpoints for this file .

JusMu · 02 Nov 2010

I have uninstalled daemon tools and SPTD. I just doesn't know how to solve that habu.sys problem. I will no try to uninstall my habu drivers and install them back like they should. Let's see what's happens.

richc46 · 02 Nov 2010

You can try with just SPTD. There was a conflict, maybe it will work with just SPTD removed

JusMu · 02 Nov 2010

Well now i have reinstalled my habu drivers and uninstalled deamon tools and STPD. My computer haven't crushed down since i uninstalled that daemon tools. So far so good. I really appreciate your help. Thanks a lot

. I will inform if BSOD comes bothering me again.

richc46 · 02 Nov 2010

Some of these reports are not clear. Yours was right on target, I think you will be OK.
good luck my friend

If you have it again.
Go to search type cmd
in cmd type driverquery and make sure sptd is gone. That was the main problem

JusMu · 02 Nov 2010

well it happened again after i wrote that.

richc46 · 02 Nov 2010

Give me the report. I am surprised, however.

JusMu · 02 Nov 2010

I made those stuff again. Even thought i read that someone had been the same problem with habu.sys. Computer didn't crached if razer habu wasn't connected. When he connected his habu again computer crashed.

richc46 · 02 Nov 2010

I cant change what is happening in your computer. It is habu, again.
Either uninstall
Find a replacement
or update and hope that it works.

Yor computer does not want to work with habu.