Windows 10: On what basis a reboot initiated through InitiateSystemShutdownEx gets marked as Unexpected...

A shutdown initiated through our internal tool was getting marked as "Unexpected Reboot" in the Windows Event Viewer.We are usingInitiateSystemShutdownW from our tool to initiate Shutdown in the with the following arguments:lpMachineName - NULLlpMessage - Shutdown message for Event ViewerdwTimeout - 0bForceAppsClosed - truebRebootAfterShutdown - Shutdown or Reboot based on the operationWe would like to know the behavior of the API used and also whether the Shutdowns initiated through it will be marked as "Unexpected" or not? If so, We need to know at what cases the shutdown will be marked as "

:)

 

Reason for the mini dump folder was created empty while unexpected reboot.

Reason for the mini dump folder was created empty while unexpected reboot.

Suggest me the steps to find the root cause of unexpected reboot in the above case

 

Unexpected reboot

Hi Ken,

ty again....

yes

Myupdate:
Hasn't rebooted since my last post but I've not had pc on for more than a couple hours in one go. (busy job).

- - - Updated - - -

are the two yellow items bad?





- - - Updated - - -

sorry- last pic didn't have correct 'raw values' view as you suggested

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.