Official GIGABYTE Forum

Z87-D3HP stability issues

esi

  • 3
  • 0
Z87-D3HP stability issues
« on: July 28, 2013, 10:44:43 pm »
I had a stable machine until I upgraded motherboard,cpu and ram as follows:
Run sysprep, select oobe.
Power down, replace motherboard, cpu and ram.
After booting with new hardware update all drivers, including all available drivers and utilities from gigabyte
relevant to this motherboard.
New motherboard : GA-Z87-D3HP : http://uk.gigabyte.com/products/product-page.aspx?pid=4519
New memory 4*8GB DDR3 from Mushkin : for a total of 32GB :
http://poweredbymushkin.com/index.php/component/djcatalog2/item?id=181:997074&cid=3:silverline
New CPU : Intel I5-4670 3400 MHz
I am running win7 x64 enterprise edition.
PSU is 500W : http://www.computeruniverse.net/en/products/90210243/inter-tech-sl-500.asp

System has since been unstable with various bsod, unexpected reboots etc, which occur at seemingly random times.
I have run memtest which once found some errors after 7 passes of tests.

Have tried both bios F4 and F5C with similar results.
An currently running F4 since beta might be unstable ?

Read somewhere that you might have a newer bios, would that be recommended ?
Also read that there might be issues with using 4 dram modules, is that a known problem ?

Is it possible that the bios is not detecting my memory timing settings correctly, it is using 1600 11-11-11-28
which is the same as specified.
Are there some more memory settings I should look into, or even voltage that needs to be raised ?

I decided to change dram timing parameters from 1600 11-11-11-28 to 1333 9-9-9-24 so that if the memory is marginal it would work better.
Will let you know if problem continues.
Have raised support ticket to Gigabyte, first suggestion was to check if cpu socket pins are ok, which they are.

There is an 8-pin power connector labeled : ATX_12V_2X4, but I had only a 4-pin connector available from my PSU, which I plugged in, which leaves 4 pins unused, is that OK ?

Looking forward to your reply and assistance.
« Last Edit: July 28, 2013, 10:58:10 pm by esi »

ysw

  • 152
  • 2
Re: Z87-D3HP stability issues
« Reply #1 on: July 29, 2013, 03:45:36 am »
you may update to f5g to check.
you can find the latest bios on tweaktown forum.
http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios.html

esi

  • 3
  • 0
Re: Z87-D3HP stability issues
« Reply #2 on: July 29, 2013, 01:57:16 pm »
you may update to f5g to check.
you can find the latest bios on tweaktown forum.
http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios.html


1) memtest during last night found some errors, even after using the lower memory settings of 1333 9-9-9-24

2) I upgraded bios as suggested to F5g. Loaded optimized defaults, including ram settings of 1600 11-11-11-28.
Selected the new option "Enhanced stability" for the memory.

Will let you know if it fails again.

Rgds, Eirikur.

Re: Z87-D3HP stability issues
« Reply #3 on: July 29, 2013, 07:10:03 pm »
I'd had a similar sounding issue (random BSOD events) which occurred with 4 DIMMs installed. Disabling C1e, C3 & C6/7 in the BIOS seemed to fix it (you can leave EIST and thermal monitoring options enabled). I am also running the F5C BIOS.  I also had no problems with BIOS defaults after removing 2 DIMMs to leave one bank populated, which is how I determined the problem was related to having 4 DIMMs installed.

As for the 4 v 8 pin on the PSU, you should be OK with this at stock speed with a 4670K provided your PSU is able to supply the power.

I am currently also testing another load of settings that re-enables C-state options but changes a couple of other things instead on the advice of Gigabyte's support staff which i'll pass on if they prove successful.

esi

  • 3
  • 0
Re: Z87-D3HP stability issues
« Reply #4 on: August 01, 2013, 04:38:51 pm »
I got some more memory errors in memtest.
Took machine back to the shop, they split the memory in 2 groups, one gave errors and they replaced those 2.
Machine has been stable now for 2 days, hopefully this is the end of my story.
Just wanted to let you know, will not reply again unless problem happens again.
So in summary, problem was caused by faulty memory module(s).
Thank you for the assistance, rgds, Eirikur.