[Critical] Recovered from automatic boot-loops - cache manager error. what to do now?!

[GhorMaanas]

[Solved] Recovered from automatic boot-loops - cache manager error. what to do now?!

Hello!

last night, i was formatting a flash-drive in Ubuntu on my VMWare player machine, when, forgetting to eject the drive first in Ubuntu, i disconnected it from 'removable devices' in the VMWare player. suddenly, i encountered the infamous blue-screen-with-a-sad-smiley error - 'your pc ran into a problem. we are collecting info and will restart it for you'. (try to search for this error later on - CACHE_MANAGER).

this was a first for me. the PC kept re-booting, without making it to the desktop shell. on every 2nd reboot, used to get the 'automatic repair' screen, of which, i tried the following:

0. shut down the PC for 10 mins, and then restarted - failed.
1. startup repair - failed.
2. startup options - cancel automatic restart upon failure --> success.
3. --"-- - safe mode (with and without networking) --> failure.
4. command prompt --> success.

i thought of keeping the 'system restore' option for the last.

from the command-prompt, i ran chkdsk for each partition, plus the memory diagnostic utility. both passed without any error. after a lot of hunting, occurred to me that since everything seems to be fine, and the error is about 'cache', and that even safe mode isn't booting, perhaps removing and re-plugging one of the memory-modules should work. i then shut down the PC, switched off the power-supply, removed the power-chord, and thought to disconnect & then reconnect the connector on the HDD and then remove the memory-modules in the morning, and re-plug only one of them to check the boot-status. however, had the hope that perhaps keeping it shut down for a few hours would solve the issue. prayed frantically & sincerely to the Lord, and retired to the bed. morning, got up, prayed again, and taking the almighty good Lord's sweet name, reconnected the power-chord and turned on the power-supply, and voila! it was back on (though a bit slow at start-up, but something better than nothing)!

now am afraid to restart or shut it down, or to run VMWare player again, unless am satisfied that i have rectified the issue wholly. hence, i seek your suggestions on what to do next to eradicate the issue completely, or/and prevent this from happening again.

some specifics:

Host OS - Win 8.1
Mainboard - Asus P8Z68V-Pro
RAM - 4GB x 2
SATA config - IDE (had tried to re-change it to AHCI in the BIOS y'day night, but then the restarts became quicker, without even showing up the error-screen before each restart)
Intel VT - for the moment, turned off
Virtual machine - VMWare player
OS on the VM - Ubuntu (latest)
RAM alloted to the VM - 2GB

do you suggest to fix the MBR, or something like that? or is it advised to follow the steps, particularly the last one, mentioned in the following linked-pages?!

Your PC Ran Into A Problem Windows 8 Fix

Your PC Ran Into a Problem and Needs To Restart - Windows 8

- - - Updated - - -

checked event-viewer. couldn't find/realise any particular event related to the error. then did system file-checker test. got the prompt that some corrupt files could not be fixed. am sharing the log-file for it here. please have a look towards the end. an advise could be to boot in safe-mode and re-run sfc, but am not quite comfortable in rebooting the PC unless someone positively replies on my question above:

*www.dropbox.com/s/9j5znazlprlpk77/CBS.log?dl=0

- - - Updated - - -

UPDATE 2:

ran a 'component store repair' DISM process. here's the result:

*i.imgur.com/sBQSunMl.jpg

 

[Vyom]

One question. Why you need to use a physical Pen drive on Virtual Ubuntu, when you can load a virtual removable driver or an ISO image through VMWare?
Maybe you can just avoid it in future, and be done with the problems that you maybe facing with using Pen drive on Virtual Ubuntu.

But reboot loop is a strange effect of a result from some VMWare issue. You tried using one module of RAM at a time? Also Cache Manager issue seems to be an issue related to Page file. How much page file memory you have allocated? Try to increase it.

 

[GhorMaanas]

yes, it seemed to be memory/page-file related issue, and hence, i finally decided to keep the PC powered off for some time, and if need be, restart with only one RAM module in its slot. however, thankfully, the PC boot up just fine upon powering it up after some hours, so didn't require the one-module start. although there was/is a pagefile set for my windows boot partition, that contains the windows folder & installation-files (system-managed pagefile), but the other partitions didn't have a pagefile on them (never felt the need to have them set). i later on set the pagefile for each partition (custom). VMWare player is installed on one such non-boot partition, the one where i usually install softwares.

i was using a flash-drive on the virtual Ubuntu to format it, create partitions, and set filesystems (linux) on it, under the command-terminal & GParted, for use in my other linux-box (a NAS-dock), to download & install debian & its packages on that flash-drive when connected to the dock. since i just disconnected the flash-drive from VMWP's taskbar after formatting it, without actually first ejecting it from Ubuntu itself, that's what must've caused the error to surface, as it came up instantaneously (also, i have allocated 2GB of the total memory to VMWP). a few days back (ie, before this issue), i had read somewhere how disconnecting a USB-drive before first actually ejecting it (on Win as well as on Linux/Ubuntu) could be moderately to severely harmful; now i was a direct witness to that.

though now the PC is thankfully running fine, as always, in the wake of every good or bad thing that happens, there are lessons to be learnt & imbibed. lessons learnt here are:

1. always remain attentive, to first eject a USB-drive from the software, before attempting to disconnect it.
2. the value of 'system restore' and paying regular attention to either manually creating a restore-point after any significant software/hardware upgrade, or checking automatically created restore points, is of prime importance.
3. similarly significant is creating regular back-ups of your (important) data.
4. don't neglect regular maintenance of your PC, be it physical, or software-based, like checking the health of HDD and defragging it regularly, scanning the system for errors and fixing them, etc., etc.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

in my search for a solution to this 'your PC ran into a problem....' screen, pertaining to the particular 'cache manager' error, i couldn't find any significant remedy for it. hence, i hope that this thread here could show up in google search if someone else facing this error is searching for a solution to it.
the remedy (atleast what worked for me) is, if one can wait, to shut down the PC and disconnect the power for a few hours (or may be even for just 15-20 mins, but be sure to disconnect the power too, after shutting down the PC), and then reboot and see, and if that doesn't help, then try the one-RAM-module test to check the start-up. if both fail, then proceed with the 'automatic repair options', in which, disable 'automatic restarts', then 'refresh your pc' (and NOT 'repair'), trying to boot into safe-mode, or/and run the command-prompt and run chkdsk, memory diagnostic utility, and dumping either small or complete memory from 'startup & recovery' menu when logged into 'safe-mode'. keep 'system restore' as a 2nd last option (this should anyway work), and re-installing Windows, either clean or retaining your settings, for the last.