Hi, in unregelmäßigen abständen bekomme ich einen BlueScreen. Darauf hin habe ich mal die DUMP Datei ausgewertet und werde daraus aber nicht wirklich schlau. Hoffentlich könnt ihr mir Helfen.Danke
Zitat:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {cc, 2, 0, 80513a77}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
Probably caused by : fltMgr.sys ( fltMgr+16d42 )
Followup: MachineOwner
---------
!analyze -v
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000cc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80513a77, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: fltMgr
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107bad
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
000000cc
CURRENT_IRQL: 2
FAULTING_IP:
nt!PsGetJobUIRestrictionsClass+d3
80513a77 8b4918 mov ecx,[ecx+0x18]
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 80513a77 to 804e187f
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f88d6c04 80513a77 badb0d00 00000000 00000000 nt!Kei386EoiHelper+0x2823
f88d6c78 8050b1af ff1427b8 00000000 824be0a0 nt!PsGetJobUIRestrictionsClass+0xd3
f88d6c8c f8286d42 ff1427b8 fe856008 82a479a8 nt!IoGetDeviceAttachmentBaseRef+0x17
f88d6cc4 f8273f64 824be068 fe856008 fe856008 fltMgr+0x16d42
f88d6cf8 804e37f7 82667da0 fe856008 fe8560c0 fltMgr+0x3f64
f88d6d30 8065e3df 8055fc90 00000001 00000000 nt!IofCallDriver+0x32
f88d6d5c 80663204 00000000 80561440 82ae1020 nt!KeI386SetGdtSelector+0x17c8
f88d6d74 804e426b 00000000 00000000 82ae1020 nt!MmMapUserAddressesToPage+0x1e5c
f88d6dac 8057be15 00000000 00000000 00000000 nt!ExQueueWorkItem+0x104
f88d6ddc 804fa4da 804e4196 00000000 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimer+0x107
FOLLOWUP_IP:
fltMgr+16d42
f8286d42 8b4dfc mov ecx,[ebp-0x4]
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: fltMgr+16d42
IMAGE_NAME: fltMgr.sys
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
|
Falls ihr noch Infos fehlen, einfach melden.
21.03.2009, 23:58
