Solved ntoskrnl.exe high CPU usage after hibernation

Hello,
I've noticed that the CPU has high utilization by ntoskrnl.exe ( System ) when I wake the laptop from sleep, but only when it goes to sleep on its own after a long period of standing.
If I go to sleep mode manually, the problem doesn't exist.
The annoying:
the load then remains. Is an oldie laptop;
The interesting thing: the problem does not occur under Windows 10.
What can you do there ?


Windows 11 22621.586

As this can be caused by a number of things, it will be a process of elimination and time consuming. (after each step, let computer go to sleep on it's own, then wake it up and see if it makes a difference. You might want to shorten your 'sleep after' time in power options to make it go faster)

Things to try:
1.. Unplug all devices connected to the computer, usb drives, even headset and microphone

2.. From command prompt as administrator
sfc /scannow (if corrupt files fixed, restart computer)
DISM /Online /Cleanup-Image /RestoreHealth (restart computer)

3.. Perform a clean boot to eliminate software conflict causing the issue. If it doesn't happen in a clean boot, you have some software conflicting with Windows. Brink's procedure will help you weed out which one. Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts Tutorial

4.. See if issue happens in safe boot.

5.. Disable Windows Search - in search type services.msc Find Windows Search in the list and stop the service. This service will automatically restart when laptop is restarted unless you change the startup type to disabled

6... This can also be caused by a driver. You will have to dig into event viewer to see if it points to which one. Look for events happening around the time the laptop goes to sleep and comes out of sleep.

The fact that it doesn't happen in 10 is immaterial here. You are running 11 on very low end incompatible specs and drivers or software may be incompatible.

Hallo,
I will test it,
thank's for the Tipps.

Hallo,
No result, I looked again at Win10, the error is there too, when the system is in hibernation for about 1 hour, I have processed everything, disabled autostart and non-Windows services, removed USB devices, no change. The weird thing I find is, when I manually hibernate everything is fine so I have to stick to that for now so don't see it as a big problem.
I tested after 30 min. all Ok. very strange !

EDIT:
i read this here
below, ( i dont use drivereasy) :
but this is interesting,
Method 4 with xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d cpuusage.etl
But now, when I open the cpuusage.etl, how do I recognize the file or the process that is triggering it?

EDIT:
Problem solved
Install the Windows Performance Analyzer
1.) download and download and Install Windows Performance Toolkit see here:

2.) after install the WPA, do this command as admin:
xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d cpuusage.etl

3.) i copy the File cpuusage.etl form System32 to my Documents,
the doubleclick on the File an the WPA load this file.

4.) you see this:


Then drag and drop the right Site, click on the Arrow System and expand this, then click on Root, expand this,
Now i see the bad risdxc64.sys File, i know, that is a Ricoh Driver, that i have installed.


Now i search with everything ( voidtools ), this File, that is in
C:\Windows\System32\drivers\risdxc64.sys and Programm Files x86 Ricoh...

while the CPU and ntoskrnl.ex are running at full speed, I uninstalled the driver and, lo and behold, everything was quiet. Then reinstalled without rebooting and waited for auto hibernate,
I set it to make it faster
Screen after 2 min, power save after 5 min and sleep after 8 min.
Problem was back.
Now go to the device manager, and disable the device there, and lo and behold, it's quiet.
Then of course I searched the net and found the right driver,
Product version 2.25...
before was version 2.24.., exactly this is activated after the Auto sleep mode, as if an SD card was inserted, so the ntoskrnl.ex goes back to full speed, althoug it is the risdxc64.sys.
The new driver and the system are now running normally.
It was pure detective work, but it was worth it
If I had had the WPA tool straight away, things would have been done in no time.

Here a link for Using the WPA

Note:
The device is a freshly bought Lenovo T530 ( used ) of an acquaintance, for her I then installed Win10 and later ironed Win11 over it, of course before backup of Win10, if she does not get along so well with Win11.
Of course, I did not want to pass on the T530 with the problem, since the acquaintance uses the sleep state a lot, I also do by the way.

Again for info.
Interestingly, the driver running on Win10 1A again creates the same problems under Win11. Habs just tested and I 100% assumed that the under Win11 also runs without problems, according to Lenovo it is a Win8.1 driver and supports Windows 10., but not Win11.
Then uninstalled again and now installed the one for Win7.
Result:
No problems !
It's strange how differently Win10 and Win11 behave, and in general, that such a mini device can cause such problems.
well, the main thing is that it runs on both systems.