Hello,

I am setting up a DQ77MK with an E3-1230V2 as an ESXi host.  I am using a PCI video card, Radeon 7000.  Bios is 058.  I was playing with bios settings but didn't get a stable system, so I loaded default bios settings.  After that, I managed to install ESXi  on an Intel 525 mSATA 30GB SSD.  Upon reboot, I got the two beeps twice.  Video card issue. I tried a bunch of trouble-shooting tips and always received the two beeps twice.  I installed a Core i3-3225 and that got me into the bios.  The event log showed:  "Video OptionRom authenticate fail", with 13 count.  What to do?  shouldn't this board boot, even without video, keyboard and mouse connected?

A couple of items I suspect based on my research, 1: Intel TXT? disabled. and 2: UEFI boot vs legacy boot?  (Both are enabled)

Anyone see an issue like this?  I need to use the Xeon because of Vt-d support.

Thanks.

Hello,

I had managed to install ESXi 5.1 on the specified system.  Upon reboot, I got the two beeps, two beeps code.  Which means video card failure.  I installed a Core i3-3225 and managed to boot into bios.

The event log showed the message "Video OptionRom Authenticate Fail" Note, I am using a PCI video card, Radeon 7000.

Can anyone shed some light on this?

Thanks.

Hi,

I have a new replacement of a defective D2500CC motherboard. It was explained in this thread:  D2500cc : strange tic-tac sound in off

This new motherboard was working right 2 days, and then suddenly the first LAN was not recognized. Now inside the BIOS there is not Lan1 mac address in the section "System Information".  Just there is the MAC address of the Lan2

In Linux, I have this error:

e1000e .... : The NVM Checksum Is Not Valid

e1000e: .... failed with error -5

in the Lan1 connector of motherboard there is one green light active, so I believe still is alive.

And also I can see the device in the SO: 

# lspci -vvvv | grep Ethernet

01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

I'm reading many informations about the problems with 82574L, in example:

e1000e interface hang on 82754L

Unbricking an Intel Pro/1000 (e1000) network interface

although I'm not an expert at all. If I understand well, maybe the EEPROM was deleted or damaged.  That's right?

- Is there some way to restore my LAN device?

- Is there some easy guide to flash a new LAN firmware from an USB boot to solve this issue with Linux?

Please, give me some support to know the right way to solve this. Or to know the right firmware to download and the procedure to fix this error.

I'm reading tons of informations around this issue, and I don't know exactly the right thing to do.

thanks

DQ77MK (0058)

Network driver 18.1

Windows 8 64 bit (uefi mode)

Will flashing DH61WW (AA: G23116-206) with BIOS 0099 up from 0044 still give me support for i5-2320 processor?

When I flashed from the original 0038 to 0046 it gave me the message "Unsupported Processor" at powerup time (and prevented the OS from loading).

Then I had to go through the complicated recovery procedure back to 0042 (because 0038 was not available to end users) which gave me Management Engine version 0.0.0.0 and an unusable board, until at last, by trial and error on version numbers, I was able to flash 0044 using the recovery procedure, so that the i5-2320 processor was recognized and the motherboard was functional again.

Now I want to correct the PS/2 keyboard issue that 0113 corrects but per the 0113 instructions I have to flash 0099 first.  However I am afraid that if I upgrade to version 0099 I will lose processor support again (since it happenned to me every time I tried a BIOS which had the 3rd Generation Core Processor Support Warning on the Relase Notes.pdf).

Can someone from Intel please confirm this, I hate bricked motherboards because they (1) force me to buy another Windows license, (2) make me think of not buying the same brand of motherboard again.  Thanks in advance,

Miguel

Hello,

I would like to build a HTPC based on one of the above MB's therer does not seem to be any Video/Graphics Windows 7 ^$ bit drives.

Does this mean these boards don't supprt Windows 7 64 bit or will the 32 bit drives work?

Many thanks

Hi,

Having fun with these boards....

On the build I've actually got working I have a CPU fan, and front & rear case fans but no aux.  The rear fan is an Arctic Pro F 3 pin, temp controlled jobby, the front, a standard 3 pin and the CPU is an Arctic Cooling Freezer 7 Pro Rev.2 PWM.

On boot, it stops at a message about the fans not working or missing.  I've looked in the BIOS but can only find settings to adjust temp thresholds etc, rather than being able to satisfy the board that all is OK.

I tried putting another fan on the aux, but that didn't help.

Incidentally on my other DP67bg build (with the RAM issues), when that boots, with only CPU & rear fans attached, there is no message.

Presumably there is a setting in the BIOS somewhere that I've missed.  I would greatly appreciate some advice on how to sresolve this.

