***Official***Z68X/P67A-UD7 Club/Discussion/Info**

[Falkentyne]

Unfortunately for me the new 7b BIOS did not fix my boot loop issues on my P67A-UD7-B3 board. After shutting down and restarting two of three times I got boot loops. I am back on F4 and have never had boot loop issues.

Infinite boot loop or overclock failed message (after three restarts)?

[stasio]

Z68 series new beta BIOS updated (and P67-UD7/UD5).

[Kent10]

Is that using shut down button within windows? Or using reset button on your case?

When you tried the new BIOS did you tweak your settings to get stable, before saying it doesn't work? You can't always use the exact same old BIOS settings between versions, so you need to test for stability before you decide.

And of course be sure you start by loading optimized after the flash, then save/apply/reboot back to BIOS to make all changes you need to make. Clearing the DMI pool while flashing is also suggested.

Great to hear F4 works for you though, at least you do have a BIOS you can use so that's a plus

Yes shut down within Windows 7 64 bit. Whenever I shut down the computer I usually get the boot loop with anything after the F4 BIOS. It doesn't loop all the time but probably half the time. What happens is it starts loading the BIOS for a few seconds and then it shuts down and then loads the BIOS again and then usually starts normally. I think there were some times that it would start a 3rd time but usually not.

No I did not do any tweaking of my settings. I did use exactly the same settings. I can't say for certain if it is stable because I didn't do any stability tests but once it boots I have never had any crashes due to instability. Also I tried it with optimized default settings and no overclock. The only settings I changed were to AHCI and disabling my sound.

Hmm I did do the optimized settings but didn't reboot before making changes. I may do that next time if I try the new F7c I see released. Also I didn't clear the DMI pool. I am not sure what that does but will research it. Yes F4 has been great for my OC of 4.7. Never had any problems with it. Thanks for your help! I appreciate it.

[Kent10]

Infinite boot loop or overclock failed message (after three restarts)?

It reboots usually a 2nd time only. It is not infinite though I have had a couple of those when testing my OC. I get no OC failed messages and my settings are never reset when I get the restart. Thanks for your help.

[Kent10]

One other interesting thing happened when I updated the BIOS. I lost the use of one of my USB ports. It took a while to figure out that if I unplugged the power supply for a couple minutes I had it back. I know some suggest doing this after a BIOS update and also clearing the CMOS on the motherboard. Maybe that would be better than just loading optimized defaults from the BIOS.

[stasio]

Did you update Backup BIOS?
CPU PLL Overvoltage Enabled or Disabled?

[Kent10]

No. I didn't do that this time because I did when I tried the F6 BIOS and still had the same problems. If you think that might make a difference I will do that when I try F7c. Do you know what the changes were for F7c. Thanks for the suggestion.

[OC Nub]

@ Lsdmeasap

Glad to see you posting again in the Gigabyte threads, we all benefit greatly from your support!

[acebmxer]

@Kent10 when flash it is suggested to always clear dmi pool and load optimized defaults after flash.

This will ensure not lefter over settings from old bios get left behind and all correct default settings are set for new bios.

@stasio or LSD any chance to get Gigabyte to change the default in q-flash to clear dmi pool? As most users either dont see it or just leave things at default.

[Kent10]

OK Thanks, acebmxer. I'll do that next time I flash.

[Lsdmeasap]

Ya Kent10, please be sure to do that when you flash! When you flashed this last time, did you see the Intel ME firmware update running at the top of the screen during the flash? If not, that may be why you still have issues, although it doesn't quite sound like you are having boot loops anyway though, maybe just a little

@ Lsdmeasap

Glad to see you posting again in the Gigabyte threads, we all benefit greatly from your support!

Thanks OC Nub, your thoughts are very much appreciated!!

@stasio or LSD any chance to get Gigabyte to change the default in q-flash to clear dmi pool? As most users either dont see it or just leave things at default.

Ya, I'll pass along the request, and I'm sure Stasio will too once he see this. They may not want change it because they might leave it set to keep DMI for people flashing that don't know what they are doing and may need to keep previous settings.

We know that's not a good way to do this, but I bet that's why they have it set that way.

[Falkentyne]

LSD: there was *NO* intel firmware update that appeared at the top during the last two bios flashes (F8B and F8C) on the UD5. Unless it "silently" flashed it or something. Are you sure there was a ME update for the ud5/ud7 boards? I think it was only assumed there was, since there was one for the Z68 boards.

