doesn't shut down..

OUMike · December 24, 2006

anyone ever have their computer restart when you tell it to shut down? What you think causes that?

Chestah · December 25, 2006

Are you running XP?

OUMike · December 25, 2006

Are you running XP?

<{POST_SNAPBACK}>

yea..XP Pro. I'll tell the computer to shut down and it'll restart.

General Lee 01 · December 25, 2006

Maybe if you click "Shut down" as opposed to talking to it?

Sorry man, couldn't resist

I've seen computers do really odd things before, and this is right up there...

Is this an "Every time" occurance or innermittent?

OUMike · December 25, 2006

Maybe if you click "Shut down" as opposed to talking to it?

Sorry man, couldn't resist

I've seen computers do really odd things before, and this is right up there...

Is this an "Every time" occurance or innermittent?

<{POST_SNAPBACK}>

hahah. Very funny..

it happens at every attempt.

Chestah · December 25, 2006

See if your computer does this in safe mode.

billcar9999 · December 25, 2006

anyone ever have their computer restart when you tell it to shut down? What you think causes that?

<{POST_SNAPBACK}>

There are lots of things that will cause that. Try here http://support.microsoft.com/kb/308029/en-us

ZZebes · December 25, 2006

right before it makes it to the POST screen turn it off manually using the button on the front of the computer. leave it off and unplugged for about half an hour. It wont reset the BIOS but it may reset the Power Supply enough to prevent a repeat. if that does not fix it you can try flashing the BIOS but not before resetting it using the jumper or battery. If that doesnt work you can go one of two ways one of which is hardware the other is software. Honestly with CougarByte in the UC and $13 copies of windows XP Pro a software refresh would be the next cheapest option. From there it is a hardware diagnosis.

If this seems like an undertaking you dont want to do send me a PM. I do this for a living and can probably get you fixed up at minimal cost since your a Coog and in a day or two.

Hope that helped.

Chestah · December 25, 2006

This behavior may occur if Windows stops responding during a typical operation or during the shutdown process. By default, the computer is configured to automatically restart when Windows stops responding. To view this setting, follow these steps:

1. Click the Start button, right-click My Computer, click Properties, click the Advanced tab, and then click Settings under Startup and Recovery.

2. Under System Failure, view the Automatically restart check box. If the Automatically restart check box is selected, Windows automatically restarts if the computer stops unexpectedly.

This will prevent your computer from restarting, but it will not fix the problem itself, if I am right.

You may want to reset your CMOS. Also make sure you don't have any viruses or similar malware that could be screwing with your operations.

ZZebes · December 25, 2006

This behavior may occur if Windows stops responding during a typical operation or during the shutdown process. By default, the computer is configured to automatically restart when Windows stops responding. To view this setting, follow these steps:

1. Click the Start button, right-click My Computer, click Properties, click the Advanced tab, and then click Settings under Startup and Recovery.

2. Under System Failure, view the Automatically restart check box. If the Automatically restart check box is selected, Windows automatically restarts if the computer stops unexpectedly.

<{POST_SNAPBACK}>

Yes but any unexpected stop of a computer especially when it develops later is something to investigate.

OUMike · December 25, 2006

Thanks guys. I actually was getting a blue screen error a while due to bad ram. New set of RAM and I'm good to go. I did however get a blue screen when I plugged in a jump drive, but I realized I hadn't installed my USB drivers (I just reloaded Windows).

I'm gonna reset the CMOS tomarrow after I wake up. I'm not reloading windows..thats for sure. Its a pain.

EDIT - Sounds like my blue screen error from before could very well be causeing the problem. Looks like I might have to reinstall winblows.