• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Intel DP67BG owners, watch out for the new BIOS update

ckryan

SSD Abuser
Joined
Nov 6, 2010
Messages
619
The new 2053 bios update is out for the Intel DP67BG -- but hold off on it. It looks like the new bios will hose up your system, requiring a BIOS reflash back to an earlier version through a bios rescue. It looks like a possible problem with nVidia cards not being detected after flashing, resulting in a no video post beep (and thus no boot). A few other people seem to be having problems as well, with the same problem.

I took out my nVidia and swapped it for an AMD gpu -- I still can't boot now, but I can get into the bios after a few cycles. Someone on the Intel forums was able to rescue to an earlier bios, so I hope I can as well.

Has anyone successfully updated to 2053? Or had the same problem?
 
It looks like I'm unable to use the recovery method at the moment -- due to the particular problem I'm having, so it looks as though my board is bricked. To reiterate, the bios flash completed without issue, all progress messages reported good results and I received a flash complete message. The updater then asks for a reboot. Upon reboot, I got two long beeps and an endless reboot cycle, and no post. If I change the jumper position I can get into the BIOS, but ONLY the BIOS after a failed boot message -- and only with my backup AMD GPU. Without being able to detect the video device in recovery jumper mode, you just get an endless cycle of beeps and reboots.

Intel Enthusiast, do you have any suggestions?
 
Last edited:
Yea I got back to you some information from technical support. They are working on a fix for this but in the mean time they advise that you try to do a CMOS clear and then revert back to an earlier Bios like 2040. At this point that is the best that I can do.
 
I was able to recover back to 2040. Subsequent attempts to flash to 2053 were met with complete failure. So at least it looks safe if you want to try to flash -- just set you BIOS settings to minimal settings first (especially memory -- set it to 1067mhz @ 9/9/9).

I was getting two pre-post errors:
No Video, two long beeps,
Bad Memory, three long beeps, obscures the no video code.

The Bad Memory code will prevent you from recovery flashing back to the earlier 2040 revision BIOS.
The No Video will not prevent you from flashing.

My memory was set at 1600mhz CL9 and I had to set it down to 1067mhz, so you may wish to do it before hand. IF YOU DID NOT DO THIS BEFORE YOU FLASHED THE BIOS WITH 2053 you could have some problems. If after the flash you get three long beeps before post, you need to change your memory settings. THIS IS NOW ONLY POSSIBLE IF YOU HAVE AN AMD GPU -- turn off the system, move the bios config jumper, and then you should be able to enter the BIOS after a few reboot cycles. IF YOU ONLY HAVE AN NVIDIA CARD, you may have to remove your CR2032 battery for what I've been told is 4 hours to default BIOS settings. Possibly, if you have some slower DDR3 with automatic profiles AND you currently have automatic memory settings enabled in the BIOS you shouldn't have had this problem anyway.

Here's how to do a recovery flash:

1) Take a USB drive and put the 2040 BIOS's .BIO file in the root folder (for best results, just use a blank, formatted drive)

2)With the system power off, remove the BIOS config jumper near the DP67BG's Exreme Skull.

3)Insert the drive, then power on the system.

4)You should not see video at this point, but the flash drive should be found and will be accessed twice -- use a USB drive with a visible activity LED so you can tell.

5)After the .bio file is found there will be a brief delay, then you should have video displaying the flashing progress.

6)After a successful recover you should get a message reminding you to replace the config jumper and to reboot. So UNPLUG your system or flip your PSU's switch. Now replace the jumper.

7)Turn your system back on. Everything should work.
 
Hm, I had no problem updating the other day. I am having some trouble getting the board to power on sometimes (lights come on/fans spin for a couple seconds, then go out... then comes back on.. then goes out.. the timing seems to be like the power button is being shorted out). It seems unplugging the power cord (flipping switch on PSU) for a few seconds then lets it boot up fine.