BTW any changelog on the bioses stasio just posted? Pretty quick for another beta (just 4 days?)

[stasio]

LSD: there was *NO* intel firmware update that appeared at the top during the last two bios flashes (F8B and F8C) on the UD5. Unless it "silently" flashed it or something. Are you sure there was a ME update for the ud5/ud7 boards? I think it was only assumed there was, since there was one for the Z68 boards.

BTW any changelog on the bioses stasio just posted? Pretty quick for another beta (just 4 days?)

How can be 4 days?
I think is more then 2 weeks and no changelog yet.

[Falkentyne]

Hmm, you're right. I only remembered the vacation until the 1st...forgot they released a bios before that...

[Kent10]

Ya Kent10, please be sure to do that when you flash! When you flashed this last time, did you see the Intel ME firmware update running at the top of the screen during the flash? If not, that may be why you still have issues, although it doesn't quite sound like you are having boot loops anyway though, maybe just a little

Thanks again for your continued help. I will clear the DMI Data Pool next time. I think I have the latest ME firmware but I am at work now and can't say which version. I seem to remember it was the same as included in the new BIOS.

I did not see the Intel firmware update running at the top because I am embarrassed to say I used @BIOS to update. I know I should be using Q-Flash but I have not been able to get my USB drive to be recognized. I have tried several USB drives and they are all FAT32 formatted. I have done lots of reading trying to get it to work and the only thing left that I could see is be sure I shut down the computer before inserting the drive. I thought I had tried that but now sure now, maybe I just restarted each time. I have used dedicated USB ports on the back of the computer and tried several. I would sure love to get it to work. I'll try again when I have time to try the F7c BIOS.

[sin0822]

you made sure the drive is in a USb 2.0 port? not the blue ones?

[Kent10]

you made sure the drive is in a USb 2.0 port? not the blue ones?

Thanks sin. I thought I tried various slots including USB 2.0 but I will confirm next time I try.

[sin0822]

yea try it, also you are doing it through the BIOS utility right? you aren't trying to do the boot up DOS or anything?

[Kent10]

yea try it, also you are doing it through the BIOS utility right? you aren't trying to do the boot up DOS or anything?

Right. I have tried accessing Q-Flash from the BIOS and also using "end" before it enters BIOS. Not from DOS.

[Falkentyne]

My "Rift" 8 GB USB drive is recognized in DOS and Bios in all of the USB ports.
I forgot if my kingston 2 GB drive is recognized in all, I think it's only recognized in four ports, and a third party microsdhc reader with my nintendo ds flashcard is only recognized in two ports in Bios when trying to boot through it (but oddly enough, the bios SEES it in all the ports), but all ports in windows.

You need legacy USB support and legacy storage support enabled, btw.

[Kent10]

I still couldn't get the USB drive to be recognized in Q-Flash. This is what I tried. I always shut down the computer and installed the USB drive in the back of the computer in a yellow USB 2.0 port. I tried 3 different ports (1 was a combo esata/USB) and I tried 3 different USB drives all formatted in FAT or FAT32. I accessed Q-Flash each time by pressing F8 in the BIOS. I also made sure USB Legacy Function, USB Storage Function and USB controllers were enabled. I may look for another USB drive to try but I can't think of anything else to try. I assume it doesn't matter what is on the drive. Thanks for the help, everyone.

[acebmxer]

If you still have no luck with USB flash drive, you can also try burning the bios to a cd, a old spare hdd, or a floppy if the board supports floppy.

[Kent10]

If you still have no luck with USB flash drive, you can also try burning the bios to a cd, a old spare hdd, or a floppy if the board supports floppy.

Thanks good idea. I might try the CD or a USB hard drive. Something has to work.

[acebmxer]

If using a internal hdd or usb hdd make sure its in fat or fat32 to be seen by q-flash.

[Kent10]

I got it to work!! I tried a 4th USB drive and that one worked. It is a Sandisk. I really don't understand why the others work fine in Windows but not the BIOS. I didn't update the BIOS yet because I don't want to spend the time right now. But I will give it a go some time. I bought one of the new Intel 520 240GB drives so I will install that first. Thanks for everyone's help. USB and Q-flash have been driving me nuts for years. No more @BIOS.