Laptop crashes Victus 15 Gaming

[Quincy74]

Let's take Dota 2 as an example.
I launch the game, and it crashes within 5 seconds.
Okay, I tried installing different driver versions for the graphics card, but it didn't help. Different NVidia settings also didn't help.
I stress-tested the laptop, and everything worked fine, including the processor.
I changed the thermal interface, and the SSD, but still crashed.
Then a friend lowered the power supply from 100 to 95, and the load decreased. I was able to launch the game, lower the settings to minimum, and set the frame rate to 100 fps. I can play, but I keep crashing. I launch the game during some fights, and it crashes immediately. This started in the spring of 2025. I've been trying to fix it myself, but I can't seem to figure it out. Please help. My guess is probably something wrong with the processor and it's just overheating.

[Venom21]

Use msi afterburner and check GPU/CPU temperatures while playing and let me know

[Quincy74]

on the 40-50 degree menu in the game, when turned off, jumps are sometimes visible against the background of Spotify and MSI 70-80

[Quincy74]

This is the CPU, I'm fine with the GPU.

[Quincy74]

I also ran tests like OCCT, Furmark, everything is stable

[Venom21]

Check if same happens in other games. Also In Steam, right-click Dota 2 > Properties > Installed Files > Verify Integrity of Game Files

[Quincy74]

Yes, I checked it in CS 2. When I go into the game, it crashes in the menu. I checked the integrity.

[Venom21]

Try finding error in Windows Event Viewer and let me which one it is

[Quincy74]

Error container 1364706323476752992, type 5
Event name: AppHangB1
Response: No data
CAB ID: 0

Problem symptoms:
P1: dota2.exe
P2: 0.0.0.0
P3: 693fcc91
P4: 8dd7
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Nested files:
\\?\C:\Users\deadp\AppData\Local\Temp\WER.3d7d633f-a235-46cf-85bb-9d732b951e53.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.95a79354-14a5-436c-949d-dc3049c57bfa .tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_dota2.exe_e6c411b6 7641aac79e3e740615c28c42a6bde6e_f58ea4e9_cab_629a3e50-1825-46db-82a4-539fcfff8c5 3\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20260312_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e1bacd0e-a73b-45b2-b9c6-0579265b7c81.tmp.etl
\\?\C:\Pro gramData\Microsoft\Windows\WER\ReportQueue\Critical_dota2.exe_e6c411b67641aac79e3e740615c28c42 a6bde6e_f58ea4e9_cab_629a3e50-1825-46db-82a4-539fcfff8c53\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.beb89286-0d0d-48f1-ac59-2e28ed87d823.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.98f8b275-9505-4cbf-bd89-b20a249744b9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43c2e6b7-4792-44fd-b2cb-955212508633.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\W ER\Temp\WER.e808e520-af3e-4a13-9ee7-9438aa420c1b.tmp.xml
\\?\C:\Users\deadp\AppData\Local\Temp\WER.f7691e5c-2b26-4aaa-9d32-9da1b3f059ee.tmp.xml
\\?\C:\ProgramData\Microsoft \Windows\WER\ReportQueue\Critical_dota2.exe_e6c411b67641aac79e3e740615c28c42a6bde6e_f58ea4e9_cab_629a3e50-1825-46db-82a4-539fcfff8c53\minidump.mdmp
WERGenerationLog.txt

These files can be found here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_dota2.exe_e6c41 1b67641aac79e3e740615c28c42a6bde6e_f58ea4e9_629a3e50-1825-46db-82a4-539fcfff8c53

Analysis Symbol:
Retry Solving: 0
Report ID: e78f2c19-d3d4-4e9c-acb2-8b7babcb4b31
Status Report: 268435456
Hashed Container: 725ee1553e39c48252f0692bb18faa60
CAB GUID: 0

[Venom21]

Is you laptop under warrenty? In event viewer,

• Left panel: Windows Logs → Application
• Right-click list → Filter Current Log
• Check Error + Critical → OK
• Find entry at crash time with Source: Application Error Double-click → General tab shows Faulting application name (game.exe) + Faulting module name (e.g., d3d11.dll, nvlddmkm.sys)

Also check,

• Windows Logs → System
• Filter to Error + Critical
• Crash-time entries: Source like Display, Kernel-Power (41), BugCheck (1001)