1000008e Fehler. Abstürze immer nur beim spielen!

Meerbi

Cadet 3rd Year
Dabei seit
Apr. 2013
Beiträge
43
Hallo, ich habe seit EINIGEN MONATEN ein grosses Problem!
und zwar hier der Fehlercode:

1000008e BCP1:C000001d BCP2: e2f53f97 BCP3: b790588c BCP4:00000000

Ich wäre sehr dankbar wenn ihr die zip datei öffnet und darin ist eine dmp datei.
Damit kann man die böse datei heraus finden! also bitte datenname der datei reinschreiben!

lg meerbi:freak:
 

Anhänge

Inzersdorfer

Vice Admiral
Dabei seit
Juli 2010
Beiträge
6.337
Hier die Auswertung mit WinDbg:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\HELP\meerbi\Mini090213-02.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
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Mon Sep 2 17:04:36.718 2013 (UTC + 2:00)
System Uptime: 0 days 0:22:28.293
Loading Kernel Symbols
......................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image ati3duag.dll, Win32 error 0n2
WARNING: Unable to verify timestamp for ati3duag.dll
ERROR: Module load completed but symbols could not be loaded for ati3duag.dll

Bugcheck Analysis:

Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, e3753970, b7dd888c, 0}
Probably caused by : ati3duag.dll ( ati3duag+109648 )
Followup: MachineOwner
---------
kd> !analyze -v
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.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: e3753970, The address that the exception occurred at
Arg3: b7dd888c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction
An attempt was made to execute an illegal instruction.

FAULTING_IP:
+109648
e3753970 f20fd6d5 movdq2q mm2,xmm5

TRAP_FRAME: b7dd888c -- (.trap 0xffffffffb7dd888c)
ErrCode = 00000000
eax=e43f5ec0 ebx=e3d6c040 ecx=0000008b edx=00000120 esi=e3dbaac0 edi=e3dbaac0
eip=e3753970 esp=b7dd8900 ebp=b7dd890c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3753970 f20fd6d5 movdq2q mm2,xmm5
Resetting default scope

CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: NFSC.exe
LAST_CONTROL_TRANSFER: from bf2b6648 to e3753970

FAILED_INSTRUCTION_ADDRESS:
+109648
e3753970 f20fd6d5 movdq2q mm2,xmm5

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7dd890c bf2b6648 e3dbaac0 b7dd89a0 e3c4e448 0xe3753970
b7dd8910 e3dbaac0 b7dd89a0 e3c4e448 bf2b6672 ati3duag+0x109648
b7dd8914 b7dd89a0 e3c4e448 bf2b6672 e3c4e454 0xe3dbaac0
b7dd8918 e3c4e448 bf2b6672 e3c4e454 e3c4e2e0 0xb7dd89a0
b7dd89a0 00000000 7dccccce 7dccccce 7dccccce 0xe3c4e448


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+109648
bf2b6648 ?? ???

SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ati3duag+109648
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 493448c7
FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag+109648
BUCKET_ID: 0x8E_BAD_IP_ati3duag+109648
Followup: MachineOwner
---------

kd> lmvm ati3duag
start end module name
bf1ad000 bf59af40 ati3duag T (no symbols)
Loaded symbol image file: ati3duag.dll
Image path: ati3duag.dll
Image name: ati3duag.dll
Timestamp: Mon Dec 01 21:27:51 2008 (493448C7)
CheckSum: 003F7D8B
ImageSize: 003EDF40
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

vhyper

Cadet 2nd Year
Dabei seit
Okt. 2005
Beiträge
22
Hallo Meerbi,

aufgrund der Debugger Auswertung und der Ausweisung der "ati3duag.dll" würde ich glatt auf ein Problem mit dem Grafikkartentreiber denken.
Hast du den aktuellsten Treiber installiert?
 
Top