9.7 rc3 (8.63)

[rflair]

DriverVer=06/10/2009, 8.630.0.0000

ONLY XP x86/x64 at this time, will update when/if Vista version becomes available.

XP x86/x64

http://www.megaupload.com/?d=KYXNVKC8

P.S. Could somone post a pic of the CCC, my XP rig is in use right now so I can not do it.

[badsykes]

if i marry rflair i will get life support for my ati card
Thx again..Always loving to beta test stuff..

[{0}Salamander{0}]

9.6 produced significant glitching in Google Earth, rolling back to 9.5 solved this.

Wonder if 9.7 has cured these issues?

[=Mustang=]

rflair does it yet again, thanks! downloading

[badsykes]

Originally Posted by {0}Salamander{0}

9.6 produced significant glitching in Google Earth, rolling back to 9.5 solved this.

Wonder if 9.7 has cured these issues?

your wonders will only be cured by your hands...

[=Mustang=]

Thank goodness, this beta fixes my corrupt text with DCS Black Shark main menu and options screens!

No problems installing on my XP SP3, heres what ATT shows under System Information

[badsykes]

Originally Posted by =Mustang=

Thank goodness, this beta fixes my corrupt text with DCS Black Shark main menu and options screens!

No problems installing on my XP SP3, heres what ATT shows under System Information

You are lucky that actually is working on your agp rig.Usually they release a hotfix for this cards but i suppose the hotfix is just some added cards in a list and you added them yourself?

[Thr0tt]

Originally Posted by badsykes

You are lucky that actually is working on your agp rig.Usually they release a hotfix for this cards but i suppose the hotfix is just some added cards in a list and you added them yourself?

The AGP hotfix are for cards that don't get recognised by the normal driver mainly so if you have no issues installing the normal set then most will also work.

[Burn]

HDR fallout 3 fix ?? .... please ...

[=Mustang=]

Originally Posted by badsykes

You are lucky that actually is working on your agp rig.Usually they release a hotfix for this cards but i suppose the hotfix is just some added cards in a list and you added them yourself?

Never had a problem with any of the drivers with my 3850, all i do is add the card info to the .inf file and it all works

[{0}Salamander{0}]

These drivers do indeed fix the Google Earth glitching.

[Tritonal]

This fixes the google earth glitch for me too, thanks.

[kn00tcn]

google earth has opengl or d3d options if i remember right, do you all use it with opengl?

[Tom|Nbk]

Originally Posted by Burn

HDR fallout 3 fix ?? .... please ...

please

[D'Argo]

No legacy support in these ? My x1900xt is not listed in the INF.

[kn00tcn]

legacy moved to 'official' 9.7 (maybe), & these are real early XP only drivers, so i bet they add legacy stuff just before the driver set is finalized & multi OS

i guess try adding yourself & see if it loads

[Dwarden]

no love for me

while testing ArmA 2

hmm it's me or on Catalyst feedback page is missing way to upload minidumps etc?

BugCheck 1000008E, {c0000005, bf8a0e6f, a69d5b40, 0}

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
Probably caused by : ati3duag.dll ( ati3duag+7cd0e )

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

0: kd> !analyze -v

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: c0000005, The exception code that was not handled
Arg2: bf8a0e6f, The address that the exception occurred at
Arg3: a69d5b40, Trap Frame
Arg4: 00000000

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
win32k!MultiUserGreTrackRemoveEngResource+17
bf8a0e6f 8b01            mov     eax,dword ptr [ecx]

TRAP_FRAME:  a69d5b40 -- (.trap 0xffffffffa69d5b40)
ErrCode = 00000000
eax=00000001 ebx=e93e3554 ecx=7ffffff0 edx=00000000 esi=7ffffff0 edi=e3cb14dc
eip=bf8a0e6f esp=a69d5bb4 ebp=a69d5bb4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
win32k!MultiUserGreTrackRemoveEngResource+0x17:
bf8a0e6f 8b01            mov     eax,dword ptr [ecx]  ds:0023:7ffffff0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  arma2.exe

LAST_CONTROL_TRANSFER:  from bf8a0e48 to bf8a0e6f

STACK_TEXT:  
a69d5bb4 bf8a0e48 7ffffff0 e6cb1010 00000000 win32k!MultiUserGreTrackRemoveEngResource+0x17
a69d5bc4 bf26ad0e 80000000 e3cb14dc e93e3554 win32k!EngFreeMem+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 ati3duag+0x7cd0e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ati3duag+7cd0e
bf26ad0e ??              ???

SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  ati3duag+7cd0e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME:  ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP:  4a306480
FAILURE_BUCKET_ID:  0x8E_ati3duag+7cd0e
BUCKET_ID:  0x8E_ati3duag+7cd0e

0: kd> lmvm ati3duag
start    end        module name
bf1ee000 bf5080e0   ati3duag T (no symbols)           
    Loaded symbol image file: ati3duag.dll
    Image path: ati3duag.dll
    Image name: ati3duag.dll
    Timestamp:        Thu Jun 11 03:57:20 2009 (4A306480)
    CheckSum:         00320B9D
    ImageSize:        0031A0E0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[Thr0tt]

Dwarden have you done a complete removal of the older drivers including CCC ? After uninstalling CCC I normally need to manually remove the ATI directory too as it stays there with some config data.

I personally have not had any crash dumps with this set and played a few hours last night. Are you able to replicate the issue or is it totally random ?

Also, in your ArmA2.cfg have you tried increasing the nonlocalVRAM equal or more than your video cards ram as I noticed when I orignally installed and played with these settings anything lower would bomb me out of ArmA2 when the memory or textures filled my card up (assumed and 512MB card).

[kn00tcn]

you can control arma's vram usage? why didnt anyone mention that (i dont browse arma forums though, wouldnt know if it's there)

welcome to GTA4 tweaking of december/january/february, where vram (& regular ram) are filled to the max on buggy drivers & buggy pre patch2 & 3 of the game, causing easy crashes or bsods within 15min

[Dwarden]

i dont need change the values as they correctly detected and set i was using the STEAM version

atm it's random and rare and clean or unclean system doesnt matter ...

i'm worried about possible BSOD issue in upcoming drivers versus our game ... thats all ...

[kn00tcn]

during GTA4's first 2 months, 'correct' vram was exactly the problem, people would get less bsods if they lowered (or was it raised) the allocated vram for the game

[Tranzmit256]

i posted this in guru3d too.

i managed to install this on windows 7 and got this

[badsykes]

That's a new CCC interface.I don't like it at least from the pictures...

[adadk]

any Vista updates yet rflair?

[Untouchable2K]

Just to let everyone know, XP drivers works on Vista 32bit. I have them install right now without any trouble and got a 30% performance increase , my guess because XP is way faster than Vista when it comes to gaming.

[AlexV]

Originally Posted by Untouchable2K

Just to let everyone know, XP drivers works on Vista 32bit. I have them install right now without any trouble and got a 30% performance increase , my guess because XP is way faster than Vista when it comes to gaming.

[Untouchable2K]

Just for proof

[spyre]

Duh, obviously you can use XP drivers in Vista. You lose WDDM1.0 though etc. Just like you can use the Vista drivers in Windows 7.

[badsykes]

by analogy you can use XP drivers in Windows 7 :P

[Hokum]

Working fine here. Seem ok, just want proper crossfire support for Arma 2.