I have
C2D E6400
2 GB PC 533
Sapphire x1950gt 256 MB
SB Live!
Abit AB9 motherboard
XP Pro SP2
THe problem I have is that when i play Two worlds, after a few minutes the screen goes black and then the computer resets. After the reboot i get a message from the OS saying that there was a loop error in the video card 100000EA.
I ran the analyzer on the minidump and this is what it came up with.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini091407-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Sep 14 18:39:10.265 2007 (GMT-7)
System Uptime: 0 days 0:13:08.842
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {87184da8, 88f19b58, bace3cbc, 1}
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
Probably caused by : ati2mtag.sys ( ati2mtag+12df93 )
Followup: MachineOwner
---------
0: 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: 87184da8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 88f19b58, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bace3cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: 87184da8
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 2
BUGCHECK_STR: 0xEA
PROCESS_NAME: TwoWorlds.exe
LAST_CONTROL_TRANSFER: from b9b9ff93 to 8052ab42
STACK_TEXT:
aab1d698 b9b9ff93 baa18e40 b9ba01e9 baa18000 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
aab1d6bc b9ba03b1 89899dd0 00000390 b9bd877a ati2mtag+0x12df93
aab1d740 b9ba2764 aab1d758 00000000 baa32ca6 ati2mtag+0x12e3b1
aab1d768 b9ba2b61 89899dd0 aab1d798 89899dd0 ati2mtag+0x130764
aab1d7a8 b9ba2bf1 11010000 89899ec0 00000200 ati2mtag+0x130b61
aab1d7d8 b9a7b905 e5ab2680 89892350 89892350 ati2mtag+0x130bf1
aab1d7ec b9a7cc73 89892350 aab1d990 89892350 ati2mtag+0x9905
aab1d804 bfa3c86f 89892350 89892350 aab1d828 ati2mtag+0xac73
aab1d808 89892350 89892350 aab1d828 aab1d9f8 ati2cqag+0x2286f
aab1d80c 89892350 aab1d828 aab1d9f8 e2400000 0x89892350
aab1d810 aab1d828 aab1d9f8 e2400000 00011000 0x89892350
aab1d814 aab1d9f8 e2400000 00011000 7fffffff 0xaab1d828
aab1d828 aab1d830 00000160 00007e00 0c000000 0xaab1d9f8
aab1d82c 00000000 00007e00 0c000000 066b6ae0 0xaab1d830
STACK_COMMAND: .thread 0xffffffff87184da8 ; kb
FOLLOWUP_IP:
ati2mtag+12df93
b9b9ff93 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ati2mtag+12df93
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46cb9a6a
FAILURE_BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_08_21
BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_08_21
Followup: MachineOwner
---------
I have tried to reinstall the newest ATI drivers as well as the latest Directx and i still run into the same problem. ANy and all help is greatly appreciated.
C2D E6400
2 GB PC 533
Sapphire x1950gt 256 MB
SB Live!
Abit AB9 motherboard
XP Pro SP2
THe problem I have is that when i play Two worlds, after a few minutes the screen goes black and then the computer resets. After the reboot i get a message from the OS saying that there was a loop error in the video card 100000EA.
I ran the analyzer on the minidump and this is what it came up with.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini091407-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Sep 14 18:39:10.265 2007 (GMT-7)
System Uptime: 0 days 0:13:08.842
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {87184da8, 88f19b58, bace3cbc, 1}
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
Probably caused by : ati2mtag.sys ( ati2mtag+12df93 )
Followup: MachineOwner
---------
0: 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: 87184da8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 88f19b58, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bace3cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: 87184da8
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 2
BUGCHECK_STR: 0xEA
PROCESS_NAME: TwoWorlds.exe
LAST_CONTROL_TRANSFER: from b9b9ff93 to 8052ab42
STACK_TEXT:
aab1d698 b9b9ff93 baa18e40 b9ba01e9 baa18000 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
aab1d6bc b9ba03b1 89899dd0 00000390 b9bd877a ati2mtag+0x12df93
aab1d740 b9ba2764 aab1d758 00000000 baa32ca6 ati2mtag+0x12e3b1
aab1d768 b9ba2b61 89899dd0 aab1d798 89899dd0 ati2mtag+0x130764
aab1d7a8 b9ba2bf1 11010000 89899ec0 00000200 ati2mtag+0x130b61
aab1d7d8 b9a7b905 e5ab2680 89892350 89892350 ati2mtag+0x130bf1
aab1d7ec b9a7cc73 89892350 aab1d990 89892350 ati2mtag+0x9905
aab1d804 bfa3c86f 89892350 89892350 aab1d828 ati2mtag+0xac73
aab1d808 89892350 89892350 aab1d828 aab1d9f8 ati2cqag+0x2286f
aab1d80c 89892350 aab1d828 aab1d9f8 e2400000 0x89892350
aab1d810 aab1d828 aab1d9f8 e2400000 00011000 0x89892350
aab1d814 aab1d9f8 e2400000 00011000 7fffffff 0xaab1d828
aab1d828 aab1d830 00000160 00007e00 0c000000 0xaab1d9f8
aab1d82c 00000000 00007e00 0c000000 066b6ae0 0xaab1d830
STACK_COMMAND: .thread 0xffffffff87184da8 ; kb
FOLLOWUP_IP:
ati2mtag+12df93
b9b9ff93 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ati2mtag+12df93
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46cb9a6a
FAILURE_BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_08_21
BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_08_21
Followup: MachineOwner
---------
I have tried to reinstall the newest ATI drivers as well as the latest Directx and i still run into the same problem. ANy and all help is greatly appreciated.
