A7V133 problems once again

[JasonC]

Ok, for those of you who helped me out with the A7V133 probs I had earlier, I thank you and once again ask for your help.

I am absolutly out of ideas as to how to fix this situation.

Here is what happens:
-Turn on computer
-Posts fine
-Detects all drives fine
-Just before it should load the Win98 splash screen the pc speaker starts beeping rapidly and will just cause the system to go into a sort of loop not letting it proceed any further in the boot up.

According to the motherboard manual, the beeps are indicating that the CPU is overheating.

This is where my problem lies. I wanted to check the temps. So I go into the Bios and sit there and watch the temps level at 34C. Hmm, weird. Try again. Rapid beeps, system won't load because its "overheating." Hmm, right after this I go back into the bios after rebooting and check the temps again, ... 34C still. The CPU is NOT overheating, it is running at 34C before and IMMEDIATLY after the beeps.

The weird thing of it all is that 30min before all of this happened, I was doing just fine in Win98 running benchmarks and what not with the SAME exact temp readings in the bios.

Thinking I somehow screwed the Bios up while tweaking, I loaded the default setup today (after letting the system be off for 12 hours), and still, it thinks its overheating. There is no way that the CPU started overheating that quickly. Even if the pump wasn't on, the CPU couldn't overheat a mere 20sec into the bootup from a cold state (off for 12 hours).

I tried to simply disable the CPU temp sensor in the bios by setting it to "ignore" but it still thinks it is overheating.

I've reseated the waterblock, checked all PCI/AGP cards, all drives, all bios settings... nothing will fix it. It's running the 1005a bios.

I am SO discouraged right now because my first watercooling system was working FINE yesterday and yet today it won't even load windows.

I am almost positive that the CPU is NOT overheating based on my previous observations about the bios temps being the exact same before and immediatly after the "overheating." Which leads me to believe that it is some sort of WEIRD motherboard error.

If ANYONE can offer ANY even REMOTLY possible solutions, I'm willing to try them.

Thanks in advance,
Jason

[JasonC]

Nevermind...somehow I fixed it in the last 30min.

Took off waterblock, took out CPU, reseated CPU, remounted waterblock, booted up fine.

Guess the waterblock was not making good contact.

Jeez, what a nightmare.

Jason