BSOD before Windows starts - only when secondary HDDs are in

Basic description ofproblemI built a new computer that occasionally has a blue errorscreen, or stop code, right before Windows starts. It successfully POSTs and
then freezes and won’t move on, it seems to happen at the exact moment when
Windows is about to fully load.
Detailed descriptionof problem
I have been able to isolate the problem to secondary harddrives plugged in, my main drive is is an NVME M.2 drive. When the hard drives
are not plugged in I never get an error. When one, or both hard drives are
plugged in I get an error about every other or every third start. I know the problem only occurs when the hard drives areplugged in because:
1)   I used the computer for a little over a weekbefore I plugged in the hard drives and never had a problem until the 2 hard
drives were first plugged in2)   After being plagued by the problem, I wanted tobe 100% sure it was isolated to the hard drives. I unplugged them and restarted
the computer fifteen times without any error. As soon I plugged the hard drives
back in I got the error on the second restart. Facts about the error
-      Computer successfully POSTs and the error seemsto come right when Windows would normally launch
-      Only happens when both or either single drive isplugged in
-      Frequency: About every other or every thirdstart. It doesn’t seem to make a difference if it is a restart or a normal
start from a powered down computer.
-      When the error occurs there is never anyprogress on the BSOD screen and no noise from the hard drives
-      When the error occurs I hold the power button toforce the system to turn off and the computer restarts successfully 100% on the
next start, and everything always seems to be fine.
-      I am not ableto enter the UEFI BIOS when the error is going to happen. This happened enough
that I can say this with a high degree of confidence: If I can enter BIOS
Windows will start okay, if I can’t enter BIOS I will get an error. 
Screen shots of theerror
I believe I’ve seen 3 different BSOD error codes. I nevertook a picture of the first one. When I would unplug things and re-seat the
hardware in an effort to isolate or fix the problem I would get a new error
code. Doing a web search for these error codes doesn't provide much
information.Error code #1
Didn’t write down or documentError code #2
Stop code: MACHINE CHECK EXCEPTION Error code #3
Stop code: WHEA UNCORRECTABLE ERRORThe percentage never moves up, nothing ever happens
Basic hardware/softwareinfo:
-      Motherboard: New Asus X99-A II
-      Primary startup disk: New NVME M.2 Samsung 960EVO 1TB
-      High quality PSU (Corsiar HX750i)
-      Hard drives creating the problem:1)   Used Seagate 1TB - used for storage: I purchasedthis drive 6 or 7 years ago and used it faithfully that entire time and never
had a problem. It doesn’t say but I’m near certain it has a SATA III 6Gb/s
interface.2)   New HGST 4TB – used for Windows 10 File History-      Using Windows 10 Pro – fully updated
-      I have the NVME M.2 drive setup as the onlystartup device. I have it set to ignore anything but the M.2 drive during
startup – even USB.
-      I downloaded and installed most current BIOS anddrivers from Asus
I don’t believe thehard drives are bad because:
I can read and write to both drives without any issue orerror. Looking at the Device Manager there are no errors. The error seems to
happen just as often when both or either one of the drives are plugged in, and
it seems unlikely both drives would be bad.
Drive #1 I used for years without issue, I even plugged itback in to the old computer (Windows 10 – non pro edition) and used it and
restarted it ten times to try to confirm the drive is good.
Drive #2 is brand new and initialized fine.
What I have done totry to fix the error
-      Unplugged and reseated motherboard ATX powersupply several times
-      Changed out SATA cables (tried a total of 4cables)
-      Changed which port the SATA cable is pluggedinto on motherboard. Tried a total of 6 ports, both traditional SATA and SATA
Express ports.
-      Used two different power cables plugged into twodifferent ports on the PSU (it is a modular power supply)-      I looked into the drivers for the for the harddrives. It looks like the drivers are good and it uses a standard commodity
driver - not really sure if there are different drivers I can try. I also
confirmed drive #1  uses the exact same
driver when plugged into old computer
Screen shot of the drivers (they both have the same version):
 Unusual side note,but seems related to me:When I first plugged in Drive #2 (new 4TB drive) andinitialized it I could read and write to the drive but File History (Windows
incremental backup system) wouldn't work. I had to go to the control panel and
view it from there for it see the error. It was something about it not being a
supported drive. I did a bit of web searching and found a simple and unusual
fix – I did it and it worked.The fix is located at the bottom of this page:
Basically the fix is: go to Control Panel > Region. OnFormats Tab hit additional settings and enter . (dot) into the decimal symbol
The weird thing is because I am in the US it was already adot, but I entered dot, restarted and File History started working and backing
up my files.
I later went through and reentered every field and of coursethat didn’t fix my BSOD error.  Thank you so much forreading this and helping.  Any help or
suggestion on how to isolate the problem is greatly appreciated.
Not sure if the problem could be my motherboard, but I haveuntil March 25 to be able to return it.
Discussion is locked
Reply to: BSOD before Windows starts - only when secondary HDDs are in
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: BSOD before Windows starts - only when secondary HDDs are in
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Clarification Request
I've seen this for a few reasons.

1. The motherboard BIOS is out of date.
2. The SATA cable was questionable.
3. The RAM was mixed (passed all memory tests but yet...)
4. The OS was infected. (Use Grif's help at )
5. There is a problem with the content on the drives.
a. Run chdksk /f on all drives.
b. There are video files on the drives and a codec is blowing up (see event viewer for more clues)

6. Try starting with a BLANK second drive. Do not put any files on there. Does it blow up?

- Collapse -
Thanks for the suggestions


1) BIOS is up to date
2) I've used 4 different brand new cables
3) The RAM has passed all test, I don't have different RAM to test and it is under a large cooler that would mean reapplying thermal paste to adjust. Besides since I NEVER have a problem when the hard drives aren't plugged in (and I have tested this thourghouly) wouldn't it mean that the the RAM is fine?
4) This is a brand new install of Windows. I feel very confident that there isn't something bad in OS.
5) I ran chdksk /f on both drives. They are fine.
6) I even formatted the new drive (drive #2) and and with a blank drive it still gives me an error. It is a new error, but still the BSOD

- Collapse -

I did not google the WHEA error. You can do that but HDDs vibrate and repeated the "remove the CPU and put it back in" fixed it for more than one person.

I'd do that since the pins are small and all it would take is some one touching a pin or pad and well, odd things.

The HDD in could be adding to the vibration and WHEA, it faults.

-> Be sure to google your motherboard model and the word "WHEA" to see if others are reporting in.

- Collapse -
Will run for days after started

Thanks for the suggestion.

Once the computer is booted up into Windows it is rock solid. I left it on for two days over the weekend. The BSOD reliably comes up every other start or every third start at the exact same time - right when I expect Windows fully load.

- Collapse -
Which makes sense.

As the CPU heats up it can lose contact and WHEA.

- Collapse -
This has been solved

turned off Fast Boot in the ASUS BIOS and that seems to have solved the problem. From what I have read Fast Boot initializes all the hardware at once rather than one by one. I think I can see a small increase in startup time but at least it is stable

CNET Forums