Striker1986
Cadet 4th Year
- Registriert
- Nov. 2010
- Beiträge
- 121
Hallo liebe CBler!
Stehe (oder sitze besser gesagt) hier vor nem kleinen Problem. Der EEE 1000 HG von nem Kollegen crasht wann er mal lustig is und startet sofort neu, als wäre nichts gewesen lässt sich danach auch arbeiten.
Das hauseigene Windows-Tool hat nach der Crash Dump Analyse folgendes ausgespuckt:
Kann einer vll rauslesen, warum das NB Bluescreens zeigt und abstürtzt?
Greets
Stehe (oder sitze besser gesagt) hier vor nem kleinen Problem. Der EEE 1000 HG von nem Kollegen crasht wann er mal lustig is und startet sofort neu, als wäre nichts gewesen lässt sich danach auch arbeiten.
Das hauseigene Windows-Tool hat nach der Crash Dump Analyse folgendes ausgespuckt:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 6cb8f058, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f6b7c801, address which referenced memory
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
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: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
6cb8f058
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT+b801
f6b7c801 f60558f0b8f604 test byte ptr [USBPORT+0x1e058 (f6b8f058)],4
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f6b7e13a to f6b7c801
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f79b3f48 f6b7e13a 8646b028 80546b3c 8646b230 USBPORT+0xb801
f79b3f74 f6b8c24b 8646b028 80546b3c 8646b028 USBPORT+0xd13a
f79b3fb0 f6b8c3c2 8646b028 00000001 b0bc9623 USBPORT+0x1b24b
f79b3fcc 80545eef 8646b64c 6b755044 00000000 USBPORT+0x1b3c2
f79b3fd0 8646b64c 6b755044 00000000 8646b0ec nt+0x6eeef
f79b3fd4 6b755044 00000000 8646b0ec 01000100 0x8646b64c
f79b3fd8 00000000 8646b0ec 01000100 82040800 0x6b755044
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT+b801
f6b7c801 f60558f0b8f604 test byte ptr [USBPORT+0x1e058 (f6b8f058)],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBPORT+b801
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 6cb8f058, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f6b7c801, address which referenced memory
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
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: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
6cb8f058
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT+b801
f6b7c801 f60558f0b8f604 test byte ptr [USBPORT+0x1e058 (f6b8f058)],4
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f6b7e13a to f6b7c801
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f79b3f48 f6b7e13a 8646b028 80546b3c 8646b230 USBPORT+0xb801
f79b3f74 f6b8c24b 8646b028 80546b3c 8646b028 USBPORT+0xd13a
f79b3fb0 f6b8c3c2 8646b028 00000001 b0bc9623 USBPORT+0x1b24b
f79b3fcc 80545eef 8646b64c 6b755044 00000000 USBPORT+0x1b3c2
f79b3fd0 8646b64c 6b755044 00000000 8646b0ec nt+0x6eeef
f79b3fd4 6b755044 00000000 8646b0ec 01000100 0x8646b64c
f79b3fd8 00000000 8646b0ec 01000100 82040800 0x6b755044
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT+b801
f6b7c801 f60558f0b8f604 test byte ptr [USBPORT+0x1e058 (f6b8f058)],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBPORT+b801
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Kann einer vll rauslesen, warum das NB Bluescreens zeigt und abstürtzt?
Greets
