Computer won't shut down

[flyted]

My apologies to those who answered a previous thread on this subject, but I can't find my original post. When I click turn off computer it goes through its normal shutdown even to the point of the monitor turning off and at the last second reboots. The on/off button will just keep rebooting it also, have to turn off the power supply to get the computer to go off.

I've removed every program I didn't need, ran anti-everything both in normal and safe mode, went to my computer/properties/advanced and unchecked restart automaticcally, shut the computer down in safe mode(sometimes it will and sometimes not), searched microsoft.com knowledge base, tried to remove startup programs from msconfig(left the ones I was unsure about), ran CCleaner. No luck so far, if anything its now gotten worse.

Any ideas would be appreciated.

 

[bldegle2]

system specs...

r u overclocking?

you may at the very least need to do a repair install, but first, you might want to try a couple of things...

maybe up the vcore a smidgen (volts to cpu)

maybe up the vdimm a smidgen (volts to mems)

what is the inside of your box like, good air flow, or a tangle of wires????

once you post system specs...

laterzzzz............

 

[WT]

Here's a similar thread:

Text

I answered with what solved my shutdown error in that thread.

 

[C1]

Again, make sure that you disable in the BIOS all available options related to "Start Up from LAN", "Start Up from Keyboard", "Start Up from Set Date/Time", etc. & Set the Power Management Option to Shutdown when the Power Button is pressed (as you didnt mention anything about BIOS settings).


Also make sure that in Control Panel, Power Options you have selected "When I press the power button on my computer then - shutdown" .

Checkout the hardware by issuing the windows shutdown command at the command prompt:

C:\shutdown -s -t01 (the -s is for shutdown & -t01 is the number of seconds before shutdown)

The above command entirely shutsdown my Fjitsu notebook (ie, everything is off - all motors).

If the computer shuts down at the command prompt then the hardware is certainly OK & I would just go ahead with the recommendation to repair the system (gonna be a lot less time consuming than nailing down a specific fix).


======

 

[flyted]

No overclocking and all temps are normal.
Checked the bios settings and all "wake on" functions are disabled.
Control panel power buttons are set correctly.
I copied and pasted the cmd function and it says invalid entry.
I noticed my MB bios hasnt been updated in a long time, I could try that once I find a diskette, I thought I could do it online but I guess not. The last shutdown was normal, didn't change anything, it just does it 95% of the time.

What should I try next?

 

[flyted]

I updated my MB bios, it was out of date by 1 revision and is still old 8/04 but is the latest they have and the last update had no relevance to my shutdown issue. Pure coincidence I'm sure, but the last 2 shutdowns prior to the bios update, were normal. Maybe my computer knows its in for a challenge and gave up. I hope so.

 

[C1]

If you enter into search "shutdown.exe" it will find it in C:\Windows\System32. Also, it isnt an invalid command. It is there.

Not sure what you pasted but at a C:\ prompt type "shutdown -s -t01" no quotes & there is one space each between shutdown & -s & between -s and -t01

 

[thegorx]

have you tried pluuging in somewhere else or to something else ?
have you added any external devices ?

It kind of sounds like it might be starting by itself not restarting

 

[flyted]

I entered the command and it displays USEAGE and lists what the -s and -t01 means but doesnt do anything else. I located shutdown.exe via search but can't open them. I see the black CMD menu for a second and then it just goes back to the search page.

No external devices, no recently added hardware or software.

Plugging in somewhere else? Not sure what that means. I'm plugged into a line conditioner and UPS.

 

[flyted]

Finally got it to shutdown via shutdown -s, it wouldn't allow a time to be specified. It did shutdown normally, however it will sometimes shutdown correctly. So what does this tell us and where do we go from here?

 

[thegorx]

try disconnecting the UPS and the line conditioner

 

[C1]

As I said before, if the computer shuts down correctly & consistently using the command prompt then the hardware is certainly OK & I would just go ahead with an OS repair (gonna be a lot less time consuming than trying to nail down a specific fix).

So with your system disk, use the repair option. All your programs & most settings will be preserved.

 

[flyted]

Looked for the repair option on my original disk and can't find a repair option. What is it listed under?

 

[janifer20]

I can't find my original post. When I click turn off computer it goes through its normal shutdown even to the point of the monitor turning off and at the last second reboots. The on/off button will just keep rebooting it also, have to turn off the power supply to get the computer to go off. It kind of sounds like it might be starting by itself not restarting. and if the computer shuts down correctly & consistently using the command prompt then the hardware is certainly OK.
janifer20
<deleted>

No spam, please

-ViRGE

 

[flyted]

I repaired my XP witht heinstall disk and it still reboots now every time I try to shutdown. I also tried using a different outlet, not sure of the theory on that but it was worth a try and still no luck. I wish it had some other symptom to help diagnos whats going on, but everything is working great except turning off the computer. Whats next?

 

[C1]

No good news Im affraid. MicroSofts WINDOWS XP - Inside & Out has a whole Chapter (number nine) on Power Management. It is very involved & there are a lot of possibilities ranging from BIOS settings, XP installing the incorrect ACPI HAL (Advanced Configuration & Power Management Interface Hardware Abstraction Layer) to an incompatible driver. There also are many settings scattered all over the OS ranging from Power Management to Device Manager which need to be checked. If you can get this book (maybe even only Chapter 9 online) then I recommend running thru the ACPI checks & tests that it provides. It also describes other methods to initiate a shutdown. For now, if the "shutdown -s" command line works for you then just write a batch file that issues it & just initiate it via an appropriate icon located on your desktop. Or shown here are some other ways to accomplish this: http://www.pctipsbox.com/4-tri...hut-down-your-windows/

 

[flyted]

The 1st clue I've found now is in the event viewer/system at the time it reboots and it has 2 errors that deal with AVG8, a free antivirus program which was removed a month ago. I did a file search and can't find anything, did CCleaner and regclean. The erroer has to do with the AVG8 Network redirector failed to start, file not found, and the AVG8 boot-start and system-start driver(s) failed to load, and it list 4 AVG files , all of which I can't locate. The last error seems highly likely as a problem. I could download AVG again and see if it fix's the problem? Worth a try or what info does this now give us?

 

[ViRGE]

At this point it couldn't hurt.

 

[C1]

Ensure that in Control Panel, System, Advanced Tab, Startup & Recovery that the "Automatically restart" box is unchecked.
(as the repair might have reset this box since that is the default)

 

[flyted]

You are right, the repair did reset it and I unchecked it. I'll download AVG tonight and see it that helps, if not I'll remove it and see if it takes the bad files with it. I also wanted to try regclean.exe in addittion to the CCleaner I already used, however regclean uses a .pf file which I don't have and the only download for a .pf file I found was 16MB. Is there a shorter download somewhere or a better registry cleaner?

 

[imported_abercrombie]

what kind of system is it? i had a notebook hp dv2000z that failed to go into suspend or shut down. this was on vista so i uninstalled and just downgraded to xp. same thing. turns out it was the Adobe Bridge software i was using that had some issue with some kind of process. so i had to close adobe bridge and then it would shut down properly. weird.