PC Crash While Gaming

Question

Hello,

My PC has been crashing for the past few months, this seems to happen exclusively while gaming.

The crashes are random but somewhat consistent, whenever I am playing pubg or the finals they occur. It happened as well while playing dota2.

I have updated my BIOS, the crashes stopped for 2 days, but then came back.

I have tried debugging a minidump file but I cannot make sense of it.

Here is a paste of the debugging Bugcheck Analysis :

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101624-6734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`31800000 PsLoadedModuleList = 0xfffff805`324134b0
Debug session time: Wed Oct 16 00:48:27.306 2024 (UTC + 2:00)
System Uptime: 2 days 5:23:14.604
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols

Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!MiProbeAndLockPrepare+0x7c:
fffff805`31a6f49c 40386c2470      cmp     byte ptr [rsp+70h],bpl ss:0018:00000000`ab96ee30=??
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffc880eec5ee50
Arg3: 00000000ab96edc0
Arg4: fffff80531a6f49c

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3296

    Key  : Analysis.Elapsed.mSec
    Value: 4185

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 437

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5199

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 95

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x7f_8_nt!MiProbeAndLockPrepare

    Key  : Failure.Hash
    Value: {905315f4-9755-aa81-5ec4-71b372a8dab0}

    Key  : Stack.Pointer
    Value: Invalid

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc880eec5ee50

BUGCHECK_P3: ab96edc0

BUGCHECK_P4: fffff80531a6f49c

FILE_IN_CAB:  101624-6734-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff930fc3bb7040

BAD_STACK_POINTER:  00000000ab96edc0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
00000000`ab96edc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiProbeAndLockPrepare+0x7c

SYMBOL_NAME:  nt!MiProbeAndLockPrepare+7c

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.4317

STACK_COMMAND:  .process /r /p 0xffff930fb20fa040; .thread 0xffff930fc3bb7040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  7c

FAILURE_BUCKET_ID:  0x7f_8_nt!MiProbeAndLockPrepare

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {905315f4-9755-aa81-5ec4-71b372a8dab0}

Followup:     MachineOwner

Answer 1

Does it happen for all games?

Have you updated your drivers too?

Open start and search for feedback and open the Feedback Hub app and report this issue.