My old gaming rig:
Antec 350w PSU
Chiantech 6600GT
AMD 64 3200+
Chaintech VNF4/Ultra MB
80gig HDD
2 gig RAM
Standard USBMouse
Standard PS2 Kyb
Win XPPro
I recently built a new quad core system for gaming and gave my old gaming system to my wife for use in her home office. Before I gave it to her, I formatted the HDD and put a fresh install of Win XPPro on it because her work wanted to install network software on it.
Right after that reinstall, I got a post code 50 when trying to boot up the system. I looked that code up and it has to do with USB conflicts so I unplugged the USB mouse. Then it booted fine. Oddly, I never had this problem in the 3 years I used the system... only after the reinstall.
Looking around different tech sites I saw a bunch of posts saying that the newest bios version has resolved the post code 50 issue. So I decided to flash the bios. I went to Chaintech's site, found my board in their archives and downloaded what I *think* was the correct file for my board. Looking under the 2006 folder, I found vn210223.bin and (assumed) it was the correct one. The flash went through properly and all seemed well.
So my wife takes it to work and it's locking up 20 seconds after getting into Windows. They can't do much with it, so they send it back. I pulled the RAM chips individually and tested them, they're not the issue. The system is running very cool as well. Never was any overclocking with it.
Sure enough, even with fail safe settings within the CMOS, it's locking up about 20-30 seconds after I get to the Windows desktop. At first I tried to flash back to an older bios, but the AWDFlash program at boot-up tells me that I'm trying to install an old bios and won't let me install anything. I tried to pull the Cmos battery and reset the jumper, but that's not affecting the actual bios upgrade. Now it's not even recognizing the internal FDD anymore, so any bios flash attempts I've made since have been off a USB FDD at boot.
Prime example here of someone playing around with a system deeper than they should have, but if you've any ideas, I'd be much appreciated. I won't blame anyone for not touching this one with a 10' pole though. : /
Antec 350w PSU
Chiantech 6600GT
AMD 64 3200+
Chaintech VNF4/Ultra MB
80gig HDD
2 gig RAM
Standard USBMouse
Standard PS2 Kyb
Win XPPro
I recently built a new quad core system for gaming and gave my old gaming system to my wife for use in her home office. Before I gave it to her, I formatted the HDD and put a fresh install of Win XPPro on it because her work wanted to install network software on it.
Right after that reinstall, I got a post code 50 when trying to boot up the system. I looked that code up and it has to do with USB conflicts so I unplugged the USB mouse. Then it booted fine. Oddly, I never had this problem in the 3 years I used the system... only after the reinstall.
Looking around different tech sites I saw a bunch of posts saying that the newest bios version has resolved the post code 50 issue. So I decided to flash the bios. I went to Chaintech's site, found my board in their archives and downloaded what I *think* was the correct file for my board. Looking under the 2006 folder, I found vn210223.bin and (assumed) it was the correct one. The flash went through properly and all seemed well.
So my wife takes it to work and it's locking up 20 seconds after getting into Windows. They can't do much with it, so they send it back. I pulled the RAM chips individually and tested them, they're not the issue. The system is running very cool as well. Never was any overclocking with it.
Sure enough, even with fail safe settings within the CMOS, it's locking up about 20-30 seconds after I get to the Windows desktop. At first I tried to flash back to an older bios, but the AWDFlash program at boot-up tells me that I'm trying to install an old bios and won't let me install anything. I tried to pull the Cmos battery and reset the jumper, but that's not affecting the actual bios upgrade. Now it's not even recognizing the internal FDD anymore, so any bios flash attempts I've made since have been off a USB FDD at boot.
Prime example here of someone playing around with a system deeper than they should have, but if you've any ideas, I'd be much appreciated. I won't blame anyone for not touching this one with a 10' pole though. : /
Facebook
Twitter