RanceJustice
Supreme [H]ardness
- Joined
- Jun 9, 2003
- Messages
- 6,630
Hello all. I'm now running on my new X99 platform rig (Rampage V Edition 10 Mobo), on which I had installed Win10 Pro x64 (unactivated as of yet) on a Samsung 960 EVO NVMe drive for overclocking and stability testing. However, I also pulled a handful of drives from my old X58 platform PC including the a Samsung 840 Pro w/Win 10 Pro x64 (activated) , a WD Black HDD without any OS acting as an overflow data drive in my old PC, and an old WD VelociRaptor with Win7 Ultimate x64.
All of these drives are detected by the W10Pro install on the 960 EVO, automatically visible and able to be browsed on the file manager. However, what I really wanted to do was to boot the Win10Pro on the 840 Pro. I had been told on some enthusiast forums and chats that W10Pro is pretty flexible and wouldn't have too much of an issue with drivers and whatnot, swapping the drive from one PC to another (a departure from earlier OSes as I recall), with the OS pulling down what it needs for core functionality in most cases. However, the problem I am having is that I can't seem to make the 840 Pro bootable at all.
When I go into my RVE10's UEFI and look at the boot options, all the drives are detected. Right now the 960 is of course the first boot drive, but there is a helpful Boot Override option where you can click on a particular drive and boot directly from that one it seems. When I try this with the 840 Pro however, sadly it does not actually boot. I get about a second of the "flashing cursor on black screen" before rebooting into the BIOS/UEFI. Its also noteworthy that unlike on my old PC, Win10 (on 960 EVO) does not automatically detect there are multiple windows installs on different drives and give me the chance to pick the one I wish to boot through its boot manager; my old PC used to give me the chance to boot Win10 (on 840) and Win 7 (on VelociRaptor) with every reboot.
Can anyone think of a reason for this or a way to boot the OSes on other drives? I've come up with a couple of theories of things that could affect it.
First, I wonder how much of this is because the new/native Win10Pro install on the 960 EVO is obviously using UEFI (possibly GPT?) parameters, whereas the old W10Pro on the 840 Pro was from the X58 days where it was using the old style BIOS (MBR?). I seem to remember that W10 will automatically decide on certain settings for one or the other given the circumstances of the install, and this can affect different things (Notably, certain activation technologies for Win7 would work on BIOS mode, but not UEFI mode ). Could this have anything to do with it and if so is there a certain setting I need to toggle or other fix that might help?
Next, I wonder if it has to do with Secure Boot or similar settings? I've left the Secure Boot on the default for the RVE10 and though I am pretty sure any W10 install should be compliant, maybe because it was installed on an old chipset without any SecureBoot support could introduce an issue.
Anything else worth looking into or solutions to try?
All of these drives are detected by the W10Pro install on the 960 EVO, automatically visible and able to be browsed on the file manager. However, what I really wanted to do was to boot the Win10Pro on the 840 Pro. I had been told on some enthusiast forums and chats that W10Pro is pretty flexible and wouldn't have too much of an issue with drivers and whatnot, swapping the drive from one PC to another (a departure from earlier OSes as I recall), with the OS pulling down what it needs for core functionality in most cases. However, the problem I am having is that I can't seem to make the 840 Pro bootable at all.
When I go into my RVE10's UEFI and look at the boot options, all the drives are detected. Right now the 960 is of course the first boot drive, but there is a helpful Boot Override option where you can click on a particular drive and boot directly from that one it seems. When I try this with the 840 Pro however, sadly it does not actually boot. I get about a second of the "flashing cursor on black screen" before rebooting into the BIOS/UEFI. Its also noteworthy that unlike on my old PC, Win10 (on 960 EVO) does not automatically detect there are multiple windows installs on different drives and give me the chance to pick the one I wish to boot through its boot manager; my old PC used to give me the chance to boot Win10 (on 840) and Win 7 (on VelociRaptor) with every reboot.
Can anyone think of a reason for this or a way to boot the OSes on other drives? I've come up with a couple of theories of things that could affect it.
First, I wonder how much of this is because the new/native Win10Pro install on the 960 EVO is obviously using UEFI (possibly GPT?) parameters, whereas the old W10Pro on the 840 Pro was from the X58 days where it was using the old style BIOS (MBR?). I seem to remember that W10 will automatically decide on certain settings for one or the other given the circumstances of the install, and this can affect different things (Notably, certain activation technologies for Win7 would work on BIOS mode, but not UEFI mode ). Could this have anything to do with it and if so is there a certain setting I need to toggle or other fix that might help?
Next, I wonder if it has to do with Secure Boot or similar settings? I've left the Secure Boot on the default for the RVE10 and though I am pretty sure any W10 install should be compliant, maybe because it was installed on an old chipset without any SecureBoot support could introduce an issue.
Anything else worth looking into or solutions to try?