F5F Stay Refreshed Software Operating Systems Error encountered while linking the second storage device

Error encountered while linking the second storage device

Error encountered while linking the second storage device

S
Squarefern
Junior Member
5
09-24-2016, 03:11 AM
#1
I usually use two SSDs—one running Windows 7 and another Windows 10—to handle different applications. At startup, I select the Windows 10 drive in the boot manager, then use a 2 TB HD for extra storage. Recently, I can only boot from the Windows 10 drive. If I try Windows 7 or the 2 TB drive, I encounter a BSOD with stop code WHEA_UNCORRECTABLE_ERROR. What should I do?
S
Squarefern
09-24-2016, 03:11 AM #1

I usually use two SSDs—one running Windows 7 and another Windows 10—to handle different applications. At startup, I select the Windows 10 drive in the boot manager, then use a 2 TB HD for extra storage. Recently, I can only boot from the Windows 10 drive. If I try Windows 7 or the 2 TB drive, I encounter a BSOD with stop code WHEA_UNCORRECTABLE_ERROR. What should I do?

D
DeathEmpireHD
Junior Member
3
10-01-2016, 07:58 PM
#2
D
DeathEmpireHD
10-01-2016, 07:58 PM #2

J
juway
Junior Member
8
10-03-2016, 12:28 PM
#3
After completing that, start the system in safe mode with networking. Ensure all your drivers are current, and install the most recent Windows updates.
J
juway
10-03-2016, 12:28 PM #3

After completing that, start the system in safe mode with networking. Ensure all your drivers are current, and install the most recent Windows updates.

L
Luckitty
Junior Member
5
10-05-2016, 09:43 PM
#4
thanks for the help! this is what ended up happeing. drive wasnt booting so i started fcking with bios settings.... then eventually i got my first drive on Sata port 1 to boot after going into cmd prompt from win10 install media and using commands : bootrec /fixMBR, bootrec /Fixboot, and bootrec /rebuildBCD. then i was able to boot. but then my other two drives when connected would cause the same BSOD again.... then i realized i changed a lot of bios settings before all this, so eventually changed everything in bios back to what it was before all this mess, and then it booted but the boot loader menu to choose boot drive was in Metro style and time out was only 2 seconds. so then i googled and ran some commands to make it back to the windows 7 style which i like more and set a longer time out. now everything is fine. i am just really baffled as why ALL of this happened including little things like bootloader style and time out changed just from me unlplugging all my drives (when computer and psu is off obvs) and then plugging in a spare drive with clean install of windows 10 on it. im taking my computer in for repair today at microcenter and didnt want my usual drives with personal info in the machine when its sitting there. so i was testing the spare drive yesterday before heading over there today, and then all of this happened when i tried to go back to my usual drives plugged in without the spare one
L
Luckitty
10-05-2016, 09:43 PM #4

thanks for the help! this is what ended up happeing. drive wasnt booting so i started fcking with bios settings.... then eventually i got my first drive on Sata port 1 to boot after going into cmd prompt from win10 install media and using commands : bootrec /fixMBR, bootrec /Fixboot, and bootrec /rebuildBCD. then i was able to boot. but then my other two drives when connected would cause the same BSOD again.... then i realized i changed a lot of bios settings before all this, so eventually changed everything in bios back to what it was before all this mess, and then it booted but the boot loader menu to choose boot drive was in Metro style and time out was only 2 seconds. so then i googled and ran some commands to make it back to the windows 7 style which i like more and set a longer time out. now everything is fine. i am just really baffled as why ALL of this happened including little things like bootloader style and time out changed just from me unlplugging all my drives (when computer and psu is off obvs) and then plugging in a spare drive with clean install of windows 10 on it. im taking my computer in for repair today at microcenter and didnt want my usual drives with personal info in the machine when its sitting there. so i was testing the spare drive yesterday before heading over there today, and then all of this happened when i tried to go back to my usual drives plugged in without the spare one

B
Brooke143
Member
61
10-06-2016, 12:40 AM
#5
If the problem recurs, consider swapping cables or ports
B
Brooke143
10-06-2016, 12:40 AM #5

If the problem recurs, consider swapping cables or ports