GIGABYTE GA-Z77-D3H - Freezing/Unstable Problems

markyb · 4 Sep 2012 at 13:14

Hey Guys,

Recently just upgraded my rig from a rock solid 775 setup (x6800, 6gb) which caused me no issues at all. I bought the following...

Antec Solo II
GIGABYTE GA-Z77-D3H rev1.0
Intel Core i5 2500
Kingston 8GB 1600MHz HyperX XMP

Using my existing components which I've had for some time now...

Leadtek 8800GT
Seasonic S12 500w PSU
WD 640Gb Hard Drive
Creative X-Fi Gamer Sound Card (PCI)

In short the system the system seems stable for a little while, then freezes/crashes resulting in the screen remaining static - any music or video just before the crash sounds choppy then locks. Resulting me having to reboot. Windows does not detect any issues upon rebooting.

I've had a look on the web and it appears im not the only one :-

http://forum.giga-byte.co.uk/index.php?topic=8885.0

Appears to be a common issue. So I upgraded the Bios to F18 which made no difference. Made the change with the BCLK (Set to 100.1) which appeared to eliminate the freezing issue, but every now and then I get application errors (this application must close) Up until last night where it froze like before.

- Everything is at stock, Memory @ 1600.
- MemTest x64 - Passed full check without any errors
- Intel Burn in - Can fail up to 10 seconds, or sometimes fully completes after 10 passes.
- Tried disabling Power Management in Windows

I'm at a loss of what to do. I know my components (GFX, PSU and HD) are all perfectly fine after using them for 3 years 24/7 without any issues. It seems to be that this Motherboard is un-stable - even at stock.

I've had the board for less than a couple of days now - return it back for something else? I've e-mailed Gigabyte - Any sugestions?

Thanks,
Mark

covenantuk · 4 Sep 2012 at 13:20

Are there any unexplained errors in the Windows event log?

mickyflinn · 4 Sep 2012 at 13:29

What is your ram voltage?

markyb · 4 Sep 2012 at 13:29

covenantuk said:
Are there any unexplained errors in the Windows event log?

Normally :-

"The previous system shutdown was un-expected" and or "Kernel Power failure"

Almost identical to the issues within this thread :- http://forum.giga-byte.co.uk/index.php?topic=8885.0

markyb · 4 Sep 2012 at 13:31

mickyflinn said:
What is your ram voltage?

Will check this tonight - but its all set to the defaults apart from enabling the RAM Extreme profile in order to obtain the 1600mhz but thats all I've touched. Running at 1333mhz or 1600mhz its still unstable - Both fully pass Mem-Test.

sadbuttrue · 4 Sep 2012 at 13:45

A lot of ram needs a small nudge in voltage over the specified value. You'll notice some ram like TeamGroup is advertised with a voltage range rather than fixed value. Passing Memtest is not a sign of memory stability in general use, which is why it's pointless running for 8 hours as some people do.

I had an S12 430 Seasonic die on me after 4 years of service a while back btw.

markyb · 4 Sep 2012 at 13:58

Thanks ill give it a check tonight.

I've noticed that in the Bios on the Statistics page, it shows the CPU running at 3.3/3.70Ghz, this is the same within Windows. I've not overclocked it, all of the CPU value should be on default - I've seen it during high load peak up to 4.1Ghz due to burst?

pecnarf · 4 Sep 2012 at 20:30

i had simiar problem with my 775 setup where it would randomly crash or hard lockup. manually set the memory value in the bio's to start off then increase memory voltage by 0.5. the other thing it could be is the psu being 500w it could be that the system is pulling near 500w so psu can't maintain the clean wattage so it drops in and out of the 500w. so if that the case get a 750w psu.

markyb · 4 Sep 2012 at 23:46

Ok, Thanks all for the suggestions so far.

This evening I've set the memory Voltage to 1.66 (Instead of the 1.650v) The ram is running at 1600mhz but one thing I have noticed is the cas is set lower. It should be 9-9-9-27 and is currently running 8-8-8-23

I can't seem to change it even though I have specified - Any ideas?

markyb · 5 Sep 2012 at 07:29

Left the machine downloading a couple of games from Steam last night. It appeared to of crashed. The event log as follows...

Code:

Log Name:      System
Source:        Display
Date:          05/09/2012 00:33:15
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Neptune
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Display" />
    <EventID Qualifiers="0">4101</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-04T23:33:15.000000000Z" />
    <EventRecordID>1173</EventRecordID>
    <Channel>System</Channel>
    <Computer>Neptune</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nvlddmkm</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Code:

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Code:

"The previous system shutdown at 00:18:55 on ‎05/‎09/‎2012 was unexpected."

Code:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          05/09/2012 00:55:01
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Neptune
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x0000000000000008, 0xfffff803c0700e70, 0xfffff88004dd1ff0, 0xfffff803c0834e28). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090512-16187-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-04T23:55:01.000000000Z" />
    <EventRecordID>1197</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>Neptune</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000007f (0x0000000000000008, 0xfffff803c0700e70, 0xfffff88004dd1ff0, 0xfffff803c0834e28)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">090512-16187-01</Data>
  </EventData>
