Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Bsod After Updating Catalyst Drivers


  • Please log in to reply
15 replies to this topic

#1 FrackinToaster

FrackinToaster

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 07 June 2008 - 02:15 PM

Hello, thanks for all who have posted some very useful info for the uninitiated!

My specs:

Cpu - AMD Athlon XP 2600+ 1.9Ghz
MoBo - Gigabyte GA-7N400-L
GPU - ATI Radeon X1650 AGP 512mb
Ram - 1024MB DDR 400
OS - Windows XP Home w/SP3
Optical Drives - LG CDRW/Sony DVDRW
Hard Drives - WD 80GB/Samsung 160GB

My problem:

I updated the drivers for my gpu to Catalyst 8.5 a few weeks back, and after this my PC would restart on me when playing any game I own. This happens immediately after a game is loaded, and happened with Half-Life 2, Oblivion, Fear, etc. An attempt to roll back the gpu driver did not fix the issue, though I did have success when I chose to load a system restore point from the previous month. However, after this a Catalyst Control Centre error would appear on boot-up every time. This, along with general clutter after five years, prompted a formatting of my system. Following the format, I've installed/updated every driver that I know of, but I'm still experiencing a restart after trying to load any 3D game. After turning off auto restarts, I received this error code in a BSOD:

"STOP: 0x0000008E (0X000001D, 0XE34067C7, 0XA9A3F88C, 0X00000000)

After seeing the link for debug analysis and installing the debugger, I got this:


Loading Dump File [C:\WINDOWS\Minidump\Mini060708-01.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 Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jun 7 07:25:33.718 2008 (GMT-7)
System Uptime: 0 days 0:05:05.324
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, e34067c7, a9a3f88c, 0}

Probably caused by : ati3duag.dll ( ati3duag+1184f8 )

Followup: MachineOwner
---------



Followed by this after using !analyze -v:



Loading Dump File [C:\WINDOWS\Minidump\Mini060708-01.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 Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jun 7 07:25:33.718 2008 (GMT-7)
System Uptime: 0 days 0:05:05.324
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, e34067c7, a9a3f88c, 0}

Probably caused by : ati3duag.dll ( ati3duag+1184f8 )

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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: e34067c7, The address that the exception occurred at
Arg3: a9a3f88c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


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

FAULTING_IP:
+ffffffffe34067c7
e34067c7 f20fd6d3 movdq2q mm2,xmm3

TRAP_FRAME: a9a3f88c -- (.trap 0xffffffffa9a3f88c)
ErrCode = 00000000
eax=e3d0d210 ebx=e2d66040 ecx=00000035 edx=00000100 esi=e2db44c0 edi=a9a3f99c
eip=e34067c7 esp=a9a3f900 ebp=a9a3f90c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
e34067c7 f20fd6d3 movdq2q mm2,xmm3
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: hl2.exe

LAST_CONTROL_TRANSFER: from bfc604f8 to e34067c7

FAILED_INSTRUCTION_ADDRESS:
+ffffffffe34067c7
e34067c7 f20fd6d3 movdq2q mm2,xmm3

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a9a3f90c bfc604f8 e2db44c0 e2d3f41c bfc60512 0xe34067c7
a9a3f910 e2db44c0 e2d3f41c bfc60512 e2d3f428 ati3duag+0x1184f8
a9a3f914 e2d3f41c bfc60512 e2d3f428 e2d3f2e0 0xe2db44c0
a9a3f918 bfc60512 e2d3f428 e2d3f2e0 00000000 0xe2d3f41c
a9a3f91c e2d3f428 e2d3f2e0 00000000 00000000 ati3duag+0x118512
a9a3f920 e2d3f2e0 00000000 00000000 e2db44c0 0xe2d3f428
a9a3f924 00000000 00000000 e2db44c0 e2d3f2e0 0xe2d3f2e0


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+1184f8
bfc604f8 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ati3duag+1184f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 48286321

FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag+1184f8

BUCKET_ID: 0x8E_BAD_IP_ati3duag+1184f8

Followup: MachineOwner
---------


I would really like to be able to maintain updated drivers for my system, so if any helpful folks could share some wisdom, it would be much appreciated. Thanks in advance!

BC AdBot (Login to Remove)

 


#2 tswsl1989

tswsl1989

  • Members
  • 260 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cymru/Wales
  • Local time:10:34 AM

Posted 07 June 2008 - 02:53 PM

