Jericho5589
New Member
- Joined
- Jun 16, 2014
- Messages
- 2
- Thread Author
-
- #1
Hello,
recently I've been receiving this error. It always appears when windows is first starting. Usually it will happen once, then once the PC restarts it will boot fine. Just today however, the error repeated itself 4 times, and I was forced to run a system restore(which made me able to boot the pc properly). However, if the issue is becoming worse I would like to get it resolved.
I've run the System File Checker, and will attach the CBS. Corrupted files were found but unable to be repaired.
recently I've been receiving this error. It always appears when windows is first starting. Usually it will happen once, then once the PC restarts it will boot fine. Just today however, the error repeated itself 4 times, and I was forced to run a system restore(which made me able to boot the pc properly). However, if the issue is becoming worse I would like to get it resolved.
I've run the System File Checker, and will attach the CBS. Corrupted files were found but unable to be repaired.
Solution
Trouble
Noob Whisperer
- Joined
- Nov 30, 2009
- Messages
- 13,722
Have a look here http://social.technet.microsoft.com...thandled-wpprecordersys?forum=winserverhyperv
See if the uncompressing of all driver files helps with your particular issue.
See if the uncompressing of all driver files helps with your particular issue.
- Joined
- Oct 16, 2009
- Messages
- 15,156
The file causing the error with the System File Check is that stupid Canon printer file that seems to effect about 85% of users. It is not part of your problem, unless perhaps you actually have a Canon printer.
You can fix that by running the command below in an Admin command prompt.
DISM /online /cleanup-image /restorehealth
You can fix that by running the command below in an Admin command prompt.
DISM /online /cleanup-image /restorehealth
Jericho5589
New Member
- Joined
- Jun 16, 2014
- Messages
- 2
- Thread Author
-
- #4
Thanks for the replys guys, Trouble's solution seems to have fixed it. 3 restarts with no BSoD so far. I will reply again if the problem returns.
Similar threads
- Article