PC crashing woes...

Flibster · 09-06-2009, 23:44

Got a PC to sort out here - Every component checks out in another machine which is annoying me.

I suspect there's something with the graphics card going on - It's a Sapphire 4870 512mb bog standard card.

In 3d apps *I'm testing with Fallout 3* after an unpredictable amount of time, sometimes under 5 minutes - sometimes over an hour, screen goes black, sound crashes and loops, and the PC eventually reboots.

In 2d - it's fine.

Power usage is way below what the power supply can provide.
CPU temps are fine...
GPU temps are fine... Set the fan to 100% and the cpu and memory speeds to the 3d settings to prevent the speed bump happening.

Tried Catalysts from 8.6 to 9.5 - same thing happens in all.

Stumped...

Error reports that I have actually got out of the machine points to Ati2mtag.sys - the driver.

Tried the Catalyst AI in on, off and advanced - no difference

Google seems to be no help. Only thing I can think of it's that it's something to do with the machine running XP64...

Any ideas?

09-06-2009, 23:44	#1
Flibster Moonshine Join Date: Jul 2006 Posts: 3,388	PC crashing woes... Got a PC to sort out here - Every component checks out in another machine which is annoying me. I suspect there's something with the graphics card going on - It's a Sapphire 4870 512mb bog standard card. In 3d apps I'm testing with Fallout 3 after an unpredictable amount of time, sometimes under 5 minutes - sometimes over an hour, screen goes black, sound crashes and loops, and the PC eventually reboots. In 2d - it's fine. Power usage is way below what the power supply can provide. CPU temps are fine... GPU temps are fine... Set the fan to 100% and the cpu and memory speeds to the 3d settings to prevent the speed bump happening. Tried Catalysts from 8.6 to 9.5 - same thing happens in all. Stumped... Error reports that I have actually got out of the machine points to Ati2mtag.sys - the driver. Tried the Catalyst AI in on, off and advanced - no difference Google seems to be no help. Only thing I can think of it's that it's something to do with the machine running XP64... Any ideas? __________________