Odd to see this in a generally released driver.
Two suggestions:
1) Uninstall all ATi Drivers and reboot. Try downloading and installing an older, stable version if it's still available
2) Reboot, and keep hitting F8 until you get to the Advanced Options menu. Choose Debugging Mode. Let the BSOD happen and analyze the dump as above. See if it's any different (if so, post it here)
Tom

Tswsl1989
Duct tape is like the force. It has a light side, a dark side, and it holds the universe together

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 55,552 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:34 AM

Posted 07 June 2008 - 03:59 PM

I also second uninstalling everything connected with ATI, drivers and catalyst software. The uninstall utility in Add/Remove Programs should reflect a utility that will uninstall everything at once, with a minimum of effort.

Then I suggest just using the drivers which shipped with your ATI card...don't worry about updating these if the system and the card work properly.

Louis

#4 snooker

snooker

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:04:34 AM

Posted 07 June 2008 - 05:22 PM

Hi , Or you can try just to install the driver itself without the catalyst software . I never install catalyst software

#5 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 07 June 2008 - 07:40 PM

Hi again, and thanks for the suggestions. I did use the ATI uninstall utility to remove all ATI-related programs, then installed an older driver (8.471.0.0 from 02/2008). Running Half Life 2 got another BSOD, this time with:

***STOP: 0x0000008E (0XC000001D, 0XE34D77C7, 0XA9C7D88C, 0X00000000)

After a debug report:


Microsoft Windows Debugger Version 6.9.0003.113 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini060708-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 Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jun 7 17:22:45.421 2008 (GMT-7)
System Uptime: 0 days 0:05:12.027
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, e34d77c7, a9c7d88c, 0}

Probably caused by : ati3duag.dll ( ati3duag+116508 )

Followup: MachineOwner
---------



After a !analyze -v:

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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: e34d77c7, The address that the exception occurred at
Arg3: a9c7d88c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


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

FAULTING_IP:
+ffffffffe34d77c7
e34d77c7 f20fd6d3 movdq2q mm2,xmm3

TRAP_FRAME: a9c7d88c -- (.trap 0xffffffffa9c7d88c)
ErrCode = 00000000
eax=e3c8d210 ebx=e2e44040 ecx=00000035 edx=00000100 esi=e2e924c0 edi=a9c7d99c
eip=e34d77c7 esp=a9c7d900 ebp=a9c7d90c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
e34d77c7 f20fd6d3 movdq2q mm2,xmm3
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: hl2.exe

LAST_CONTROL_TRANSFER: from bf292508 to e34d77c7

FAILED_INSTRUCTION_ADDRESS:
+ffffffffe34d77c7
e34d77c7 f20fd6d3 movdq2q mm2,xmm3

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a9c7d90c bf292508 e2e924c0 e2e27418 bf292522 0xe34d77c7
a9c7d910 e2e924c0 e2e27418 bf292522 e2e27424 ati3duag+0x116508
a9c7d914 e2e27418 bf292522 e2e27424 e2e272e0 0xe2e924c0
a9c7d918 bf292522 e2e27424 e2e272e0 a9c70000 0xe2e27418
a9c7d91c e2e27424 e2e272e0 a9c70000 86ace000 ati3duag+0x116522
a9c7d920 e2e272e0 a9c70000 86ace000 e2e924c0 0xe2e27424
a9c7d924 a9c70000 86ace000 e2e924c0 e2e272e0 0xe2e272e0
a9c7d928 86ace000 e2e924c0 e2e272e0 bf292f9d 0xa9c70000
a9c7d92c e2e924c0 e2e272e0 bf292f9d e2e272e0 0x86ace000
a9c7d930 e2e272e0 bf292f9d e2e272e0 bf2924e0 0xe2e924c0
a9c7d934 bf292f9d e2e272e0 bf2924e0 0000000c 0xe2e272e0
a9c7d938 e2e272e0 bf2924e0 0000000c 00000000 ati3duag+0x116f9d
a9c7d93c bf2924e0 0000000c 00000000 e2e272e0 0xe2e272e0
a9c7d940 00000000 00000000 e2e272e0 e568b040 ati3duag+0x1164e0


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+116508
bf292508 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ati3duag+116508

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 47c37e37

FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag+116508

BUCKET_ID: 0x8E_BAD_IP_ati3duag+116508

Followup: MachineOwner
---------


