Shutdown Always Restarts

  • Thread starter Thread starter NEWBIE
  • Start date Start date
N

NEWBIE

This just started.

When I shutdown, the machine always automatically restarts. I have
looked at the BIOS, but do not see anything that would cause that,

I select 'shutdown' when I exit from XP SP3.

Help

Newbie
 
This just started.

When I shutdown, the machine always automatically restarts. I have
looked at the BIOS, but do not see anything that would cause that,

I select 'shutdown' when I exit from XP SP3.

Help

Newbie
Click to expand...

Your system is blue screening, then doing an automatic restart.
The blue screen (BSOD) is caused by some code being run
during shutdown (cause unknown).

Control Panels:System:Advanced:Startup And Recovery:Settings and
untick the "Automatically restart" box.

After that change, the next time you attempt to shut down, the
screen will turn blue, and the error information (hex numbers,
and maybe a driver name), will be presented.

At least with that setting, you're no longer under the
impression the shutdown is "normal". Doesn't really
get to the root of the problem though. The blue screen
means your system crashed. And it's been crashing
during shutdown. It's that tick box that prevents it
from being more messy.

*******

Check the Event Viewer for error information. It's
possible the events are being recorded in there, and
you already have evidence collected as to what is
wrong.

If you manage to fix it first, then it's a bit academic
whether you use the above tick box or not.

If you clear the tick box above, the idea is, you
get to see the hex dump. Which would be useful,
if you were incapable of getting the information
in any other way. If there's nothing interesting
in Event Viewer, then get it to blue screen instead
by clearing the tick box.

Paul
 
Your system is blue screening, then doing an automatic restart.
The blue screen (BSOD) is caused by some code being run
during shutdown (cause unknown).

Control Panels:System:Advanced:Startup And Recovery:Settings and
untick the "Automatically restart" box.
Click to expand...

did that
After that change, the next time you attempt to shut down, the
screen will turn blue, and the error information (hex numbers,
and maybe a driver name), will be presented. BSOD:

0x0000008e
(0xc0000005,
0x804ef1e5,
0xb14a8a0,
0x00000000)


At least with that setting, you're no longer under the
impression the shutdown is "normal". Doesn't really
get to the root of the problem though. The blue screen
means your system crashed. And it's been crashing
during shutdown. It's that tick box that prevents it
from being more messy.
Click to expand...

duly unticked

*******

Check the Event Viewer for error information. It's
possible the events are being recorded in there, and
you already have evidence collected as to what is
wrong.
Click to expand...


Ohboy - event viewer - gotta find where that is and what is in it.
If you manage to fix it first, then it's a bit academic
whether you use the above tick box or not.

If you clear the tick box above, the idea is, you
get to see the hex dump. Which would be useful,
if you were incapable of getting the information
in any other way. If there's nothing interesting
in Event Viewer, then get it to blue screen instead
by clearing the tick box.

Paul
Click to expand...

Thank you

Newbie
 
snip
BSOD:

0x0000008e
(0xc0000005,
0x804ef1e5,
0xb14a8a0,
0x00000000)
snip
Click to expand...

Please provide all the info on the blue screen. There may be a file or
driver named, and if so, that will narrow down where your issue is. An
8e stop error is usually due to a hardware incompatibility or an
incorrect or corrupt device driver.
 
That's the HEX code of the error but not the text such as...

KERNEL_MODE_EXCEPTION_NOT_HANDLED
Irql_Not_Less_or_Equal
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
INACCESSIBLE_BOOT_DEVICE
Click to expand...

Yes - I understand hex (0-15).
I see no similar text - just the word STOP: preceding the hex codes.
Thanks
Newbie
 
David said:
Alright. NT Stop Error 0x0000008e is associated with memory.

The first think to try is to reseat the RAM. If you have two or more
modules, swap the sockets the RAM is inserted into.
Click to expand...

I was hoping to see the name of a driver file in the dump.

Paul
 
David H. Lipman said:
Alright. NT Stop Error 0x0000008e is associated with memory.

The first think to try is to reseat the RAM. If you have two or more
modules, swap the sockets the RAM is inserted into.
Click to expand...

0x8e can be due to any hardware, not just RAM, and can also be caused by
an incompatible or corrupt device driver.
 
In
David H. Lipman said:
I was thinking of the POV of starting with the RAM and
work from there as it could be as simple as "Chip Creep".
Click to expand...

I've seen my share of those screens and the Stop screens too, shutting down
to prevent damage to the computer, on several machnes. To date it has NEVER
been a hardware problem. I guess it's better to err on the side of safety
and throw such errors, but ... they are so inaccurate it's ridiculous.
I think in most cases it's been a virus issue and a few have been
imperfectly designed software apps. A very few have required a reinstall of
the OS, but that got rid of the issue.

I do agree with testing memory though; sure cannot hurt anything. Use a
thorough tester that runs it thru all the various routines.

