Windows 10: New Laptop keep on crashing and producing mini dump

Hi team,just recently purchase a new laptop that run on Windows 11.Upon setting up the laptop and removing bloatware the laptop start crashing eratically and I even has to reset it to make it a bit stabilise,May I please get some help in reviewing the mini dmp on what actually is causing the laptop to crash all the time.

:)

 

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

 

Windows 10 - Interpreting two BSOD Crash Mini Dump Files

After reinstalling Windows 10 stable release over the Windows 10 Insider Preview OS I had two separate BSOD crashes. I ran them both through WinDbg and have links to the plain text of the Windbg !analyze -v outputs.

BSOD Error Mini-Dump File #1 (Think it's something to do with Broadcom Driver) - Solutions?

Win 10 Crash Mini-Dump Output#1

BSOD Error Mini-Dump File #2 (This one is FREAKING ME OUT because it's saying something about memory corruption?!) - Cause?/Hardware?/Software? - because maybe I installed Windows 10 on top
of Windows 10 Insider (not a clean install)--- most importantly.... Solutions?!?

Win 10 Crash Mini-Dump File #2

Thank you all!

 

Asus G752VSK hard crashing when playing games

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.