GA-Z97X-UD3H with M.2 Crucial SSD as Boot Drive and Dual Channel Memory issues

jjc01

Reputable
Oct 19, 2014
15
0
4,520
I'm getting failure to boot problems which resolve themselves when I remove the drive and plug it back in.

I've also had an issue with the Dual Channel Memory. Gigabyte Technical support suggests I might have a bent pin in the 1150 socket.

Anyone encounter either of these problems?

PS - I saw a reference in another thread to the gigabyte M.2 support list, that prompted me to check the list - crucial was not on it, but I had a time crunch, and I could will call the M.2 SSD, and couldn't get any other M.2 SSDs . . . so I built it that way.

---- This is the first build I've done in 10 years, I knew there would be a learning curve, but I had no idea how detailed sorting out the components compatibility would be. Next build I'm going to check all the component support lists, and order all components online instead of going with brick retail outlets. In hindsight, I might have been up and running in the same time frame with a more reliable build. ---- :)
 
Solution
I think I've solved it. Been operating for about 4 weeks now with no issues. I talked to the Gigabyte Customer Service people over the phone and they sent me a new BIOS, Z8 (as I recall), which didn't exist yet on their website for download. That seemed to fix the m.2 ssd recognition problem.

I was still getting crash dumps and all the diagnostic tools I tried just reported the same thing, suggested it was driver related, but couldn't identify the driver and couldn't indicate if it was a driver associated with hardware or software. The crash dumps would occur at a certain time after I'd stopped all activity on the system. So I suspected it was associated with the power management settings. I went into those settings and changed...

jjc01

Reputable
Oct 19, 2014
15
0
4,520
Thanks Tradesman1

Mb: ga-z97-ud3h
SSD: Crucial M500 240GB, 6Gb/s M.2 (2280-D2-B-M) CT240M500SSD4
PCIe: Trendnet M600 Wireless Dual Band PCIe Adapter
Second SSD: SAmsung 840 EVO

The system is stable except under certain conditions:
While I'm using the system, everything seems fine. If I leave the system running, or sometimes when I'm starting it up, I get the dreaded blue screen. If I unplug the M.2 SSD, and unplug the Samsung SSD, then plug the M.2 SSD back in, I can recover. I then shut down, plug in the Samsung and I'm back in business.

So it sounds to me like a compatibility issue, and possibly an issue with the system getting confused between the M.2 SSD and the Samsung SSD. There have been times when I've gone into the BIOS and the system doesn't list the M.2.

Note: While building the system I installed the Samsung SSD and installed windows on it. I then realized I could buy the Crucial M.2 SSD and install it in the MB slot. I was under a time crunch, didn't check compatibility, and just went with the Crucial M.2 SSD because I could pick it up the same day. It was later that I (under advisement) checked the MB compatibility list and found the Crucial wasn't on the list. There is no 'incompatibility' list I can find, so not being on the list doesn't mean it isn't compatible . . . right?
 

jjc01

Reputable
Oct 19, 2014
15
0
4,520
Tradesman1, your answer is a little over my head - I will check the BIOS settings and see if I can find where to do this.

Can you supply a little more information? Why would tweaking VCCSA voltage help? (I'm googling VCCSA now)
 

jjc01

Reputable
Oct 19, 2014
15
0
4,520
PS, I've googled it and now understand it's the voltage that supplies the PCIe, memory and display voltage. So it seems reasonable. I'll add more information to the system:

I'm not overclocking
The case is a Raidmax Super Viper, with a PSU that only has the 4 pin CPU cable. The MB has the 8 pin connector, I called GB and they strongly suggested replacing the power supply.

The PSU is loud, so I plan to replace it with a 520W fanless PSU soon. I now know what to look for in terms of the CPU power cable, so that upgrade might help if this is a CPU Power Voltage issue.

As someone who has not built a computer in 10 years, I can see that a forum like this is indispensable.

I'll probably build another system within the next three months, taking advantage of everything I've learned.
 

jjc01

Reputable
Oct 19, 2014
15
0
4,520
Had the problem of the system not finding the M.2 drive this morning. Pulled out the drive, disconnected the SATA SSD, disconnected the power to the 'old hard drive' (which prior to this was powered, with no SATA cable).

I investigated VCCSA, found it's referred to as 'System Agent' in the Bios. It's setting was Auto. Hitting the + key changed it to Normal, and continuing, I could change it to -.3, then each hit of the + key would increase it.

I've set it to +.03.

I'll leave it at that for a few days and if there is no repeat of the problems, I'll hit the 'Pick as the solution' button with relief!

--- later in the day . . . the system experienced a 'crash dump' - - -

4 days later, no problems - got my fingers crossed
5th day, same old problem.
------------------------------
8th day: I put in a Seasonic 520W Fanless power supply, added two additional 120mm fans, and an AeroCool Touch-2100 fan display (the original power supply that came with the RAIDMAX Super Viper case only had a 2x2 CPU power cable, and the fan was LOUD! The new PS has the appropriate 2x4 CPU power cable. The RAIDMAX case also has a fan built into the front of the case. I've turned that front fan off, and am running the other 3 at 800 rpm.

The system is SILENT, I can't hear anything even though I can feel the airflow out the top and back. I'm monitoring the Core temps and temps at one of the MB HeatSinks, as well as the air temp above the stock CPU fan, and in between the two 8 GB DDR3 memory modules. As I write this the max CPU Core temp (displayed by the utility: Core Temp 1.0 RC6) is 39C Outside air temp is 21C and the highest internal temp is 27C between the memory modules.

I did not have any trouble booting the system after upgrading it and reseting the BIOS, and will update this in a few days
 

igBlofeld

Reputable
Nov 26, 2014
1
0
4,510
I have the same combo of motherboard and m.2 ssd, I also have the same issue. I find that if I turn off my pc at the mains for about a minute then turn it back on the drive reappears.

Did you fix the problem?
 

jjc01

Reputable
Oct 19, 2014
15
0
4,520
I think I've solved it. Been operating for about 4 weeks now with no issues. I talked to the Gigabyte Customer Service people over the phone and they sent me a new BIOS, Z8 (as I recall), which didn't exist yet on their website for download. That seemed to fix the m.2 ssd recognition problem.

I was still getting crash dumps and all the diagnostic tools I tried just reported the same thing, suggested it was driver related, but couldn't identify the driver and couldn't indicate if it was a driver associated with hardware or software. The crash dumps would occur at a certain time after I'd stopped all activity on the system. So I suspected it was associated with the power management settings. I went into those settings and changed them so the system would never sleep or hibernate. I then got rid of another thing that seemed to be related: the BIOS Utility Updater software.

Things seem to be stable now.
 
Solution

SslasherR

Reputable
Apr 11, 2015
1
0
4,510
jjc01

Can I email gigabytes to send me also the newer bios update of board? We have the same board and ssd used and I'm suffering also what you have experienced before. Please advise. Thanks