Results 1 to 22 of 22

Thread: D975XBX stuck in configure mode -- UPDATE fixed!

  1. #1
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19

    D975XBX stuck in configure mode -- UPDATE fixed!

    Just put together my new Conroe system, and for some reason the BIOS is stuck in configure mode. Every time I turn it on it puts up the Intel splash screen, then the Silicon Image configure prompt, then the screen goes black, it flashes a few more POST codes in the bottom right corner and then dumps me into BIOS setup. On exiting that I get the message 'Turn off power and reinstall the jumper in the Normal position'. But the BIOS config jumper *is* in the normal position! On powering off then on, the result is the same. I've tried changing it to configure, I've tried removing it, I've tried taking out the battery (which resets the time in the BIOS, but doesn't clear the event log), but it behaves the same.

    Any ideas?

    Specs:
    Seasonic 600W PSU
    Intel D975XBX
    Core 2 Duo E6600
    2Gb G.Skill ZX RAM
    7300GS PCIe video card

    UPDATE
    I'd tried removing the battery for 5 mins or so with no joy. Since everything else had failed, I left the battery out overnight. Fired it up this afternoon (bit of a lie-in, heh) and bingo! the CMOS had finally reset!
    Managed to flash it to 1304 and I'm now partitioning the RAID.
    I had tried shorting the 'Clear CMOS' pads, which did absolutely nothing, it looks like letting the charge die over several hours was the only option. Why Intel did not put a proper CMOS clear function on this board is beyond me. I should send them a bill for the amount of my time they've wasted.
    Thanks to mdzcpa for suggesting I leave the battery out for a long time - saved me the huge hassle of RMAing the board.
    Last edited by charleski; 08-06-2006 at 05:46 AM.

  2. #2
    Xtreme Member
    Join Date
    Apr 2006
    Posts
    279
    I would try updating to the most recent bios. If that doesn't work then I would try to clear the cmos. To do this remove the battery and locate the terminals to clear the cmos and short them with a screw driver or piece of wire. If that dosen't work then it might be rma time.
    P182
    E6400 @ stock
    Asus P5B Deluxe
    8800 GTS 320 mb
    G.skill PC6400 2x2 gigs
    CL x-fi xtreme music
    PCP&C Silencer 750
    3 x 160 gb 16 mb cache WD r.e. hard drives (raid 0)
    Dual Layer burner
    Ultima 90
    Vista 32


    Coming soon: 4x4 or penryn, another 4 gb's of memory, and Vista 64


  3. #3
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    There are 3 solder pads labelled 'clear CMOS' next to the battery. Anyone know which I need to short? (i.e. 1-2 or 2-3)

  4. #4
    xtreme energy
    Join Date
    Oct 2004
    Location
    Europe, Latvia
    Posts
    4,145
    Had similar problem. I am afraid you will have to RMA it
    ...

  5. #5
    Xtreme Enthusiast
    Join Date
    Sep 2002
    Location
    Dallas Tx
    Posts
    736
    Those clear CMOS jumper pads don't seem to do anything on my board. I've even soldered pins in and place a jumper across, does nothing. Also have the same prob removing all PSU connectors and pulling the battery even over night only resets the date and time...nothing else

    My board isn't stuck in config mode but I'm having a cold boot issue even with every thing set to defaults. Once I ever get into windows it runs fine. Am about at the end of my rope with this board.

  6. #6
    Skulltrail Junkie
    Join Date
    Jan 2005
    Location
    Milwaukee, WI
    Posts
    985
    i had a similar problem with my previous 302 board, and i had to RMA it
    • Lian Li PC-75B • Corsair Professional Series 850w •
    • 2x Intel Xeon E5420 @ 3.0GHz (400x7.5) • Intel D5400XS Skulltrail •
    • 8GB (4x2GB) A-Data DDR2-800 FB-DIMM ECC (1:1 @ 400MHz) •
    • MSI Radeon HD4870 1GB • Creative X-Fi Titanium HD •
    • 2x WD VelociRaptor 150GB (RAID 0) + 2x WD Caviar Black 500GB •
    • 2x EK Supreme HF CPU • EK S-MAX NB • EK VGA Supreme GPU • Blastflow Tidal SB •
    • Thermochill PA120.3 • Swiftech MCRes-Micro • Laing D5 w/ Bitspower Top •

    -----------------------------------------------------------------
    Heatware • http://www.heatware.com/eval.php?id=34593

  7. #7
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    Quote Originally Posted by Sneaky
    i had a similar problem with my previous 302 board, and i had to RMA it
    /sigh
    Well thanks for the reply, saves me wasting more hours fiddling with it.

  8. #8
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Hold on!

    Make sure you understand how that cmos jumper works. That jumper is NOT a clear cmos jumper.

    In position 1-2 (top and middle pins), the board boots normally. Pressing F2 gets you into the BIOS.

    In position 2-3 (middle and bottom pins), the board boots into configuration (maintenence mode). Essentially all this does is boot the board at default settings and puts you automatically into the BIOS screen to make maintenance changes.

    If you overclock too far, you put the jumper on 2-3 and boot into maintenance mode and change the settings you need to.

    It sounds like you simply have the jumper in the wrong position.

    Edit- if you have a problem with the mobo booting into maintenance mode even though you have the jumper in "normal" position, then do the following. Power down. Put the jumper on "config" mode. Power up...the system should go into maintenance mode. Alter some your settings in the BIOS when you are in maintenenace mode. Make sure all the settings are good. Save and exit. Power down as instructed and put the jumper back into normal mode. Power back up.
    Last edited by mdzcpa; 08-05-2006 at 11:39 AM.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  9. #9
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    Quote Originally Posted by mdzcpa

    It sounds like you simply have the jumper in the wrong position.
    Nope, this occurs no matter which position the jumper is in, and happens if I remove the jumper completely. The jumper was in the normal position when I first powered up the board and found this happening.

  10. #10
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Quote Originally Posted by charleski
    Nope, this occurs no matter which position the jumper is in, and happens if I remove the jumper completely. The jumper was in the normal position when I first powered up the board and found this happening.
    See my edit above. Make sure you go into maintenance mode with the jumper in maintenance position. Set everything to defaults or known workable settings. Save and exit BIOS. Power down as instructed and change the jumper back.

    The key is to power up into maintenance mode while the jumper is in maintenance mode and make changes to you BIOS settings and save.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  11. #11
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    One last trick is to remove the battery for about an hour. That seems to help as well.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  12. #12
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    Quote Originally Posted by mdzcpa
    Make sure you go into maintenance mode with the jumper in maintenance position.
    Thanks for the suggestion. I powered off, set the jumper to configure mode, powered on and selected 'Load Optimal Defaults', saved and powered off. Set jumper back to normal and powered on again - still boots into maintenance mode .

    I'll try leaving the battery out overnight.

  13. #13
    xtreme energy
    Join Date
    Oct 2004
    Location
    Europe, Latvia
    Posts
    4,145
    You might also try bios rescue when you have to remove jumper, insert floppy and it will try rewriting bios. Just take a look at Intel bad axe bios download section, it has everything you need to know


    mdzcpa:

    Is you bad axe rig always on 24/7 or you are powering it on/off daily, overclocking, resetting settings etc (or changing settings often)? Glad to hear that your boad is still working fine with conroe even overclocked
    Last edited by kiwi; 08-05-2006 at 12:04 PM.
    ...

  14. #14
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    Quote Originally Posted by kiwi
    You might also try bios rescue when you have to remove jumper, insert floppy and it will try rewriting bios. Just take a look at Intel bad axe bios download section, it has everything you need to know
    Yeah, I got the latest recovery bios on a floppy, but since the board is stuck in maintenance mode it won't read the disk when I boot up without the jumper on.

  15. #15
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Quote Originally Posted by kiwi
    mdzcpa:

    Is you bad axe rig always on 24/7 or you are powering it on/off daily, overclocking, resetting settings etc (or changing settings often)? Glad to hear that your boad is still working fine with conroe even overclocked
    It gets repowered a few times a week when I change settings. It gets powered down every now and then when I know I'll be off the system for more than a day. Other than that it runs 24/7.

    The only thing I have encountered which annoys me about the board is a cold boot issue at higher overclocks. It'll always boot, but sometimes it fails to get into windows. I need to do a warm reset and all is well. It has to do with the cpu voltage. A higher cpu voltage fixes the problem, but its more voltage than I need when I just warm reboot. If I warm reboot at the lower voltage the system runs fine and is rock solid double prime and 3D stable for days on end. I prefer the lowest voltage needed to run like that, so i tolerate the cold boot issue.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  16. #16
    Xtreme Enthusiast
    Join Date
    Sep 2002
    Location
    Dallas Tx
    Posts
    736
    Quote Originally Posted by mdzcpa

    The only thing I have encountered which annoys me about the board is a cold boot issue at higher overclocks. It'll always boot, but sometimes it fails to get into windows. I need to do a warm reset and all is well. It has to do with the cpu voltage. A higher cpu voltage fixes the problem, but its more voltage than I need when I just warm reboot. If I warm reboot at the lower voltage the system runs fine and is rock solid double prime and 3D stable for days on end. I prefer the lowest voltage needed to run like that, so i tolerate the cold boot issue.
    Thank You for say this, thought I was the only one in the intire world with this issue.
    I have the same issue but with a twist. Once this started happening {after flashing to 1334 BIOS} It allways happens now even at stock 2.66ghz. Upping the vcore doesnt cure mine though.

  17. #17
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Quote Originally Posted by Blue078
    Thank You for say this, thought I was the only one in the intire world with this issue.
    I have the same issue but with a twist. Once this started happening {after flashing to 1334 BIOS} It allways happens now even at stock 2.66ghz. Upping the vcore doesnt cure mine though.
    Hmmmm...now that you mention it, it may indeed have started with the new BIOS flash for me as well. Since I gained absolutely nothing from going to 1334, perhaps I should just move back to 1304.

    Sorry for the OT here.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  18. #18
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Okay, flashed back to 1304 and the cold boot issue is history. Now I can boot just fine at lower cpu volts. Ba-bye 1334
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  19. #19
    XIP
    Join Date
    Nov 2004
    Location
    NYC
    Posts
    5,524
    Same thing happened to me (it stays on maint. mode and the other stuck @ F5 on post). This is my 4th bad axe and so far so good

  20. #20
    Xtreme Recruit
    Join Date
    Jul 2006
    Posts
    19
    Thanks to those offering suggestions. After the long wait for Conroe the MB problem was maddening.

  21. #21
    Memory Addict
    Join Date
    Aug 2002
    Location
    Brisbane, Australia
    Posts
    11,651
    weird no probs with powering down and up on both my bad axes with 1334 bios but i flashed my with my own custom modded 1334 bioses
    ---

  22. #22
    Xtreme Member
    Join Date
    Nov 2003
    Posts
    188
    The way to clear the cmos on intel boards is to remove the battery and then short the contacts from the center and the metal battery retaining clip with a plastic handled metal screw driver

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •