Desktop computer crashes: doesn't wake up, reset button doesn't work

Additional hint: it seems that the computer crashes specifically when waking up the computer, not before. The computer flashes the power LED when on S3 sleep. Then I press a button to wake it up. Power LED stops flashing, now stays lit. But nothing else happens. The computer has crashed. The last System log is indeed "The start type of the Background Intelligent Transfer Service service was changed from demand start to disabled." and then the next lines are after powering up from shut down. And I found these two, as some of the first lines after powering up:

"Kernel-Boot: The last shutdown's success status was false. The last boot's success status was true."

"Kernel-Power: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

- - - Updated - - -

Megahertz said:

The best anti-static shield is to have the computer grounded. Is your outlet third pin grounded?

Yes, it should all be normally grounded, the apartment is built in 2001, one outlet was added in 2006 (did not hear any problems from the electrician).

I actually have done all of those just a few days ago. No difference.

Now I've ruled out BITS, it probably is not related. Because I stopped the service for that and that didn't make a difference (the last log entry was then not BITS, but some random other event).

My motherboard unfortunately doesn't have the boot state digits display so no information from there. But it does seem like it always crashes when trying to restore from S3 state (changes from power LED flashing to power LED lit and wake up stops there).

As the memory doesn't seem to be the problem, and CPU/memory is not overclocked, what is the most probable culprit? Is it the motherboard? Is it possible to change to the same motherboard model (if I can find one) and continue using Windows like nothing happened? Or will my Windows stop working because of changing the motherboard?

I now filled the system specs for my desktop computer.

I guess the Windows 10 license is the least of the concerts, I can manage that. I'm now testing what happens when running Ubuntu and suspending there. I'll report about that in a few days.

Is it possible that a USB device could cause this problem, ie. disconnecting the problematic USB device, the problem could end? (I will try removing USB devices after the Ubuntu suspend test.)

I have now finished the Ubuntu test. Which overrides the clean boot test. Because Ubuntu is super clean, ran from USB with nothing installed. All cables unchanged. Results: first day no crash, no problem. Keyboard woke up Ubuntu from Suspend. A few days later: power LED flashing, pressed keyboard, no response (strange!). Pressed the front power switch and the computer is stuck exactly as in Windows. So this rules out a problem in Windows. It's a hardware problem.

Do you suggest I should exchange the whole motherboard?