Computer powers off when game is loading after starting it

Hey all,
So I am running my laptop on TB3 100w, which should be more than plentiful as the OEM charger is a mere 45w.

I'm having this weird problem that only seems to arise when I load that particular game title (The Sims 4). It maxes out the CPU and the Intel iGPU. It isn't always reproachable as sometimes it loads completely and I'm able to play the game. It doesn't always happen at the same point in the loading sequence either.

If I open up Event Viewer I can see some Kernel-Power events which would correspond to the power offs.

I'm at a loss as to why this is happening.

This doesn't happen with any light usage.

Windows 10 1909 Build 18363.476

Please run IPDT and post images into the thread:

Download Intel(R) Processor Diagnostic Tool


Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums

- - - Updated - - -

I don't think it's heat related as @topgundcp has suggested. The system is cool when i start the game

- - - Updated - - -

I checked CPU temps using Open Hardware Monitor and nothing is out of the ordinary.

I started the game and the CPU temp got to ~83C before the system powered off. Which is still far from the critical temps

1) There are log collectors used in another forum room.
Run V2 and upload results into this thread:
BSOD - Posting Instructions


2) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer


3) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10


4) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10

Unfortunately the Prime 95 and FurMark test do not complete. My system powers off immediately after starting Prime 95 and FurMark after only a couple seconds of running

Please post a link for the computer manufacturer's website displaying drivers/BIOS.

There were > 60 crashes in the past 30 days
(these could have been power offs due to hangs/freezes or spontaneous crashes)
(please indicate how often hangs and freezes with power offs occurred)

The computer had 1 BSOD on 11/21.

What is the Warranty status?


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

11) Make sure that there is no over clocking while troubleshooting.

12) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

13) Run Memtest86 version 8.2 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.
MemTest86 - Official Site of the x86 Memory Testing Tool
Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)
Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

14) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

15) Open the BIOS
Find a camera or smartphone camera to take pictures and post images into the thread.

What are the BIOS 3.3, 5 and 12 voltage values?

What are the CPU voltage and frequency?

16) The IPDT software has a menu option for text report.
Please post a share link into the thread using one drive, drop box, or google drive.

• Manufacturer drivers download page.
• Out of warranty
• Commands output:
  Windows PowerShell
  Copyright (C) Microsoft Corporation. All rights reserved.
  
  Try the new cross-platform PowerShell Installing PowerShell - PowerShell | Microsoft Docs
  PS C:\WINDOWS\system32> sfc /scannow
  
  Beginning system scan. This process will take some time.
  
  Beginning verification phase of system scan.
  Verification 100% complete.
  
  Windows Resource Protection did not find any integrity violations.
  PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth
  Deployment Image Servicing and Management tool
  Version: 10.0.18362.1
  
  Image Version: 10.0.18363.476
  
  [==========================100.0%==========================] No component store corruption detected.
  The operation completed successfully.
  PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth
  
  Deployment Image Servicing and Management tool
  Version: 10.0.18362.1
  
  Image Version: 10.0.18363.476
  
  [==========================100.0%==========================] The restore operation completed successfully.
  The operation completed successfully.
  PS C:\WINDOWS\system32> sfc /scannow
  
  Beginning system scan. This process will take some time.
  
  Beginning verification phase of system scan.
  Verification 100% complete.
  
  Windows Resource Protection did not find any integrity violations.
  PS C:\WINDOWS\system32> chkdsk /scannow
  Invalid parameter - /scannow
  PS C:\WINDOWS\system32> chkdsk /scan
  The type of the file system is NTFS.
  Volume label is Blade Stealth.
  
  Stage 1: Examining basic file system structure ...
  2608896 file records processed.
  File verification completed.
  5588 large file records processed.
  0 bad file records processed.
  
  Stage 2: Examining file name linkage ...
  4734 reparse records processed.
  3167882 index entries processed.
  Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  4734 reparse records processed.
  
  Stage 3: Examining security descriptors ...
  Security descriptor verification completed.
  279494 data files processed.
  CHKDSK is verifying Usn Journal...
  37276088 USN bytes processed.
  Usn Journal verification completed.
  
  Windows has scanned the file system and found no problems.
  No further action is required.
  
  485653810 KB total disk space.
  303291960 KB in 1390088 files.
  731768 KB in 279495 indexes.
  0 KB in bad sectors.
  2732942 KB in use by the system.
  65536 KB occupied by the log file.
  178897140 KB available on disk.
  
  4096 bytes in each allocation unit.
  121413452 total allocation units on disk.
  44724285 allocation units available on disk.
  PS C:\WINDOWS\system32> wmic recoveros set autoreboot = false
  Updating property(s) of '\\BLADE-STEALTH\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
  Property(s) update successful.
  PS C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7
  Updating property(s) of '\\BLADE-STEALTH\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
  Property(s) update successful.
  PS C:\WINDOWS\system32> bcdedit /enum {badmemory}
  Invalid command line switch: /encodedCommand
  Run "bcdedit /?" for command line assistance.
  The parameter is incorrect.
  PS C:\WINDOWS\system32> bcdedit /enum
  
  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
  
  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
  PS C:\WINDOWS\system32>
• No overclocking.

- - - Updated - - -

I'll post the results of the other tests as soon as I get them.

1) Some commands do not work in PS.
Please run the bcdedit command using administrative command prompt.

2) For startup and recovery system failure:
a) uncheck automatically restart
b) reboot to maintain settings

3) For this link there was no BIOS download seen
Please submit a support ticket for information about BIOS updates.
The current BIOS: Razer 1.50, 2018-02-26

1) Some commands do not work in PS.
Please run the [ bcdedit /enum {badmemory} ] command using administrative command prompt.
Or run [ bcdedit /enum all ] using PS

2) For startup and recovery system failure:
a) uncheck automatically restart
b) reboot to maintain settings

3) For this link there was no BIOS download seen:
Razer Support
Please submit a support ticket for information about BIOS updates.
The current BIOS: Razer 1.50, 2018-02-26

4) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive