Intel Communities: Message List - Still no fixed BIOS for DZ68BC

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Tue, 07 May 2013 00:20:21 GMT

Intel, please help us with this board!

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Sat, 04 May 2013 17:59:47 GMT

Still No Fix, Intel Please Produce a fix, i have been through three DZ68BC Boards Versions 402, 403, 403 and all have same issues with the 003X BIOS

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Thu, 24 Jan 2013 05:14:25 GMT

They are not into building Desktop Boards after 8 Series so anyway they shut down the desktop board department after 4th gen and 8 series boards after that only chipsets and CPUs are what they'll produce so anyway we will be using third party boards from there on

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Wed, 23 Jan 2013 22:15:00 GMT

Quick update from me:

I've put my board back into service. I acquired a need to run test configurations of Windows Server 2012 - a few VMs at a time. A few weeks ago, I set up my DZ68BC motherboard again with a view to using it as a virtual hose. When I had retired it to its box, it had become very unstable and unpredictable after Bios 36 and37 updates. The updates had been performed, by the book but the board ended up unpredictable even with my trusty Celeron processor / 8GB of 1333MHz ram combination that had been stable before. Prior to those updates going wrong, the worst of my issues had been related to running with my 3rd gen i7-3770 processor and 1600MHz ram - supposedly a supported combination but they just would not work reliably.

After a lot of faffing, I managed to get my board downgraded back to Bios 35 and again basically reliably stable with the Celeron and the 8GB or 1333 ram. I ran it like that testing a VM or two (severely memory starved of course) for a couple of weeks, and it was stable enough and with sufficient functionality for my needs.

So what to do, obviously an 8GB system with a Celeron is not really a suitable test virtual host to test entire network configurations on!!! Do I dare to spend some money to buy a better processor and more RAM?

In the end I decided to perform the upgrade, but to attempt to play it safe - I bought a long supported i5 2nd gen processor (i5-2500) and 32GB of Kingston 1333MHz RAM (4 * KVR1333D3N9/8G ). This evening, I installed those parts. I had one wobble - I installed two RAM modules and tested OK, but with all four in, the POST stopped at 35. A quick reset of the BIOS and all four modules went in OK, Windows 8 (yuk!) booted OK, and consistently. Similarly the board accepted the i5-2500 CPU successfully, and the board so far appears relatively stable in this configuration (OMG! I've said t now!).

Fingers crossed!!!!

I'm not saying everything's fixed - I know that it's not - For instance, I'm sure that if I were to try more exotic processors for instance or try to overclock I'd again run into issues. Of course, I am still furious with Intel for letting this situation roll on and on. In the long term they have lost future business from me and all those to whom I professionally recommend systems to.

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Wed, 26 Dec 2012 18:17:38 GMT

I am on 0039, the only thing it got solved is the Marvell/Ahci.
I am unable to OC my i5 3570K, averything is greyed out, an even i dont have the field to manually select my memory speed...
Truth is, this MOBO has been a huge disappointment, and i dont have any chance of RMA (cos´ Intel does no say a word bout this, so, it is no ´malcfunction´) and they´re dropping it...
So, im stuck with a limited Board, and CERO advantages of having an Unlocked K Procesor... a shame, really...
I wish that a 0040+ version comes out solving all the OC, Host Freq, Memory, etc, issues this Mobo has.

Extreme series???... yeha... sure... :/

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Wed, 19 Dec 2012 18:55:15 GMT

Fixed issue where hard disk drive is not recognized when SATA mode is set to AHCI

Relative to what version? Was this a problem in 0028? I'm seeing this now with one drive all of a sudden, though it's worked fine with 0028 for most of a year (I haven't updated the BIOS). Of late, it's normally still in the BIOS but sometimes drops out, which is a problem. It drops out of Windows all the time. I've now pulled the drive and am testing it in an old system, where it's working fine so far.

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Sun, 16 Dec 2012 06:34:48 GMT

It's been tried:

DZ68BC Bios 39

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Sun, 16 Dec 2012 06:23:46 GMT

Guys, there is a new 0039 BIOS update!

anyone tried it yet?

Also, has the overclocker of this board been fixed or not yet?

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Thu, 22 Nov 2012 18:23:19 GMT

Thanks for this workaround procedure. Currently I have the issue that when I do a "save settings" in the BIOS it won't restart but just hangs. I need then to power off before the system restart. The settings are saved however. Maybe your procedure also helps for this problem.

Re: Still no fixed BIOS for DZ68BC

webadmin@intel.com — Thu, 22 Nov 2012 04:28:57 GMT

Nothing yet, most likely dead and forgotten.

Tho i have a permanent fix for the Intel ME and PCH issues, fix works for me tested on BIOS 0036, 0037 and 0035, I recommend using BIOS 0036 or 0037 for this fix.

4. The issues could resurface if you over clock your memory or use XMP profiles but not to worry, just make sure any XMP or memory overclock is applied before following the steps below tested XMP 1600 and also memory over clocks 1866, 2133MHz with the method

1. Shut down PC make sure all power is gone from the board, then Remove all the RAM sticks.

2. Install 1 RAM stick in the first slot immediately after the CPU, DIMM 3, then switch on PC and go into BIOS to check if the issues are gone, if not yet gone just restart the PC and the issue will be gone if you check the BIOS.

3. Switch off PC, Reinstall any other memory sticks in the correct dual channel arrangement without removing the first ram stick in DIMM 3, then you are good to go the issues are gone.