F5F Stay Refreshed Software Operating Systems Code for boot loop issue

Code for boot loop issue

Code for boot loop issue

F
foxiflaimeur
Member
110
09-18-2016, 08:49 PM
#1
I just set up Windows 10 on my new HDD. It booted after a while when I first tried, but after an update it had some issues yet functioned. When I updated again, it entered an automatic repair mode and started diagnostics. After three hard restarts, it reached the Automatic Repair window, where error details were listed in SrtTrial.txt. I checked it and saw a 0x0 error code, with only one check for LCU showing a 0x17 error. I suspect this might be the cause, but I couldn’t find a solution online. I ran the chkdsk /f/r command and got an error message: '766f6c756d265e63 470'. Searching online didn’t yield any answers. One person claimed it worked by pure luck. Can you help me figure this out?
F
foxiflaimeur
09-18-2016, 08:49 PM #1

I just set up Windows 10 on my new HDD. It booted after a while when I first tried, but after an update it had some issues yet functioned. When I updated again, it entered an automatic repair mode and started diagnostics. After three hard restarts, it reached the Automatic Repair window, where error details were listed in SrtTrial.txt. I checked it and saw a 0x0 error code, with only one check for LCU showing a 0x17 error. I suspect this might be the cause, but I couldn’t find a solution online. I ran the chkdsk /f/r command and got an error message: '766f6c756d265e63 470'. Searching online didn’t yield any answers. One person claimed it worked by pure luck. Can you help me figure this out?

T
Turtle02536
Junior Member
22
09-18-2016, 09:43 PM
#2
The drive is functioning properly.
T
Turtle02536
09-18-2016, 09:43 PM #2

The drive is functioning properly.

F
Fes0
Junior Member
11
09-18-2016, 10:22 PM
#3
No, your CPU is not overclocked.
F
Fes0
09-18-2016, 10:22 PM #3

No, your CPU is not overclocked.

T
52
10-03-2016, 10:06 PM
#4
It happened at 2.2GHz back then, but a year ago I pushed it up to 2.4GHz, and according to the specs, it can reach up to 2.6GHz. Why is this causing an issue?
T
TheStreetFlyer
10-03-2016, 10:06 PM #4

It happened at 2.2GHz back then, but a year ago I pushed it up to 2.4GHz, and according to the specs, it can reach up to 2.6GHz. Why is this causing an issue?

L
Lord_Phoenix77
Junior Member
3
10-06-2016, 10:53 AM
#5
It could be. Verifying it is simple.
L
Lord_Phoenix77
10-06-2016, 10:53 AM #5

It could be. Verifying it is simple.

U
urukhei
Junior Member
36
10-11-2016, 03:40 PM
#6
It was only the messed-up filesystem, a random hex label from an NTFS folder, that got resolved. Make sure you check your hard drive health with CrystalDiskInfo to confirm it’s not failing.
U
urukhei
10-11-2016, 03:40 PM #6

It was only the messed-up filesystem, a random hex label from an NTFS folder, that got resolved. Make sure you check your hard drive health with CrystalDiskInfo to confirm it’s not failing.

E
elgrandetaco77
Junior Member
11
10-22-2016, 10:25 AM
#7
Its a brand new HDD. And even after that it wont start. I even tried resetting it, but it did nothing.
E
elgrandetaco77
10-22-2016, 10:25 AM #7

Its a brand new HDD. And even after that it wont start. I even tried resetting it, but it did nothing.

S
Stainbes
Junior Member
48
10-22-2016, 03:41 PM
#8
I’d probably begin testing the hard drive on another machine first to rule out its issues, since a forced shutdown could corrupt the filesystem. Running chkdsk might help fix any problems, but I wouldn’t assume the drive is faulty just because it’s new—make sure the installation media and .iso are correct before proceeding. Edited February 16, 2019 by Guest
S
Stainbes
10-22-2016, 03:41 PM #8

I’d probably begin testing the hard drive on another machine first to rule out its issues, since a forced shutdown could corrupt the filesystem. Running chkdsk might help fix any problems, but I wouldn’t assume the drive is faulty just because it’s new—make sure the installation media and .iso are correct before proceeding. Edited February 16, 2019 by Guest