Answer the question
In order to leave comments, you need to log in
How to correctly interpret the cause of bsod?
Good afternoon.
The machine began to fall into the blue screen and I can not find for what reason. Please help me figure it out:
*The computer was restarted after a critical error. Error code: 0x0000007e (0xffffffffc0000005, 0xfffff88001a14f99, 0xfffff880039cba38, 0xfffff880039cb290). The memory dump is stored in: C:\Windows\MEMORY.DMP.*
WinDBG gives this dump analysis:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff88001a14f99, fffff880039cba38, fffff880039cb290}
Probably caused by : Unknown_Image ( ndis!NdisFreeIoWorkItem+9 )
Followup: MachineOwner
---------
16.5: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001a14f99, The address that the exception occurred at
Arg3: fffff880039cba38, Exception Record Address
Arg4: fffff880039cb290, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
ndis!NdisFreeIoWorkItem+9
fffff880`01a14f99 48 dec eax
EXCEPTION_RECORD: fffff880039cba38 -- (.exr 0xfffff880039cba38)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 27348889
Parameter[0]: fffffffffffff880
Parameter[1]: 0000000000000002
Parameter[2]: 0000000000000000
Parameter[3]: 0000000000000000
Parameter[4]: 0000000000000000
Parameter[5]: 0000000000000008
Parameter[6]: 0000000000000000
Parameter[7]: 0000000000000000
Parameter[8]: 0000000000000000
Parameter[9]: 0000000000000000
Parameter[10]: 0000000000000000
Parameter[11]: ffffffffffffffff
Parameter[12]: 000000000000007f
Parameter[13]: 0000000000000000
Parameter[14]: 0000000000000000
Attempt to execute non-executable address 0000000000000002
CONTEXT: fffff880039cb290 -- (.cxr 0xfffff880039cb290)
Unable to read context, NTSTATUS 0xC0000147
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ndis!NdisFreeIoWorkItem+9
fffff880`01a14f99 48 dec eax
SYMBOL_NAME: ndis!NdisFreeIoWorkItem+9
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: INVALID_KERNEL_CONTEXT
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
16.5: kd:x86> lmvm Unknown_Module
start end module name
Answer the question
In order to leave comments, you need to log in
The error code is:
bsodstop.ru/0x0000007e-system-thread-exception-not...
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question