F5F Stay Refreshed Software Operating Systems wut

wut

wut

Pages (2): 1 2 Next
B
Baallog
Member
189
04-24-2020, 06:57 AM
#1
I just purchased a new drive to swap in for my outdated 9-year-old HDD. I formatted it properly and moved all files from the failing drive to the new one. After restarting, I got an error saying "HECI Disabled, Proceeding to Boot!" The system froze completely, so I had to reboot again. Then it showed a black screen, another reboot, and finally entered recovery mode with corrupted system files. This happened twice, so I’m ignoring the other thread.
B
Baallog
04-24-2020, 06:57 AM #1

I just purchased a new drive to swap in for my outdated 9-year-old HDD. I formatted it properly and moved all files from the failing drive to the new one. After restarting, I got an error saying "HECI Disabled, Proceeding to Boot!" The system froze completely, so I had to reboot again. Then it showed a black screen, another reboot, and finally entered recovery mode with corrupted system files. This happened twice, so I’m ignoring the other thread.

W
WQDJincase
Junior Member
3
04-24-2020, 08:10 AM
#2
Your old hard drive is causing problems and won't start up properly. Swap it for an SSD, as this often resolves the issue when the drive is faulty.
W
WQDJincase
04-24-2020, 08:10 AM #2

Your old hard drive is causing problems and won't start up properly. Swap it for an SSD, as this often resolves the issue when the drive is faulty.

M
MyLax
Member
105
04-24-2020, 02:59 PM
#3
As I mentioned earlier, that’s the update I just installed. The system is now using an SSD, while the old HDD held games and applications—so why would Windows switch like that? It’s pretty strange.
M
MyLax
04-24-2020, 02:59 PM #3

As I mentioned earlier, that’s the update I just installed. The system is now using an SSD, while the old HDD held games and applications—so why would Windows switch like that? It’s pretty strange.

A
Andrezw
Junior Member
2
04-24-2020, 03:26 PM
#4
Consider changing the title of your forum thread to accurately reflect the problem you're facing. This can lead to better understanding, support, and recognition for your request.
A
Andrezw
04-24-2020, 03:26 PM #4

Consider changing the title of your forum thread to accurately reflect the problem you're facing. This can lead to better understanding, support, and recognition for your request.

S
sunemoonsong
Senior Member
380
04-28-2020, 09:29 AM
#5
It seems there might have been an issue with the previous drive that Windows attempted to resolve before allowing access to the new one. Give it some time and observe the outcome.
S
sunemoonsong
04-28-2020, 09:29 AM #5

It seems there might have been an issue with the previous drive that Windows attempted to resolve before allowing access to the new one. Give it some time and observe the outcome.

R
Robater
Member
86
04-28-2020, 12:11 PM
#6
The bootloader is present on the HDD. Faulty drives might cause issues because the system needs input timing. It could also be a simple glitch. If the device starts up normally, disregard any warnings.
R
Robater
04-28-2020, 12:11 PM #6

The bootloader is present on the HDD. Faulty drives might cause issues because the system needs input timing. It could also be a simple glitch. If the device starts up normally, disregard any warnings.

R
Reltzy
Member
111
05-18-2020, 12:50 PM
#7
I’m not sure what the problem is, honestly. It’s running perfectly now, so it must have been a temporary glitch. I think Windows might have crashed or restarted itself, which is why I’m checking for issues right away. This has left me really confused.
R
Reltzy
05-18-2020, 12:50 PM #7

I’m not sure what the problem is, honestly. It’s running perfectly now, so it must have been a temporary glitch. I think Windows might have crashed or restarted itself, which is why I’m checking for issues right away. This has left me really confused.

F
Figgle
Junior Member
13
06-09-2020, 08:54 AM
#8
The bootloader resides on the SSD. The previous/damaged HDD was cleaned and formatted after moving all files to the new drive. I’m leaning toward a bug because everything works just right, though it froze several times during startup before then.
F
Figgle
06-09-2020, 08:54 AM #8

The bootloader resides on the SSD. The previous/damaged HDD was cleaned and formatted after moving all files to the new drive. I’m leaning toward a bug because everything works just right, though it froze several times during startup before then.

_
_sharktapus_
Member
107
06-09-2020, 04:26 PM
#9
I've never encountered anything like this before, huh? Probably not too serious unless it's actually functioning now.
_
_sharktapus_
06-09-2020, 04:26 PM #9

I've never encountered anything like this before, huh? Probably not too serious unless it's actually functioning now.

T
TheCoolNerd
Member
73
06-09-2020, 04:38 PM
#10
Thread combined with a duplicate entry.
T
TheCoolNerd
06-09-2020, 04:38 PM #10

Thread combined with a duplicate entry.

Pages (2): 1 2 Next