</Event>

Interestedly 20 minutes before it locks, the display driver stops responding. I'm using Windows own driver WDDM for now to ensure the driver is stable.

Vimes · 5 Sep 2012 at 08:14

Extreme Memory Profile (XMP) - set it to disabled and thus the timings you are entering should override the values (wrong) you are seeing. That should allow you to use the correct voltage as well for the memory.

EDIT: Also set the Dram timing selectable to Expert.

markyb · 5 Sep 2012 at 10:26

Vimes said:
Extreme Memory Profile (XMP) - set it to disabled and thus the timings you are entering should override the values (wrong) you are seeing. That should allow you to use the correct voltage as well for the memory.

EDIT: Also set the Dram timing selectable to Expert.

Thanks, ill give this a try tonight.

Vimes · 5 Sep 2012 at 10:46

np- from the few screens you have posted I know that you will get crashed dues to the memory timings being incorrect, at least doing what I have written will put that potential issue aside.

markyb · 5 Sep 2012 at 18:51

Right. I've disabled the Extreme profile and set the CAS options correctly, I've also set the ram to 1600. Its all running correctly at 9-9-9-27 however the ram does not want to change...

As you can see its set to 1.66v but on the right hand side its showing as running at 1.64 which is .5 lower than it should be. I'm trying to +0.5 it to ensure it runs stable.

What am I missing here?

Vimes · 5 Sep 2012 at 19:09

If your ram is rated at 1.65v that is what you should set it at. There is no point in trying to overvolt it without a specific reason. If you wanted to run your RAM 0.5v more than it would that would work out at 2.15v..!!!
You are setting it at 1.660v and it is shown at 1.644v so to me that is only 0.016v difference - which is totally negligible. It is not 0.5v lower.

markyb · 5 Sep 2012 at 20:14

Vimes said:
If your ram is rated at 1.65v that is what you should set it at. There is no point in trying to overvolt it without a specific reason. If you wanted to run your RAM 0.5v more than it would that would work out at 2.15v..!!!
You are setting it at 1.660v and it is shown at 1.644v so to me that is only 0.016v difference - which is totally negligible. It is not 0.5v lower.

Sorry yes

- However, the RAM should be set at 1.65v, but the Motherboard is running the ram at 1.644 - would this count towards any issues?

Thanks for the help. I'm really hoping these settings solve my issues.

alexx · 5 Sep 2012 at 20:19

if not run your ram in single channel and let me know if that solves your problems... im having trouble with a z77 board running dual chan for no reason..

Vimes · 5 Sep 2012 at 20:27

markyb said:
Sorry yes - However, the RAM should be set at 1.65v, but the Motherboard is running the ram at 1.644 - would this count towards any issues?

Thanks for the help. I'm really hoping these settings solve my issues.

The difference is so small that you can account for that in just general normal fluctuations or errors in reporting etc etc etc. It is perfectly normal and no different to what anyone else would see.
The point is you are fine with the RAM voltage and now you have the correct RAM timings set that also will ensure you should be ok.

Just see how you go on. I notice that your performance enhance is set to "normal" which is quite conservative as mine is set to "Turbo" but leave it at that for stability whilst you are ensuring that all is well.

markyb · 6 Sep 2012 at 06:44

Crashed again this morning at around 05:00. PC was just left on downloading from steam which finished before. Same error logs

- 05:25 - Display driver nvlddmkm stopped responding and has successfully recovered.
- 05:46 - The previous system shutdown at 05:24:37 on ‎06/‎09/‎2012 was unexpected.
- 05:46 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0xfffff88000e65cb0, 0xfffff88003338fe0, 0xfffff803a232d509). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090612-11796-01.
- 05:46 - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

pecnarf · 6 Sep 2012 at 12:27

markyb said:
Crashed again this morning at around 05:00. PC was just left on downloading from steam which finished before. Same error logs

- 05:25 - Display driver nvlddmkm stopped responding and has successfully recovered.
- 05:46 - The previous system shutdown at 05:24:37 on ‎06/‎09/‎2012 was unexpected.
- 05:46 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0xfffff88000e65cb0, 0xfffff88003338fe0, 0xfffff803a232d509). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090612-11796-01.
- 05:46 - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

i know that error well as i had crap load of them with my 775 setup. once i had swap out my ocz memory and got my 8gb kingston hyperx memory in plus new ax1200 psu.
i had finally got solve the issue of it crashing, but a this error now so i tweak the memory setting in the bio. the trick to find out what the max voltage your memory can take it normally something like 1.9v so check mobo manual and memory for max safe voltage then work from what the standard voltage and increase by 0.5 at a time until you find voltage that work now here the trickie bit you need to know that max safe voltage before you start this so that you don't hit it or go pass it. now reason why you getting the message is because you not getting the right amount of voltage on the ram. i got it because i had all 4 ram slot full memory so i had to increase in the voltage from 1.5v to 1.75v plus set manual timing and find correct advance timing setting. i got to point where i had manual set standard timing some of the advance timing and voltage at 1.75v rest of the memory was put back to auto it been stable since then.