maynardc Posted October 13, 2004 Posted October 13, 2004 I’ve been using this board for now 3 weeks or so and haven’t had any problems until now. Now every time I cold boot or even after a restart computer from Windows XP, I get to the very first black screen which displays the "Phoenix AdwardBios" info and the "8/27/2004-nForce-CK8S-6A61CD49C-00" (hitting ESC or DEL does nothing at this point even though it appears at the bottom of the screen) AND it will pause at this screen for just about 3 WHOLE minutes! During this very long pause, the hard drive light is on the entire time. http://www.angrygames.com/pics/nf3/nf3_bios1.jpg Look at this pic above...this is where I get stuck except it hasNOT YET displayed the Main Processor info, mem test, detecting IDE drives... part yet. After the 3 minute pause, these 3 things appear (CPU identification appears, next the memory settings appear and finally the Detecting IDE drives)…and it boots up to XP quickly (as it normally does). Everything is normal after that…XP works fine and all applications work fine, including games. I have the latest BIOS and have tried loading the optimized settings etc. I have NO idea why this is happening and it's very frustrating. Can someone please help? Thanks. Quote Share this post Link to post Share on other sites More sharing options...
bldegle2 Posted October 13, 2004 Posted October 13, 2004 the system, or have you overclocked/played with this OS install, and now there is a delay???? sometimes the boot sector can get semi hosed with really aggressive OC attempts, leading to the delay you describe. have you checked for viri recently? done a spyware check? i would do the above right away, prolly won't fix it. have you tried a system restore to a previous point?, it is a nice little feature. the only drawback is if your restore doesn't go back far enough to give you a clean slate. hope this helps. baldy:D Quote Share this post Link to post Share on other sites More sharing options...
RGone Posted October 13, 2004 Posted October 13, 2004 ...good thing you posted here "maynardc" as I just emailed you from the location of your other request for help and what I thought you were descrbing and what I had 'just' happen to me are NOT the same two things. That is why I try to get so many people to come to a good forum and post pics if needed and in general better describe the problem to look for the solution. I would have never understood where you are hung at when I thought you were seeing "my" new forkup. Hehehehehe. Disregard my email to you! It does not count in your situation. Let me now see if I see a pattern in the problem you currently have. RGone... Quote Share this post Link to post Share on other sites More sharing options...
Samurai Jack Posted October 13, 2004 Posted October 13, 2004 Try reflashing the bios with winflash, clear all blocks & reset the bios up. SJ Quote Share this post Link to post Share on other sites More sharing options...
maynardc Posted October 13, 2004 Posted October 13, 2004 Originally posted by Samurai Jack Try reflashing the bios with winflash, clear all blocks & reset the bios up. SJ I will try this. Thanks. And to the other DFI member's question: no, I've not overclocked anything. Quote Share this post Link to post Share on other sites More sharing options...
Lith1um Posted October 13, 2004 Posted October 13, 2004 Angry_Games posted some info about jumper positions on WD drives stalling the boot process, A master or slave setting without the counterpart being present usually appears as the system hanging or freezing. On detection timeout, the system usually tries to continue booting, often with the boot drive not being found either. Attempted warm reboots sometimes allow the system to boot, but with some risk of subsequent data corruption. http://www.dfi-street.com/forum/showthread...=&threadid=1541 Could this be a possible cause? Maybe it affects other drives? Good luck anyway! Quote Share this post Link to post Share on other sites More sharing options...
maynardc Posted October 14, 2004 Posted October 14, 2004 Originally posted by Lith1um Angry_Games posted some info about jumper positions on WD drives stalling the boot process, http://www.dfi-street.com/forum/showthread...=&threadid=1541 Could this be a possible cause? Maybe it affects other drives? Good luck anyway! I read this info, and I'm not using WD drives. I have a Maxtor (master) and a Samsung (slave). I even disconnected the slave to see if anything happened. Nothing did. I flashed the bios, cleared the CMOS to no avail. This is really frustrating. Any other ideas. The bios settings are correct too (first boot is Hard disk) everything looks good. This problem just appeared out of nowhere. Please help. Quote Share this post Link to post Share on other sites More sharing options...
RGone Posted October 14, 2004 Posted October 14, 2004 :confused: I don't see the power supply in the signature and I have seen a few of this type hard drive detection issue rest at the feet of a power supply weaking. Is the supply out of a prevous build by any chance. Did you reload the O/s yet after writing zeros to the drives. These things are crashing somewhat different than what I am used to and they say the MBR gets messed up some or partially corrupted. Normally these board have been so trouble free that it has not had a lot of symptoms to point to a single thing to just say Ok now when you see this> do this. I know the bios is full of things that can be off if you load optimized. It is just strange that it up and does it without any other warning and in a case like this I usually run the manufacturer's drive utility to see if the drive is ok. Then I wipe the drive completely and start over. Using only a single hard drive and Cdrom to get up and them on different channels and if that does not work > I would RMA the board as I would have exhausted all means known to verify what was wrong. Sincerely, RGone... Quote Share this post Link to post Share on other sites More sharing options...
icywater Posted October 14, 2004 Posted October 14, 2004 I have the similar problem, Sometime it does not detect my rator 74 on the nvidia control, Then it change the order of my boot. I have to go in the bios to change it back other wise, i get non system disk error. It try to boot with my WD 800JB. It every annoying. Quote Share this post Link to post Share on other sites More sharing options...
maynardc Posted October 14, 2004 Posted October 14, 2004 Originally posted by RGone :confused: I don't see the power supply in the signature and I have seen a few of this type hard drive detection issue rest at the feet of a power supply weaking. Is the supply out of a prevous build by any chance. Did you reload the O/s yet after writing zeros to the drives. These things are crashing somewhat different than what I am used to and they say the MBR gets messed up some or partially corrupted. Normally these board have been so trouble free that it has not had a lot of symptoms to point to a single thing to just say Ok now when you see this> do this. I know the bios is full of things that can be off if you load optimized. It is just strange that it up and does it without any other warning and in a case like this I usually run the manufacturer's drive utility to see if the drive is ok. Then I wipe the drive completely and start over. Using only a single hard drive and Cdrom to get up and them on different channels and if that does not work > I would RMA the board as I would have exhausted all means known to verify what was wrong. Sincerely, RGone... looks like I'll be RMA'ing this board. how do I go about doing this? thanks again for all of your help and advice. Quote Share this post Link to post Share on other sites More sharing options...
Angry_Games Posted October 14, 2004 Posted October 14, 2004 RMA through the vendor you bought it from. A more complete sig might have helped us help you. or maybe you could try to boot without a hdd and see what happens...then boot with the Samsung hdd only and see what happens....then boot with only maxtor but jumpered differently and see what happens....then boot with maxtor on the secondary and see what happens...or boot without the (if you have one cuz i dont see nothing in your sig) cd-rom or dvd and see what happens... i'd bet you money its not the board but something in how you have it setup. But RMA it and get another one to eliminate the possibility of the board being bad. If your replacement does the same thing then you know its not the board but either some piece of hardware or how you are setting it up. Quote Share this post Link to post Share on other sites More sharing options...
Samurai Jack Posted October 14, 2004 Posted October 14, 2004 IceWater - I see you have a 380 PSU, although some 380s may be enough to carry a a64 it is very unlikly that it would be enough power to supply such a board. I have a 480 TP on a NF2 board that holds me back on overcocking, I can put my 550TP on it and Vid card & CPU will clock better. Also from the looks of your sig you have enough going on to need no less than a 550, a 620 would be more like it. maynardc - I really dought that the board is bad. A simple thing like a CDrom drive not agreeing with the system could cause this to happen. I understand the aggrivation that you are going threw. But the truth is RMA may not help. You should do more testing before giving up so easy. Maybe a list of all bios settings would help, or if its to much to go threw someone could get on a messenger with you to help sort the problem. It really would suprize me to see that the board was the problem. The a64s really can be tricky sometimes, and any piece of hardware could be the problem, or just simply a setting. Something as silly as a bad IDE cable. SJ Quote Share this post Link to post Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.