Author Topic: Graphics card driver keeps failing (Read 17016 times)

Druby-chan · « **on:** November 22, 2010, 11:49:39 AM »

Hello!

I am running Windows XP Home. My graphics card is a Radion 9000 and it is fairly old. Lately I have been having a problem with the screen suddenly flashing off to black, then coming back competely scrambled, and then if I'm LUCKY it'll flash back again to usable, but if I have to scroll it shows up in a sort of wave from the top of the screen to the bottom, and it is PAINFULLY slow at changing from one window/picture/text paragraph to the next. It seems to sort itself out when I reboot and it's pot luck when it happens. After rebooting from this problem I generally get a message saying that 'the system has recovered from a serious error and would I like to send an error report'..

After a bit of research I believe the problem to be my driver, although I am fairly uncertain that this is actually what is wrong. Any help would be appreciated, and feel free to ask questions. I'll try and answer them as best as possible.

ALSO! (and I dunno if I can post this here too.. $:-\$ but here' goes)

My computer is running SO SLOWLY. I have no idea if this is because of the driver issues, or if it is just that it's gotton OLD.. but it never used to be this way. I run my virus scanner once a week and I run Malwarebytes around once a week too, along with Uniblue Registry cleaner. Help on this is needed too, but not as important.

Thank you in advance for any help!

Allan · « **Reply #1 on:** November 22, 2010, 11:54:49 AM »

1) Registry cleaners CAUSE problems, they don't cure them.
2) Drivers have nothing to do with your problem. Either a piece of hardware is failing, an app is conflicting, or your registry cleaner screwed up something.

First let's find out if the reboot is caused by a blue screen error. Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Next, you can boot to safe mode and see if the system runs smoothly or if there is still a problem there.

Then you can run diagnostics on all hardware components (ram, hd, etc).

Druby-chan · « **Reply #2 on:** November 22, 2010, 12:09:19 PM »

==================================================
Dump File : Mini112210-01.dmp
Crash Time : 22/11/2010 16:21:15
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x85f1c7f8
Parameter 2 : 0x86d66f60
Parameter 3 : 0x86b370d8
Parameter 4 : 0x00000001
Caused By Driver : ati2cqag.dll
Caused By Address : ati2cqag.dll+14961
File Description : Central Memory Manager / Queue Server Module
Product Name : ATI Radeon Family
Company : ATI Technologies Inc.
File Version : 6.14.10.0310
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112210-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini110710-01.dmp
Crash Time : 07/11/2010 14:43:29
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x860b0bc8
Parameter 2 : 0x86b3fec8
Parameter 3 : 0xf78c2cbc
Parameter 4 : 0x00000001
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+a67
File Description : Watchdog Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini110710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101910-01.dmp
Crash Time : 19/10/2010 17:17:01
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x86246a00
Parameter 2 : 0x86b41280
Parameter 3 : 0x86ebd848
Parameter 4 : 0x00000001
Caused By Driver : ati2cqag.dll
Caused By Address : ati2cqag.dll+16c6a
File Description : Central Memory Manager / Queue Server Module
Product Name : ATI Radeon Family
Company : ATI Technologies Inc.
File Version : 6.14.10.0310
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101910-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini092810-01.dmp
Crash Time : 28/09/2010 22:39:39
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x86b32da8
Parameter 2 : 0x85f5f3c0
Parameter 3 : 0xf78b6cbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+2f63
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini092810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091810-01.dmp
Crash Time : 18/09/2010 06:53:38
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x859f22d0
Parameter 2 : 0x86b406f0
Parameter 3 : 0x86c94728
Parameter 4 : 0x00000001
Caused By Driver : ati2cqag.dll
Caused By Address : ati2cqag.dll+16c71
File Description : Central Memory Manager / Queue Server Module
Product Name : ATI Radeon Family
Company : ATI Technologies Inc.
File Version : 6.14.10.0310
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091210-03.dmp
Crash Time : 12/09/2010 09:54:13
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x86916bc8
Parameter 2 : 0x86ad3008
Parameter 3 : 0xf78b6cbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+2f63
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091210-03.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091210-02.dmp
Crash Time : 12/09/2010 09:49:07
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x85bb3bd0
Parameter 2 : 0x86aee8e0
Parameter 3 : 0xf78b6cbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+2f63
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091210-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091210-01.dmp
Crash Time : 12/09/2010 09:46:36
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xaeb0e178
Parameter 2 : 0x00000000
Parameter 3 : 0x805717bd
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+9a7bd
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.3670 (xpsp_sp2_gdr.100216-1441)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091210-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini082310-01.dmp
Crash Time : 23/08/2010 05:51:03
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x86b34020
Parameter 2 : 0x86b252f8
Parameter 3 : 0xf78bacbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+2f63
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082310-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini030210-01.dmp
Crash Time : 02/03/2010 09:09:05
Bug Check String : SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPRO PER_DRIVER_UNLOAD
Bug Check Code : 0x100000d4
Parameter 1 : 0xf28a0f38
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000001
Parameter 4 : 0x804e164e
Caused By Driver : HSF_CNXT.sys
Caused By Address : HSF_CNXT.sys+9569e
File Description : HSF_CNXT driver
Product Name : SoftK56 Modem Driver
Company : Conexant Systems, Inc.
File Version : 7.04.05 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini030210-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

