New
#1
Dell XPS M1530 Startup Repair Loop, Offline SFC does NOT function
Dear Everyone,
Sorry to trouble all of you, but I've pretty much exhausted my google-fu. Thus, I figured that I should stop trying to throw things against the wall, and rather just see if there's someone wiser here who can help me out. Now, before you tell me, I am totally aware that I could easily cut my losses just by doing a re-install, which would make the Windows.Old folder and such, most of which can be easily put back via a command prompt script. However, being that this computer has software whose installation disks I do not have, I do NOT want to do a re-install, since it'll break program association and possibly other things which I cannot correct by re-installing them.
As far as I know, the machine in question is a Dell XPS M1530, with Intel Core 2 Duo T7250, Nvidia 8400M GS, 2GB RAM, and WD Scorpio Blue 250GB Hard Drive. It is running Windows 7 Ultimate, upgraded from Vista Home Premium, with all updates, software patches, and security fixes current according to Windows Update. As far as virus and malware goes, it has ESET NOD32 v4.7, Malware Bytes, and Spybot-S&D installed, with each being fully updated and scans immediately prior to the crash stating that the machine was clean. In addition, after the crash, I attempted to scan it with Avira, Dr. Webb, and Hiren's Boot CD, all of which stated that the machine is free of infection/threat.
Below, I'll attempt to take you guys and gals through everything, from the initial symptoms to the bag of tricks that I've employed, with each of its effect(s):
- Initial Outbreak & Symptoms: The Computer was fine, with everything being in tip top shape. However, being that Mozilla Firefox 10.2 had been stuck on loading a page when I attempted to shut it down, I used the "hold power button for 4 seconds" method to force it to quit (Yes, I know I shouldn't have done it.). Afterward, the system booted up and proceeded to go through the Dell Logo BIOS, followed by a brief version of the Windows 7 Waving Flag Splash screen. But, it abruptly changes into the Windows RE "Loading Windows Files" white bar, which leads to the Startup Repair. Initially, Startup Repairs states that the system had some corrupt files, which it will not be able to repair. The System then rebooted itself. At this point, I cannot launch Safe Mode (Any), pressing F8 does not lead to anything, and booting never completes.
- Treatment 1: Using Windows RE, I launched Chkdsk C:/R /X, which found and weeded out quite a few entries of corruption on the first run, which was corrected then and never showed up in any of the repeated scans of Chkdsk. Currently, when Chkdsk is run, it reports that it found no problems.
- Treatment 2: Trying to figure out if I messed up any hardware, I attempted to run Dell's built-in Diagnostic system, which initially told me that the Hard Drive was not detected with an error of 2000-0141 or 2000-0146 (they alternated), which is stated by Dell to be fixable by the removal and reinsertion of the Hard Drive, which was true. However, I've never been able to get through a scan without the 2000-014X error log, since it appears to be stuck in the log "from a previous scan", even though it has been corrected. As far as I can tell, the physical hard drive is fine, if its connection might have been a bit loose when the first scan was run.
- Treatment 3: Using Windows RE and CMD, I used the Startup Infinite Loop Registry trick, even though the file sizes of everything in my regback was drastically different than in the guide. However, being that I read others had mentioned they've got varying sizes (All nonzero) also, I thought I might be okay. Indeed, I thought things got a bit better afterward, since it brought back the ability to launch the Advance Boot Options via F8. Although, testing revealed that booting to Safe Mode (Any), Last Known Good Configuration, and Start Normally all result in the Startup Repair situation.
- Treatment 4: Just as a Hail Mary, I tried Bootrec /FixMBR and /FixBoot, both of which did NOT resolve the situation. However, it did seem to make the boot process more smooth and lasted somewhat longer before the Startup Repair takes over.
- Treatment 5: Now, this is the first and last thing I tried, so trust me when I say that this machine does NOT like SFC right now. Initially, when run via Hard Drive, SFC /Scannow yielded a message about Windows Protection Resource not able to perform. However, if run by Installation CD, SFC /Scannow says that it is waiting for a repair to complete, which requires a restart... even after it was restarted. Now, regardless of running it via CD or Hard Drive, if I use "SFC /Offbootdir=C:\ /Offwindir=C:\Windows", I get a little frozen stuttering cursor that blinks for a bit, then a message stating that "SFC Found Corrupt Files, but it was unable to repair them."
- Hypothesis: After throwing a whole bunch of tricks at it, now Startup Repair makes through the scan and states that it cannot figure out what is wrong. Yet, every time I turn on the computer, this problem pops up. Based on my thoughts, I'm of the mind that if SFC could run, it could probably easily fix whatever corruption there exists. Unfortunately for me, I'm like a guy with a loose screw whose screwdriver has broken off its handle. Thus, I'm of the mind that if one of you guys and gals and point me to salvation, I'd be really grateful. Why? Well, my reasons are:
- If you wish, you can find the extended CBS Log here. The computer broke on 02/22/2012, which means that the SFC haven't been logging, or perhaps doing, anything for the past few days, even as I've been repeatedly trying to run it, which leads me to think that my screwdriver's kaput.
- Going by the CBS Log, you can see that between 02/12/2012 and 02/20/2012, the SFC was running successfully, along with that nasty little percentage bar. However, when I attempt SFC of any kind now, there is no percentage bar, just a crazy little blinking cursor, followed by the "corrupt and unrepairable" message.
- Current State: When Startup Repair is run, whether repeatedly or just once, it keeps on telling me that it cannot repair the problem. However, when you check out the details, it tells you that it cannot figure out what the problems are, as the machine passes all of its tests. Yet, it still is stuck in the loop. Occasionally, it'll say that the flaw resides with rdyboost.sys file being corrupt, but if I do chkdsk and recheck, it states that it can't find anything wrong.
- Caveat: Sorry about this, everyone. But, please keep in mind that:
- While I would LOVE to do a repair install, I cannot do it because I cannot log into Windows, and Windows 7 only allow repair install from inside the OS! (What idiots designed this?!)
- I have checked everything from CPU to RAM to the display cables, everything is now well connected. So, I do not think that it is a loose connection.
- Yes, I know that you'd probably advise me to just re-install, which I could easily do so. But, as I mentioned, I know that it'll break all kinds of software and stuff, leaving me a big mess and unable to fix them due to lack of installation media. I really don't want to do it, unless there's literally no other way, which I find surprising.
Please, everyone. Help me out here. How the hell do I help the program that's supposed to be helping me?! How does one manually switch in a good rdyboost.sys file? Help?