i have the same problem with my DH67GD.
First of all onboard-LAN wasn't working and after loading the "setup defaults" the PC does`t boot. -> No bootable device found!:-(
Big Problem: You are not able to downgrade to 0132, only to 0146 but it isn't availible in the download center.
Intel DH67GD, H67 (B3)
Intel Core i5-2500, 4x 3.30GHz, boxed
Kingston ValueRAM DIMM Kit 4GB PC3-10667U CL9 (DDR3-1333) (KVR1333D3N9K2/4G)
Kingston ValueRAM DIMM Kit 8GB PC3-10667U CL9 (DDR3-1333) (KVR1333D3N9K2/8G)
OCZ Vertex 2 60GB, 2.5", SATA II (OCZSSD2-2VTXE60G)
Samsung EcoGreen F3 1000GB, SATA II (HD105SI)
LG Electronics GH22NS50
Sapphire Radeon HD 5750, 1GB GDDR5, 2x DVI, HDMI, DisplayPort
be quiet! Straight Power E7 450W ATX 2.3 (E7-450W/BN114)
I used the Express BIOS Update method (self-extracting .exe in Windows).
Device Manager says the Network driver is version 188.8.131.52 signed by Intel (30 Nov 2011).
The OS is installed on a Crucial M4 SSD, there's a 2TB Samsung HDD, a 1TB Seagate HDD, a Liteon Blu Ray writer, Logitech bluetooth keyboard attached by USB and a USB TV tuner.
What kind of RAM are you using?
I have installed LAN-Driver 184.108.40.206, but it doesn't work.
Now i have downgraded to 0132 via recovery CD and its works fine.
I have to be carefull with early bios updates and intel boards in the future.;-)
That was the third time 0128, 0146 and 0150 where the BIOS was bad.
I have Version AAG10206-205 of the DH67GD and there will be no 22nm support for this board regarding to
DH67GD AAG10206-210 or later AAG10206-206 BLH6710H.86A.0132 BLH6710H.86A.0146 or later
Why does Intel not check this 22nm-Ready AA#s in in the BIOS-Update process to prevent failures?
Which AA#s are you using?
The loss of LAN after updating to BIOS version 0150 is caused by a previously unseen memory allocation conflict between ATI* video cards and the onboard LAN resources. This behavior has not been observed with other manufacturer’s add-in video cards. As a temporary workaround, LAN connectivity can be restored by removing the ATI video card and using onboard video instead.
Intel regrets any inconvenience caused by this issue and is working to provide a corrected BIOS as soon as possible.