[SOLVED] Gigabyte GA-X99-UD4 and Seagate Barracuda not playing well together

muddyh2o

Reputable
Feb 6, 2015
3
0
4,510
Hey everybody

My new build keeps restarting, and the windows event logs aren't giving me any help. It looks like some type of disagreement between my motherboard and my secondary HDD.

It might cut out after 5 minutes or 2 hours - it actually just happened while I was trying to write this message.

The system just freezes for a few seconds then restarts as if after a complete power outage.

This problem does not seem happen when the Seagate Barracuda is disconnected. Nor does it appear to happen when I'm just sitting in the BIOS settings screen (before Windows installs), but I haven't thoroughly tested the latter. I'm going to run memtest overnight when I get out of the office.

User @darkbreeze mentions something similar in another thread, but I couldn't find any definitive solution.

Nothing shows in the Windows Event logs except errors that the system restarted unexpectedly:

The previous system shutdown at 7:39:32 PM on ?2/?4/?2015 was unexpected.

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

All devices have the correct drivers, latest BIOS versions and are behaving otherwise normally.

Any ideas what's up or how to troubleshoot it?

Specs below:

Intel Core i7-5820K
Gigabyte GA-X99-UD4 BIOS F12 Serial number A0194A0B16GB
Crucial Ballistix Sport 2x8GB DDR4 BLS8G4D240FSA
EVGA SuperNOVA 850G2 Corsair H80i
Gigabyte R9 290 GV-R929OC-4GD
Thermaltake Commander MS-I running
Windows 8.1 64-bit
SanDisk Ultra II 240GB SATA III 2SDSSDHII-240G-G25
Seagate Barracuda 3000DM001-1CH166 with latest firmware
 
Solution
Just came across this, as you reference me by name, sorry I didn't see it before. Did you get this solved/sorted out? My first thought would be that perhaps the SATA header that it's connected to is different than the primary drives header, which isn't uncommon, board manufacturers often use multiple controllers on their boards, has an issue or doesn't have the correct drivers installed for it.

Might try connecting it to a different color SATA header.

If not, run Seatools for DOS on the drive in a pre-windows environment to check the drive's health. You can download it here:

http://www.seagate.com/support/downloads/item/seatools-dos-master/


If you've already solved the issue, that's all moot, heh.
Just came across this, as you reference me by name, sorry I didn't see it before. Did you get this solved/sorted out? My first thought would be that perhaps the SATA header that it's connected to is different than the primary drives header, which isn't uncommon, board manufacturers often use multiple controllers on their boards, has an issue or doesn't have the correct drivers installed for it.

Might try connecting it to a different color SATA header.

If not, run Seatools for DOS on the drive in a pre-windows environment to check the drive's health. You can download it here:

http://www.seagate.com/support/downloads/item/seatools-dos-master/


If you've already solved the issue, that's all moot, heh.
 
Solution

muddyh2o

Reputable
Feb 6, 2015
3
0
4,510
@darkbreeze, your a real star. Thanks for answering!

Yes, I tried the SATA swaps, cables, etc. Seemingly I did everything I could imagine. Pulling memory, reinstalling Windows.

Anyway, I found a mention in a thread somewhere that Google Chrome Hardware Acceleration could cause this type of crash. I turned it off in Chrome and it's been running for two days.

Fingers crossed. I'll stress test it and install some apps later in the week

But I think I can blame Google Chrome for this. Or at least an incompatibility between Chrome and my hardware.

God, I hope I've solved this. There's nothing worse than having your system restart when your right in the middle of someth
 
If you have further problems or even if you finally determine that WAS for sure the issue, come back and let me know. I always like to add possible solutions to the repertoire for folks who have "ghost in the machine" issues that standard resolutions don't help. Hope it WAS your only issue. Good luck.
 
If the storage controllers have failed on the board, keep at Gigabyte help or try a different tactic with them. I've not had issues with them in the past so maybe you got somebody who smoked their lunch or had somebody pee in their Wheaties that day.