Overclock.net › Forums › Intel › Intel - General › Why did updating the BIOS cause CPU problems?
New Posts  All Forums:Forum Nav:

Why did updating the BIOS cause CPU problems?

post #1 of 11
Thread Starter 
Ok, so I recently built my first computer, kinda new to this, but it seemed pretty darned easy to me. Everything went together just fine, booted right up and was able to install Windows. In fact, before about ten minutes ago, my only gripe with this system was that the graphics card refused to overclock. Big deal. Well, I was attempting to overclock the CPU, and tried to install ASUS AI Suite II. Seemed to install ok, but didn't show up in the system tray. After looking online at the other updates available, I saw that the newest BIOS release added compatibility with AI Suite. So I download that and follow the instructions in the motherboard user guide to flash the new BIOS. And that seemed to work just fine too. After a minute or so, I saw a screen saying that it was successful. I exited out of the update utility and attempt to reboot. No dice. Won't show anything on the screen and the CPU LED is lit up. Any idea on how I can fix this? I had everything running perfectly fine for a few days before attempting to flash BIOS. I'm figuring something went wrong there, but is there any way to fix it? Could the problem actually be with the CPU, even though it was working just fine before the update? Sorry if this has been asked a dozen times before, but I couldn't find an answer...
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
post #2 of 11
reset bios. pull on board battery and pull power plug and wait a couple minutes. dont use software applications to overclock your processor, only use software for graphics cards.

Overclock cpu in your bios screen. you should still get image but it wont post or maybe even nothing at all until you do this.
P50
(15 items)
 
   
CPUGraphicsRAMHard Drive
Intel Core i7-6700HQ NVIDIA Quadro M1000M 4GB Gskill 32gb 4x8gb DDR4 2300mhz Samsung 850 PRO - 1TB SSD m2 
Hard DriveOptical DriveOSOS
Seagate 2TB w/ 128MB Cache (ST2000LM007) Pioneer External USB-C Blu-Ray Burner Fedora 25 Win 10 LTSB 
MonitorMonitorMonitorPower
15.6" 1920x1080 IPS BenQ GL2460HM 24" LED BenQ GL2460HM 24" LED Lenovo 170w Power adapter 
MouseOther
MX-580 or Razor bluetooth something or other Docking station 40A50230US 
CPUMotherboardRAMHard Drive
i7 3770k BIOSTAR TH67+ 32gb 4x8 Corsair Vengence 1600 1x 256gb m2 
Hard DriveOSPowerCase
6x Seagate 2.5" 3tb > ~8.5tb raid 10 OpenSuse Seasonic G 550w Silverstone SG11B 
Other
Raid card 
  hide details  
Reply
P50
(15 items)
 
   
CPUGraphicsRAMHard Drive
Intel Core i7-6700HQ NVIDIA Quadro M1000M 4GB Gskill 32gb 4x8gb DDR4 2300mhz Samsung 850 PRO - 1TB SSD m2 
Hard DriveOptical DriveOSOS
Seagate 2TB w/ 128MB Cache (ST2000LM007) Pioneer External USB-C Blu-Ray Burner Fedora 25 Win 10 LTSB 
MonitorMonitorMonitorPower
15.6" 1920x1080 IPS BenQ GL2460HM 24" LED BenQ GL2460HM 24" LED Lenovo 170w Power adapter 
MouseOther
MX-580 or Razor bluetooth something or other Docking station 40A50230US 
CPUMotherboardRAMHard Drive
i7 3770k BIOSTAR TH67+ 32gb 4x8 Corsair Vengence 1600 1x 256gb m2 
Hard DriveOSPowerCase
6x Seagate 2.5" 3tb > ~8.5tb raid 10 OpenSuse Seasonic G 550w Silverstone SG11B 
Other
Raid card 
  hide details  
Reply
post #3 of 11
You could try resetting the CMOS using the button on the motherboard, and if this doesn't work you could remove the battery a couple of minutes.
post #4 of 11
Thread Starter 
I tried resetting CMOS, didn't help. I also was able to overclock through the BIOS before, but I read good things about this utility and wanted to give it a shot. Will pulling the battery fix it if the BIOS was flashed incorrectly? I was under the impression that it just cleared BIOS settings. Still, I suppose it couldn't hurt to try. Am I correct in thinking that this isn't a problem, or is at least unlikely to be a problem, with the CPU, since it was running earlier?
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
post #5 of 11
Quote:
Originally Posted by Greensystemsgo View Post
reset bios. pull on board battery and pull power plug and wait a couple minutes. dont use software applications to overclock your processor, only use software for graphics cards.

Overclock cpu in your bios screen. you should still get image but it wont post or maybe even nothing at all until you do this.
The above response is right on the mark. Not much more to recommend except that if you continue having issues with this BIOS rev. I would suggest wiping out this troublesome BIOS and revert to the one you were using before. In a perfect world updating BIOS should be cake and normally is. But the pros I know do not bother updating BIOS if all is well. That is unless a substantial gain in performance or a resolved compatibility issue can be had.
post #6 of 11
Thread Starter 
Just pulled the battery. No luck. I connected the system speaker and removed the videocard and memory to see what would happen with just the CPU. With everything else disconnected, I get one long beep and two short beeps repeated. If I insert memory, I've tried both sticks, or one at a time, in the right slots, I don't get any beeps and sometimes the system will reboot endlessly. Any ideas?
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
post #7 of 11
Are you sure you flashed the correct BIOS?

