Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. I Don't know if this is the right section to put my thread, but I could not find anywhere else, since I am using Vista SP1 at the moment. The Loading bar will appear for 1 second, then it will flash a BSOD for half a second before rebooting, too quickly to read the STOP error code, so i cannot tell you which error it is.
I cannot escape this loop, and I have tried many things, from Checkdisk, to System Restore, to Startup repair. Safe mode will not work either, as it still has to pass the Splash Screen.
I do have a repair disc for Vista, however it did not do anything, as all it does is offer me tools such as Startup repair and System restore I have browsed endless threads and have not found one that is exactly similar to mine. Over the years I've had the unfortunate stance of talking with many manufacturer's technical support people. I don't know the exact reason why, but it is likely a combination of things -- they hire unknowledgeable people that read from a database of problems, those that do know what is going on and can think their way out of a paper bag get sucked into product development, and sometimes I just can't understand the person's words through their thick accent.
Most often their solution is "Can you reinstall from scratch? That fixed the problem. Thank you, come again! Kind of overkill. But believe it or not, sometimes that is the most cost effective way to get rid of that squeak -- wipe it out and start over.
At least it is cost effective for them. They don't care about the client, the data on the system, or the time it will take to get all those programs re-installed and re-configured so it will work right.
I'm sure within the bowels of Microsoft there are people that are very adept at bringing systems back from death without data loss, but none of us mere mortals will ever talk to them via the usual technical support channels. My godson gave me his computer and let me have my way with it. This particular system came with an HP Recovery Disk, which unfortunately was only good for reinstalling the operating system.
Most standard XP Install disks allow you to boot into a 'Recovery Console', which lets you boot a system and look around at various files. So I grabbed one of my other XP disks, booted into the recovery console, and had a look at various files. Starting in December , his system had been getting them pretty regularly. Gateway is long done developing drivers for this model, so I get to live with the bugs and various reboots.
Most of the time BSODs are due to bad or buggy driver code. Drivers are the software that makes specific hardware devices work like your screen, sound, bluetooth adapter, etc. Increasing frequency points to something that is getting worse and worse, perhaps a hardware problem or new software that is buggy and causing the BSOD. I needed to do a crash dump analysis on the dump file to see what the cause was, and if it was the same thing over and over again or something different each time.
But the recovery console doesn't let you copy files off to anything but a floppy disk, which this notebook doesn't have. What is a crash dump? Back in the old days, we wrote our programs by punching cards, wrapping some JCL Job Control Language cards around our program deck, and gave it to an operator through a cubby hole into the computer room. They took our program deck, ran it, and gave it back to us wrapped up with a printout of our program's execution output.
Sometimes our program went completely haywire and crashed badly. When it did, the computer not knowing exactly what to do dumped out all the memory as hex or octal numbers in a list to the line printer. This was called a 'core dump' and by looking over what was in memory when the program did its bad crash we could see exactly what it was doing at the time of the crash and hopefully figure out where our program went haywire.
Everything old is new again. The crash dump file is similar in concept to that memory dump of those old days. In fact, options will let you save different sized memory dumps in case you need more to analyze. See the box 'Write debugging information' in the screen shot here: What is really nice is Microsoft has automated much of the manual analysis of these dump files -- you can load up a dump file into the debugger, ask it to analyze, and sometimes it will tell you which driver or program caused the problem.
These are the Nvidia Display drivers for this particular notebook. DLL file back to how it was. The other thing I noticed was the new minidump files weren't created as the system was doing its reboot loop. They were recent, but not happening every time. So whatever was making the reboots now wasn't far enough into the boot process where the system knew enough to create new minidump files. The system also rebooted pretty quickly -- from the Windows XP splash screen and moving bar at the bottom it would flash the blue screen and immediately reboot.
There is an option -- see the screen shot above -- to not automatically restart, but given the system couldn't be booted you had no easy way to uncheck that box so you could read the screen. In cases like this, stopping time will let you see the screen, which I've had good luck using a small digital camera with a movie mode in it.
That or stare intently reading as much of the screen as you possibly can, put together what the error message is. Unfortunately, the repair directory has what registry file was created when you first installed your computer's operating system.
I'm unaware of anything that updates that repair directory with a newer copy. Ok, so the software registry hive is corrupted. The good news: Copying this older software registry file let the system boot. The repaired registry was 8,KB big. The bad registry was 28,KB big. But at least the notebook would boot now. All kinds of programs that were attempting to start weren't working right, nor should they be expected to work right -- their critical information had been lobotomized out of the registry.
This was AM on Friday. I started a disk scan to see if there were bad sectors and went to bed. I'd been poking at the system for a little over an hour. Friday AM I resumed working on the notebook. Disk scan seemed OK, but the old registry file still gave CRC errors when I tried to copy it, so it is likely a 'soft' error on disk -- one that would be corrected if the bad block was written to with zeroes. These are often caused by abruptly powering off while the disk is writing.
So, how do we get the software registry back? I searched around on the web and the only thoughts related to System Restore. I ran it but system restore found no restore points to restore from except the one just taken that morning when the system booted. In my opinion, System Restore was the "killer feature" included in XP that made upgrading from Windows a must-do for most people.
Prior to System Restore, it was easy to turn your system into a brick that required reinstallation, and System Restore lets most users take a step back in time and get their system working again after one of these bad program installations, without major file surgery. I searched the web for how to manually restore a file out of a restore point but found nothing. But I did find where the restore points are saved Hmmmmm -- another puzzle to solve -- how to manually restore a registry hive out of a system restore point.
I couldn't find anything about this topic anywhere on the web.
0コメント