*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from bf8bf279 to bf819785
STACK_TEXT:
eeb58408 bf8bf279 e112d5c0 eeb5860c eeb585c8 win32k!psSetupDstSurface+0xb
eeb58620 bf83dfbf e112d5c0 e1ef6818 eeb58650 win32k!EngAlphaBlend+0x163
eeb5881c 804de7ec 58010797 00000000 e1e23238 win32k!NtGdiAlphaBlend+0xb55
eeb5881c 7c90eb94 58010797 00000000 e1e23238 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006eb24 00000000 00000000 00000000 00000000 0x7c90eb94
FOLLOWUP_IP:
win32k!psSetupDstSurface+b
bf819785 53 push ebx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!psSetupDstSurface+b
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 422511a2
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x7f_8_win32k!psSetupDstSurface+b
BUCKET_ID: 0x7f_8_win32k!psSetupDstSurface+b
Followup: MachineOwner
---------
Behöver hjälp av tolka en bugcheck analysis av debugging tools
2 svar · 224 visningar · startad av Fasos
Ännu en blåskärm...:(
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: ef0ae5c6, The address that the exception occurred at
Arg3: ff27c668, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p "0x%08lx" refererade till minnet p "0x%08lx". Det gick inte att utf ra en minnes tg rd. F ljande fel returnerades: The memory could not be "%s".
FAULTING_IP:
NavEx15+615c6
ef0ae5c6 0000 add [eax],al
TRAP_FRAME: ff27c668 -- (.trap ffffffffff27c668)
ErrCode = 00000002
eax=00000090 ebx=f8dbc008 ecx=00000000 edx=00000000 esi=f8dbde51 edi=f8dbc008
eip=ef0ae5c6 esp=ff27c6dc ebp=ff27c7f0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
NavEx15+0x615c6:
ef0ae5c6 0000 add [eax],al ds:0023:00000090=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
MISALIGNED_IP:
NavEx15+615c6
ef0ae5c6 0000 add [eax],al
LAST_CONTROL_TRANSFER: from ef0a1ce7 to ef0ae5c6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ff27c7f0 ef0a1ce7 f8dbc0ff ff27cc58 f8dbc008 NavEx15+0x615c6
ff27c824 ef076dac f8dbc008 e1689460 000000f8 NavEx15+0x54ce7
ff27cc6c ef078b91 f8dbc008 e1689460 ff27ccf0 NavEx15+0x29dac
ff27ccf4 ef078f92 00000001 e16bbf00 f8d61314 NavEx15+0x2bb91
ff27ce98 ef079648 ef13f5f8 e16bbf00 e1689460 NavEx15+0x2bf92
ff27cecc ef110afd ef13f5f8 e16bbf00 e1689460 NavEx15+0x2c648
00000000 00000000 00000000 00000000 00000000 SAVRT+0x21afd
FOLLOWUP_IP:
NavEx15+615c6
ef0ae5c6 0000 add [eax],al
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: NavEx15+615c6
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .trap ffffffffff27c668 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_NavEx15.Sys
BUCKET_ID: IP_MISALIGNED_NavEx15.Sys
Followup: MachineOwner
---------
Andra crachen va Norton antivirus
Men knappast de som är ursprungliga felet
Som vanligt säger jag
Testa minnena
Kolla tempraturerna så dom är ok
Installera senaste chipset/ljud/grafik drivrutiner