Quizzes & Puzzles2 mins ago
Explanation Please From Those In The Know.
This is not a serious problem, just a minor irritation which is really getting on my titties.
Almost always, when I power up my laptop, I am greeted with the following:
(: Your PC has run into a problem and will need to restart. We're just collecting error information and then we'll restart.
I then get the message: "To skip disk checking press any key within x seconds"
The whole process takes less than a minute, but I find it intensely annoying. (Patience is the one virtue which has passed me by).
Has anyone else experienced this?
Almost always, when I power up my laptop, I am greeted with the following:
(: Your PC has run into a problem and will need to restart. We're just collecting error information and then we'll restart.
I then get the message: "To skip disk checking press any key within x seconds"
The whole process takes less than a minute, but I find it intensely annoying. (Patience is the one virtue which has passed me by).
Has anyone else experienced this?
Answers
Best Answer
No best answer has yet been selected by Jackdaw33. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.Theres a fix here
http:// www.the windows club.co m/your- pc-ran- into-a- problem -and-ne eds-to- restart
Not sure how easy to do though maybe wait for the experts here first
http://
Not sure how easy to do though maybe wait for the experts here first
I would run a disc error check.
Open windows Explorer and right-click on your system disc.
Choose "properties" and then the "Tools" tab.
Under "Error Checking" click "Check now" and tick both option boxes.
You willget a message saying the disc is in use and offering to do the check when you restart - agree.
Next time you start your computer it will warn you it is about to start a disc check and offer you an opt out (just in case you're too busy to wait).
Your system disc will be thoroughly checked and any "iffy" sectors will be replaced.
Discs have spare sectors so that, if a sector starts to become difficult to read/write it can be replaced by a spare.
This process can take a while, depending on the size of disc, but worth doing if you think there might be problems. No guarantee it will fix your problem but is completely harmless and cannot possibly make the system worse.
Open windows Explorer and right-click on your system disc.
Choose "properties" and then the "Tools" tab.
Under "Error Checking" click "Check now" and tick both option boxes.
You willget a message saying the disc is in use and offering to do the check when you restart - agree.
Next time you start your computer it will warn you it is about to start a disc check and offer you an opt out (just in case you're too busy to wait).
Your system disc will be thoroughly checked and any "iffy" sectors will be replaced.
Discs have spare sectors so that, if a sector starts to become difficult to read/write it can be replaced by a spare.
This process can take a while, depending on the size of disc, but worth doing if you think there might be problems. No guarantee it will fix your problem but is completely harmless and cannot possibly make the system worse.
By ignoring this problem you could be storing up an even bigger problem
The error message is indicating a dodgy sector that could go bad at some point, if this sector contains data you may just lose a file or two (unlikely to be a data sector as windows does not check data files on boot up) if however the sector contains a Windows system file you may well not be able to boot your computer
Do as BHG has suggested
The error message is indicating a dodgy sector that could go bad at some point, if this sector contains data you may just lose a file or two (unlikely to be a data sector as windows does not check data files on boot up) if however the sector contains a Windows system file you may well not be able to boot your computer
Do as BHG has suggested
If you are experiencing persistent boot errors be sure to have your data backed up as it indicates a faulty hard disk
Among other things it could be multiple sectors going bad or a problem with the boot sector
There are certain files stored on a hard drive that have to be in a certain sector of the disk (The boot sector) if this sector becomes bad the whole disk will become unusable, these files cannot be moved to another sector so while windows may detect an error it can do nothing about it. This is a worst case scenario.
Back up your data
Among other things it could be multiple sectors going bad or a problem with the boot sector
There are certain files stored on a hard drive that have to be in a certain sector of the disk (The boot sector) if this sector becomes bad the whole disk will become unusable, these files cannot be moved to another sector so while windows may detect an error it can do nothing about it. This is a worst case scenario.
Back up your data
Tricky one Jackdaw. HP and Microsoft are aware of the issue that came about after the recent Creators update. If you are pretty teched up there is a fix if not I would wait and see but let the scans run for now until they provide a patch. As you have said it is not massively inconvenient but a little disconcerting for sure.
The Creators Update Microsoft came with KB4016871.
With that Microsoft updated "autochk.exe" (C:\Windows\System32) to version "10.0.15063.296" .
That should have addressed the following issue where autochk.exe can randomly skip drive checks and not fix corruptions, which may lead to data loss. But on certain systems notably HP laptops didn't. If you know how to replace autochk.exe with the previous version "10.0.14393.0"
Otherwise I would wait a while. It has strangely been a huge issue in Holland.
The Creators Update Microsoft came with KB4016871.
With that Microsoft updated "autochk.exe" (C:\Windows\System32) to version "10.0.15063.296" .
That should have addressed the following issue where autochk.exe can randomly skip drive checks and not fix corruptions, which may lead to data loss. But on certain systems notably HP laptops didn't. If you know how to replace autochk.exe with the previous version "10.0.14393.0"
Otherwise I would wait a while. It has strangely been a huge issue in Holland.
Been having a look around and it appears that instead of reverting to an older system check version some people have found that if they go into AutoChkSkipSystemPartition and change the 0 to 1 it cures it. Again not for the less than advanced user.
You can find that Via System\CurrentControlSet\Control\Session Manager\AutoChkSkipSystemPartition.
You can find that Via System\CurrentControlSet\Control\Session Manager\AutoChkSkipSystemPartition.