12 april is al een tijdje geleden, ben je zeker dat dit de laatste is?
BugCheck EA, {86596020, 8a357910, 8a4529d8, 1}
Probably caused by : nv4_disp.dll ( nv4_disp+285b6 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 86596020, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 8a357910, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8a4529d8, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
FAULTING_THREAD: 86596020
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: nvsvc32.exe
LAST_CONTROL_TRANSFER: from e1967010 to bd03a5b6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a4e5e518 e1967010 e1967010 e1967010 00053600 nv4_disp+0x285b6
a4e5e51c e1967010 e1967010 00053600 bd04e140 0xe1967010
a4e5e520 e1967010 00053600 bd04e140 00000000 0xe1967010
a4e5e524 00053600 bd04e140 00000000 00000000 0xe1967010
a4e5e528 bd04e140 00000000 00000000 00000000 0x53600
a4e5e52c 00000000 00000000 00000000 e1967010 nv4_disp+0x3c140
STACK_COMMAND: .thread 0xffffffff86596020 ; kb
FOLLOWUP_IP:
nv4_disp+285b6
bd03a5b6 894c2414 mov dword ptr [esp+14h],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+285b6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ba03b7a
FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2010_03_17
BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2010_03_17
Followup: MachineOwner
---------
de blue screen van 12 april wijst op een probleem met de videodriver
), deze bevindt zich onder C:\Windows\Minidump