4850 Stops responding

[iviv]

Its happened a few times now. I'm just in windows browsing the internet or chatting on MSN, both moniters go blank for a second and a popup in the tray says that the display driver stopped responding and has recovered.

It can't be overheating, as I've been thrashing it around in a few games and it runs perfectly, so could it just be a slightly buggy driver? (Catalyst 8.9, and running at 37C according to the overdrive tab, though its not been overclocked)

 

[metamorphpwner]

maybe the GPU is damaged, try running it on only one monitor that could also cause problem.

 

[H4wklord]

I kept having this issue with the cat 8.9's so reverted back to 8.8's. Not had a driver failer since doing so

 

[bee]

your running vista 64?

 

[H4wklord]

Yes I am.

 

[londonbairn]

try running DVI/HDMI on 2nd screen rather than VGA (that fixed it for me, assuming its applicable)

 

[iviv]

Well, it just happened again. Or rather, it happened 4 times in a row then bluescreened, pointing to the ati<something>.sys

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800754E3C0
BCP2: FFFFFA6002618730
BCP3: 0000000000000000
BCP4: 000000000000000D
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

If that helps.

To answer the above questions, its Vista 64, and both monitors are DVI. I'll try rolling back to 8.8, see if that does anything.

Edit: Hmm, just uninstalled then reinstalled the 8.8, got into windows and its saying it can't find a compatable ATI card. I'll install again, then try the 8.10 beta I saw floating around the forum.

 

[iviv]

I'm running the 8.10 beta's now, after I had problems with the 8.8's and it seemed fine. Then woke up this morning to the login screen, and windows telling me that it had bluescreened again.

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800020BA2DD
BCP3: 0000000000000000
BCP4: 00000000000000D0
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

I'm downloading windb to check the minidump, but I'm guessing its going to be the driver again.

Edit: No, it says ntoskrnl.exe this time. But I find it hard to believe that its unrelated.

 

[Eggman]

Known problem with ati cards/drivers on some peoples dual monitor setups. Aint a true fix but for some people say turning aero theme off in windows seems to help...

 

[iviv]

I've been going through a support ticked, updated my BIOS, mobo drivers and various other things, and game me this list of things to change in the BIOS:

2. Basic BIOS options.

NOTE: These options may vary depending on the type/version of your system. You may or may not have all these options present.

* Video BIOS Shadow - DISABLED
* Init Primary Display - AGP (Toggle this setting if your video card is PCI)
* AGP MASTER 1W/S READ/WRITE - ENABLED/DISABLED (Toggle this option)
* AGP Aperture size - 128 MB
* AGP Driving Control - AUTO
* Disable AGP 8x/4x mode in the BIOS.
* Disable AGP Fast Writes in the BIOS.
* AGP Driving Control - AUTO
* AGP Performance Control - ENABLED/DISABLED (Toggle this option)
* Assign IRQ for VGA - ENABLED
* System Bios Cacheable - DISABLED
* Video BIOS Cacheable - DISABLED
* VIDEO RAM Cacheable - DISABLED
* Read Around Write - ENABLED/DISABLED (toggle this setting)
* PnP OS installed - YES

3. BIOS Settings for ADVANCED USERS:

NOTE: These options may vary depending on the type/version of your system. You may or may not have all these options.

* Load optimized defaults in your BIOS
* Set your memory settings to default values (I.e.. DRAM Timing = SPD)
* Lower the memory frequency to 133/166mhz (effectively DDR266/333mhz)
* If available increase AGP Voltage to 1.6 - 1.8 in the BIOS
* SDRAM Cycle length - 2.5
* Bank Interleave - ENABLE/DISABLE (toggle this setting - It will only make a difference if you have more than one memory module.)
* DRAM Burst length - 4

I can only find one of these in my BIOS, the others seem to be for AGP cards ¬_¬

 

[LoadsaMoney]

Try the official 8.10's :- http://forums.overclockers.co.uk/showthread.php?t=17929850

 

[iviv]

Well, I've been running at stock processor speeds since my last post, and that seems to have cleared up the problem.

Which is a shame, and still rather weird since it never happened during any CPU/GPU intensive operations, always just at the desktop. I'll try the overclock with the new driver, see if it causes any problems. If it does, could it be that it needs more power, or something?