PDA

View Full Version : Could having the GPU block at the top have caused this?


CAPiTA
02-12-05, 01:32 PM
I've just finished installing my WC system in my new case. When I turned it on this morning there was one long beep, and two short. Nothing on the monitor. Second time I got graphical corruption but it seemed fine other than that. Third time, everything was perfect; nothing looked wrong.

So I got thinking. Is it possible that air trapped in the GPU block caused this when I first booted the computer? And that after awhile the pump moved the air out and water in so that the heat could be properly dissapated?

Hopefully, it's the above. My other concerns were that the AS5 shorted the card and/or the block was crushing the core.

Alacritan
02-12-05, 02:38 PM
It's hard to say. I had a motherboard that did that periodically and I couldn't tell you why. I thought it was the video card for a long time, until I upgrade my mobo and magically it stopped. It might be your AGP slot but really, it's hard to say with something like this. It's not a consistent, reproducible problem. You might want to look up the beep code but I think it's the one to let you know you don't have a video card connected. If everything's okay now I wouldn't worry about it though. If it does happen again, I'd take out the video card and blow some compressed air into the AGP slot and make sure the card is secure when you put it back in the slot.

CAPiTA
02-12-05, 03:26 PM
If it happens again I'll do that. I remember this happened a long time ago, but I never figured out what it was. You're probably right: the mobo is the best bet for the problem.

Thanks for the reply.