It seems to be running smoothly at the moment, and has been for the past few hours.. but who is to say it will do so tomorrow? There's the log.

Thanks!

Allan · « **Reply #3 on:** November 22, 2010, 12:20:13 PM »

Wow, lots of issues. The graphics card may be on the way out though. Read this: http://support.microsoft.com/kb/293078

Other errors relate to other items. If the problems recur I'd like you to do a clean boot or try safe mode, either one.

Druby-chan · « **Reply #4 on:** November 22, 2010, 12:34:44 PM »

So what to do about the problems then? I came here for some fix answers, lol.

I am currently in safe mode as rebooted and had same problem.. Anything you want me to do while I'm here?

Allan · « **Reply #5 on:** November 22, 2010, 12:48:25 PM »

Yes, wait and see if the system fails.

Druby-chan · « **Reply #6 on:** November 22, 2010, 12:49:31 PM »

Quote from: Allan on November 22, 2010, 12:48:25 PM

Yes, wait and see if the system fails.

LMAO

I think I'll be waiting a while then.

Computer_Commando · « **Reply #7 on:** November 22, 2010, 01:28:04 PM »

Quote from: Allan on November 22, 2010, 12:20:13 PM

Wow, lots of issues. The graphics card may be on the way out though. Read this: http://support.microsoft.com/kb/293078

Other errors relate to other items. If the problems recur I'd like you to do a clean boot or try safe mode, either one.

Method 4: Replace your video card (from: http://support.microsoft.com/kb/293078)
It looks like ATI card hardware errors are locking up the PCI Bus, hence the WatchDog Timer & Modem card errors. It's also possible that the Modem card has gone bad, if you don't use it anymore, remove it to see what happens.

Druby-chan · « **Reply #8 on:** November 22, 2010, 03:03:29 PM »

Okay, I can see if removing the onboard modem helps, but so far in safe mode the problem has not recurred. I've been itching to clean out the inside of my poor computer for a while. Now I've got an excuse to do it. 8D

Thanks Commando. *thumbs up*

Allan · « **Reply #9 on:** November 22, 2010, 03:06:13 PM »

If the system hasn't rebooted from safe mode please try this: open msconfig and choose "selective startup" (disable everything from loading) and reboot. See if the system remains stable. If it does, it may indeed be a software issue.

patio · « **Reply #10 on:** November 22, 2010, 04:00:33 PM »

Flakey PSU could also be a suspect here...
Swapping it out with a borrowed replacement will cost nothing...

Allan · « **Reply #11 on:** November 22, 2010, 04:02:41 PM »

I sincerely doubt that would have generated those specific blue screen error messages patio. Also, a bad ps wouldn't differentiate between safe mode and regular mode.

Druby-chan · « **Reply #12 on:** November 23, 2010, 12:52:02 AM »

Right. Rebooted as you said to, but I've got to do school runs and such today so I can't sit here and chat. I'll be about this afternoon though. We'll see how it goes...

BC_Programmer · « **Reply #13 on:** November 23, 2010, 02:10:34 AM »

I say video card failure.

Allan · « **Reply #14 on:** November 23, 2010, 05:47:19 AM »

Quote from: BC_Programmer on November 23, 2010, 02:10:34 AM

I say video card failure.

And I agree, as I said above. But ruling out software first isn't a big deal so why not try?

Computer Hope Forum

News:

Author Topic: Graphics card driver keeps failing (Read 17016 times)

Druby-chan

Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing

Druby-chan

Re: Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing

Druby-chan

Re: Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing

Druby-chan

Re: Graphics card driver keeps failing

Computer_Commando

Re: Graphics card driver keeps failing

Druby-chan

Re: Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing

patio

Re: Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing

Druby-chan

Re: Graphics card driver keeps failing

BC_Programmer

Re: Graphics card driver keeps failing

Allan

Re: Graphics card driver keeps failing