evo mene opet!
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini060309-10.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jun 3 16:00:15.625 2009 (GMT+2)
System Uptime: 0 days 0:08:16.359
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {89af87c0, 8a84b348, ba4e3cbc, 1}
Probably caused by : nv4_mini.sys ( nv4_mini+505fb )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: 89af87c0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 8a84b348, Pointer to a DEFERRED_WATCHDOG object.
Arg3: ba4e3cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: 89af87c0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 10
BUGCHECK_STR: 0xEA
PROCESS_NAME: cnc3game.dat
LAST_CONTROL_TRANSFER: from b91925fb to 8052b8fa
STACK_TEXT:
b4aa0d14 b91925fb b7e84410 b93c2614 8a859260 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b4aa0d1c b93c2614 8a859260 8a821808 00009410 nv4_mini+0x505fb
b4aa0d20 8a859260 8a821808 00009410 8a967418 nv4_mini+0x280614
b4aa0d24 8a821808 00009410 8a967418 8a821808 0x8a859260
b4aa0d28 00000000 8a967418 8a821808 7029fc08 0x8a821808
STACK_COMMAND: .thread 0xffffffff89af87c0 ; kb
FOLLOWUP_IP:
nv4_mini+505fb
b91925fb ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nv4_mini+505fb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4990a8d2
FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2009_02_09
BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2009_02_09
Followup: MachineOwner
---------
Maknuo sam drivere, stavio nove i opet ista greška... pomoć!
