ProArt X870-E: powering on itself

[solip90]

I have 2 of the ProArt X870-E boards.

Both came with an older BIOS and both were flashed to 1003.
One had an outdated firmware on the ASM4242 USB4 controller, the other one did not.

The one with the previously outdated ASM4242 firmware keeps powering on itself every x minutes. The only way to prevent that is to disable WoL/from PCIe in BIOS.

The other mainboard does not behave this way and does WoL when called for.

CMOS reset etc. brings no change. Swapped memory, OS drive, CPU between these two boards - it's not that.

Not a big problem, but unconvenient for me. Wanted to leave this info here.

[Katana1074]

Hi....

Have you updated the ASM4242 USB4 controller firmware on the board that is giving you issues ?

Can you please follow the guide at the 11 forums and post back with the last wake event ?

https://www.elevenforum.com/t/find-wake-source-for-windows-11-computer.7007/

Regards

[solip90]

The powercfg -lastwake shows 0 events.

Th eventlog logs 577, 172, 109 events at every cycle but does not reveal a source.

[solip90]

It looks like powercfg -lastwake is only applicable for wakeups from sleep/hibernate/powersave.

My board powers on itself from complete off. No windows fast start, no sleep.

[solip90]

Hi,

I did flash the ASM4242 with the updater provided by Asus support. It clearly says update done or not needed.

Put the BIOS setting for WoL back in - gonna check the last wake record.

[Katana1074]

Hi...

It may sound stupid, can you list any hardware differences between both systems if any..

Second if you disconnect the ethernet cable from the affected system, does the system power on by itself still ?

[solip90]

System stays off when the network cable is disconnected.

[solip90]

Hi,

the differences are: power supply, ram and CPUs. GPUs are the same, NVME too.

The working board had 9800x3d on it and 9950x. The non-working board had them both too and showed the same error with both.

RAM ist just a 2 x 48GB kit vs a 2 x 16GB Kit - both Kingston Fury, both DDR5-6000, all sticks tested with memtest.

Good point with the plugged in LAN cable. I had the problem with Intel 226 and Marvell Qaction iirc, but use the Marvell NICs now. Will try that out!

[Katana1074]

Hi...

So if your system stays off when you disconnected the ethernet cable, do you have any devices on your network that are sending

wake on lan packets (magic packets) to your system?

[solip90]

I have an app to send magic packets to control machines, which I want to use of course.

But besides that no unwanted wakeup calls on the net.

The issue has been resolved by disconnecting from the switch for a longer time and also switching off the PSU. I think the marvell qaction was Ok then, but I switched to the intel 226 for other reasons. No more unwanted wakeups.

Win settings also had no effect on the issue. Whatever is in the power settings of the cards did not affect the behaviour.

If anyone encounters this issue - take away physical power over night, I think that does the trick.