Also staff, I've tried doing downgrade since I can't tell BIOS to look at USB first or anything I can't. I've spent 3 hours so far trying to figure this out so you can see that the more I mess with it the more I get mad.
Sorry to hear you've been sucked up to this loop of mess by the slew of bad BIOS produced by Intel, anyway all the BIOS from 0035 and above are full of issues and trouble, its like Intel decided to abandon us on the pages and pages of reported issues about the DZ68BC, there are many posts about issues with this board and 0035 all the way 0042 BIOS.
I still hope Intel will fix the issues but its been years now maybe 3 or more and they have done nothing to help the many customers who bought the DZ68BC, I mean how hard can it be to fix this issues, I'm willing to put in work for Intel and head a team that can produce a BIOS fix for Intel though I'm no pro in codding.
Just to help you I've been in this situation and you will have to run recovery mode.
- Remove the BIOS jumper
- Insert a USB or DISC with the BIOS eg 0039.BIO
- Switch on the PC and it should locate the BIOS and revert back to 0039 version.
0039 is where you want to be at the moment its far from stable but its better than the other 003x or 0042, its unfortunate there is no way to revert to the 002x BIOS those were the last stable BIOS for this DZ68BC, 0028 was the last stable BIOS.
INTEL PLEASE HELP WITH THIS ISSUE
I know what you will get from support is that the DZ68BC is EOL (End of Life Support) for quite sometime now, but we should not take that and shut up because the slew of BIOS updates that brought with them problems come before EOL.
Yeah, with a clear head this morning I tried doing the 0039 and I can boot up to Windows now. I can say the media side of me wants to write one big post about Intel. I write about video games and etc. I've NEVER had an issue like this and with a problem like this it tells me Intel is only caring about the money that comes in. Though CS EARLY this morning ran me through the recover, but kept telling me 0042. After research I found 0039 and tried it and it worked. Glad I have a laptop near by. >.<