pow32kwatchdog.dmp. PSU ISSUE?

[sew333]

Hello.

Hello. I think i was get bsod but not sure. System was hanged and lags after crash in game to desktop.

After 1 minute i get system reboot ( like power cut ) and logged to system.

Screen from event log:

20:17:30 reported time of unexpected reboot. There was not bugcheck.

https://i.postimg.cc/520rmq80/we2.jpg

Also found file in : windows/livekernelreports/ pow32kwatchdog.dmp.

Time: 20:18:00

https://i.postimg.cc/SKwspb8z/we1.jpg

When that happened i dont saw a BLUESCREEN on display,only simply reboot. But my question is. Is that file windows/livekernelreports/ pow32kwatchdog.dmp , was related to that unexpected reboot? Thanks


Or it was psu issue?

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
mb: Asus Prime Z390-A
SSD: Crucial 1TB
HDD: WB BLUE 1 TB
Case: Cooler Master Cosmos C700P

[Lowkey]

My games had lags for 1-2 Seconds and then the pc rebooted. After i had changed the mainboard the problem never happend again. No log, no BSOD.

[sew333]

But it crashed to desktop normally. After moment my system rebooted like i told. And i am not sure if that was caused by that file or just hardware psu or gpu?

[Asaraki]

This is from memory, but should still apply :
- Reason for the quick reboot (BSOD with auto reboot, but no time to actually view the BSOD!) can happen when you don't have enough free space for the memory dump (system drive) and still have auto reboot set to ON. (just imagine dump being done in .0001 seconds and then reboot)

So I suggest fixing both if applicable :
- Increase free space on system drive to >MemorySize
- Disable auto reboot. Either via advanced system settings or command prompt : wmic recoveros set AutoReboot = False
(See the system failure doc to also enable logging if not enabled: https://docs.microsoft.com/en-us/windows/client-management/system-failure-recovery-options)

After that you should actually know the real reason of the BSOD and can then proceed from there :)

[sew333]

This is from memory, but should still apply :
- Reason for the quick reboot (BSOD with auto reboot, but no time to actually view the BSOD!) can happen when you don't have enough free space for the memory dump (system drive) and still have auto reboot set to ON. (just imagine dump being done in .0001 seconds and then reboot)

So I suggest fixing both if applicable :
- Increase free space on system drive to >MemorySize
- Disable auto reboot. Either via advanced system settings or command prompt : wmic recoveros set AutoReboot = False
(See the system failure doc to also enable logging if not enabled: https://docs.microsoft.com/en-us/windows/client-management/system-failure-recovery-options)

After that you should actually know the real reason of the BSOD and can then proceed from there :)

Really appreciate it for help . Yes i have checked automatically reboot ON actually,in system settings.

https://i.postimg.cc/htjx8KPT/m.jpg



And there was not also bugcheck in event log after reboot.

I opened that file and post here screens.
If of course that file was related to that reboot.

windows/livekernelreports/ pow32kwatchdog.dmp

size is 1,7GB

1:
https://i.postimg.cc/kXL8KP81/w1.jpg

2:
https://i.postimg.cc/13cttkKN/w2.jpg

[Lowkey]

But it crashed to desktop normally. After moment my system rebooted like i told. And i am not sure if that was caused by that file or just hardware psu or gpu?

You can run some stress tests, memory tests etc...

I startet a game and got a ctd in the menu. And i had the same issue like you: ctd, wait..., reboot and no log. Whocrashed found nothing.

[sew333]

Yeah but my situation was different it was happened once noting to reproduce :)

[Asaraki]

No, you want to turn AutoReboot OFF! :D And then google what the BSOD says ;) Assuming it happens again of course. AutoReboot ON is really only good for unattended systems or further family members :D

To explain further : I expect the BSOD to point to a driver file, which will then allow you to have a better idea of which device is causing it

[sew333]

But my reboot was caused by psu or it was bsod?

[Asaraki]

But my reboot was caused by psu or it was bsod?

That's a stupid question mate :D That's what we're trying to find out by actually ALLOWING the BSOD to happen and show.

[sew333]

So i have actually settings that they not make a bugcheck and not dump file, after reboot? ( when bsod happen ) Yes?

[Asaraki]

So i have actually settings that they not make a bugcheck and not dump file, after reboot? ( when bsod happen ) Yes?

You have the setting, so that after the dump process is completed in case of a BSOD then your PC automatically restarts.

If you turn that off, it will remain on the BSOD and you have all the time in the world to read it properly :)

[sew333]

So my reboot ,that was BSOD or just reboot like power cut?

So i understand that file
windows/livekernelreports/ pow32kwatchdog.dmp, was not related to that restart reboot?


I have all on default settings:

https://i.postimg.cc/htjx8KPT/m.jpg

pagefile i have on 4200MB

[Lowkey]

a. PC => Freeze => Reboot => no log
b. PC => Freeze => Reboot => log
c. PC => Freeze => BSOD => log

You always gets a log about "shutdown failed".