Yes, the downgrade from 0070 to 0064 worked for me. See my reply in this thread of May 14, 2012.
Downgraded to 0057. Now I'll just wait to see if any other BIOS updates come up. 0070 is not for me.
The same thing happened to me. The problem was the monitor. I was using a VGA monitor plugged into the display port via an adapter.
I switched to a DVI monitor plugged in to the HDMI port via an adapter and it worked. Since then I've found it will also work with a DVI monitor plugged in to the display port via an adapter.
Also I can use a graphics card plugged into a a PCIE slot.
BIOS update 0083 was just posted by Intel. If anyone dares to try it, please post your results. That is, post your results if your computer still works. Thanks!
The Release Notes doesn't say much. http://downloadmirror.intel.com/21636/eng/BH_0083_ReleaseNotes.pdf
For this update:
Yes I dared to use the new 0083 BIOS and still F2 not working! Not at all!!!
I get the impression that the BIOS development is done in some isolated universe, making changes to maintain compatibility with new hardware and new conventions, but completely detached from the bug reports that come in from the real world. Is there any linkage between what comes up here and the issues that actually get investigated and perhaps fixed? I understand that it can be difficult or even impossible to validate and reproduce reports from the field, and much of the time people blame the hardware for their own dumb mistakes. But it would be a good idea for Intel to at least look at this stuff, especially when the bug reports are confirmed by multiple users.
F2 or F10, etc. wont work for me at the Startup Screen, however after some troubleshooting I got it to work:
When I use my Microsoft Wireless Keyboard 3000 v2.0 it doesn't work (any keys)
If I plug my microsoft wired keyboard in, I can hit F2, F10, etc. and enter the bios
My hardware:
Microsoft Wireless Desktop 3000, which consists of:
Microsoft Wireless Keyboard 3000 v2.0
Microsoft Wireless Mouse 5000
Microsoft USB Bluetooth Adapter
best part is, once in the bios I can unplug the Wired keyboard and my wireless keyboard\mouse work without issue in the bios.
So for some reason Intel wont let my wireless keyboard/mouse hit F2, but in the bios they both work without issue.
Hopefully someone at Intel tries this combo and can figure out what's going on.
Earlier posts claim to have observed that the choice of video connectors have affected this problem, and now you've noticed a difference depending upon the keyboard. Hmmmmm.
I bumped into the problem with BIOS 0070 upon my initial setup. I was using a wired keyboard (don't recall if it was PS2 or USB) and a Radeon 7750 video card, with an old VGA monitor connect to the DVI port with a converter (so I never used the on-board video connectors). At the time, I didn't try alternative video or keyboard configurations; I wasn't aware of any reason those factors might make a difference. I'm not anxious to try that test now, since I'm using the PC for work and don't want to put it at risk.
It's worth mentioning that even the boot-to-BIOS button failed. When in boot-to-BIOS mode, the attempt to boot into BIOS would crash and restart. After this happened 3 times in a row as part of the automated process, it would give up. I reverted to BIOS 0064, and it worked properly.
But the keyboard thing is different. He is using a wireless keyboard and no keys work. I assume that is because the BIOS has no way to communicate with the wireless keyboard.
The problem the rest of us have is the BIOS crashes. The title of this thread is misleading. The F2 key works, but the BIOS setup doesn't.
I think the VGA monitor with an adapter is the culprit. With a good adapter, maybe it would work. Actually I have my VGA monitor plugged into a VGA port on my Radeon 5450 card now and it is working okay. It failed when plugged in to the display port with a cheap adapter.
I'm guessing when a monitor is plugged in to a display or HDMI port, the BIOS asks it what size it is, or something like that. If the monitor (or adapter) responds differently from what the BIOS expects, or doesn't respond at all, the BIOS hits a bug and crashes.
I doubt if a VGA monitor can respond to an inquiry. Especially the one I'm using which is very old. A good adapter may fake a response but I have a cheap one.
Steve17 wrote:
...I'm guessing when a monitor is plugged in to a display or HDMI port, the BIOS asks it what size it is, or something like that. If the monitor (or adapter) responds differently from what the BIOS expects, or doesn't respond at all, the BIOS hits a bug and crashes...
Sure, that's a reasonable line of speculation. But if there were anything like that going on...well, one would reasonably expect that the BIOS team could identify and fix the problem. Except, as I said before, that the BIOS team seems to reside in some isolated universe, completely unaware of, and oblivious to, the problems that real users are experiencing. I don't suppose anyone from Intel would care to step in and suggest otherwise?
If you haven't already done this, you should go to the technical support section of this website, select technical support and then look for the "contact us" option. You can either send an e-mail or use the "live chat" option. Neither will probably provide a direct solution (although I am occasionally amazed) but that will get a real live problem report entered into Intel's internal bug tracking and resolution system.
I don't think the title is misleading; the only key that doesn't work on my 3 keyboards when the system is booting with 0070 or 0083 is f2. Both f7 and f10 work perfectly fine.
I've tried connecting the system directly to the monitor (my Toshiba tv) and through my Yamaha AV receiver. Nothing works. I've even tried with a discreet graphics card to no avail.
So BIOS 0070 and 0083 don't allow me to access BIOS settings at all. When I press f2, the system simply restarts. I re-flashed BIOS back to 0057 and it worked brilliantly. I've repeated this process 5 times today (I can afford to do so because I've a spare DZ77BH-55K).
What in hell's bathroom am I missing here?
rbmorse wrote:
If you haven't already done this, you should go to the technical support section of this website, select technical support and then look for the "contact us" option. You can either send an e-mail or use the "live chat" option. Neither will probably provide a direct solution (although I am occasionally amazed) but that will get a real live problem report entered into Intel's internal bug tracking and resolution system.
I have hesitated to submit a tech support report, in that working with tech support usually requires some degree of validation to be taken seriously. At this point, with a working system that I depend upon, I'm not willing to reflash my BIOS or remove and add devices as advised in order to demonstrate to the guy at the other end that the problem is real and substantial. And I'd guess -- do you think I'm wrong about this? -- that tech support will shrug and mark the report as "closed" if I've got a work-around and I'm not prepared to do follow-up.
I'm not unsympathetic to tech support, because they're stuck in the unenviable position of trying to figure out what's real and what's a user error. Tech support calls are always awkward, and in my experience best avoided unless one is completely dead in the water. (Last year, I had a new monitor which displayed a distorted image. This symptom was visible when the monitor was in setup mode, not attached to any computer. I called tech support (a necessary preliminary to warranty repair), and got asked a bunch of questions about my computer and the video card and the monitor cable. I tried to explain that those factors were demonstrably irrelevant, since the monitor was generating the image internally, but it was difficult/impossible to get that point across. Aargh!)
I might hope that threads such as this on the Intel board, which get discussed and confirmed from a number of independent users, might give developers something they could sink their teeth into.
