When I try to boot into safe mode, it starts scrolling the itemized list up the screen, but after that it bluescreens for a fraction of a second then reboots. The bluescreen goes by too fast to read. Is this possibly a virus?
Not typically but possible. A blue screen is usually a hardware or driver issue. If it wont boot at all usually the easiest and perhaps quickest remedy is to just do a repair install.
Ugh. Automatic reboots make it impossible to tell what’s going on.
This won’t help the OP, but for everyone else, I strongly recommend turning off the automatic reboots. With XP, it’s pretty easy:
Right-click “My Computer” and select Properties.
When the System Properties window opens, click on the Advanced tab.
Click on Settings in the Startup and Recovery section.
Uncheck the “Automatically restart” option.
Click OK.
Click OK.
Now, if you ever have a startup failure, your PC will not endlessly keep trying, and you’ll actually be able to see the error message.
There is at least one virus that deliberately removes essential registry entires to prevent you from using Safe Mode to fight it. It is a really effective dirty trick. Something done by one virus will soon be copied by other scumbag virus authors.
Here are some tips on a blog:
Good luck!
Well, maybe it did. At least I can read the damn message:
Done and done, with a number of different products, including several online scanners. All report the system is clean.
N/A
Done.
Does anyone outside of Microsoft know what this crap means?
The system seems to be working fine when booted into regular mode. It just won’t go into safe mode without generating the above error. :mad::mad::mad:
Anyone convicted of authoring a virus should be strapped to an anthill in the middle of the desert and covered with honey. I support the death penalty, but in general think it should be applied in a painless fashion. Virus authors should be given more “imaginative” methods for their demise.
That is a rare error code, invoked at the very start of the kernel booting.
Could be virus-induced, I suppose.
One guy had it back on Win NT because he put a “/break” command in his boot.ini.
Other people say this:
Are you sure it’s 0x78 and not 0x7B? 7B is very common, caused when windows can’t read the hard drive (because it’s missing drivers or other).
Yes, you are correct. 7B. So, what can I do about it? Assuming it is not a virus, this is still a problem. I may need to boot into safe mode for some other reason, and my computer does not seem to be able to do it. :eek:
You can’t. My guess is you have a board that windows does not have an integrated SATA driver for.
This often involves downloading the sata drivers to a floppy
Pressng f6 During windows install to load SATA drivers from the floppy, then proceeding with the install. It is a PITA
You have a floppy drive?
One other possibility is flipping your SATA configuration in bios to a different compatibility mode. Sometimes they are set to RAID to facilitate OEM RAID configurations that are no big deal to them because of the preloaded driver on the drive image.
This is not always obvious how to do this.
I don’t think we had a virus earlier this year, but our computer was misbehaving. We couldn’t update iTunes, or re-install our Palm Pilot desktop software; troubleshooting the error message we got from the Palm software suggested we needed to go into Safe Mode - and that failed also.
I wound up reinstalling Windows and it’s behaved perfectly since then. I guess we had some drivers messed up, or some other system files had gotten corrupted.
Try booting off your XP CD to the Recovery Console. Then run CHKDSK C: /F
Fuggeddabout it. The recovery console is next to useless in most common circumstances. In all probability some sort of essential system driver or component has become corrupted or deleted.
The easiest way to fix this is to get out your XP CD and boot from it. Let it load all of its drivers and other crap; do NOT go into the recovery console, but instead go past that part to the point where it asks you where you want to install XP to. There will be an option “R” available to repair your existing XP installation. Choose that option. It will go through the motions of effectively reinstalling your OS, but only the critical components, drivers, etc. Your installed programs, the registry, and other stuff like that will be untouched. Let it do its thing and then reboot. In most cases you should be thrown back into XP like nothing ever happened. If not, then the problem very well might be virus-related, or some other sort of malware. If you can get into Windows any case, run a thorough virus check, preferably with whatever antivirus you’re using, plus a third party’s, such as the online scan HouseCall at TrendMicro. Also scan for malware and spyware and stuff with relevant programs just to get whatever you can found and eliminated.
If nothing else works, then it might be hardware-related. It could be your hard drive is dying (consistently crapping out at the same point), flaky RAM (inconsistent errors at seemingly random places) or flaky power supply (similar symptoms as flaky RAM).
This is not my experience.
Well, the Gigabyte website has a driver, but XP is already installed. Any way to install the SATA driver AFTER XP has been set up, or am I basically screwed for ever getting into safe mode?
Safe mode hasn’t worked after the clean install?
I am doing everything I can do avoid a clean install. I just did one a couple of months ago because of these damn viruses and malware (virumonde) and it takes me DAYS to get my system back to where it was. I cannot afford to have that kind of downtime right now, or actually ever.
I have no idea why safe mode gives 0x7B, especially since you haven’t installed any 3rd party drivers. That’s all I got to say.
That, and virus checks can be run by booting from special CDs. Or moving the hard drive to another computer.
Well, there may not BE a virus at this point, but it would still be nice to be able to boot into safe mode.
Go into the BIOS and set the SATA mode to Compatible.
Is that one of those changes that creates a 7B on any system, or does setting it to “compatible” have some other effect? There is RAID, AHCI, and IDE emulation (in increasing order of compatibility, but all causing 7B’s when changed afaik). What would “compatible” mode be?