On Feb 12, 5:10*pm, francwalter <francwal...@gmail.com> wrote:
> Am Thu, 11 Feb 2010 16:21:49 -0800 (PST) schrieb Jose:
> > What kind of external HDD is it? *Make and model? *Does it connect
> > with a USB port?
> > What is the most time you waited for shutdown? *5 minutes? *10
> > minutes?
> > When your system does not shutdown properly, what is the last thing
> > you see on the screen? *Don't paraphrase, try to type in what you see
> > as best you can.
> > If you want to fix your shutdown problem:
> > To eliminate questions and guessing, please provide additional
> > information about your system.
> > Click Start, Run and in the box enter:
> > msinfo32
> Hello Jose,
> firstly thanks for your help.
> The time i waited is maybe hours. It is the computer for a restaurant
> cash register (till).
> There is no virus on it. Only the cash program is running.
> The last thing i read is: "Windows wird heruntergefahren..." (Windows
> shuts down).
> The HDD is an external USB 2.0 Drive with a 500 GB IDE-HDD.
> There is a share on this drive.
> I am not at place now, so i cannot put msinfo32.
> If i disconnect the ext. HDD the shutdown is OK.
> I tried with devcon but this doesn't work, gives me an error and
> doesn't allow to disconnect when in use i think, if i remember well.
> Thank you,
> Regards, franc
Okay - you should not have to wait hours. I would start to wonder if
it took more than a minute or two or three...
I would not recommend pulling the plug if you can help it, or else you
may have a new topic called "my computer won't boot anymore".
What is the manufacturer of your external HDD? I want to look on
their WWW page for ideas too. It sounds like it has something to do
with it, but we need to do some other things first (like msinfo32!)
Other folks will have some ideas too.
Reduce the chances of malicious software by running some scans.
Download, install, update and do a full scan with these free malware
Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
These can be uninstalled later if desired.
There may be clues in the Event Log, so when you are ready to shutdown
again, let some minutes tick by, try to shutdown, wait several minutes
to give it a chance, restart and look in the Event Log to see what was
happening paying attention to the time stamp of the events so you can
see the right ones.
Here is some info about the Event Log. We just want the stuff that
looks like what was happening when you shut down.
Look in the Event Viewer for clues around the time of the incident
Here is a method to post the specific information about individual
To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.
A shortcut to Event Viewer is to click Start, Run and in the box
Click OK to launch the Event Viewer.
The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.
Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.
If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.
When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.
To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.