Tonight I played a game several times and measured the time it took for my XPS to lock up or corrupt, in an effort to find any kind of consistency in the crashing. While I was doing this, I discovered the location of the log files that Windows generates after a crash. Here are my test results as well as the contents of one of these log files (test #10):
------
Notes:
------
-Installed Midnight Club II Demo (available for free @ http://www.fileshack.com)
-Set to 1920 x 1200 resolution
-Hyperthreading enabled in all tests
-Did not use Powerstrip, using factory-installed Windows XP and Dell ATI drivers from 02/26/04
-Selected Circuit race (puts a timer on the screen in upper left hand corner)
-Didn't touch anything, just let the car sit stationary as the timer counted up
-Ran the game ten times and each time the game froze (requiring a hard shutdown) or corrupted (requiring a reboot)
-Windows generated a log file each time the game locked up - indicates that the display driver got stuck in an infinite loop
-Log files located in C:\Windows\LogFiles\Watchdog\ (readable in Notepad)
-All of the log files contain the same EventType: OxEA - Thread Stuck in Device Driver. Maybe this is why disabling Hyperthreading works as a fix for some people?
-Next step: Disable Hyperthreading and rerun test to see if freeze or graphics corruption occurs
---------------------------------------
Test Results: (time in minutes:seconds)
---------------------------------------
1) 06:22 - freeze
2) 11:33 - corruption
3) 06:11 - corruption
4) 12:44 - corruption
5) 07:31 - freeze
6) 28:26 - freeze
7) 45:23 - freeze
8) 09:10 - corruption
9) 04:26 - freeze
10) 44:39 - freeze
------------------
Log file contents:
------------------
//
// Watchdog Event Log File
//
LogType: Watchdog
Created: 2004-03-13 21:31:18
TimeZone: 360 - Central Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver
//
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
//
EaRecovery: 1
ShutdownCount: 79
Shutdown: 0
EventCount: 8
BreakCount: 8
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: ati2dvag
EventFlag: 1
DeviceClass: Display
DeviceDescription: ATI MOBILITY RADEON 9700
HardwareID: PCI\VEN_1002&DEV_4E50&SUBSYS_017C1028&REV_00
Manufacturer: ATI Technologies Inc.
DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A18FC 0006000E 000A18FC 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: ATI Technologies Inc.
DriverFileDescription: ATI Radeon WindowsNT Display Driver
DriverFileVersion: 6.14.10.6396
DriverInternalName: ati2dvag.dll
DriverLegalCopyright: Copyright (C) 1998-2002 ATI Technologies Inc.
DriverOriginalFilename: ati2dvag.dll
DriverProductName: ATI Radeon Family
DriverProductVersion: 5.2.3790.2
------
Notes:
------
-Installed Midnight Club II Demo (available for free @ http://www.fileshack.com)
-Set to 1920 x 1200 resolution
-Hyperthreading enabled in all tests
-Did not use Powerstrip, using factory-installed Windows XP and Dell ATI drivers from 02/26/04
-Selected Circuit race (puts a timer on the screen in upper left hand corner)
-Didn't touch anything, just let the car sit stationary as the timer counted up
-Ran the game ten times and each time the game froze (requiring a hard shutdown) or corrupted (requiring a reboot)
-Windows generated a log file each time the game locked up - indicates that the display driver got stuck in an infinite loop
-Log files located in C:\Windows\LogFiles\Watchdog\ (readable in Notepad)
-All of the log files contain the same EventType: OxEA - Thread Stuck in Device Driver. Maybe this is why disabling Hyperthreading works as a fix for some people?
-Next step: Disable Hyperthreading and rerun test to see if freeze or graphics corruption occurs
---------------------------------------
Test Results: (time in minutes:seconds)
---------------------------------------
1) 06:22 - freeze
2) 11:33 - corruption
3) 06:11 - corruption
4) 12:44 - corruption
5) 07:31 - freeze
6) 28:26 - freeze
7) 45:23 - freeze
8) 09:10 - corruption
9) 04:26 - freeze
10) 44:39 - freeze
------------------
Log file contents:
------------------
//
// Watchdog Event Log File
//
LogType: Watchdog
Created: 2004-03-13 21:31:18
TimeZone: 360 - Central Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver
//
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
//
EaRecovery: 1
ShutdownCount: 79
Shutdown: 0
EventCount: 8
BreakCount: 8
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: ati2dvag
EventFlag: 1
DeviceClass: Display
DeviceDescription: ATI MOBILITY RADEON 9700
HardwareID: PCI\VEN_1002&DEV_4E50&SUBSYS_017C1028&REV_00
Manufacturer: ATI Technologies Inc.
DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A18FC 0006000E 000A18FC 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: ATI Technologies Inc.
DriverFileDescription: ATI Radeon WindowsNT Display Driver
DriverFileVersion: 6.14.10.6396
DriverInternalName: ati2dvag.dll
DriverLegalCopyright: Copyright (C) 1998-2002 ATI Technologies Inc.
DriverOriginalFilename: ati2dvag.dll
DriverProductName: ATI Radeon Family
DriverProductVersion: 5.2.3790.2






.


Anxiously awaiting! 