K8T Master2-Far Will not POST unless CMOS is freshly cleared!

Question

Hey all, thanks for helping out.
I came back to my computer one day to find it in a coma. The system was on, but the screen was getting no signal and would not come on by moving the mouse/keyboard like usual. I thought that maybe it had turned off the monitor for power save and then frooze some how. After restarting the computer I found that it was still doing the same thing. I shut down the system and unpluged. After waiting about 5 min i plugged back in and flipped the switch on the powersupply. This started the computer right up (even though i had not pushed th power button) and left it in the same condition as before. It simply would not post. After closer inspection I found that it was not posting because it wasn't getting far enough in the process before it was being restarted. I checked the restart button and even went as far as removing it from the motherboard. This did not help. I knew it was restarting because i could see it checking the optical drives then waiting for about 4 seconds, then a weird noise from the speakers (like a soft cruching so to speak) would happen, then it would do this all over again, non stop. That noise was familliar though, it was the normal noise that I hear when I push the restart button (I'm guessing a release of electricity etc..) so I knew what was going on.
After switching the memory out and in all orders, I stripped the system down to the bare min. This however did not change anything. I put the system back together and flashed the cmos. This made the system restart once, then "BEEP" it posted. It said CMOS Checksome Error - Defaults Loaded. I first pushed DEL to get into the bios. I changed everything back to how its suppost to be (time, apature, etc...) then saved and exited. This made the system go back into its restarting state. I then flashed the cmos again and pushed F1 to continue. The system booted up just fine. In safemode of course. Then i restarted. It then went back into its restarting state. I flashed the bios again. And after pushing F1 to continue selected it to go into windows normally. Everytime it does this it gets different results. One time it got past the windows xp loading screen and sat at the black screen before you get your curser and welcome screen (sigh... restart... flash..). It also once got in just fine, and after about 5 min got a blue screen about "bad pool caller". It most the time however gets a random blue screen right after you see the welcome screen. These blue screens consist of "bad pool caller", "IRQ Equal or Lesser Value", or No notes, just generic blue screen.
If i change anything in my bios it will not post. If i dont flash the cmos, it will not post. If i dont change anything in bios and continue, then restart, it will not post. The only way for it to post and for me to see anything on the screen is to flash the cmos. I thought it might be the power supply, but the only extra i have does not have the extra plug to power the 2nd cpu. After thinking about it though. I dont know if it could be a power supply issue, if it was then would it even load up into safe mode? Or why would it not load up into safe mode again after restarting. I have tried an extra stick of memory that i know works in a separate computer, but nothing changed. I have tried a different videocard... nothing changed. I have removed everthing accept the basics (motherboard, cpu's,videocard,memory,psu) and nothing changed.
I have worked on this for about 1 week now and can not figure it out. I have my useless MCSE/CSE/A+ certifications (I say useless because I dont have a job that uses them) but this one is beyond me. If anyone could help I would appreciate it.
Thanks,
Brandon
P.S. I dont know if this is related, but I did have to change from useing the DVI connection to RGB plug to even see anything once I heard it post. I was useing DVI before, and once i figured out that it would post after flashing cmos, I had to change to RGB to get any visual. The DVI will not work now at all. I have even tried changing cords. The DVI wont work in safemode either. Thanks

Answer 1

I reckon these mobos have a fault that really needs to be sorted.  You say that your PC was working fine using PC 3200 memory with 240's. I have a similliar problem, I am using 246's with Kingston' PC3200 KVR333X72RC25/512D 2.5 ECC REG.  The PC worked fine for about two weeks and then one day went on a blink, every time I power it up all I get is beeps.  I was forced to order new BIOS, which didn't work everything else has been tested and works fine.
So I ordered micron memory 2X512 PC 2100 266 ECC REG which I was told by the supplier that it was compartible, that didn't work either.  I then went on to check the battery, to my surprise the battery was low so I thought I had nailed it, went out bought a new battery but the problem still exits.  I must say though after installing the micron memory it did boot up but when I went into BIOS to change settings to boot fro CDROM  the damn thing would not restart I had to switch it off using the power button to restart it and when it restarted all i got was beeps.  After that to  get it to bootup I have to reset CMOS using the jumper and when it boots up it gives a checksum error message.  I have a choice of two at this stage
(1) To Press F1
(2) To Press delete o go into BIOS setup
The F1 option takes me as far as the windows log on screen and that's it cuts off as if it is gonna boot itself backup but just hangs there.
The Delete option takes into BIOS which when exited the PC does nothing until powered down and powered up again, from here I have to reset CMOS to get it to bootup.
I have been told that the  kingston memory is not compatible but my question is how did it work the first two weeks?
Good ol' Bas have helped out on this one quite often but here I am three months on still in a struggle.  I thought of RMAing the board but it would cost me about 160 pounds and with that kind of money I could pick up another boad from kompllete.com and remain with some change for a couple of buds.
"To bass You said in the last post that the poblem could be the power supply changed it but that has not solved my problem"