Not sure what that is all about, but I had a bit of trouble before the BIOS update too. I don't think this completely started after the BIOS update. At first I thought it was an issue with the board.. then I thought maybe memory after playing with the sticks a bit, but now I'm not sure anymore. It is fairly intermittent and doesn't seem to be an issue once the computer is actually up and running, so I'm not concerned as this computer isn't going to get shut down/rebooted once it is up and running for good.

Maybe I'll try reverting to 2040 though just for the hell of it as some of your symptoms seem very very similar to mine (I had some intermittent RAM beep issues as well as the endless reboot cycle).

FWIW, I'm using a Radeon X300
 
It looks as though there is some problem updating to 2053 with certain NF1xx nVidia cards. But that's just what I've gathered from discussions over at the Intel support forums. So it looks like in most every case you can recover back to 2040.

I would suggest some of your problems could be memory related. If you open the case up so you can see the leds on the bottom of the board while you're having the false boot lights on/fans spin ect. look for the red light -- the rest are green. If you're running 4x4GB you may need to make some adjustments to memory voltage, system agent voltage, change some timings, ect. I had this problem when I first got the board, but haven't had any problems since. The board (see a Toms hardware review of 1155 launch boards from January) used to have cold boot issues at >=1600mhz with 2 sticks of ram, and 1333 or higher with 4 sticks of ram. I see in your sig you're running 16gb, and I'm running 12gb -- but I've had no problems like that for quite some time. My problem was caused mainly by having too aggressive timings and frequencies with 4 sticks. Loosening some of my timings helped, but I imagine some more SA voltage could help as well.
 
Shame on me for not doing a quick search before a BIOS flash to make sure it wasn't an epic fail release, cuz this one is. Why is it even up on their site still? :rolleyes:

I have a gtx570 and after the update I got 2 beeps (no video) but I could see via my G15 keyboard it was booting into Windows.

I took out the CMOS battery and unplugged the P/S for 10 mins and a recovery flash to 2040 worked thankfully.
 
It looks as though there is some problem updating to 2053 with certain NF1xx nVidia cards. But that's just what I've gathered from discussions over at the Intel support forums. So it looks like in most every case you can recover back to 2040.

I would suggest some of your problems could be memory related. If you open the case up so you can see the leds on the bottom of the board while you're having the false boot lights on/fans spin ect. look for the red light -- the rest are green. If you're running 4x4GB you may need to make some adjustments to memory voltage, system agent voltage, change some timings, ect. I had this problem when I first got the board, but haven't had any problems since. The board (see a Toms hardware review of 1155 launch boards from January) used to have cold boot issues at >=1600mhz with 2 sticks of ram, and 1333 or higher with 4 sticks of ram. I see in your sig you're running 16gb, and I'm running 12gb -- but I've had no problems like that for quite some time. My problem was caused mainly by having too aggressive timings and frequencies with 4 sticks. Loosening some of my timings helped, but I imagine some more SA voltage could help as well.

That might be a good idea. It did seem to boot better sometimes with only two sticks vs. four. I might as well try dropping it down a bit to see what happens.. it isn't like I'll notice it I'm sure. It isn't THAT important, but I haven't had any time to work on it with family in town, and I'm waiting on another pair of fans, so I might try to play with it in the next couple days.

EDIT 9/29/11: I don't feel the need to bump this thread since it turns out my issue wasn't BIOS-related at all, but I wanted to post this in case anyone runs into similar issues in the future. My issue was simply the undercurrent protection on my power supply. I'm using a triple-12V-rail power supply, and I didn't have anything connected aside from the 24pin and 8pin PSU connectors, leaving nothing on the 3rd rail whatsoever. Once I plugged in a few drives, all of my random boot issues disappeared.
 
Last edited:
I updated to 2053 a while back and didn't even realize it was the root of my inability to switch to any other video card but the 5850 that I had in when I flashed it. GTX 560 Ti, Radeon X1650, and Radeon 5450 all produced the error beeps and lack of video on POST described above. Just flashed to the newest BIOS (2070-something) and all is well again.

Bumping this thread on the chance that it may help someone else.
 
Back
Top