Poniżej wklejam mój Bluesceeen Proszę o pomoc i za odpowiedzi dziekuję.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Michal\Desktop\122810-35427-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50
Debug session time: Tue Dec 28 17:36:40.070 2010 (GMT+1)
System Uptime: 0 days 2:15:53.693
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image \SystemRoot\system32\DRIVERS\USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {4, fffffa8003157660, fffffa8004a9ae48, fffffa8004fb9c00}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : USBPORT.SYS ( USBPORT+16eb7 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
that is already pending in the USB bus driver.
Arg2: fffffa8003157660, Address of IRP
Arg3: fffffa8004a9ae48, Address of URB
Arg4: fffffa8004fb9c00
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: USBPORT
FAULTING_MODULE: fffff8000305e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88002a61eb7 to fffff800030ce740
STACK_TEXT:
fffff880`023b4948 fffff880`02a61eb7 : 00000000`000000fe 00000000`00000004 fffffa80`03157660 fffffa80`04a9ae48 : nt+0x70740
fffff880`023b4950 00000000`000000fe : 00000000`00000004 fffffa80`03157660 fffffa80`04a9ae48 fffffa80`04fb9c00 : USBPORT+0x16eb7
fffff880`023b4958 00000000`00000004 : fffffa80`03157660 fffffa80`04a9ae48 fffffa80`04fb9c00 fffffa80`04a9ae48 : 0xfe
fffff880`023b4960 fffffa80`03157660 : fffffa80`04a9ae48 fffffa80`04fb9c00 fffffa80`04a9ae48 fffffa80`03186710 : 0x4
fffff880`023b4968 fffffa80`04a9ae48 : fffffa80`04fb9c00 fffffa80`04a9ae48 fffffa80`03186710 00000000`0000001b : 0xfffffa80`03157660
fffff880`023b4970 fffffa80`04fb9c00 : fffffa80`04a9ae48 fffffa80`03186710 00000000`0000001b fffffa80`04a9ae48 : 0xfffffa80`04a9ae48
fffff880`023b4978 fffffa80`04a9ae48 : fffffa80`03186710 00000000`0000001b fffffa80`04a9ae48 fffff880`02a6d356 : 0xfffffa80`04fb9c00
fffff880`023b4980 fffffa80`03186710 : 00000000`0000001b fffffa80`04a9ae48 fffff880`02a6d356 fffffa80`03a96000 : 0xfffffa80`04a9ae48
fffff880`023b4988 00000000`0000001b : fffffa80`04a9ae48 fffff880`02a6d356 fffffa80`03a96000 fffffa80`029a4220 : 0xfffffa80`03186710
fffff880`023b4990 fffffa80`04a9ae48 : fffff880`02a6d356 fffffa80`03a96000 fffffa80`029a4220 00000000`00000000 : 0x1b
fffff880`023b4998 fffff880`02a6d356 : fffffa80`03a96000 fffffa80`029a4220 00000000`00000000 fffffa80`03a96050 : 0xfffffa80`04a9ae48
fffff880`023b49a0 fffffa80`03a96000 : fffffa80`029a4220 00000000`00000000 fffffa80`03a96050 00000000`00000000 : USBPORT+0x22356
fffff880`023b49a8 fffffa80`029a4220 : 00000000`00000000 fffffa80`03a96050 00000000`00000000 fffffa80`00000000 : 0xfffffa80`03a96000
fffff880`023b49b0 00000000`00000000 : fffffa80`03a96050 00000000`00000000 fffffa80`00000000 00000000`00000000 : 0xfffffa80`029a4220
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT+16eb7
fffff880`02a61eb7 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT+16eb7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
that is already pending in the USB bus driver.
Arg2: fffffa8003157660, Address of IRP
Arg3: fffffa8004a9ae48, Address of URB
Arg4: fffffa8004fb9c00
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: USBPORT
FAULTING_MODULE: fffff8000305e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88002a61eb7 to fffff800030ce740
STACK_TEXT:
fffff880`023b4948 fffff880`02a61eb7 : 00000000`000000fe 00000000`00000004 fffffa80`03157660 fffffa80`04a9ae48 : nt+0x70740
fffff880`023b4950 00000000`000000fe : 00000000`00000004 fffffa80`03157660 fffffa80`04a9ae48 fffffa80`04fb9c00 : USBPORT+0x16eb7
fffff880`023b4958 00000000`00000004 : fffffa80`03157660 fffffa80`04a9ae48 fffffa80`04fb9c00 fffffa80`04a9ae48 : 0xfe
fffff880`023b4960 fffffa80`03157660 : fffffa80`04a9ae48 fffffa80`04fb9c00 fffffa80`04a9ae48 fffffa80`03186710 : 0x4
fffff880`023b4968 fffffa80`04a9ae48 : fffffa80`04fb9c00 fffffa80`04a9ae48 fffffa80`03186710 00000000`0000001b : 0xfffffa80`03157660
fffff880`023b4970 fffffa80`04fb9c00 : fffffa80`04a9ae48 fffffa80`03186710 00000000`0000001b fffffa80`04a9ae48 : 0xfffffa80`04a9ae48
fffff880`023b4978 fffffa80`04a9ae48 : fffffa80`03186710 00000000`0000001b fffffa80`04a9ae48 fffff880`02a6d356 : 0xfffffa80`04fb9c00
fffff880`023b4980 fffffa80`03186710 : 00000000`0000001b fffffa80`04a9ae48 fffff880`02a6d356 fffffa80`03a96000 : 0xfffffa80`04a9ae48
fffff880`023b4988 00000000`0000001b : fffffa80`04a9ae48 fffff880`02a6d356 fffffa80`03a96000 fffffa80`029a4220 : 0xfffffa80`03186710
fffff880`023b4990 fffffa80`04a9ae48 : fffff880`02a6d356 fffffa80`03a96000 fffffa80`029a4220 00000000`00000000 : 0x1b
fffff880`023b4998 fffff880`02a6d356 : fffffa80`03a96000 fffffa80`029a4220 00000000`00000000 fffffa80`03a96050 : 0xfffffa80`04a9ae48
fffff880`023b49a0 fffffa80`03a96000 : fffffa80`029a4220 00000000`00000000 fffffa80`03a96050 00000000`00000000 : USBPORT+0x22356
fffff880`023b49a8 fffffa80`029a4220 : 00000000`00000000 fffffa80`03a96050 00000000`00000000 fffffa80`00000000 : 0xfffffa80`03a96000
fffff880`023b49b0 00000000`00000000 : fffffa80`03a96050 00000000`00000000 fffffa80`00000000 00000000`00000000 : 0xfffffa80`029a4220
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT+16eb7
fffff880`02a61eb7 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT+16eb7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
