A callout to Win32k did not return promptly

Hello . I have an question. I want to ask.

I found that in pc.

I have in windows/livekernelreports/pow32kwatchdog.dmp <---.



Bugcheck 1a1 when i open dmp file.
"A callout to Win32k did not return promptly"


Is that error called "Clock Watchdog Timeout " ( bugcheck 101 )?
Or this is different error what i have?

Please see posting instructions:
BSOD - Posting Instructions


It was a Win32k callout watchdog livedump: 1a1

It was not a clock watchdog timeout: 101


The first was a live kernel event.

The second is a BSOD.

After that ( pow32kwatchdog.dmp ) error my pc get auto rebooted with KERNEL POWER 41. So why it get rebooted if this is not BSOD but livekernelevent ?:) Last question.

Please see posting instructions:
BSOD - Posting Instructions

Live kernel events can produce dump files.
Often they can be debugged like BSOD.

There could be other or related problems.
So logs are troubleshooted.

I will upload later dump file. But can you answer me ,thx.

I left Metro Exodus running by character standing on the same place for 12 hours. When i back to home i clicked ESC and while exiting to MAIN MENU ( moment where GPU LOAD drops ) i get BLACK SCREEN and no monitor signal for 1 minute, and crash to desktop with TDR driver crash in event log.
Then i log out from system and log in again,and bum unexpected reboot.

So that reboot ( KERNEL 41 ) was related to event--> pow32kwatchdog.dmp ?

Information about underlying computer problems may be in the logs.
Or information my be available in file debugging.

When available please upload V2 so that files can be troubleshooted.

ok screens:

Please use English as the default language and upload V2 into this thread:

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

BSOD - Posting Instructions