Guru3D.com Forums

Go Back   Guru3D.com Forums > Videocards > Videocards - AMD - ATI Drivers Section
Videocards - AMD - ATI Drivers Section In this section you can discuss everything Catalyst related. AMD Catalyst drivers are for all AMD ATI based graphics cards. This is also the place to discuss modified Catalyst drivers.


Reply
 
Thread Tools Display Modes
X1950XTX CF Win7 drivers?
Old
  (#1)
vf
Maha Guru
 
Videocard: *
Processor: *
Mainboard:
Memory:
Soundcard: ProMedia GMX A-2.1
PSU: *
Default X1950XTX CF Win7 drivers? - 01-15-2010, 01:10 | posts: 1,431 | Location: UK

So I was lead to believe 9.3 would work on Windows 7 and then actually finding the drivers fail to install.

I have even tried running the installer under Vista SP2/Vista compatibility modes and still no success.

Quote:
Note: AMD’s DirectX 9 ATI Radeon graphics accelerators are not officially supported under Windows 7. If the user chooses to, they can install the ATI Catalyst Windows Vista graphics driver under Windows 7. Please be aware that none of the new Windows 7 graphics driver (WDDM 1.1) features are supported (as the Windows Vista level graphics driver is limited to WDDM 1.0 level support). Using the ATI Catalyst Windows Vista driver under Windows 7 is not officially supported by AMD, and as such AMD will not provide any form of customer support for users running in this configuration
Quote:
Any customers using a combination of a ATI Radeon™ HD 2000 Series, ATI Radeon™ HD 3000 Series, or ATI Radeon™ HD 4000 Series product with any of the legacy products listed above in a single PC system must use the ATI Catalyst 9.3 or earlier driver. All future ATI Catalyst™ releases made available past the ATI Catalyst™ 9.3 release will not include support for the legacy products listed above or any of the features associated with those legacy products.
What drivers/procedures/alterations will install successfully to Windows 7 32bit and allow me to access the CCC so I can upscale my picture on the HDTV as it's in a somewhat scaled down window at the moment due to the default Microsoft drivers. I guess CrossFire is out of the picture? that I'd have to boot into Vista instead for that or what?...

As I really don't want to buy a new graphics card at the moment. Any experts know how to by pass this? it would be greatly appreciated.

It sounds really stingy reading this. http://forums.amd.com/game/messagevi...hreadid=111437
   
Reply With Quote
 
Old
  (#2)
Exodite
Maha Guru
 
Videocard: Gigabyte 6950 2GB @ Stock
Processor: Intel i7 2600K @ 1.15V
Mainboard: ASUS P8P67 Pro B3
Memory: 8GB Kingston PC10600
Soundcard: Realtek 892
PSU: Seasonic SS-460FL
Default 01-15-2010, 02:03 | posts: 1,652 | Location: Luleå, Sweden

I'm afraid I can't help you with your problem but I'd recommend staying away from the AMD forum if you care about your mental health. Spyre is quite the obnoxious troll for one thing, "moderator" or not.
   
Reply With Quote
Old
  (#3)
vf
Maha Guru
 
Videocard: *
Processor: *
Mainboard:
Memory:
Soundcard: ProMedia GMX A-2.1
PSU: *
Default 01-28-2010, 13:41 | posts: 1,431 | Location: UK

Just followed this up with the working legacy 9.11 set... started getting one or two occasional blue screens at startup last week..., usually happens upon a cold boot up. Sometimes it doesn't happen. Seems to be intermittent.

Quote:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Username\Desktop\012810-33546-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a3c000 PsLoadedModuleList = 0x82b84810
Debug session time: Thu Jan 28 12:24:52.500 2010 (GMT+0)
System Uptime: 0 days 0:00:25.250
************************************************** *******************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
....................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8f42ea58, 807f7670, 0}

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

************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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+ *
************************************************** *******************
************************************************** *******************
* 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+ *
************************************************** *******************
Probably caused by : hardware ( atikmdag+41aa58 )

Followup: MachineOwner
---------
   
Reply With Quote
Old
  (#4)
fagoatse
Member Guru
 
Videocard: nvidia
Processor: haswell
Mainboard:
Memory:
Soundcard:
PSU: 650W
Default 01-28-2010, 18:50 | posts: 122

There's a certain guy doing modded drivers but I'm not sure if I'm allowed to talk about it.
google **************
   
Reply With Quote
 
Old
  (#5)
vf
Maha Guru
 
Videocard: *
Processor: *
Mainboard:
Memory:
Soundcard: ProMedia GMX A-2.1
PSU: *
Default 01-29-2010, 01:45 | posts: 1,431 | Location: UK

Why not?

"KillerSneak: So they are here. I will be working on them this weekend."

I must ask him if he can do anything for the X1950XTX's or if he'll only be modding them for the latest cards.
   
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



Powered by vBulletin®
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
vBulletin Skin developed by: vBStyles.com
Copyright (c) 1995-2014, All Rights Reserved. The Guru of 3D, the Hardware Guru, and 3D Guru are trademarks owned by Hilbert Hagedoorn.