Problem powering down my A7V333... need suggestions...

Malichite321

Junior Member
Jul 6, 2002
4
0
0
I have an unlocked Athlon XP 1800+, which I am currently running at 10x166 on a ASUS A7V333 motherboard. Recently however my system doesn't seem to power down correctly. Whether I have windows shut down or simply hit the Power Button (both modes: Soft Off <4secs or Override ATX power down >4 secs), the system shuts off and then powers back on in 2-3 secs. I have searched the web/forums for this problem, but all I find are stupid questions related to hanging on the Windows shut down screen (ARRGH!). This is a strange problem that I have never seen and I hoped one of you may have seen it before and know the solution. BTW I also have a Shuttle AK31A and it works fine when I swapped it in place of the A7V333, so I think that eliminates the PSU, CPU, and problems realted to the case power button bouncing/shorting.
 

onelin

Senior member
Dec 11, 2001
874
0
0
1) Check your ACPI settings in your BIOS and try making sure it is off.

2) Check your windows settings and make sure your power profile is always on, though you said it works with the shuttle so that is probably not the case.

3)What BIOS are you using? If not the latest (1007 last I checked), try flashing. With the Asus board, it's a very painless process.

4) ACPI seems like a tricky matter, I've seen it mentioned on more than one occasion that changing your BIOS settings related to ACPI (or flashing that changes ACPI) doesn't always take effect. What OS are you running, and did you reformat when you put in your new board?

I am guessing you may not have reformatted w/ the board switch, and if so...that MAY be the cause for your ACPI woes. I'm not overly knowledgeable in the area, but I hope this helps. I run an A7V333-raid on an AthlonXP 1900+ and it powers down just fine. Did with 1005 bios, does with 1007 bios. (I reformatted after a great deal of issues) I've also heard about different boards not shutting down properly when overclocking... but I think it's probably #4 that is the issue, not your overclock ;)