PDA

View Full Version : Error in land battle



alvabsas
4th Mar 2008, 17:13
The dump file of the crash... anyone can understand this, thanks.


Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini052008-01.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Tue May 20 05:21:51.910 2008 (GMT-3)
System Uptime: 0 days 15:18:41.488
Loading Kernel Symbols
..............................................................................................................
Loading User Symbols
Loading unloaded module list
...................


Bugcheck Analysis



Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : nv4_disp.dll ( nv4_disp+2c60c0 )

Followup: MachineOwner
---------

kd> !analyze -v

* *
* 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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: ImperialGlory.e

LAST_CONTROL_TRANSFER: from e20f9ac0 to e24fcf11

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b83a5990 e20f9ac0 bf2d80c0 e3c29040 e1ed4800 0xe24fcf11
b83a5994 bf2d80c0 e3c29040 e1ed4800 bf2d80c0 0xe20f9ac0
b83a5998 e3c29040 e1ed4800 bf2d80c0 e20f7000 nv4_disp+0x2c60c0
b83a599c e1ed4800 bf2d80c0 e20f7000 e20f99bc 0xe3c29040
b83a59a0 bf2d80c0 e20f7000 e20f99bc e3c29040 0xe1ed4800
b83a59a4 e20f7000 e20f99bc e3c29040 e20f9ac0 nv4_disp+0x2c60c0
b83a59a8 e20f99bc e3c29040 e20f9ac0 b83a5b20 0xe20f7000
b83a59ac e3c29040 e20f9ac0 b83a5b20 bf1f103b 0xe20f99bc
b83a59b0 e20f9ac0 b83a5b20 bf1f103b e20f99bc 0xe3c29040
b83a59b4 b83a5b20 bf1f103b e20f99bc e20f9ac0 0xe20f9ac0
b83a59b8 bf1f103b e20f99bc e20f9ac0 bf2d80c0 0xb83a5b20
b83a5b20 bf13d529 e200c880 e24a5d80 00009d7a nv4_disp+0x1df03b
b83a5b24 e200c880 e24a5d80 00009d7a 00000001 nv4_disp+0x12b529
b83a5b28 e24a5d80 00009d7a 00000001 b83a5b5c 0xe200c880
b83a5b2c 00000000 00000001 b83a5b5c b83a5b58 0xe24a5d80


STACK_COMMAND: kb



FOLLOWUP_IP:
nv4_disp+2c60c0
bf2d80c0 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp+2c60c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 439abe39

FAILURE_BUCKET_ID: 0x7f_d_nv4_disp+2c60c0

BUCKET_ID: 0x7f_d_nv4_disp+2c60c0

Followup: MachineOwner
---------

Starmatske
14th Jun 2008, 15:09
Update your videocard driver