System has recovered from a serious error
The error message windows has recovered from a serious error can mean a number of things, but much of the time it’s not quite as dire as the message would have us believe.
What causes the error? this is virtually impossible to say due to the wide variety of possibilities, but by applying a little bit of deductive reasoning we can usually ascertain what causes this.
For example has anything recently been installed? If it’s a laptop computer in a docking station was it undocked correctly, so the error usually indicates that something has changed on your computer, this can also include system or application updates or even when a computer is left and a screen saver or power saving cuts in.
One of the ongoing problems that can occur after a system has recovered from a serious error is the problem of the error being repetitive; this can be very deceptive as it looks as though the error is actually occurring again and again, whereas it’s a flag in the paging file that is not being reset.
The way to get around this is to reset the paging file; there are two methods of doing this
- From the Start Menu > Control Panel > System > Advanced > Settings > Advanced > Change > Make a Note Of Your Page File Settings & Selectno paging file > Set > Now change your page file settings back to the previous > Set, once done click ok, ok, ok and restart your computer.
- Go to the Start menu > Run > type secpol.msc > Local Policies > Security Options > find Shutdown: Clear virtual memory pagefile > change option to Enabled, as below
This will force Windows to clear the page file on shutdown; it may mean that Windows may take slightly longer to shutdown however as the Paging file can get very large.
Apart from clearing persistent errors it also removes a security risk as keeping the paging file after shutdown does mean a copy of any file is still resident on your computer.
To help prevent this error make sure that your computer is kept up with the latest Microsoft updates, Microsoft’s update fix for this issue is 322389
Search for more on when system has recovered from a serious error