BSOD: ASUS N71JQ

[pdxnet96]

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols;SRV*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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`03287e50
Debug session time: Sun Jul 18 15:06:59.626 2010 (UTC + 2:00)
System Uptime: 0 days 6:53:03.093
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, a, fffffa80065aa000}

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

Followup: MachineOwner
---------

3: kd> !analyze -vv
*******************************************************************************
* *
* 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: 000000000000000a, TimeoutCode
Arg4: fffffa80065aa000

Debugging Details:
------------------

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************

BUILD_VERSION_STRING: 7600.16539.amd64fre.win7_gdr.100226-1909

SYSTEM_MANUFACTURER: ASUSTeK Computer Inc.

SYSTEM_PRODUCT_NAME: ASUSTeK Computer Inc.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: N71Jq.207

BASEBOARD_MANUFACTURER: ASUSTeK Computer Inc.

OVERLAPPED_UNLOADED_MODULE: Address regions for 'dump_iaStor' and 'dump_iaStor.sys (unloaded)' overlap

CPU_MICROCODE: 6,1e,5,0 (F,M,S,R) SIG: 3'00000000 (cache) 3'00000000 (init)

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: PDXNET96-PC

ANALYSIS_SESSION_TIME: 07-18-2010 15:49:13.0890

LAST_CONTROL_TRANSFER: from fffff880058369ec to fffff800030ba600

STACK_TEXT:
fffff880`0337ec18 fffff880`058369ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`0000000a : nt!KeBugCheckEx
fffff880`0337ec20 fffff800`033b7827 : fffffa80`065a4050 fffffa80`0a4ad0e0 ffffffff`dc3a58a0 fffff800`0325f5f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`0337ec80 fffff800`030c7861 : fffff880`04258700 fffff880`04258744 fffffa80`03ceb680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`0337ecb0 fffff800`0335fa86 : c775c775`f731f731 fffffa80`03ceb680 00000000`00000080 fffffa80`03cd2890 : nt!ExpWorkerThread+0x111
fffff880`0337ed40 fffff800`03098b06 : fffff880`03167180 fffffa80`03ceb680 fffff880`031720c0 25502550`6a326a32 : nt!PspSystemThreadStartup+0x5a
fffff880`0337ed80 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`0337e970 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`058369ec cc int 3

FAULT_INSTR_CODE: 8f8d48cc

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

ANALYSIS_SESSION_ELAPSED_TIME: 39ec

Followup: MachineOwner
---------

Heeft iemand een idee ?

[Mexel]

Zelf al eens gezocht op de foutcode die de BSOD geeft, en gebruik de zoek functie eens hiero

[pdxnet96]

Mexel schreef op zondag 18 juli 2010 @ 16:03:
Zelf al eens gezocht op de foutcode die de BSOD geeft, en gebruik de zoek functie eens hiero

Ja Ja, geen oplossing..