Site Search

Site Info

Home » Forums » Forum Archives » Operating Systems » Topic # 788

Safe Mode Problem
nilodherr Jul-13-02 00:07 AM
My computer suddenly freezes and I try to reset it. The Microsoft Windows Millenium Startup Menu shows up with a warning. "Warning: Windows did not finish loading on the previous attempt. Choose Safe mode, to start Windows with a minimal set of drivers." I try to run Safe Mode, but all it comes up with is the blinking underbar. ( _ )It stops there. The same thing happens when I try to use Normal mode. Should I run a surface scan? If yes, what else? Please help.

Thank you

1. RE: Safe Mode Problem
lbyard Jul-13-02 06:26 PM
In response to message 0
Yes. See what happens. Larry

2. RE: Safe Mode Problem
Zeno Jul-14-02 07:18 PM
In response to message 1
Thoughts on trouble-shooting... maybe some will apply.

A blinking bar, after POST completes, usually indicates a driver loading problem related to:
1) resource conflict (IRQ, DMA, I/O Port, etc.)
2) failed driver/hardware installation
3) driver or .inf file corruption
4) legacy junk in config.sys or autoexec.bat files
5) startup software conflict (AOL, WINAMP, NAV, McAffee, etc.)
6) a virus (very unlikely)

The list above assumes HD and MBR are OK, and WINME is trying to load.

Ask yourself if you recently installed any new hardware or software just before this started to happen?

If you have an OEM thunker under warranty, you may want to let the OEM deal with it. Also, you might want to try the "System Restore” disk, or what ever your OEM calls it. Some of them are a waste of time, but the Dell and Compaq System Restore disks often actually work. If you've added some new hardware, the “System Restore” could become the “System Shredder.” The System Restore disk will usually try to load the drivers for the original hardware configuration. If it finds new hardware it doesn't recognize, it could go bonkers. (Older HP and Gateway System Restores do this a lot.) It doesn’t hurt to try.

OR....Here’s a completely different ball game!

If a blinking bar appears early in the boot, before POST completes, then most of the 6 items above DO NOT apply. From your forum post, it's hard to tell which is the case. I'm going to assume you made it past BIOS POST, and WINME is trying to load. A little more info here would really help.

What do you see during boot? Do you see a memory check counter? Do you see a hardware recognition screen? Do you see any BIOS error messages or DOS error messages? Any BIOS error messages with numbers like 1780, 1781, 1790, 1791? Do you hear one beep after POST indicating hardware is OK? Or more than one beep?

If you made it past BIOS POST and started to load WINME, your master boot record (MBR) is probably OK or you wouldn't have made it that far into the boot. Also, if your MBR failed, you'd probably see a BIOS error message something like "Disk Boot Failure", depending on your BIOS.

If you can see a blinking cursor, then at least you have minimal video and your video card/chip is probably OK. Do you have integrated sound or video??

3. RE: Safe Mode Problem
Zeno Jul-14-02 07:28 PM
In response to message 2
Developing strategies...Plan A and Plan B

There are several ways to approach this problem, and most of them involve using of an Emergency Start-up Disk (ESD). I will assume you have one, or can make one from someone else's WINME setup.

Here's a practical RULE OF THUMB that works about 90% of the time:

If you can force an ESD to boot to a DOS prompt, and you can access all of your drives, you most likely have a software problem, and *NOT* a hardware problem. This is often a *HUGE* time saver in troubleshooting, but there are a few important exceptions: (a) intermittent PSU voltage fluxes, (b) occasional lockups due to over-heating and air-flow, (c) a totally fried ISA/PCI card such as sound, modem, NIC. However, these exceptions are relatively unlikely, and probably do not apply in your situation. The rule of thumb usually works because software fails far more often than hardware.

The overall, big-picture strategy includes Plan A and Plan B. Plan A assumes you know some basic DOS commands, which you probably do. Plan B assumes you are comfortable working inside your case, which you probably are.

PLAN A STRATEGY: Force a normal or SAFE mode boot (if possible) and check the Device Manager for resource conflicts. If you find them, disable the offending hardware/driver and reboot. Then reinstall the driver or get rid of the hardware.

PLAN B STRATEGY: If plan A fails, open your case and start pulling out cards, one at a time, beginning with the last one installed. After each pull, try to reboot. You may have to pull everything except the video card (if you have one). However, if you have a virus or funky start-up software, Plan A or B will not help until you dump them.

PLAN A: Insert your ESD and boot to the start-up menu. Start your computer WITHOUT CD-ROM support. (First, you won’t need your CD drive, and second, your CD drivers might interfere with this process.) Boot to the A:\> command prompt. Switch to the root directory of the HD with the active partition, if possible. This is usually C:\> (If this fails, go to PLAN B.)

You are at C:\>. You are going to use the scanreg.exe utility to restore the registry. By default, you should have 4 or 5 compressed backups of your registry with file names like rb001.cab up to rb004.cab.

1) You need to find the scanreg.exe file, which is usually located in C:\Windows\Command.
2) Switch to the directory with scanreg.exe and type scanreg to launch the utility.
3) When the utility launches, you'll see a gray on blue screen with 2 buttons.
4) Select the button that says "Start."
5) On the next screen, choose "View Backups". Next you will see a list of .cab files.
6) Choose the most recent backup that says "Started" in the left column.
7) Choose the "Restore" button.
8) Take your ESD out of the floppy drive.
9) Choose the "Restart" button.

If the registry restore works, you should get a normal boot into WINME, perhaps with a few error messages and attempts to detect hardware. You may not have to deal with SAFE mode at all. Cancel any hardware detection screens. Go to the Device Manager and start looking at "Resources" tabs (if present) for conflicts on each device. If the Resources tab says 'No Conflicts' move on. If conflicts are listed, go to the General Tab and check the box that says "Disable in this hardware profile." OR, remove the device and attempt to reinstall the driver. Read Larry's articles on solving resource conflicts.

If the registry restore doesn't work, then you need to come in under the radar, guns blazing, with a sneak attack. There are many ways to force SAFE mode. This is my favorite. This method requires a little more knowledge of DOS, and ability to edit the Autoexec.bat and Config.sys files.


1) Insert the ESD and boot as before (without CD support) to the A:\> prompt.
2) Switch to the C:\> prompt (or the root directory of the active partition).
3) Type: edit autoexec.bat (You should see the blue screen of the DOS editor.)
4) Edit the 1st line as follows: C:\WINDOWS\ WIN /D: M
5) Win.com is usually in C:\WINDOWS. If not, you'll have to change the path above.
6) If there are other lines in the autoexec.bat file, type REM at the beginning of each line to temporarily disable it. Remember to remove these REMs when you finish trouble-shooting.
7) Likewise, edit the config.sys file. You may need to put some REMs there too, if you have entries.
8) Remove your ESD and push CTRL+ALT+DEL to reboot.

If this works, you will automatically boot into SAFE mode, and you can use Device Manager to resolve conflicts. If this doesn't work, then you have pretty serious problems and need to try Plan B.

Plan B involves some specialized case-bashing. Since I have no idea what kind of computer you have, you'll have to figure that one out for your self.

Best Wishes...

4. RE: Safe Mode Problem
lbyard Jul-14-02 08:32 PM
In response to message 0
What happened (when you did a surface scan)? Larry

5. RE: Safe Mode Problem
nilodherr Jul-16-02 07:26 PM
In response to message 4
I did a surface scan and there seemed to be no bad sectors. I then decided to just reinstall my WinMe, and it's up again. Thanks for all your help, Dan

| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |