Hard to troubleshoot a no-post computer... help?

Ubermouser

Limp Gawd
Joined
Dec 13, 2003
Messages
255
Well, my rig, for reference:
Intel Pentium 4 3.0E socket 478 (2 days old)
2x 512mb Mushkin Black level 2 ddr3500 dimms (1 year old)
Abit Ic7 Max3 I875 motherboard (10 months old) /w Bios 13, revision 1.0
Asus 9800xt 256mb Radeon graphics card (1 year old)
Turtle Beach Voyetra 7.1 surround sound card (1 year old)
2x Western Digital 10000rpm Sata 36gb Hard Drive "raptor" (10 months old)
Antec 550 watt Truecontroll power supply (7 months old)
Lite on 24x/40x/24x cdrw/dvd drive (1 year old)
Mitsumi 7-in-1 Media drive (floppy/memory) (1 year old)

I chose to watercool my computer, but dropped the CPU (2.6C) during the Xfer. I bent back the ruined pins and tried anyways, attaching everything into the motherboard. The system boots, but gives CPU unworkable. I skip the bios, (I didnt change settings), and boot to windows. During the 10 seconds before the "Welcome" screen and after the "windows is loading" screens show up, the computer crashes. It ceases to boot again. I remove the cpu in order to replace it but find the now dried up remains of the radiator fluid underneath the processor. I dry the board with a multitude of cotton ear-schwabs, giving the motherboard its "pristine beauty" again.

I then insert an Intel Pentium 4 3.0E into the setup, and to my suprise, the computer works flawlessly. The computer easily flys through its 25-hr test, though I didnt extensively try any Prime95 or Memtest86.

I wakeup to very low temperatures, nearly 10C lower than the night before. Time for some overclocking.. but first I had to do homework.

In the process of reading a document, the computer crashes - no blue screen, simply frozen. No response from any perhiperals. I restart, thinking the whole thing was a fluke.
THE COMPUTER DOESNT BOOT! Same error as before: no bios beep, no display, nothing going on upstairs - though both motherboard power lights are on, including the case light. The hard-drive light indicates the hard drives seem to be spinning up. Yet there is no bios beep. (no leaks)

I havent done anything up to this point, but could anyone here supply me with technical support? Its so upsetting to have a product work for nearly a year, then succumb to an unknown fate..
 
Have you checked for leaks? obviously the fluid didn't get there by itself. I would pull the cpu and clean everything with rubbing alcohol and take a hair dryer to it.
 
yup... thats the first thing I did. Added like twice as many zip ties to the tubing as well...

leaks most likely arent the problem.
 
This could be a little tricky. Chances are you picked up a short with the first leak. Thsi could have caused a problem that didn't show up until the system was re-heated or a certain pin/trace was used in data/power transfer.

I would have a friend check the CPU. If it works flawlessly in another board you will know it isn't the problem, if it doesn't work flawlessly you might just pooch your friends mobo, heh, but that's half the fun.

If the CPU works, check the memory and PSU on the other computer as well, again keep in mind you could be F'ing up that computer as well.

If the PSU, CPU, and memory all work, its your motherboard. See if you can pop the BIOS chip and get it reprogrammed, it may have gotten damaged during short--if you're luck this is the only problem with the board. Once the BIOS chip is re-flashed try the system again only keep the setup to a minimum (no Hdds, optical drives, PCI cards).

If everything is Ok set the rest of the sys up and see if you can reproduce the problem of the PC crashing during the opening of the OC'ing doc.

Most people will chuck the mobo once they know everything else but it works as that is the easiest way to go and in the long run probably the safest from a data security standpoint [you will never really know just how stable the mobo is unless you can get it factory retested or tested by a certified tech with the necessary equipment to suss out the gremlins].

Heh but look on the bright side I could be completely wrong and the prob might be a virus, power sag, excess static electricity and or signal noise, poor grounding, misaligned celestial bodies or fuk-luk, hard to tell really.

Good luck
:D
 
Back
Top