Network Productivity Group
... a computer consultancy
diverting off to backup schemes we had started to talk about blue screens,
shutdown and startup problems. We
had talked about blue screens and the basic approaches to troubleshooting
them. Shutdown is very
similar with a couple of added elements.
shutting down properly is usually caused by one of these things: a blue screen (in which case, fix that problem first, refer
to Tech tip #26), a driver conflict (same as #26 again), a conflict among
hardware devices, or a conflict between Windows and your system's
first step to troubleshooting shut down problems is to boot to Safe Mode.
If you don't know how to do that, this might be a good time to test
the "Hey, How Do I?" link.
While this is a pretty simple test, see if you machine will shut
down normally from Safe Mode. If it won't, skip down to the paragraph that shows an
Internet link to Microsoft. If
it will, then refer to Tech tip #26 and using MSCONFIG, start Windows
using CONFIG.SYS, AUTOEXEC.BAT, SYSTEM.INI, WIN.INI but not using any of
the items in Startup. If you
can now shut down the problem is a conflict among two or more of those
items. Try putting half of
them back, then another half, etc., until shutdown fails.
The cause is in the last you group you added.
Selectively try booting with and without items in that group until
you can shutdown. Note that
if you take the Advanced tab in MSCONFIG you can turn off running Scandisk
after every bad shutdown. Just
remember to reset that when you are done and run Scandisk when you have
found and fixed the problem.
to Windows 95 users: You do
not have MSCONFIG. To mimic
its capability you need to go to the Start Up Menu (hold down F8 while
booting) and select "Selectively load Windows components" (I no
longer have a 95 to check this on and am working from memory, I think that
is what it says). The first time through make a list of all the drivers that
Windows loads and then load only half, then half of those, etc., until
Windows shuts down normally. You
can turn off Scandisk by changing its setting in a file called "MSDOS.SYS".
It is hidden, a system file and read only so you may need some help
with that (see "Hey, How Do I?" above).
loading with no startup files does not solve the problem then go the next
step, don't load WIN.INI, then SYSTEM.INI, then AUTOEXEC.BAT, then
CONFIG.SYS. If you can't
shutdown then it means the problem is a conflict among your hardware
devices. The next step is to disable them until we find the bad guy.
Telephone US (562) 930-1343- Fax (562) 439-7174