Thank you.

sorry for the errors, i am not speak english, i have a big problem with a DH61BE board that i bought 3 month ago. When i bought the board the first thing i do was to update the bios to 099 revision, then the usb 3.0 ports had an intermittent disconnection but, this bug was fixed by the renesas 2.1.28.0 driver update. So, later i updated the bios again with de 0109 revision and with this, the intermittent disconnection with the usb 3.0 ports come back again, forever. I have tried many many many kinds of fixes but nothings works, this is the history of my solutions:

1- I have updated to 0111 and 0113 revision

2- I have updated to the last driver/firmware of renesas.

3- I have cleared de cmos/bios.

4- I have worked with energy options in control panel

The disconnection is whithout a time rule, mostly when the pc is turned on, woken from a sleep state, and in longer periods of inactivity of usb 3 ports (3-4 hours)

Please, i have only 25 hours of internet connection, i have suffered this bug for 4 month, there is no warranty in my country, im cuban and to buy a board again is very difficult for me, i will appreciate any kind of suggestion for this problem, waiting help at every minute, Richard

when I install windows 8 on my new DZ77GA-70K I get BSOD CLOCK_WATCHDOG_TIMEOUTS when I shutdown or restart. it happens when installing windows 8 to. I can install windows 7 with no issues at all. This is a replacement board. The first DZ77GA-70K did the same thing. It would run windows 7 with no issues. But windows 8 will not.

I am using the newest BIOS. I'm thinking maybe there's a BIOS update that fixed this issue that I can download and install.

my system

1. Mainboard: DZ77GA-70K

2. Memory: Corsair Vengeance CMZ8GX3M2A1600C9B

3: Video Card: EVGA Geforce: 670.

Over the past year, I have built 6 systems running SCO OpenServer 6.0.0  using this board,  However, the latest two boards do not work.

The microcode level is 28, and the AA numbers end in 207, and the BIOS is rev 110.

The problem is that after the system boots, the display is corrupted.  I believe that the operating system is written using 7 bit ascii, but the display shows characters with values from 128 to 255, instead of 0 to 127.

My question is, can I resolve this by reverting to bios revision 44 (used with AA -206, and microcode level 26)?

As the title states I found the root cause of all the misery and agony that DZ68BC users have been encountering with the 003X BIOS.

The root cause is the Intel Management Engine Version.

Initially the DZ68BC was designed to run only one version and that was the Version 7. which works pretty well. Then Introduction of 3rd gen had them Include Version 8 in the BIOS file and by doing so lead to the problems encountered with various versions of the 003x BIOS.

The issues arise coz the BIOS files carry two versions of Intel ME which are 8 & 7, the initial ones did not have both versions in the BIOS files they had only one version hence there were no issues.

I will not go into details of various methods that lead me to this conclusion, unless if any one wants please reply in the thread and i will explain.

DZ68BC Boards that I have tested versions 403 and 402.

The simplest answer and conclusion is Intel should compile 2 separate BIOS files for the DZ68BC

1. For people with 2nd Gen the BIOS should only have the Version 7 Intel ME

2. For people with 3rd Gen the BIOS should only have the Version 8 Intel ME

eg the 0039 BIOS should be two (0039 2nd Gen) and (0039 3rd Gen)

The problem arises when the two are present, and the board cant determine correctly which to install depending on scenario of the set up.

eg If you are to install a 3rd gen you need to have 2nd gen to update then while updating the BIOS the Intel ME stays at the V7 instead of moving to V8 then when you instal 3gen CPU it works but the system becomes unstable mostly with the 0035 BIOS, if you update from 0035 to any 003x or run recovery with same BIOS it moves to V8 the instability is gone but you get Intel ME and PCH issues and if on the 0035 Overclock issue on it.

So its either Intel Complies 2 BIOS for the Board or 1 that has only Version 7 of the Intel ME and they should forget about the Version 8.

Intel PLEASE RESPOND TO THIS acknowledge by also producing a BIOS UPDATE

I just bricked my DZ77GA-70K after the setting some option in my brand new 0057 BIOS...

s

I'm usually booting using UEFI to Windows 8 system with success, previously with the 0053 BIOS.

After upgrade to the 0057 BIOS I noticed the Legacy Boot checked along with the UEFI boot checked. I decided to disable legacy boot and remove the USB and optical boot to reduce my boot time. I didn't touch to the new secure boot feature.

On reboot, no video output and two beeps :'(

I tried all the recovery methods: Back2BIOS button, configuration mode jumper (2-3), recovery mode jumper (no jumper at all), and removing the battery to clear CMOS all the night without AC cable. All attempts were unsuccessful.

My attached devices :

USB stick FAT 32 formatted (my usual BIOS upgrade stick) with only the brand new 0058 .BIO file on it, on the first yellow USB port, no other USB device attached (no mouse, no keyboard)

One DDR3-RAM stick (i switch between 4 ones to be sure one is not causing problems)

My steps with BIOS recovery mode (jumper removed) :

1. power on

2. status 31 : my usb stick is flashing

3. one beep

4. status 92 : two beeps, twice

5. status EA -> 77 -> 40 -> 42 -> 44 -> 48 -> 4A -> 4B -> FE (???), seems the last status (I waited 5 minutes)

6. reset button

7. status 15 -> 14 : three beeps, looping

8. reset button

9. status 15 -> 14 : three beeps, looping

And of course absolutely no video output...

I tried Intel Support by chat and the guy suggested me returning the MB to the reseller under warranty.

You really think that could happen only with setting a bad option in the BIOS ?

But... aren't all these recovery methods supposed to repair that ?

What there purpose if they all failed at restoring this setting ?

I switched from ASUS motherboards to Intel because I wanted serious work on hardware and BIOS level, and I'm really disappointed...

If you can help me, guys, I'll be very glad.

Geoffrey

Hopefully I'm in the right place. 

I put together a new computer today and everything was going well until when installing Windows the monitor went blank.  I thought hopefully it was a fluke and reformatted hard drive and re-installed.  Windows installed!

I started installing drivers from Intel's website for the motherboard.  I installed the correct display driver for my system and after booting up from restart the computer freezes and the monitor shows a screen full of dark red, fuzzy rectangles. 

I uninstalled driver and everything works fine again except obviously the display has a very low resolution.  Tried re-installing same driver-same thing.  Tried installing the WDDM driver-same thing. 

Also, I cleared CMOS and made sure all wiring is correct.

So I'm thinking its a display driver issue.  Any thoughts?  Is there a generic driver that could fix this?

Mobo- Intel DZ77SL-50K LGA 1155

CPU-  Intel Core i5 3570K

Monitor- Acer  (can get exact model tomorrow)

Connecting monitor to mobo via HDMI.

MB: Intel DX79SI

CPU: Intel i7 3930K (socket 2011)

PSU: Corsair CX600 (600 W)

Graphics: Gigabyte GeForce GTX 650

RAM: Corsair Vengeance 2133 mhz  4x16 GB

Fan: Intel Thermal Solution RTS2011AC

I have just bought these components, except the RAM and the PSU. First I assembled the computer with all the components, the computer started (the fan lights up blue and spins), but I noted I didn't got any picture. I also noted that I didn't get any information on the digital number display on the motherboard. The beeper didn't give any sound information.

I have then tried to take the RAM and hard disk drives away from the setup. I have also taken out the motherboard from the computer case and placed it on the outside to avoid eventual shorts. If I don't have any RAM memory or graphics card in the setup, I guess I should get warning information from the beeper, but I don't get any.

* If I have the graphics card assembled in the setup, with or without RAM, these LED:s are lightened up on the motherboard:

http://i42.tinypic.com/kqc7b.jpg

The LED to the very right is red, and the LED left of the red one is green. The number display doesn't show anything and the beeper is quiet.

* If no RAM and no graphic card is assembled, the LED:s will now light up differently. The LED to the very right is not lightening up anymore, but the LED left of it is still green. And, without the graphics card the CPU fan will now spin much faster. However, still no info from the number display and the beeper is all quiet.

* If the setup is the same as the last one, no RAM and no graphics card, but I switch to an older PSU which I have, a 520 W which I use on my old computer setup (Intel i7 920, Gigabyte motherboard), then again the LED to the very right will light red and the LED left of it will light green (like on the example picture). No info from the number display, and the beeper is all quiet.

I have tried many different situations, like take the motherboard battery away in a couple of minutes, or update the BIOS by putting the latest .bio file on an USB stick and start the computer with the USB stick inserted (after taken the BIOSCFG jumper away). Nothing seems to help. I have also tried another graphics card (NVidia GeForge 8600 GTS).

Which ideas do you have about where the problem is?

Hi,

I am trying to find the physical connector specification of the eDP connector used on the DQ77KB.

Table 32 in the technical manual states "40 pin eDP Connector" and gives the electrical pin out.  What is the manufactuer/part no of that connector?  Is anyone aware of any off the shelf open ended cables or know of a supplier for made up cables for this board?

Best regards,
David.

