R
RedBrain
Guest
Moin,
als ich King of the Road gespielt habe, kommt ne BSOD raus...
BSOD-Meldung:
Heute:
Gestern:
Ich kenne diese fehlermeldung nicht, was soll ich den jetzt machen????
als ich King of the Road gespielt habe, kommt ne BSOD raus...
BSOD-Meldung:
Heute:
Code:
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 858248a0, The pool entry we were looking for within the page.
Arg3: 85824968, The next pool entry.
Arg4: 0a190005, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: cmuda
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 43a105d7
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
858248a0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 8054c4c1 to 8053380e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b7e3fa2c 8054c4c1 00000019 00000020 858248a0 nt+0x5c80e
b7e3fa7c 8054be39 858248a8 00000000 00000001 nt+0x754c1
b7e3fa8c f71b402c 858248a8 867085f0 b7e3fb14 nt+0x74e39
b7e3fa90 858248a8 867085f0 b7e3fb14 86708618 cmuda+0xa602c
b7e3fa94 867085f0 b7e3fb14 86708618 f71b44e4 0x858248a8
b7e3fa98 b7e3fb14 86708618 f71b44e4 00000000 0x867085f0
b7e3fa9c 86708618 f71b44e4 00000000 8596f960 0xb7e3fb14
b7e3fb14 f70eafba 00000001 865500e8 863a89e0 0x86708618
b7e3fb28 f70f0fae 85849e74 b7e3fb4c f70fb2ae portcls+0xfba
b7e3fb34 f70fb2ae 85849e60 86550030 863ac700 portcls+0x6fae
b7e3fb4c f728910c 86654c20 863ac700 b7e3fb74 portcls+0x112ae
b7e3fb5c f70fa8c0 86550030 863ac700 00000000 ks+0x910c
b7e3fb74 f70fa881 86550030 863ac700 b7e3fbe4 portcls+0x108c0
b7e3fb84 f7247137 86550030 863ac700 863ac710 portcls+0x10881
b7e3fbe4 80564777 0096fcf8 8596fce0 00000000 cmuda+0x139137
b7e3fc00 804e36d5 8596fcf8 00000000 804d9050 nt+0x8d777
b7e3fc24 b8214125 86707018 e2732b00 b8212ba2 nt+0xc6d5
b7e3fc3c b821335c 00000001 866c8a90 b7e3fc5c sysaudio+0x4125
b7e3fc4c f7289695 86644ee0 86707008 b7e3fca4 sysaudio+0x335c
b7e3fc5c 804e37f7 86644ee0 86707008 86707008 ks+0x9695
b7e3fca4 80564777 0096fde0 8596fdc8 00000000 nt+0xc7f7
b7e3fcc0 804e36d5 8596fde0 00000000 000005b4 nt+0x8d777
b7e3fce4 80567847 860c4020 e2dd87a8 864156b0 nt+0xc6d5
b7e3fcfc 805678b0 e2dd87a8 8596fde0 000005b4 nt+0x90847
b7e3fd44 805678fa 000005b4 00000001 00000000 nt+0x908b0
b7e3fd58 804de7ec 000005b4 0012fd44 7c91e4f4 nt+0x908fa
b7e3fd64 7c91e4f4 badb0d00 0012fd40 b82abd98 nt+0x77ec
b7e3fd68 badb0d00 0012fd40 b82abd98 b82abdcc 0x7c91e4f4
b7e3fd6c 0012fd40 b82abd98 b82abdcc 00000000 0xbadb0d00
b7e3fd70 b82abd98 b82abdcc 00000000 00000000 0x12fd40
b7e3fd74 b82abdcc 00000000 00000000 00000000 0xb82abd98
b7e3fd78 00000000 00000000 00000000 00000000 0xb82abdcc
STACK_COMMAND: kb
FOLLOWUP_IP:
cmuda+a602c
f71b402c ?? ???
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: cmuda.sys
SYMBOL_NAME: cmuda+a602c
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------Gestern:
Code:
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 865e98d0, The pool entry we were looking for within the page.
Arg3: 865e9d48, The next pool entry.
Arg4: aa8fae9a, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 865e98d0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 8054c4c1 to 8053380e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba6b6980 8054c4c1 00000019 00000020 865e98d0 nt+0x5c80e
ba6b69d0 8056744e 865e98d8 00000000 ba6b6d64 nt+0x754c1
ba6b6d48 804de7ec 00000040 00223500 00000001 nt+0x9044e
ba6b6d64 7c91e4f4 badb0d00 03b3fd90 ba6b6d98 nt+0x77ec
ba6b6d68 badb0d00 03b3fd90 ba6b6d98 ba6b6dcc 0x7c91e4f4
ba6b6d6c 03b3fd90 ba6b6d98 ba6b6dcc 00000000 0xbadb0d00
ba6b6d70 ba6b6d98 ba6b6dcc 00000000 00000000 0x3b3fd90
ba6b6d74 ba6b6dcc 00000000 00000000 00000000 0xba6b6d98
ba6b6d98 00000000 7c91e4f4 00cc4bc0 73e735d8 0xba6b6dcc
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+5c80e
8053380e 5d pop ebp
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
SYMBOL_NAME: nt+5c80e
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------Ich kenne diese fehlermeldung nicht, was soll ich den jetzt machen????
