P4C800-E MB reboots on Windows Power Down?
zeke7
desktop (Windows 2000, SP4)--using 'Shut Down', not 'Restart'--after
the OS closes out and the machine powers down as it should, as soon as
the fans have shut off the whole thing fires back up again: fans kick
on, the MB comes to life, BIOS boots and Windows fires up again. If I
want this machine to stay shut down, I have to flip the back power
switch off as soon as I hear the fans shutting down.
A related problem occurs using System Standby: once the standby
initiates, the monitor, fans, and HDs shut down, but then the MB, fans
[and disks?] immediately start up, the monitor remains off, and the
system can't be awakened; even the reset button doesn't work. A
physical power down and reboot is necessary. (Win2K's Power Options to
Turn off monitor and Turn off hard disks does work fine.) No screen
saver is being used.
This same machine--identical hardware, OS and software (other than
updates)--has worked fine in the past, both with Shut Down and System
Standby procedures. I did have to reset the MB bios to default values
a few times when it mistakenly thought I was overclocking when I
booted up (I've never touched those settings in BIOS or elsewhere).
I've played with the bios power management settings extensively since
this problem started occurring and haven't found the right settings to
correct the problem. All software and the BIOS are updated with the
manufacturers' latest updates. I did read on this forum of someone's
power problems with the ATI AIW Remote Control, and tried uninstalling
that, with no change in the shut down problem.
Have just done a fresh format and reinstall of the OS (to eliminate
Norton Pestworks from my system), and the problem remains, right from
the fresh Win2K + SP4 install, before installing any further updates,
drivers, or software. I'm thus pretty sure it's not the OS telling the
MB to restart, but rather something in the MB telling itself to do so.
[I did pull out and reinsert all the MB's jumpers and cable
connections once when experiencing mysterious bootup problems (which
turned out to be a bad memory card), so there's a remote but very
unlikely possibility that I replaced something incorrectly that's
causing this.]
Can any knowledgeable sorts out there advise what the BIOS Power Mgmt
settings should be to fix this? I could live with having to switch the
power button off when shutting down, but I very much like to use
System Standby as I live in a warm climate and the machine contributes
an excessive amount of room heat when not being used. Any suggestions
greatly appreciated.
Trying to keep this brief; here's some system info:
==============================
Basic systems specs:
-ASUS P4C800-E MB (AMIBIOS rev1023)
-Pentium IV 2.8MHz CPU
-ATI 9800 A-I-W Video Card
-Promise Ultra TX2-100 IDE controller card, 4 hard drives
-Antec True Blue 480W power supply
-ATI All-in-Wonder Remote Control (USB-RF)
-MS Wireless Intellimouse Explorer 2.0
-Windows 2000 SP4 OS, all Windows Updates current
-No screen saver being used
==============================
Here's the BIOS Power tab settings I'm currently using (have tried
changing various combinations of these with no luck):
Suspend Mode - Auto
Repost Video on S3 Resume - Y
ACPI 2.0 Support - Y
ACPI APIC Support - Enabled
BIOS to AML->ACPI Table - Enabled
APM Configuration:
APM Power Mgmt - Enabled
Video Power Down Mode - Suspend
Hard Disk Power Down Mode - Suspend
Suspend Time Out - Disabled
Throttle Slow Clock - 50%
System Thermal - Enabled
Power Button Mode: On/Off
Restore on AC Power Loss - Power Off
Power on by: [-All Disabled]
-RTC
-External Modems
-PCI Devices
-PS2 Keyboard
-PS2 Mouse
Core2Duo
"zeke7" <zeke...@gmail.com> wrote in message
news:d59627a4-e904-45b9...@s12g2000prg.googlegroups.com...
I'll have to restart my system to have a look, but my initial thoughts are
turn off the APM Power Mgmt, because I think this makes the OS control the
power management, not the BIOS - mind you this is only my initial thoughts.
If that's not it, I did think it could be the power switch wiring/jumper,
but then again if it was ON constantly the PS would power down after 4 secs
so I doubt this is a problem.
Core2Duo
zeke7
> A bit drastic, but have you considered re-flashing the bios?.
Core2Duo: Yes, I've just finished reflashing the BIOS, v1023 (I see a
beta 1024 out there but am not keen on BIOS betas). No change in the
problem. Had the same version installed previously, just tried
reinstalling the same in case it helped, but no go.
And have just recently tried turning off the BIOS APM, still with no
improvement. Hunting through the manual doesn't help much, it doesn't
tell you much more than the spartan help messages in the BIOS menu
itself.
I'll get down and check the jumpers soon.
Thanks for the suggestions.
~misfit~
Just for giggles, will you try checking the vcore is in spec please? CPU-Z
(ver 1.41) is the most reliable tool for this IMO. The CPU is under a lot of
load when it's shutting down, maybe moreso than start up. Maybe the CPU
isn't getting enough voltage?
--
TTFN,
Shaun.
Fred
Recovery > System Failure. If so you may be experiencing an error on
shutdown leading to a restart.
Starting up Windows in safe mode and then seeing if the pc shuts down
correctly might help you troubleshoot this problem.
"zeke7" <zeke...@gmail.com> wrote in message
news:d59627a4-e904-45b9...@s12g2000prg.googlegroups.com...
Paul
Another small experiment you could try.
Disconnect Ethernet cable from the computer.
Shutdown or enter standby.
Did that change the symptoms ?
That would be assuming this is a Wake On Lan kind of problem.
Paul
Bill Anderson
> Here's a bit of a strange problem: whenever I shut down my home-built
> desktop (Windows 2000, SP4)--using 'Shut Down', not 'Restart'--after
> the OS closes out and the machine powers down as it should, as soon as
> the fans have shut off the whole thing fires back up again:
I have waited two days to respond to this because I had the exact same
symptoms with one of my previous computers when I first built the
system. The problem is that I can't remember exactly what the problem
was or how I solved it, or even whether it was a problem with my old
P2B-F or P4T-E rather than the P4C800-E. Gah, I'm getting old. So since
my memory hasn't improved in the two days I've been thinking about this,
I'll just offer the following for you to consider.
I am certain that this problem cropped up with WinXP. Not sure about
Win2K, but I was running a dual boot system with both OSs, so perhaps
this applies to Win2K also. Or heck, it may have been Win98.
When you installed the OS, did you interrupt the installation process
right at the beginning using F5 (or maybe it's F4)? If you do, in WinXP
anyway you'll be given a small window with three lines displayed.
Scroll up in the window and you'll see lots more options. The third
line from the top (in WinXP) is the ACPI option. I had to activate it
in order to get the computer to shut down properly, and the only time
the ACPI activation can be done (easily, anyway) is upon installation of
the OS.
And of course this may not apply to you at all. In fact, this may have
been the solution to a different problem altogether -- like getting the
"you may now shut down the computer" screen rather than an actual
shutdown. I dunno. Sorry. This is just bugging me. At some time in
the past I did have exactly the problem you've described and I solved it
pretty quickly, as I recall. My new computer would start right up after
shutting down. If only I could remember ....
Was it simply a BIOS setting? Have you played with the power settings?
--
Bill Anderson
I am the Mighty Favog
zeke7
Many thanks gents for the posted suggestions, but still no go; here's
a rundown:
Core2Duo:
APM Power Mgmt in BIOS: on or off, no difference
Power switch wiring/jumper: haven't managed this yet, requires
removing my hard disks to see! Will give that a shot though.
BIOS reflashed: tried (1023), still no change
misfit:
Core voltage: CPUZ report fluctuates between 1.376-1.392v.
Looked up specs on Intel's site, quite confusing for this novice,
found these numbers, which if applicable seem to be in range:
VID = 1.475, Vmax = 1.370 V, Vmin = 1.290 V, VID = 1.500, Vmax = 1.395
V, Vmin = 1.315 V and VID = 1.525, Vmax = 1.420 V, Vmin = 1.340 V
(http://processorfinder.intel.com/details.aspx?sSpec=SL7EY#)
Fred:
Set for automatic restart in Startup and Recovery > System Failure: it
was set for restart, tried turning it off, no change
Paul:
Ethernet cable disconnect: tried many times, with BIOS wake up on LAN
setting either way, no change
Bill A.:
mine's a straightforward setup, no dual boot or multi-partitions etc.
No interruption in install process apparently available, a straight
automated install; it was similarly installed and worked fine using
same install disk and process (and hardware) in the past. AFAIR, W2K
never provides a "You may now shut down" screen; believe those are
from WinME/98 days. Yes have played w/BIOS power settings ad
infinitum, no luck. I can certainly relate to your brain's reported
'file recall' problem (-; ; keep dredging those mem-banks please!
---------------
Thanks again, this nagging problem's still here, please keep the
suggestions coming.
~misfit~
<snippage>
> misfit:
> Core voltage: CPUZ report fluctuates between 1.376-1.392v.
> Looked up specs on Intel's site, quite confusing for this novice,
> found these numbers, which if applicable seem to be in range:
> VID = 1.475, Vmax = 1.370 V, Vmin = 1.290 V, VID = 1.500, Vmax = 1.395
> V, Vmin = 1.315 V and VID = 1.525, Vmax = 1.420 V, Vmin = 1.340 V
> (http://processorfinder.intel.com/details.aspx?sSpec=SL7EY#)
That voltage could be borderline. The VID (CPU-requested voltage) for your
CPU is anything from 1.475 to 1.55V. Your voltage is well below that range.
Can you please go into BIOS and change vcore. I assume you have it on
"default"? Change it to 1.50V, then boot back into Windows and re-test with
CPU-Z. If CPU-Z doesn't say 1.50V then take into account the difference and
go back into BIOS and adjust accordingly until you get 1.50V showing on
CPU-Z.
Fingers crossed, it just might fix the problem. Can't do any harm anyway,
you can always put it back.
--
TTFN,
Shaun.
Bill Anderson
>
> Bill A.:
> mine's a straightforward setup, no dual boot or multi-partitions etc.
> No interruption in install process apparently available, a straight
> automated install; it was similarly installed and worked fine using
> same install disk and process (and hardware) in the past. AFAIR, W2K
> never provides a "You may now shut down" screen; believe those are
> from WinME/98 days. Yes have played w/BIOS power settings ad
> infinitum, no luck. I can certainly relate to your brain's reported
> 'file recall' problem (-; ; keep dredging those mem-banks please!
>
Have you looked at this page?
http://www.annoyances.org/exec/show/article07-016
zeke7
Shaun--I'm keen to try changing the voltage, but just did a thorough
hunt through my BIOS menu, couldn't find any voltage setting, only fan
speeds, temperatures & the like. Can you give me a clue what menu it
might be buried in? All I can figure is maybe it's a popup menu that
only appears when I enable a currently disabled feature (like the APM
menu), but tried several of those and nothing showed up. We are
talking about the AMIBIOS menu accessed by hitting Del on bootup,
right, or is there another bios menu I can access?
Bill: Had a look at the Annoyances page you gave; one link on it was
outdated and in spite of the very encouraging header, the two options
they talk don't sound sound likely: there is basically no shutdown
screen to tweak with in Win2K (other than a small box saying Windows
is Now Shutting Down), and I've certainly never tweaked anything
there. And as best as I can keep track I'm up to date on drivers--
video, LAN, BIOS, sound, mouse, Windows updates, IDE card, etc.
For all, a new occurrence is happening that may point things to my
Antec True480 power supply. As noted, to keep the system from
rebooting when I want to power down, I have to flip off the power
supply switch in back. Now, whenever I do want to restart, as soon as
I hit the back power switch, things start to fire up for about 3
seconds before petering out; if I then hit the front-panel reset, it
will restart and boot fine. But previously, under normal operating
conditions, when I flipped on the back switch, nothing happened except
to light up the MB's internal indicator light: I would have to press
the front-panel power button to actually get the power rolling.
Core2Duo
You must check the connection of the power switch to the MB. It sounds like
it could have the wrong orientation.
Also check the Reset switch.
Your comment "things start to fire up for about 3 seconds before petering
out" implies the power button is 'activated' as far as the MB is ocncerned,
& thus causing the actual PS to power down, just as it should under normal
circumstances ie. a forced Power Down.
~misfit~
<snip>
> You must check the connection of the power switch to the MB. It
> sounds like it could have the wrong orientation.
LOL. No offence man but it doesn't matter what "orientation" it's at.
> Also check the Reset switch.
Same with the reset switch.
--
TTFN,
Shaun.
~misfit~
> hunt through my BIOS menu, couldn't find any voltage setting, only fan
> speeds, temperatures & the like. Can you give me a clue what menu it
> might be buried in? All I can figure is maybe it's a popup menu that
> only appears when I enable a currently disabled feature (like the APM
> menu), but tried several of those and nothing showed up. We are
> talking about the AMIBIOS menu accessed by hitting Del on bootup,
> right, or is there another bios menu I can access?
No, you're in the right place.
Try "Advanced" "Jumperfree Configuration" "AI Overclock Tuner". Set to
manual. That should (hopefully) give you access to the "CPU Vcore Voltage"
option. Change it from "Auto" to, say 1.50V. (leave everything else as-is
for now). Then boot into Windows and check what CPU-Z is telling you.
> For all, a new occurrence is happening that may point things to my
> Antec True480 power supply. As noted, to keep the system from
> rebooting when I want to power down, I have to flip off the power
> supply switch in back. Now, whenever I do want to restart, as soon as
> I hit the back power switch, things start to fire up for about 3
> seconds before petering out; if I then hit the front-panel reset, it
> will restart and boot fine. But previously, under normal operating
> conditions, when I flipped on the back switch, nothing happened except
> to light up the MB's internal indicator light: I would have to press
> the front-panel power button to actually get the power rolling.
Ok, you possibly changed a setting in the BIOS. On the "Power" tab, under
"APM Configuration" there is a "Restore on AC power loss" that you can set
to 'Power on", Power off" or "last state". Perhaps you changed that from off
to on?
Either that and/or your PSU could be playing up. That could explain
everything. Let's hope not.
Cheers,
--
Shaun.
GMAN
Unlike an LED where the cathode and annode can be reversed and then not work,
a Power and reset switch are momentary contact switches and are not affected
by reverse polarity
Core2Duo
> Unlike an LED where the cathode and annode can be reversed and then not
> work,
> a Power and reset switch are momentary contact switches and are not
> affected
> by reverse polarity
>
Thanks for your comments.
I still say the 3 secs shutdown is somehow related to the power
switch/wiring.
Core2Duo
"~misfit~" <misfi...@yahoot.com.au> wrote in message
news:474eabf8$1...@news2.actrix.gen.nz...
Thanks for your comments.
Rob
> Here's a bit of a strange problem: whenever I shut down my home-built
> desktop (Windows 2000, SP4)--using 'Shut Down', not 'Restart'--after
> the OS closes out and the machine powers down as it should, as soon as
> the fans have shut off the whole thing fires back up again: fans kick
> on, the MB comes to life, BIOS boots and Windows fires up again. If I
> want this machine to stay shut down, I have to flip the back power
zeke, I've read all of this thread and replies, but can't see if this
PC ever did shut down properly, and now has this problem.
If it has always been like this, it's likely that you didn't have the BIOS
set to ACPI when you installed the OS. In most cases, it's not
possible to correct this without re-installing the OS as a new HAL is
needed.
To non-destructively test this idea, try an install to an old/spare hd,
if you have one.
HTH,
--
Rob
zeke7
> "zeke7" <zekeba...@gmail.com> wrote in message
Thanks again gents for all the suggestions. Here's a rundown results
for results of the latest ones:
Shaun: I tried upping the core voltage in BIOS, it needed a 1.6v
setting to get a 1.5+ reading in the CPUZ program, but still no luck,
rebooting on shutdown. And yes, I've had APM's Restore on Power Loss
set to off; have tried it both ways with no change in the result.
Rob: I've done a number of OS re-installs, and checked it from as soon
as I got W2K/SP4 installed, before doing any updates or further
installs other than the chipset driver; the problem is there from the
beginning, and continues throughout the updates (interestingly, the
Standby option doesn't show up in the Power Mgmt menu until well into
the Win Update procedure). Unfortunately I don't have an install disk
for a different OS to test if it is in fact the software doing this.
CoreDuo2: I'm with you, will check the wiring connections this
weekend. Have been reluctant as it requires pulling out 3 HDs to see
what's going on, and since my hard copy of the MB's manual is in a
storage locker, I'll have to reference the PDF version of it from my
PDA while I have things stripped down... tedious but tenable.
Core2Duo
Also check that you don't have the Power and Reset cabling swapped over.
eg Reset on MB -> Power wiring -> Power switch and similarly Power on MB ->
Reset wiring ...
zeke7
Thanks Core2Duo--I think you're on to something, I noticed that my
box's front-panel green power indicator light isn't functioning;
things could have got switched the last time I had it stripped down,
which may coincide with the onset of this problem. Those tiny pin
connectors are a challenge for my aging eyes. Trouble is just don't
have time to do a full strip-down this week, but will get to it as
soon as time permits.
Core2Duo
Result?
zeke7
Hi Core2Duo: thanks for staying on this. Result of inspecting all the
wiring connections & jumpers on the MB: only the front panel Power On
LED indicator light had a misplaced neg connection; set it to the
right pin and it works. The reset/power button connections were all
fine.
So after several new installs of Win2K on different hard disks and
testing the reboot on at various steps (ie, after fresh install before
executing Windows Updates, etc.), the restart and locked-up-on-standby-
mode problem remains.
Although this would seem to indicate it's something on the MB or power
supply making it do this, have just discovered a slew of MS
Knowledgebase articles addressing this issue:
Just applied a "48-bit LBA large-disk support" regfix (KB-305098), as
I also experienced disk corruption with my larger disks. (This manual
reg-tweak it turns out is required in addition to all the Win2K
updates, SPs, and Hotfixes to enable support for >137gb drives in
Win2K.)
Applying the 48-bit reg-tweak didn't correct my restart problem. But
one related KB article written for XP (KB-331958) indicated standby/
restart problems might be linked to this 48-bit issue. That led me to
slew of other KB articles written for W2K on restart/standby issues:
http://support.microsoft.com/kb/323153/
http://support.microsoft.com/kb/266169
http://support.microsoft.com/kb/242414/EN-US/
http://support.microsoft.com/kb/242495/EN-US/
I have yet to work through these; or for starters, figure out why I
have no APM tab in my Control Panel's Power Options menu, as KB-242414
indicates I should:
"1. In Control Panel, double-click Power Options.
2. On the APM tab, click Enable Advanced Power Management Support."
So still plenty of work to wade through these articles; will post here
if anything comes of it.
To clarify the history of this computer, I've recently pulled it out
of storage after 3 years, and now am experiencing these problems.
Before storing it, it ran fine, including standby/shutdown and running
>137gb disks with no corruption.
nick...@gmail.com
>
> I have yet to work through these; or for starters, figure out why I
> have no APM tab in my Control Panel's Power Options menu, as KB-242414
> indicates I should:
>
> "1. In Control Panel, double-click Power Options.
> 2. On the APM tab, click Enable Advanced Power Management Support."
>
> So still plenty of work to wade through these articles; will post here
> if anything comes of it.
>
> To clarify the history of this computer, I've recently pulled it out
> of storage after 3 years, and now am experiencing these problems.
> Before storing it, it ran fine, including standby/shutdown and running
>
>
>
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
I had the exact same problem as the original poster - after shut down
and power off, it boots up again, and when turning on from being off,
it turns everything on but doesn't POST until reset is pressed.
My configuration: homebuilt system (Asus P5W DH, Core2Duo E6600, ATI
X1900XT, Antec NeoPower 480, etc), running Vista Ultimate x64.
SOLUTION: I found that *indeed* the connectors to my power button,
reset button, and hard drive light were all flipped the wrong way when
connected to the motherboard. Simply flipping each one around solved
the problem.
Also, related to the voltage feedback - I don't think the proper
voltage for his core2 is 1.4v or higher. Mine is at 1.3v. If it was
some sort of low voltage situation, wouldn't this then be solved by
running a stress test in Prime95 and seeing whether the CPU is
functioning properly? BIOS' are usually very good at setting default
voltages correctly.
Good luck, and I hope this helps!
Keywords for searches: "automatically reboots after shutdown", "reboot
after shutdown", "boot after shutdown", "boot problems", "reboot
problems"
zeke7
I did double-check my power & reset buttons, they were/are correct,
but since that fixed your occurrence I'll try reversing them one by
one to see. Thx for the notice.