Sign in with
Sign up | Sign in
Your question

Ati2dvag display driver has stopped working

Last response: in Graphics & Displays
Share
February 9, 2012 2:43:27 AM

I have had a continue, yet very random video issue for years and with two different video cards now. The previous was an Nvidea 7900GT. The new card is an AMD 6850
It likely the mother board but I was never able to to really know.

Today it happened again.
Order of events:
1. Was on Amazon using firefox. This was the only thing running.
2. I closed the browser and ever icon on the desk top, the task bar, and the cursor had vertical lines spaces a 1/2" apart running though them. The lines are shimmering colors. But only a pixel wide.
3. screen goes black for a minute
4. The threads title comes up as an error when the display comes back and windows is now in safe mode at 640x480.

Any help is much appreciated.
I am about to build another PC but I would really like to figure out the issue on this one too.


Window did make a log dmp file of this.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Craig Wiley\Local Settings\temp\WER782c.dir00\Mini020812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 8 22:13:29.156 2012 (UTC - 5:00)
System Uptime: 0 days 3:51:31.953
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image ati2dvag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {8970c928, 88e7bad0, 88bf5920, 1}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ati2dvag.dll ( ati2dvag+338f9 )

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



Any help is much appreciated.
I am about to build another PC but I would really like to figure out the issue on this one too.
a b U Graphics card
February 9, 2012 6:22:55 AM

Firstly, it's not just the ATI driver problem, that is one of them.
From the log, it seems that you have used this very HDD in an older rig and then reused it without formatting the OS, just installed it and let the drivers be updated or refreshed.
The first step here now is to Format it after you have cleaned out the rig of all the dust and grit that may have accumulated within.
Then install the latest Drivers from the 6850 from the AMD site.
Everything will work out fine.
Too many corrupt windows files are causing the drivers to get corrupt too.

m
0
l
February 9, 2012 10:25:21 AM

So just F-disk and reload operating system?
m
0
l
a b U Graphics card
February 9, 2012 10:31:10 AM

Yup. Not Fdisk as in the dos command, but Format the Disk and install the OS.
m
0
l
!