My BIOS doesn't allow me to see the voltages. I know there's a way to mess with it in a way that would allow me to, but I don't feel very comfortable messing with it since I'll be trying to return this laptop.
Even in advanced mode I can't find the voltage anywhere. This is a screenshot of it (taken from the internet, it's not from my own):
Attachment 175675
In this thread multiple times you have been able to produce a dump file for debugging and at the same time the logs displayed that there were no mini or memory dump files.
Please explain how you modify the settings and then are able to produce dump files for debugging.
How were you able to create a watchdog dump file?
And at the same time not have a mini or memory dump file?
The event file displayed: Dump file creation failed due to error during dump creation.
And somehow you still had a watchdog dump file.
Please explain.
I have no idea. I didn't even know those Live Kernel/Watchdog dumps existed until we started this process.
Whenever this computer crashes due to a game, one of those Live Kernel Dumps shows up in that c:\Windows\LiveKernelReports\WATCHDOG folder, but no regular minidumps or Memory dumps in the c:\Windows\Minidumps or c:\Windows folders.
The only time where regular dump files showed up was when you instructed me on how to simulate a crash via WhoCrashed.
The WATCHDOG files that the OP provided were created by the system when it detected a hardware problem. They are recorded in a special LiveKernelReports folder inside the Windows folder. These are not BSOD crashes and do not produce the normal crash dump files that get saved in the minidump folder. They are found by the new beta08 log collector and are reported in the Error Reports section.
These events will also show up if you view the Reliability History. You can then click through to the Problem Reports and they will be listed under the Windows section. I happen to have an example from my own system:
Attachment 175688
Normally the system recovers from these events, I am not sure why the OP is getting reboots after this occurs but I am sure it is related. For some reason the most recent occurrence of the 141 event did not go on to produce an error report and so it was not listed in the log collector result that was uploaded.
Last edited by philc43; 05 Feb 2018 at 09:00. Reason: corrected an error
philc43 like you I was also puzzled when it did not display a WER.
Typically when viewing the livekernalevents most often they are in text and cannot be used for windbg debugging.
In this thread the livekernalevents were regularly producing watchdog files that could be processed by windbg.
The beta log collector is frequently displaying watchdog files in threads that have no collected dumps.
So for this and other threads it was an may be possible to find misbehaving drivers when the mini dump and memory dump files are empty and the event viewer displays Dump file creation failed due to error during dump creation.
This is going a little off-topic but yes, there may be times when these LiveKernelEvents can be useful. They are really there for Microsoft to perform automatic analysis of crashes and as I showed earlier they get reported via the WER process automatically to MS and this gets logged in the Problem Reports page under Windows as shown in my earlier post #74.
My feeling is the number of times this would be useful is very small - better to ask for the dump file if you know it is there from the error reports and think it would be useful. As I said these are not BSOD events.
Quote