I like the DN2800MT motherboard support eDP and LVDS bus interface; I seen the documentation showing the connection and the pin out and can't find any word of the panel side? Which include eDP and LVDS sink devices? Especially I am very interesting in eDP sink device and I like to know which vendor has such product available to be paired with DN2800MT as completed system?

Regards,

Jack Hsieh

I am sick of being dumped on by Intel every time I try to udate the BIOS on for the DZ77BH-55K motherboard.

I decided to update my BIOS to improve the way Visual BIOS performed with a Wireless desktop.

So I updated to Ver. 0099 from 0083 and my PC would not get past post when I booted!!!!

I removed the Digital TV Tuner card and hey it booted.  Replaced the card and the PC refushed to boot. In Ver. 0093 there is a fis "Fixed issue where TV Tuner card is not recognised" It's now recgnised and refuses to boot with the card installed - GREAT JOB INTEL!!!!!!!!!!

I went back to Ver. 0083 and it boots with the  Digital TV Tuner card in place, no problems.

This board has had more issues than any other I have ever had.

My suggestion is the Intel Engineers responsible for the DZ77BH-55K get their heads together and read the other 1,000,000 posts on and off this site about the board and FIX the issues properly.

Hi I've just joined the forum and request some help with an issue I'm having with this motherboard.

I've almost completed building a system using the following components:

Intel DQ77KB

Intel i5-3470s

G.skill 8gb ddr3 1333mhz

Samsung 840 120gb SSD

Samsung SH-224 DVD Writer

PA-1181-02XX 180w 19V Power adapter ( as recommended in the Intel thin Mini-ITX Component Catalogue 1H,2013)

Lian Li PC-Q11B Case.

As I'm still building the PC, I'm constantly in and out of the case and sometimes have to unplug all the cable including the power cable.

Unfortunately when I reconnect the power cable the PC immediately turns on (without me having touched the power button) with one of the following messages:

The following are warnings that were detected during this boot.

These can be viewed in setup on the events log page.

Warning : CMOS Battery Failure

OR

The following are warnings that were detected during this boot.

These can be viewed in setup on the events log page.

Warning : CMOS Battery Failure

Warning : CMOS Checksum Error

Warning : CMOS Time Not Set

The end result is that the bios is reset and the time reverts to it factory defaults. All settings are lost.

My biggest concern is that the AMT vPro settings which I've painstakingly input for remote KVM will be lost in the event the client accidently turns the power switch off or if there is a general power failure.

Once I've reset all bios settings and as long as the power cable isn't removed everything is fine, the PC boots up and shuts down as expected.

Please help!

Any ideas what could be causing this problem?

Thanks

Chima Madujibeya

I'm sure like most of you, your USB 3.0 ports are not working under Windows 8.  When I saw the firmware updates dated 5/9/2013, I thought finally.  Well after installing the update I can say they still don't work.  I install both updates, front and rear.  The front update processes fine...and those ports may work, but I don't have them hooked up.  The rear update throws the message Device not found!

Any help to get this working under Windows 8, would be much appreciated.

Regards...

Hello,

I am a generally-happy owner of the DZ77SL-50k motherboard with a PCIe graphics card used as the primary display adapter. A few days ago I attempted to enable General Optimisations in the BIOS boot configuration, as a result of which action the system has ceased to recognise the graphics card - and neither disabling this option nor even resetting the whole BIOS configuration to default values has helped. See below for more details. I will be very much obliged for any assistance with this, as I have pretty much run out of ideas.

More configuration details:

Originally BIOS video settings were "use the PCIe card as primary but keep internal graphics enabled", two DVI monitors connected to the external card and nothing connected to integrated HDMI (haven't got this two-card set-up working yet).

Exact symptoms:

After powering on the computer the computer produces the "two beeps, then two beeps" sound and blinks the power LED, while both monitors connected to the PCIe card remain in power-saving mode. The system then proceeds to boot and once video control has been passed from UEFI to the Linux kernel both PCIe monitors do come to life, although it seems the card is not in entirely normal state because X.org fails to detect it and therefore doesn't start.

If I connect a display to integrated HDMI while leaving the PCIe card that one shows nothing as well. It does work fine if I remove the PCIe card. Come to think of it, I had better check what happens if I leave the PCIe card in but force integrated graphics as primary in BIOS configuration.

If I switch the BIOS Configuration jumper to maintenance mode, the problem magically disappears - both PCIe displays come up the moment the system's powered up, no error beeps occur and and if I tell the system to boot, everything up to and including X.org starts up fine. However, switching back to normal mode makes the problem reappear.

Switching the jumper to recovery mode doesn't seem to help.

Let me know if you need any more information.