Hello, I am new user and member, KBT. I am having a problem, and as the few others who had similar problems' solutions didn't work, I thought I would be straightforward and create a new thread to attract attention rather than posting in an old one. Forgive me if this is improper conduct.
WARNING: Wall of Text Ahead
My computer is about a year old, and has had no major issues until a few days ago. For the first time, and I do not know why, on startup, Startup repair... started. I was not even aware of this programs existence until that moment. After a lengthy wait time, I was asked to restart. I restarted, used my computer as normal, wrote it off as nothing more than a virus, and performed a full scan with MS Security Essentials (and later, at the behest of a much more knowledgeable friend, another with Malware Bytes'). Two startups later, and the process repeats. This time, I view the results. The root cause was something called error "0xa" in which critical file ci.dll failed to boot (paraphrased). I was also missing several files, and had a few I'd deleted. I went online, did as the first google result said without any thought, and moved on. Every second startup would still have to repair, and occasionally a few files would follow the same fate (thanks to an event called "restore point" I later discovered). Tired of it happening and eating so much time to find and "fix" the problem, I started trying other measures: sfc/scannow, disabling startups in MS Config, and sfc/verify. No changes. Being the arrogant dumba** I am, I thought I could just delete ALL past restore points and create a new one every time I was about to start my computer, and just deal with having to wait only five additional minutes before shutdown as opposed to 2-3 hours before startup. Good news: ci.dll is no longer listed as the problem. Bad news: startup repair cannot find the problem (which is listed as the "root cause", and I can't even enter Safe Mode. I have actually tried a "Restore to system default" and was rewarded with a single, brief glimpse of no data before the problem persisted. I have also tried Dzomlija's repair, and no luck. As I no longer have anything left to lose, and it is all just data that can be regained eventually, I have no problems with having to remove any and all memory. However, is there is a way to avoid this, as well as a way to prevent it from ever happening again, I open to ideas.
My laptop is an eMachine that boasts Windows7 and intel Celeron. I personally know no way to tell you anything else about it, do not have any sort of disk in the box (though I do have a small book wrapped in plastic, but alas, no disc was within), hate long walks in direct sunlight, and could probably write what I know about computers on a cigarette with a sharpie.
TL;DR I got problems, ese, and I already did this (http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html).
WARNING: Wall of Text Ahead
My computer is about a year old, and has had no major issues until a few days ago. For the first time, and I do not know why, on startup, Startup repair... started. I was not even aware of this programs existence until that moment. After a lengthy wait time, I was asked to restart. I restarted, used my computer as normal, wrote it off as nothing more than a virus, and performed a full scan with MS Security Essentials (and later, at the behest of a much more knowledgeable friend, another with Malware Bytes'). Two startups later, and the process repeats. This time, I view the results. The root cause was something called error "0xa" in which critical file ci.dll failed to boot (paraphrased). I was also missing several files, and had a few I'd deleted. I went online, did as the first google result said without any thought, and moved on. Every second startup would still have to repair, and occasionally a few files would follow the same fate (thanks to an event called "restore point" I later discovered). Tired of it happening and eating so much time to find and "fix" the problem, I started trying other measures: sfc/scannow, disabling startups in MS Config, and sfc/verify. No changes. Being the arrogant dumba** I am, I thought I could just delete ALL past restore points and create a new one every time I was about to start my computer, and just deal with having to wait only five additional minutes before shutdown as opposed to 2-3 hours before startup. Good news: ci.dll is no longer listed as the problem. Bad news: startup repair cannot find the problem (which is listed as the "root cause", and I can't even enter Safe Mode. I have actually tried a "Restore to system default" and was rewarded with a single, brief glimpse of no data before the problem persisted. I have also tried Dzomlija's repair, and no luck. As I no longer have anything left to lose, and it is all just data that can be regained eventually, I have no problems with having to remove any and all memory. However, is there is a way to avoid this, as well as a way to prevent it from ever happening again, I open to ideas.
My laptop is an eMachine that boasts Windows7 and intel Celeron. I personally know no way to tell you anything else about it, do not have any sort of disk in the box (though I do have a small book wrapped in plastic, but alas, no disc was within), hate long walks in direct sunlight, and could probably write what I know about computers on a cigarette with a sharpie.
TL;DR I got problems, ese, and I already did this (http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html).
My Computer
At a glance
Windows 7 64bit
- OS
- Windows 7 64bit
. I then ran SR 3 times in a row before restarting my laptop. I still have that ImgBurn on my laptop (the last thing I was able to download after System Default), but since I was supposed to backup any data on a portable medium, I can't help but feel that I've screwed up. I have to restart/shutdown for some updates, so I'll try SR before boot once more to see if anything persists and update you then. Whether this does it or not, thank you so very much, especially you, Scarecr- er, gregrocker.