I also did a bit of digging into the "ati3duag.dll" that seems to be a troublemaker, and found this link (it's a bit of a lengthy read):

http://www.ngohq.com/graphic-cards/11589-a...l-death-et.html

I tried to install the two critical updates he refers to, but Windows won't allow it, as it says SP3 is newer than these updates. I will try F8ing on boot-up...but any other suggestions first?
Much thanks once again!

Edited by FrackinToaster, 07 June 2008 - 07:41 PM.


#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,552 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:34 AM

Posted 07 June 2008 - 08:21 PM

The ati3duag.dll should be part of your WDM driver package (it is on my AIW 9600 installed on this system).

I would have to guess that it's corrupt or missing...and I would try to reinstall it, after checking the status of the ATI drivers in Device Manager.

I don't know what else to tell you, sorry :thumbsup:.

FWIW: I do not allow WinUpdate to install ATI driver updates on my systems. There was one a few months ago that was classified as a critical update...at the time, I was experimenting with autoupdate...and it downloaded, installed, and immediately knocked out my capture capabilities.

I thought that it was pretty strange that an ATI driver update could be classified as a critical update....but it happened.

Louis

#7 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 07 June 2008 - 08:30 PM

Thanks hamluis, I'll give the .dll file a download and see what happens. Is there a program needed to run it after it's downloaded, or do .dll files generally install as per an .exe file?

#8 snooker

snooker

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:04:34 AM

Posted 07 June 2008 - 10:42 PM

Hi , I just place the dll file here >>> C:\WINDOWS\system32

You can get from site below , its the top one

http://www.dlldll.com/dllfiles/A_page28.html

#9 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 08 June 2008 - 02:54 AM

Thanks snooker, I'll give it a shot :thumbsup:

#10 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 08 June 2008 - 12:17 PM

Hello again, I tried to place the ati3duag.dll file in Windows\System32, but it gave an error message saying that it being used by another program or person. I didn't have any programs running at the time, unless the act of being within the Windows Explorer is what it's referencing. I'm not sure what else to try really...anyone have any last suggestions?

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,552 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:34 AM

Posted 08 June 2008 - 01:00 PM

I did not mean to try to install that one .dll...I was referring to the WDM drivers for that card.

That .dll is just a minor part of the WDM package. It may itself be the problem, it may be the problem in conjunction with other files that belong to the WDM drivers.

Louis

#12 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 08 June 2008 - 02:44 PM

Hi once again, sorry for the confusion hamluis, I was trying what snooker mentioned about getting that one .dll file that seemed to be the culprit. As noted, it didn't do the trick. I then tried your suggestion, uninstalled all things ATI, fresh installed with the disc that came with my card, and so far all seems well (tested with Half Life 2)! The driver details indicate that they're from August of 2006 (v.8.282.0.0), and I'm a bit concerned that playing more recent games might cause other problems due to the age of the drivers. What do you do when this situation arises? Thanks again for all the help folks!

#13 snooker

snooker

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:04:34 AM

Posted 08 June 2008 - 03:57 PM

What do you do when this situation arises? Thanks again for all the help folks!

Have you try to just install the driver itself without the catalyst software ? The catalyst software usually does cause problems with others to

#14 hamluis

hamluis

    Moderator


  • Moderator
  • 55,552 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:34 AM

Posted 08 June 2008 - 04:17 PM

I wouldn't worry about problems with games...until they occur :thumbsup:.

If they do occur, then what I would do is go online and check out what other users with that card...do when confronted with such. Omega drivers are one alternative many seem to prefer.

I now treat ATI video drivers in the same manner that I treat the idea of BIOS updates...if the function works, there is no reason at all to update it and take the chance of screwing things up. This attitude has been learned from trying to deal with ATIs approach to drivers (one size fits all).

Not to be cynical (or overly cynical) but...you have to remember that ATI turns out products like hotcakes and have no vested interest in producing drivers which allow yesterday's cards...to compete with today's or tomorrow's sales.

As for the CCC, I've never figured out its purpose...and sometimes I install it, sometimes I don't. Depends on how much time I want to spend trying to get my cards to work properly :flowers:.

Louis

#15 FrackinToaster

FrackinToaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:34 AM

Posted 08 June 2008 - 05:37 PM

Hey again, just wanted to drop a quick response. I've now tried a couple more games and all seems to be well. When installing the drivers on the disc that came with my card, CCC was installed without asking me, but it doesn't seem to be causing any issues right now. It's still weird and a bit frustrating that everything was fine using drivers that were released later than the ones on the disc until I tried the most recent ones, but I can appreciate the "ain't broke, don't fix" perspective. In any case, just wanted to sincerely thank all who offered help and advice, and I hope I can return the favour some day. Game on!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users