Hi,
I've had this problem since I built my rig (which isn't amazing by any means).
The BSOD says Hardware Malfunction. Your system has halted. Contact the retailer/service vendor and that would be me...
I don't know what the event log is trying to tell me. Could someone tell me if it's graphics or power or something else?
Have uploaded the first minidump.
Thanking you!
Chazz
Can you go into c:\windows\minidump, zip the dump file (*.dmp) and upload it to us. the text file clips things off and I cant put it thru the debugger.
thanks
Ken
yo,
zipped 1st dump file.
cheers
CM
You know that USB you have? It probably caused this BSOD. time for a driver update. Are you having issues with sleep/hibernation?
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\082909-23244-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Sat Aug 29 04:03:05.128 2009 (GMT-4)
System Uptime: 0 days 10:50:06.188
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {8, 6, b, fffffa8005ec8b20}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000b, TimeoutCode
Arg4: fffffa8005ec8b20
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'hiber_dumpfve' and 'spsys.sys' overlap
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05af19ec cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbhub
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc2d
FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Followup: MachineOwner
---------
Hope this helps
Ken
thanks a lot!
you think a USB device caused a blue screen? driver update of one of 6 items then... the error log says US hub - you don't think it's my MoBo?
no sleep/hibernation problems.
That's weird - I don't use an external usb hub!
Even so, the other dump files (multiple) refer to nvoclk64.sys being the driver that caused the crash. I've got the latest nvidia drivers, and I don't know how to solve this. Any ideas?
Quote