F5F Stay Refreshed Hardware Desktop System failure detected during SFC check PC remains powered off despite scan completion

System failure detected during SFC check PC remains powered off despite scan completion

System failure detected during SFC check PC remains powered off despite scan completion

Pages (3): Previous 1 2 3 Next
B
bronzered
Member
74
12-27-2016, 04:43 PM
#11
Is your setup functioning well? No issues detected? Everything seems stable. If you noticed something but it wasn’t obvious, let me know. If not, I’ll help identify what’s causing the concern. We need to understand your concerns together.
B
bronzered
12-27-2016, 04:43 PM #11

Is your setup functioning well? No issues detected? Everything seems stable. If you noticed something but it wasn’t obvious, let me know. If not, I’ll help identify what’s causing the concern. We need to understand your concerns together.

E
ElitexWizard
Member
210
01-02-2017, 07:29 PM
#12
Only the message from the ASUS MMO part of the boot has appeared lately. When I opened the over provisioning section in Magician, it warned that the volume might be corrupt—never interacted with that tab before or even understood its purpose. I performed a manual scan, which triggered when the system boots, and the final result matched the image shared in the previous post.
E
ElitexWizard
01-02-2017, 07:29 PM #12

Only the message from the ASUS MMO part of the boot has appeared lately. When I opened the over provisioning section in Magician, it warned that the volume might be corrupt—never interacted with that tab before or even understood its purpose. I performed a manual scan, which triggered when the system boots, and the final result matched the image shared in the previous post.

R
RonniMolo4ko_
Member
172
01-04-2017, 06:25 AM
#13
And the only other odd occurrence was that once the scan corrected the issues and I powered off and restarted the computer, it stopped working again :9. After a thorough reboot, it functioned properly. It turned out this problem appeared around six times during the week, not just once. Volume C needs to be disconnected for a full disk check. Use "CHKDSK /F" from the command line or run "REPAIR-VOLUME <drive:>" locally or remotely with PowerShell.
R
RonniMolo4ko_
01-04-2017, 06:25 AM #13

And the only other odd occurrence was that once the scan corrected the issues and I powered off and restarted the computer, it stopped working again :9. After a thorough reboot, it functioned properly. It turned out this problem appeared around six times during the week, not just once. Volume C needs to be disconnected for a full disk check. Use "CHKDSK /F" from the command line or run "REPAIR-VOLUME <drive:>" locally or remotely with PowerShell.

D
DoodyMon
Member
55
01-17-2017, 10:51 AM
#14
Alright, just remember that.
D
DoodyMon
01-17-2017, 10:51 AM #14

Alright, just remember that.

M
MilitaryGaming
Junior Member
10
01-17-2017, 01:12 PM
#15
You might want to run CHKDSK to check your disk health. Don’t worry about the photos—backing them up is important.
M
MilitaryGaming
01-17-2017, 01:12 PM #15

You might want to run CHKDSK to check your disk health. Don’t worry about the photos—backing them up is important.

D
darkwolf644
Member
183
01-19-2017, 03:06 AM
#16
It's wise to back up your data. We're here to help with any questions you have. Disabling notifications can be tricky—remember I faced a similar issue before and had to reset the system. A good idea was to run the disk check again and restart your computer, using commands like 'Run (x for drive letter)' followed by 'chkdsk x:' and 'chkdsk /f /r x:' in drive C, setting it for next restart if needed. Keep an eye on the results.
D
darkwolf644
01-19-2017, 03:06 AM #16

It's wise to back up your data. We're here to help with any questions you have. Disabling notifications can be tricky—remember I faced a similar issue before and had to reset the system. A good idea was to run the disk check again and restart your computer, using commands like 'Run (x for drive letter)' followed by 'chkdsk x:' and 'chkdsk /f /r x:' in drive C, setting it for next restart if needed. Keep an eye on the results.

B
Broflash
Senior Member
740
01-19-2017, 03:15 AM
#17
Yes, you execute both commands. One for general checks and another to repair errors on drive C.
B
Broflash
01-19-2017, 03:15 AM #17

Yes, you execute both commands. One for general checks and another to repair errors on drive C.

N
nini0212
Junior Member
38
01-19-2017, 09:10 AM
#18
yes
N
nini0212
01-19-2017, 09:10 AM #18

yes

T
240
01-23-2017, 06:57 PM
#19
I executed the initial command and received the results in the prompt (images attached). Then I performed the second step. It prompted a restart, which I did, and it repeated the disk repair twice, briefly turned the screen black, then launched into Windows XP. I’m puzzled but seem to think the drive is functioning properly.
T
TheDonnelTrain
01-23-2017, 06:57 PM #19

I executed the initial command and received the results in the prompt (images attached). Then I performed the second step. It prompted a restart, which I did, and it repeated the disk repair twice, briefly turned the screen black, then launched into Windows XP. I’m puzzled but seem to think the drive is functioning properly.

N
226
01-23-2017, 08:04 PM
#20
Everything seems fine. However, did the message vanish once the system restarted?
N
n_tiffanyblue_
01-23-2017, 08:04 PM #20

Everything seems fine. However, did the message vanish once the system restarted?

Pages (3): Previous 1 2 3 Next