Thanks [B]eric93se[/B] for reaction
I think I might have find the problem. I think is the AMD CPU driver.
I’ve already flashed the latest BIOS after buying the motherboard.
The only driver that’s not the latest one is for CPU. I have an Athlon X2 BE-2400 CPU and default Win XP drivers (both 32bit amd x64 version) was from 2004. I took the latest drivers from AMD site and , on Win XP SP2 32bit that I’m using now, it can succesfuly wake-up from stand-by . I must install Win XP x64 to see if there are problems there. In readme file of new CPU drivers package it’s written that they have fixed S3 issues :
"Driver Version 188.8.131.52- 6/19/06:
Driver Change - This release fixes an S3/S4 â€œResumeâ€ event issue introduced in driver v1.3.1. Specifically, this driver properly restores the p-state that was in effect at the previous S3/S4 â€œSuspendâ€ event.
Known Issues - None.
Driver Version 184.108.40.206- 5/11/06:
Driver Change - This release fixes an S3/S4 â€œSuspendâ€ issue introduced in driver v1.2.2.
Known Issues - Under power schemes where policy is enforced one (i.e., non-adaptive policy), on a â€œresumeâ€ event, the v1.3.1 driver fails to restore the p-state that was in effect at the corresponding â€œsuspendâ€ event. This condition remains in effect until there is a change in policy, either by a change in power source (AC/DC), or a change in power scheme.
Impact of Known Issues - Either battery life or performance, depending on the expected p-state, compared to the current p-state. For example, resuming at a high p-state, instead of the expected low p-state, would degrade battery life.
Driver Version 220.127.116.11- 4/14/06:
Driver Change -Support added for 100Mhz frequency steps when available.
Driver Version 18.104.22.168 - 3/09/05:
The processor driver supports performance state transitions on the AMD dual-core processor systems.
Known Issues - Under power schemes that enforce adaptive policy (e.g., â€œPortable Laptopâ€), and under stress conditions that force the processor to make p-state transitions, while at the same time the system is attempting to â€œsuspendâ€ (S3/S4 sleep state), the v1.2.2 driver may reach a dead-lock condition by attempting a p-state transition while in the midst of the â€œsuspend sequence.
Impact of Known Issues - Investigation and testing confirms that the dead-lock condition is very unlikely to occur under normal user scenarios. However, if it does occur, the system will soft-lock (e.g., the system will remain at: â€œPreparing to Standbyâ€¦â€), and would have to be rebooted."