New
#1
Strange boot problem (StartupRepair kicked in)
Hi,
I had some strange thing happen to my relatively fresh system yesterday which I would really like some professional opinion of.
I needed to move the PC yesterday so I switched of the PSU (and pushed the power button after that to clear capacitors). After moving and plugging back in the computer booted directly to startup repair and started a repair process. The info window stated that j:\windows\ci.dll was missing and had to be repaired. (I don't have a partition j: but I guess the letters got remapped during the recovery startup). After restarting Windows booted fine, although Kaspersky did complain about corrupt databases. After another restart this went away as well.
Some research I did on the logs and event managers showed this:
- event viewer says, that the system was unexpectantly shut down when this happened (which it wasn't).
- startuprepair obviously was missing ci.dll and restored the system to an earlier restore point
- volsnap deleted my previous restore points
furthermore system stability also shows errors:
- there was a problem with ReadyBoot
Now, this poses 2 questions for me: Are there any more ways to troubleshoot what happened and can I continue to use the system without fearing that more files got corrupted.
I did run a "sfc /verifyonly" on an elevated command prompt and it came back with no errors. I noticed some small oddities though: my last fm tray icon went back to being red (i had set it to black), there was a firefox addon that still showed in the addon list but wouldn't get loaded. All these I think could be because of the system restore, I think the Kaspersky problem (it complained about databases some boots later again but after a db update it works flawlessly) could be because of this as well...
Long story short, I would really appreciate the opinion of someone who has more insight in what windows does on startup repair and such:
- is there a way for me to find out which restore point was used and is there a protocol of what exactly the startup repair did
- if startup repair used a restore point and fixed files can I be sure that these copies aren't defective (as in: are the backups somehow checksummed)
- I am not sure how old the last restore point would have been, but I am guessing that I can't have changed that many settings after that (except for the stuff I mentioned). What are the chances that other programs are affected.
I am quite paranoid about data integrity (hence all these questions), so I guess it boils down to this question:
If there was an error on my disk (which is an SSD), can I continue to use the system in this situation or is it likely that more files are affected and my programs will work faulty? Should I just wait and see how the system behaves? Or would you instantly reinstall?
To sum up: after the events I described the systems seems completely normal and stable, there wasn't any error afterwards, the only things I noticed were the settings that changed (most likely because of startup repair setting the system back to an earlier restore point).
Sorry if this was quite a long text, I tried to provide as much info as possible. If there's any more I can provide in terms of logs etc. please let me know. Also, feel free to throw technical stuff at me, I am in the Computer Science field as well and would really like to know inside info as to what happened
many thanks
Markus
Quote