How did you reset the cmos?
The correct method is to power off the system, unplug the PSU or turn off the PSU rocker switch, to cut ALL standby power to the board, then move the CMOS jumper to the clear position for 30 seconds, then move it back, and power everything back up. If there is a more convenient CMOS button instead, then pressing that for five seconds also does the trick.

Anyway, if you did, though this bricking of your motherboard is precisely why i *NEVER* *ever* flash a motherboard BIOS in windows. The most I do is download the updates in windows. I always use a good old MS DOS Boot disk (in this case, a USB flash drive; used to use floppies before this build).

Even the BIOS ezflash program is much safer than flashing a BIOS in windows.

You need to RMA the board. And for the future, all motherboard and video card BIOS updates should always be done with a command line DOS flasher whenever possible, unless no such flasher exists. It's just safer and saner, that way.

Also, flashing in DOS allows you to power off the board after the flash is complete, then immediately clear the CMOS with the power supply unplugged, by moving the CMOS jumper to the clear position for 30 seconds.
(Some people have bricked their boards after flashing, by NOT clearing cmos, and restarting the computer, and then resetting it *AGAIN* before it's even fully loaded the BIOS...)
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
post #8 of 11
Thread Starter 
Quote:
Originally Posted by Falkentyne View Post
Are you sure you flashed the correct BIOS?

How did you reset the cmos?
The correct method is to power off the system, unplug the PSU or turn off the PSU rocker switch, to cut ALL standby power to the board, then move the CMOS jumper to the clear position for 30 seconds, then move it back, and power everything back up. If there is a more convenient CMOS button instead, then pressing that for five seconds also does the trick.

Anyway, if you did, though this bricking of your motherboard is precisely why i *NEVER* *ever* flash a motherboard BIOS in windows. The most I do is download the updates in windows. I always use a good old MS DOS Boot disk (in this case, a USB flash drive; used to use floppies before this build).

Even the BIOS ezflash program is much safer than flashing a BIOS in windows.

You need to RMA the board. And for the future, all motherboard and video card BIOS updates should always be done with a command line DOS flasher whenever possible, unless no such flasher exists. It's just safer and saner, that way.

Also, flashing in DOS allows you to power off the board after the flash is complete, then immediately clear the CMOS with the power supply unplugged, by moving the CMOS jumper to the clear position for 30 seconds.
(Some people have bricked their boards after flashing, by NOT clearing cmos, and restarting the computer, and then resetting it *AGAIN* before it's even fully loaded the BIOS...)
I did flash in DOS. Didn't clear the CMOS immediately afterwards tho. Didn't know you were supposed to, it wasn't mentioned in the manual. I did completely power down everything when I cleared the CMOS, I tried using the jumper method, but that didn't help anything. In order to remove the battery, I had to take everything out of the case to remove the Thermal Armor on the Sabertooth P67, which was a major pain in the ass, and so it was definitely powered down. Probably going to have to RMA the board...
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
post #9 of 11
Oh....it seemed like from your description that you flashed directly with AI suite/Asus update (as I know that's possible, and there's some option to "allow bios downgrade" in it).

This is the first time I've ever seen a board get bricked from a DOS flash, unless the firmware were bugged. Most of the problems I saw previously were from windows flashers.

The one time I forgot to clear cmos after a flash (because I arrogantly thought it wasn't necessary anymore), I had my PCIE running at X8, unless I ran the BCLK over 100.0....(Clear cmos fixed that).

Sorry about the RMA.

If you flashed in DOS, then this brick should be happening to other people as well. Did you check the Asus forums for more information? I'm particularly concerned since I was going to buy this board for a friend...(and if you have to remove the armor just to get to the cmos jumper... :/)
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
post #10 of 11
Thread Starter 
Quote:
Originally Posted by Falkentyne View Post
Oh....it seemed like from your description that you flashed directly with AI suite/Asus update (as I know that's possible, and there's some option to "allow bios downgrade" in it).

This is the first time I've ever seen a board get bricked from a DOS flash, unless the firmware were bugged. Most of the problems I saw previously were from windows flashers.

The one time I forgot to clear cmos after a flash (because I arrogantly thought it wasn't necessary anymore), I had my PCIE running at X8, unless I ran the BCLK over 100.0....(Clear cmos fixed that).

Sorry about the RMA.

If you flashed in DOS, then this brick should be happening to other people as well. Did you check the Asus forums for more information? I'm particularly concerned since I was going to buy this board for a friend...(and if you have to remove the armor just to get to the cmos jumper... :/)
The CMOS jumper is not underneath the armor, but the battery is. I looked at the ASUS support forums, but there wasn't anything mentioned, suppose I'll post there and see what they say.

Thanks for all the responses everyone.
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
X-Creed
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k ASUS Sabertooth P67 Palit GTX 560 Ti 2Gb 8GB G.Skill DDR3 1600MHz 
Hard DriveOptical DriveOSKeyboard
2x Seagate 1TB in Raid 0 LG BD-RE Windows 7 Ultimate x64 Logitech G11 
PowerCaseMouseMouse Pad
OCZ 1250W Cooler Master HAF-X Cyborg R.A.T. 7 Rocketfish 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › Why did updating the BIOS cause CPU problems?