There is already the 0043 BIOS available. You could try that and report back!
actually I already did that.--> edited the message header to reflect bios 042-043
After a first few reboot cycles, usb3 seems to be working again (with fast boot), but it's not thursday yet, need to keep an eye on it.
However, WOL still doesn't work. Is there a hidden BIOS setting somewhere, that needs to be set (like power the eth.or disable some other device..).
Wol is working on all my boards (incl other intel), some of which have the same chip.
What exactly is WOL?
I remember having an issue while on 0032 BIOS, the system couldn't boot when boot from USB devices was also enabled. I had to disable this option in order to be able to boot. With 0040 and 0042 BIOS update this problem was fixed. Does the 0043 BIOS update affect the system in any other way? Hopefully is not Overclocking affected again... Should I do it or not? My USB 3.0 ports seem to work fine from the first moment that I bought the board. I do personaly haven't used the fast boot settings so I can't say anything on that.
Is there anybody else who has performed the BIOS update and can share his opinion with us?
Well since the BIOS updates change the board's devices behaviour, it is not impossible that other things work and others do not. I have met this in other non-Intel BIOS updates too, like Asrock or Aopen.
1 of 1 people found this helpful
WOL = Wake On LAN
It allows you to wake up a PC that's sleeping (S3/S4) or off(S5) by sneding a 'magic packet over the LAN.
Of course your Pc needs to be configured appropriately to allow that. All my Pcs have that and actually I never had any problems with it in the past for at least 6 years or so.
So either there is some new or hidden setting in this board/Bios that I missed or it's broken.
- I reset BIOS to defaults
- I reapplied BIOS 043 with the recovery method
- Reapplied the few changes I require (fast boot, disable a few USB ports, disable CIR)
- Booted a few times and cycled S1-S3
Now USB3 and Wol are working as expected.
For Me this issue is resolved.
Is everything else working properly (including overcklocking)?
Sorry, I don't believe in (do) overclocking, so I have no idea. TBH, I was kinda grateful that the 'basics' are working and that the bios upgrade didn't brick my board like the previous one.
Apart from from disliking overclocking in general, IMO this board isn't really meant for that. More a mild technology DEMO of overclocking gently here and there maybe.
Well, you know, just want to know that everything is fine. I am not the overcklocking type too, just want to have this possibility of gently overclocking "health" and active. Since there are no complaints about it, I guess that the 0043 BIOS helps our dear DZ68DB be stable and solid.
I have bricked two DZ68DB mobo´s when upgrading the bios, what method would be the safest? Used F7-method when brick occured, previously updated succesfully in Windows. A bit shy to try anymore, currently on bios 0032 with the mobo I got through warranty. Had 0032 and 0040 on the two mobo´s that were bricked.
This is what I did to get from 032 to 042:
- Reset BIOS to defaults
- Use F7 to apply 042
This worked FOR ME, and for me only. I cannot guarantee it will work for you.
However, it seems that 040 BIOS was bad, and 042/043 is better.
From previous Boards I know that the recovery method seems to be the only safe way to also get the ME updated properly.
So I suggest to reset BIOS to defaults and use the recovery method.
That's exactly what I did too.
1) I reset to BIOS defaults.
2) Update the BIOS using the F7 method.
With 0043 on it now, Board performs excellent!
Ok, so should I use F7 or recovery method? Which would you prefer?
And earlier some people suggested that the bios flash boot delay option should be enabled, is it so? If I revert to defaults but enable that?
I really would prefer not to brick this motherboard for the third time..
Message was edited by: Janne H The third time tells the truth: update to 0043 from 0032 was succesfull with above method. Am so happy! Almost lost faith in Intel.. I reset to defaults, didn't even enable the flash delay, used thumbdrive and F7.