pseudo-crashing with Omega 4.8.421

curtmack · Apr 19, 2008, 02:29 AM

I have a WinXP SP2 with an ATI Radeon 9550 AGP recently installed. After learning that the ATI official drivers no longer support 9550 I installed Omega drivers. 4.8.442 didn't work very well at all, and after learning that Catalyst 7.12 might be to blame, I downgraded to 4.8.421.

Now the setup works, but it's highly unstable. If I try to run, as an example, Warsow, for too long, the system will suddenly stop functioning - the monitor displays "No signal found," there is no sound, and the computer no longer responds to keyboard or mouse input. The only way to turn off the computer is by holding the power button. This isn't unique to games either - just now it crashed in this way when clicking on a link in Firefox!

Does anybody know why this might be occurring? Soon would be nice, as I can't even run my computer from the looks of things until this gets worked out.

Edit: At least, not for too long.

curtmack · Apr 19, 2008, 06:36 PM

I just cleaned out the computer with compressed air and its still not working, and mobo monitor says it's only 48 degrees, so it's not overheating... now I'm really baffled...

**temeteus82** · Apr 19, 2008, 06:39 PM

You might want to test some older Omegas. Like ones based on CAT 6.X drivers. Remember to uninstall the installed driver first!

curtmack · Apr 20, 2008, 12:36 AM

How far back should I go before I know that isn't the problem? 4.8.291 (CAT 6.9) made it even worse, so I'm trying 4.8.273 now.

curtmack · Apr 20, 2008, 01:09 AM

Okay, I'm giving up on it anyway, it only seems to get worse the older I go. Me and a friend think the problem might be the power supply - mine is rated for about 500 W (100 - 147 V @ 4.0 Amps), which should be sufficient, but its possible that it's just not sufficient. Does that seem plausible to you guys?

curtmack · Apr 20, 2008, 07:39 PM

Okay, never mind that... upgrading from 218 W to 400 W didn't solve anything (we were accidently measuring AC input instead of DC output). Any OTHER ideas?

Apr 19, 2008, 02:29 AM	#1
curtmack DriverHeaven Newbie Join Date: Apr 2008 Posts: 5 Rep Power: 0	pseudo-crashing with Omega 4.8.421 I have a WinXP SP2 with an ATI Radeon 9550 AGP recently installed. After learning that the ATI official drivers no longer support 9550 I installed Omega drivers. 4.8.442 didn't work very well at all, and after learning that Catalyst 7.12 might be to blame, I downgraded to 4.8.421. Now the setup works, but it's highly unstable. If I try to run, as an example, Warsow, for too long, the system will suddenly stop functioning - the monitor displays "No signal found," there is no sound, and the computer no longer responds to keyboard or mouse input. The only way to turn off the computer is by holding the power button. This isn't unique to games either - just now it crashed in this way when clicking on a link in Firefox! Does anybody know why this might be occurring? Soon would be nice, as I can't even run my computer from the looks of things until this gets worked out. Edit: At least, not for too long. Last edited by curtmack; Apr 19, 2008 at 02:36 AM.

Apr 19, 2008, 06:36 PM	Thread Starter #2
curtmack DriverHeaven Newbie Join Date: Apr 2008 Posts: 5 Rep Power: 0	I just cleaned out the computer with compressed air and its still not working, and mobo monitor says it's only 48 degrees, so it's not overheating... now I'm really baffled...

Apr 20, 2008, 12:36 AM	Thread Starter #4
curtmack DriverHeaven Newbie Join Date: Apr 2008 Posts: 5 Rep Power: 0	How far back should I go before I know that isn't the problem? 4.8.291 (CAT 6.9) made it even worse, so I'm trying 4.8.273 now.

Apr 20, 2008, 01:09 AM	Thread Starter #5
curtmack DriverHeaven Newbie Join Date: Apr 2008 Posts: 5 Rep Power: 0	Okay, I'm giving up on it anyway, it only seems to get worse the older I go. Me and a friend think the problem might be the power supply - mine is rated for about 500 W (100 - 147 V @ 4.0 Amps), which should be sufficient, but its possible that it's just not sufficient. Does that seem plausible to you guys?

Apr 20, 2008, 07:39 PM	Thread Starter #6
curtmack DriverHeaven Newbie Join Date: Apr 2008 Posts: 5 Rep Power: 0	Okay, never mind that... upgrading from 218 W to 400 W didn't solve anything (we were accidently measuring AC input instead of DC output). Any OTHER ideas?