Windows 10: Win32k_callout_watchdog_livedump BSOD or not BSOD?

Hello.
My question is. I get crash in game when i click exit to desktop. Black screen for 1 minute,nothing responding. Then desktop appeared ,screen appeared and after 1 minute pc just reset itself.
I open eventog and there was only about KERNEL-POWER 41,but not bugcheck. So it was bsod or not?
But i have found in windows/livekernelreports/ watchdogPOwin32k.sys ,screens:




















So is this possible for BSOD without bugcheck in event log then? Reboot was 20:22:00. That file watchdogPOwin32k.sys in livekernelreports are 20:18:00. Like i stated reboot was with KERNEL POWER 41 in event log. No bugcheck in eventlog. Only that file which i stated.



My pc:

Monitor:AORUS AD27QD
Cpu: i7-9900K stock 4.7 with Noctua NH-D15
Gpu: Rtx 2080 Ti Aorus Xtreme Waterforce stock no oc,temps max 63C on load
Ram: 32gb 2x16 GB DDR4 GSKILL 3000MHZ XMP
Psu: Seasonic Ultra Prime Titanium 850W
Monitor: AORUS AD27QD
SSD: Crucial 1TB
HDD: WB BLUE 1 TB
Case: Cooler Master Cosmos C700P

:)

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

BSOD randomly

friend keeps getting BSOD
any suggestions?

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.