Crosshair V Formula-z + FX-9590 BSOD issues

[Fortinbra]

I'm having issues with a newly built PC, when attempting to install anything, the system BSODs. I will also get the same result when installing the latest SATA controller drivers. Here are my system specs:

AMD FX-9590
ASUS Crosshair V Formula-Z
Crucial M500 480GB SATA SSD
G.Skill Tident X 16GB (2x8GB)
EVGA GeForce 750 1GB
Corsair HX750 (PSU)
Corsair H80i (liquid cooler)
WD Black 1TB 7200RPM

Specific installs by which it would BSOD are
MS SQL Sever 2008 R2 SP1
MS Visual Studio 2010 SP1
MS Visual Studio 2013 update 2 (specifically during Windows Phone 8.1 installation)

I've also read through a few other posts trying to find answers, and yes both the 4pin and 8pin power connectors are connected, and I have not attempted to OC in anyway, shape or form. Here is my CPU Z screenshot



I've been attempting to monitor the voltages, and seems like the vcore voltage is dropping drastically right before the BSOD.

Any additional insight would be greatly appreciated.

*Edit*
Should also add that the error messages in the memory dumps are:
CRITICAL_PROCESS_DIED(ef)
WIN8_DRIVER_FAULT
failure also listing csrss.exe as failed process

These appear to be software related issues, but I've never had issues with compatibility with any of these programs before, running an identical software environment on an Intel build with no issues.

[Fortinbra]

I had to run the stress test twice, the first time got about 2 min in and then BSOD, the second ran all the way through. Here is the HWMonitor from that.

[MeanMachine]

Hi Fortinbra

Looking at your temps your TMPIN2 is way over what it should be, however if this sensor was reading correctly your MB would have fried by now.

Im guessing a faulty sensor or HWMonitor is looking for a sensor where there isn't one, for some reason it has this sensor mapped to the wrong location for your motherboard and since its not getting any data at all, its reading at its max possible value (128 C)

It might be best to try another monitoring package to check against. But only check with one at a time.

All other readings are just fine, assuming the readings are at idle.

You need to run a small stress test and carefully monitor temps during a cycle to see if you encounter a core failure or bsod. My bet is your temps will rise to 80c plus under max load so be carefull.

A bsod can be a driver related issue too so make sure they are up to date.

Running sfc /scannow is a good idea and will attempt to fix any corrupted files, (in windows only) and reading the results of the log files is difficult.

Please report back.

[Fortinbra]

I wasn't able to do the alternate install this past weekend, and because of the holiday this weekend, I won't be able to either. I did notice that not all the driver packages are listed for Windows 8.1 64bit on the Asus support pages, there are a few that are listed for Windows 7 x64 instead. Just to be sure I've got all my drivers properly installed, could you get me a list of all the drivers your running for this board?

I'll try to get the alternate install up and running as soon as I can and report whether or not it's a Windows issue.

[Fortinbra]

I managed to get a blank drive, and do the alternate install, Windows seemed stable, I didn't have much time to stress test, but no BSOD. I don't think that it's a fair indicator of the issue though, being that I disconnected 2 drives, and a fan (attached to the side panel of the case), then connected the new drive. The power consumption was completely different. So I do think that the entire issue is an under powered PSU. I checked the ASUS PSU calculator and it suggested a minimum 800W, before factoring in USB devices. We have a 1000W on order, hopefully that solves the problem.

[HiVizMan]

With the 9550 CPU you can not skimp on PSU - will check back later to see how it turns out.

[Fortinbra]

Just as another test, I've tried running with a second PSU (650W), and moving all peripherals over to it, but I still got the BSOD. After discussing this with a friend of mine (electronics engineer), he suggested removing the SSD, putting everything else back to the start. Right now I'm running everything except one fan (it's on the side panel which is currently removed), and the SSD, and so far no problems at all. It looks like the SSD may have been the entire problem.

Also, I tried doing an fresh install directly to the SSD, without the HDD hooked up, and got the BSOD again.

[HiVizMan]

A faulty SSD - darn that is rare.

Will keep checking back to see how this is resolved.

[Fortinbra]

The SSD is a mSATA SSD sitting an cradle to make it a full SATA SSD. I'm now trying all the steps the guaranteed a BSOD before, only now on a Maximus V Extreme, since this MB has the mSATA support directly on board. So far I've made it almost all the way through without any issues. It's not any faster than my other SSD in this system. I'm thinking that the cradle for the drive is what caused all the issues.

[Fortinbra]

End results:
SSD performed flawlessly connected directly to the motherboard.
SSD failed on Windows install when connected to same motherboard via the SATA adapter cradle

Conclusions:

The adapter cradle has been the source of all the problems from the start.


Thank you all for your help.

[HiVizMan]

Thank you for the very detailed feedback. Enjoy your system you have deserved it.