Hi guys,
In order to resolve issues in a specific game, I recently installed a new 500W Fortron Blue Storm. During the process, it seems like I lost my CMOS chip, and I got a new identical motherboard while I have the old one fixed.
So I put everything together, it boots to the BIOS, I am happy as can be. I flash the bios to version 6/23 and change the settings such as voltage, etc. Then I run into a bit of trouble. If I try to boot into the autorun Windows install from my CD-ROM drive, my pc will reboot right after the "analyzing system settings..." message prior to the setup launching. Also, if I try to boot on my HD which has my old Win XP install on it, it shuts down like 5 seconds after I see the logo.
Suprisingly, I can boot to a floppy drive or safe mode windows without any issues. Here is some information on what I have tried:
- I ran memtest on my 3 different OCZ Dimms for hours, and everything turns out fine. I currently have the voltage set to 2.7v manually.
- I have my old Fortron 530W that I could try. I upgraded from this PSU as the 12v rail is not sufficient. What are the chances that my brand new Fortron 500W Blue Storm is causing my rig to reboot or shutdown? Why would it always shutdown the system when I try to load a Windows install CD, but never when I boot into safe mode if it was my PSU?
- I pulled out both the CD-ROM and floppy drives, and it still shuts down while I load windows on my Raptor. This is a previous install before hardware upgrades. I see the Windows logo and the progress bar going accross the screen for about 5-10 seconds, then I get the shutdown.
- Before I took the rig apart to replace the PSU, my rig was running fine. CPU was passing prime95, no problem. I am booting the mobile at 1.55v at the moment to try to resolve these issues.
There has to be something that I am missing here... are there any known issues with the booting process with this board. Anything in the BIOS that might be causing this? When I get home I plan to rip everything apart and get back to troubleshooting. However, if any of you have any tips that I might try prior to starting from scratch it would be appreciated. This has been going on for weeks now and I can't wait to have peace of mind.
In order to resolve issues in a specific game, I recently installed a new 500W Fortron Blue Storm. During the process, it seems like I lost my CMOS chip, and I got a new identical motherboard while I have the old one fixed.
So I put everything together, it boots to the BIOS, I am happy as can be. I flash the bios to version 6/23 and change the settings such as voltage, etc. Then I run into a bit of trouble. If I try to boot into the autorun Windows install from my CD-ROM drive, my pc will reboot right after the "analyzing system settings..." message prior to the setup launching. Also, if I try to boot on my HD which has my old Win XP install on it, it shuts down like 5 seconds after I see the logo.
Suprisingly, I can boot to a floppy drive or safe mode windows without any issues. Here is some information on what I have tried:
- I ran memtest on my 3 different OCZ Dimms for hours, and everything turns out fine. I currently have the voltage set to 2.7v manually.
- I have my old Fortron 530W that I could try. I upgraded from this PSU as the 12v rail is not sufficient. What are the chances that my brand new Fortron 500W Blue Storm is causing my rig to reboot or shutdown? Why would it always shutdown the system when I try to load a Windows install CD, but never when I boot into safe mode if it was my PSU?
- I pulled out both the CD-ROM and floppy drives, and it still shuts down while I load windows on my Raptor. This is a previous install before hardware upgrades. I see the Windows logo and the progress bar going accross the screen for about 5-10 seconds, then I get the shutdown.
- Before I took the rig apart to replace the PSU, my rig was running fine. CPU was passing prime95, no problem. I am booting the mobile at 1.55v at the moment to try to resolve these issues.
There has to be something that I am missing here... are there any known issues with the booting process with this board. Anything in the BIOS that might be causing this? When I get home I plan to rip everything apart and get back to troubleshooting. However, if any of you have any tips that I might try prior to starting from scratch it would be appreciated. This has been going on for weeks now and I can't wait to have peace of mind.