Has the Event Viewer been checked for errors? Sometimes that can tell a lot
about a machine.

HTH,

Twayne`
 
Posting this again because I don't see any evidence that the first
post went thru. Excuse the dupe,

Newbie


Alright. NT Stop Error 0x0000008e is associated with memory.

The first think to try is to reseat the RAM. If you have two or more
modules, swap the sockets the RAM is inserted into.
Click to expand...


Interesting.

Turns out that there were 4 RAM modules.
1GB
512MB
256MB
256MB

I took them out one at a time, and re-ran. Still got the error until
I removed the 1MB.
Anyway, I had some RAM, so I replace the mix with a single 2GB'er.
Been running and testing on-off with it since we last talked. Still
no BSOD. So for now, I am thinking and hoping that the problem as
gone.

Hope so & thanks.
Newbie
 
Twayne said:
In

I've seen my share of those screens and the Stop screens too, shutting
down to prevent damage to the computer, on several machnes. To date it
has NEVER been a hardware problem. I guess it's better to err on the
side of safety and throw such errors, but ... they are so inaccurate
it's ridiculous.
I think in most cases it's been a virus issue and a few have been
imperfectly designed software apps. A very few have required a
reinstall of the OS, but that got rid of the issue.

I do agree with testing memory though; sure cannot hurt anything. Use
a thorough tester that runs it thru all the various routines.

Has the Event Viewer been checked for errors? Sometimes that can tell
a lot about a machine.
Click to expand...

0x8e is almost always hardware related, though it may be a driver
issue.... which you could technically classify as a software problem.
 
Posting this again because I don't see any evidence that the first
post went thru. Excuse the dupe,

Newbie





Interesting.

Turns out that there were 4 RAM modules.
1GB
512MB
256MB
256MB

I took them out one at a time, and re-ran. Still got the error until
I removed the 1MB.
Anyway, I had some RAM, so I replace the mix with a single 2GB'er.
Been running and testing on-off with it since we last talked. Still
no BSOD. So for now, I am thinking and hoping that the problem as
gone.

Hope so & thanks.
Newbie
Click to expand...

Good news! David may have nailed it. Let us know in a few days if it
holds up.
 
So you now have one 2GB module and no BSoD - thant's great.

Looking at the; 1GB, 512MB and the two 256MB modules, what are the they
(example: PC2100, PC3200, etc) ?
Click to expand...


1GB PC2 4200U DDR2 533MHz MICRON
512MB PC2 4200U 1Rx8 Samsung
256MB PC2 4200U 1Rx16 ProMOS
256MB PC2 4200U 1Rx16 ProMOS

Newbie
 
Something for everyone's memory banks...

This just started.

When I shutdown, the machine always automatically restarts. I have
looked at the BIOS, but do not see anything that would cause that,

I select 'shutdown' when I exit from XP SP3.

Help

Newbie
Click to expand...

I had this happen on an old Gateway desktop once. No BSOD, though. The
only way to shut the computer down was to press the power button.

It happened as soon as I installed a particular security update. MS
Tech support from New Delhi even gave up on it.

I watched them struggle with it, and I watched what was happening here.
When they gave up, I thought about the situation, what was actually
happening and when.

I changed the Ethernet card, and the problem went away. I have no idea why.


--
Ken

Mac OS X 10.8.2
Firefox 18.0.1
Thunderbird 17.0.2
LibreOffice 3.6.3.2
 
Something for everyone's memory banks...


I had this happen on an old Gateway desktop once. No BSOD, though. The
only way to shut the computer down was to press the power button.

It happened as soon as I installed a particular security update. MS
Tech support from New Delhi even gave up on it.

I watched them struggle with it, and I watched what was happening here.
When they gave up, I thought about the situation, what was actually
happening and when.

I changed the Ethernet card, and the problem went away. I have no idea why.
Click to expand...


Moral of story:

When desperate and all else seems fruitless, start swapping out
components.

Newbie
 
I wouldn't call it "desperate". It is called "the process of elimination".

I don't know why Ken replaced the NIC (he didn't relate why hw chose that.
Albeit it could be simply its in a PCI slot.) but it could have been a
faulty card or a problematic OS driver.
Click to expand...

I didn't relate why because I didn't think anyone would be interested! LOL

So, here's the details, although I can't relate the truly specific
details as I simply don't remember them.

While MS tech support, an engineer a couple steps above the normal
person you work with, kept looking at things, I simply sat here on the
phone with him, and observed what was happening. I found it interesting
that they used Teamviewer rather than MS's own supplied Remote Desktop
application. I wonder if that should tell us something. LOL

While I watched the tech, and at the end of each session, I did my
normal overall system shutdown procedures (I've more than one computer
here, often all are online), I realized one time that if the modem was
off, the computer would shut down. If the modem was on, it would reboot.

I figured there was some kind of software bug, but I had no clue where.
So, I let tech support do their thing until they eventually gave up,
called it quits, and filed it as an unresolved issue.

I've no technical education in this area, I listen to the experts, the
people who know more than I do, but I always take things with a grain of
salt. I observe what's going on, think and analyze for myself. I think
outside the box, asking myself "What if" questions even when the
question isn't logical. After confirming the fact that if the modem was
off, it worked, modem on it didn't, I wondered... What would happen if
I change the Ethernet card.

Yes, it was in a PCI slot, no onboard Ethernet.

The card was a relatively new Linksys card, it was still on their
website. I have a box of old cards, so picked one out of the box and
swapped. Bingo! Modem on, the computer shut down.

I contacted Linksys to see if there was any kind of firmware update, but
there wasn't , so I just left the old card in the computer, and never
looked back. It's just a suspicion, but I suspect some type of conflict
between the security update, Linksys software, and/or BIOS that was the
source of the problem.

It was an old Gateway that was on the market when XP first came out. I
was redoing everything to donate it to a local social agency for
someone's use. The original COA sticker was till on the computer. :-)
The only copy of XP that I had that would successfully install was XP
SP1. Not 1a, 1. Then I had to go through the process of running MS
Updates manually. I don't turn on automatic updates at this point. As
soon as a particular high-priority update would install, the shut down
would fail. But there is a note in that particular update that if the
user had problems, free technical support was available. And I made use
of it. <grin>

AFAIK, the computer is still running. I actually had enough pieces
around here that it was a complete system including printer.

--
Ken

Mac OS X 10.8.2
Firefox 18.0.1
Thunderbird 17.0.2
LibreOffice 3.6.3.2
 
Ken said:
I didn't relate why because I didn't think anyone would be interested!
LOL

So, here's the details, although I can't relate the truly specific
details as I simply don't remember them.

While MS tech support, an engineer a couple steps above the normal
person you work with, kept looking at things, I simply sat here on the
phone with him, and observed what was happening. I found it interesting
that they used Teamviewer rather than MS's own supplied Remote Desktop
application. I wonder if that should tell us something. LOL

While I watched the tech, and at the end of each session, I did my
normal overall system shutdown procedures (I've more than one computer
here, often all are online), I realized one time that if the modem was
off, the computer would shut down. If the modem was on, it would reboot.

I figured there was some kind of software bug, but I had no clue where.
So, I let tech support do their thing until they eventually gave up,
called it quits, and filed it as an unresolved issue.

I've no technical education in this area, I listen to the experts, the
people who know more than I do, but I always take things with a grain of
salt. I observe what's going on, think and analyze for myself. I think
outside the box, asking myself "What if" questions even when the
question isn't logical. After confirming the fact that if the modem was
off, it worked, modem on it didn't, I wondered... What would happen if
I change the Ethernet card.

Yes, it was in a PCI slot, no onboard Ethernet.

The card was a relatively new Linksys card, it was still on their
website. I have a box of old cards, so picked one out of the box and
swapped. Bingo! Modem on, the computer shut down.

I contacted Linksys to see if there was any kind of firmware update, but
there wasn't , so I just left the old card in the computer, and never
looked back. It's just a suspicion, but I suspect some type of conflict
between the security update, Linksys software, and/or BIOS that was the
source of the problem.

It was an old Gateway that was on the market when XP first came out. I
was redoing everything to donate it to a local social agency for
someone's use. The original COA sticker was till on the computer. :-)
The only copy of XP that I had that would successfully install was XP
SP1. Not 1a, 1. Then I had to go through the process of running MS
Updates manually. I don't turn on automatic updates at this point. As
soon as a particular high-priority update would install, the shut down
would fail. But there is a note in that particular update that if the
user had problems, free technical support was available. And I made use
of it. <grin>

AFAIK, the computer is still running. I actually had enough pieces
around here that it was a complete system including printer.
Click to expand...

Did the NIC have a RealTek RTL8169SC GbE Ethernet chip on it ?

I have two of those, and on my other PC the other day, I got
a report from Linux of an "interrupt storm". I'm beginning to
wonder if there isn't something wrong with the design. The
second card has given me some anomalous symptoms before as well.

Paul
 
Did the NIC have a RealTek RTL8169SC GbE Ethernet chip on it ?

I have two of those, and on my other PC the other day, I got
a report from Linux of an "interrupt storm". I'm beginning to
wonder if there isn't something wrong with the design. The
second card has given me some anomalous symptoms before as well.

Paul
Click to expand...

If the card I just pulled from my pile of junk is the card I removed,
it's a Linksys LNE100TX, version 5.1, but it does not have a RealTek
chip on it.


--
Ken

Mac OS X 10.8.2
Firefox 18.0.1
Thunderbird 17.0.2
LibreOffice 3.6.3.2
 
Back
Top