Unsolved

This post is more than 5 years old

Closed

2 Posts

10151

February 28th, 2004 15:00

"infinite loop" ?

ATI Mobility Radeon in an inspiron 600m, I get the blue screen of death, and then when I manage to start up, windows sends me to this file:

 

//
// Watchdog Event Log File
//

LogType: Watchdog
Created: 2004-02-28 12:19:14
TimeZone: 300 - Eastern 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: 149
Shutdown: 0
EventCount: 11
BreakCount: 11
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: ati2dvag
EventFlag: 1
DeviceClass: Display
DeviceDescription: MOBILITY RADEON 9000
HardwareID: PCI\VEN_1002&DEV_4C66&SUBSYS_011E1028&REV_09
Manufacturer: ATI Technologies Inc.
DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A18E3 0006000E 000A18E3 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: ATI Technologies Inc.
DriverFileDescription: ATI Radeon WindowsNT Display Driver
DriverFileVersion: 6.14.10.6371
DriverInternalName: ati2dvag.dll
DriverLegalCopyright: Copyright (C) 1998-2002 ATI Technologies Inc.
DriverOriginalFilename: ati2dvag.dll
DriverProductName: ATI Radeon Family
DriverProductVersion: 5.2.3763.0

 

This recently started happening, along with the computer just stopping and the screen showing funny colors. I tried upgrading the drivers for the video card, didn't work.

5 Posts

February 28th, 2004 18:00

Where did you get the driver from?

2 Posts

February 28th, 2004 18:00

Dell's support site. It's the right driver.

5 Posts

February 28th, 2004 19:00

did u select the right OS for ur driver

February 28th, 2004 20:00

I would uninstall the driver and reinstall. After you uninstall, you might want to use a cleaning utility to get rid of all traces of the old driver.

35 Posts

March 22nd, 2004 14:00

Isn't there a better way to definitively differentiate a problem between the video card 
and the Operating System, without having to reformat the disk and reinstall the Operating System ?


ATI Radeon 9000 video errors ; infinite loop
18-NOV-2003:  received Inspiron 8600 notebook
27-NOV-2003:  getting errors indicating an infinite loop in the ATI video driver.
16-FEB-2004:  replaced motherboard;  video errors persist.
17-FEB-2004:  replaced motherboard again;  video errors persist.
18-FEB-2004:  replaced video card;  video errors persist.
22-MAR-2004:  upgraded BIOS and video drivers; video errors persist.
23-MAR-2004:  ran debugger on crash-dump file. It indicates a problem in the video driver.
Uninstalled and reinstalled the video driver,
upgraded the video driver ( currently at the latest version: A04 ),
upgraded the system BIOS ( currently at A05 ),
disabled POWERPLAY(tm),  and the problem persists .
There are no other errors or indications of an OS problem.
Still, DELL tech-support recommends reformatting the hard-disk and reinstalling everything again.
I see that others have this problem. 
It seems more likely that the video card or video driver are defective.
Isn't there a better way to definitively differentiate a problem between the video card 
and the Operating System, without having to reformat the disk and reinstall the Operating System ?

It seems too often that DELL's solution is to reformat and reinstall the OS.
23-MAR-2004:  Formatted the drive and reinstalled the OS, and the problem persists.
24-MAR-2004:  Downloaded and installed Radeon driver from www.omegacorner.com and problem persists.
                         Diagnostics indicate no errors.
24-MAR-2004:  called DELL again; replacement parts ordered (motherboard, video card, CPU)

UPDATE:   25-Mar-2004:
                   After replacing the motherboard twice, video card twice,
                   and the problem persisted, the Intel Pentium Mobile CPU
                   was then replaced, which resolved the problem.

 

Message Edited by danielss on 06-15-2004 04:27 PM

0 events found

No Events found!

Top