Computer powers off when game is loading after starting it

Does it happen only when powered by the battery charger or also on battery power?

My battery is dead. So it is always plugged in

- - - Updated - - -

The memory test I only could do once, as I had to leave it overnight and wasn't available during the day to run another test. The memory test passed on all passes

Is the power supply you are using a OEM device? I'm suspecting the power supply may be faulty.

The OEM charger doesn't work anymore. So I am using a TB3 dock to charge it (Elgato TB3 Dock; non-pro version)

For all steps / tests please post images into the thread.
For any problems posting images please use share links (one drive, drop box, or google drive)


Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums


For RAM testing 8 passes are needed.

Heres the output of bcdedit /enum all:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\WINDOWS\system32> bcdedit /enum all

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{501504b6-164c-11ea-9fe3-806e6f6e6963}
{8c445de8-1776-11ea-8698-806e6f6e6963}
{0a6e71bd-e580-11e9-9a73-806e6f6e6963}
{742f0bc6-72f7-11e7-bfda-f8cbe90d9e4e}
{78195f7a-17a8-11ea-8699-806e6f6e6963}
{78195f7d-17a8-11ea-8699-806e6f6e6963}
{78195f7f-17a8-11ea-8699-806e6f6e6963}
timeout 0

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
default {current}
resumeobject {69325fe5-0211-11ea-9b05-995dd6cd2c92}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 0

Firmware Application (101fffff)
-------------------------------
identifier {0a6e71bd-e580-11e9-9a73-806e6f6e6963}
device partition=\Device\HarddiskVolume2
path \EFI\UBUNTU\SHIMX64.EFI
description ubuntu
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {501504b6-164c-11ea-9fe3-806e6f6e6963}
device partition=D:
description UEFI: VerbatimSTORE N GO 1100, Partition 1
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {742f0bc6-72f7-11e7-bfda-f8cbe90d9e4e}
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {78195f7a-17a8-11ea-8699-806e6f6e6963}
description UEFI:CD/DVD Drive
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {78195f7d-17a8-11ea-8699-806e6f6e6963}
description UEFI:Removable Device
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {78195f7f-17a8-11ea-8699-806e6f6e6963}
description UEFI:Network Device
badmemoryaccess Yes

Firmware Application (101fffff)
-------------------------------
identifier {8c445de8-1776-11ea-8698-806e6f6e6963}
device partition=\Device\HarddiskVolume9
description UEFI: VerbatimSTORE N GO 1100, Partition 2
badmemoryaccess Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {6971be68-01f8-11ea-9552-ce3d942b3a3a}
displaymessageoverride Recovery
recoveryenabled Yes
badmemoryaccess Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {69325fe5-0211-11ea-9b05-995dd6cd2c92}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

Windows Boot Loader
-------------------
identifier {6971be68-01f8-11ea-9552-ce3d942b3a3a}
device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{6971be69-01f8-11ea-9552-ce3d942b3a3a}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
badmemoryaccess Yes
osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{6971be69-01f8-11ea-9552-ce3d942b3a3a}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {b038daf9-b464-11e7-8609-bbdf8cca6bc9}
device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{b038dafa-b464-11e7-8609-bbdf8cca6bc9}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
badmemoryaccess Yes
osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{b038dafa-b464-11e7-8609-bbdf8cca6bc9}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {69325fe5-0211-11ea-9b05-995dd6cd2c92}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {6971be68-01f8-11ea-9552-ce3d942b3a3a}
recoveryenabled Yes
badmemoryaccess Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
badmemoryaccess Yes
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local
badmemoryaccess Yes

RAM Defects
-----------
identifier {badmemory}
badmemoryaccess Yes

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
badmemoryaccess Yes

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
badmemoryaccess Yes

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
badmemoryaccess Yes
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
badmemoryaccess Yes

Device options
--------------
identifier {6971be69-01f8-11ea-9552-ce3d942b3a3a}
description Windows Recovery
badmemoryaccess Yes
ramdisksdidevice partition=\Device\HarddiskVolume5
ramdisksdipath \Recovery\WindowsRE\boot.sdi


- - - Updated - - -

Memory test Pass 1:
https://i.imgur.com/dhdp1Ku.jpg and see included attachment

- - - Updated - - -

Here are the results for the second round for the RAM test: Imgur: The magic of the Internet

- - - Updated - - -

Unfortunately, there was no mention of any voltage whatsoever in the BIOS.

When available please post:
a) text report for IPDT
b) text reports for Memtest86

Read these links on Windows driver verifier: (learn how to use the reset and bootmode commands) (do not use the tool until it is communicated in the thread)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Here's the only log of the RAM test I have, it's from the second run
MemTest86.log

Intel Processor Dianostic Tool (IPDT) can be reran and a text report posted into the thread.
When available post images of the HD Tune results

Do you have an alternative power source that you can try or even a spare battery? I still think this is related to a faulty or incorrect power set up that fails under load.