BSOD while playing games

Question

BSOD while playing games

Anonymous

Hi i've a problem with my pc. Usually while gaming with games like Diablo,Baldur's Gate 3 my pc crashes and restart alone and i don't know why. I've found some minidumps of the crash that are happening. I tried to check what was inside the mindump, but i don't know how i can understand what is the problem that it's making my pc crash.

This is the last dump i had last saturday

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

   -- 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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

Loading Dump File [C:\Windows\Minidump\090223-12375-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 = 0xfffff801`5d000000 PsLoadedModuleList = 0xfffff801`5dc130e0
Debug session time: Sat Sep  2 01:52:01.323 2023 (UTC + 2:00)
System Uptime: 6 days 14:11:03.570
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000031`65aaa018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`5d432230 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffbc80`b740f280=000000000000001a
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: 00007ff3bfbddad0
Arg3: 000000000000000d
Arg4: ffffbc80b740f3a0

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1561

    Key  : Analysis.Elapsed.mSec
    Value: 7096

    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: 124

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key  : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: 7ff3bfbddad0

BUGCHECK_P3: d

BUGCHECK_P4: ffffbc80b740f3a0

FILE_IN_CAB:  090223-12375-01.dmp

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  bg3_dx11.exe

STACK_TEXT:  
ffffbc80`b740f278 fffff801`5d459fd8     : 00000000`0000001a 00000000`00061941 00007ff3`bfbddad0 00000000`0000000d : nt!KeBugCheckEx
ffffbc80`b740f280 fffff801`5d442e29     : ffffe282`fefa9080 00000152`89cd45f0 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x21a2f8
ffffbc80`b740f3a0 00007ff6`5767f6e9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x369
00000031`674df180 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`5767f6e9

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Followup:     MachineOwner
---------
Thanks in advance for any help or assistance with the matter.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

8 answers

Answer 1

Jonathan Deives 74,060 Independent Advisor

Yes, the cause of the problem is RAM related. Check if the problem occurs with just one stick.

0 comments

Answer 2

Anonymous

Ok thank's, i tried to do both things, the Windows Memory Diagnostic and i had 0 errors. WIth MemTest64 after 5 minutes i had black screen in my pc, can be related to the ram problem? I'm going to try now with only one stick of ram and the i'll try the other.

Thanks

0 comments

Answer 3

Jonathan Deives 74,060 Independent Advisor

Your minidump file indicates hardware memory (RAM) corruption.

In this case, use Windows Memory Diagnostic, see if any problems are found. Also do a test using MemTest64, if you have more than one stick, test one at a time.

0 comments

Answer 4

Anonymous

Hi Jonathan,

This is the link for the zip with my dumps

https://drive.google.com/file/d/1-lqbKr21VwKR_6QRSA3QCNIFa_t9p2fx/view?usp=drive_link

Thanks

0 comments

Answer 5

My name is Jonathan Deives. I'm an Independent Advisor and I'll be glad to help you today.

See if your computer is creating minidump files.

These files are in "C:\Windows\Minidump".

Copy any files you have to your desktop and store them in a ZIP file. Then upload the ZIP file to the cloud (OneDrive, Google Drive, Dropbox, etc...), choose to share it, and get the link.

Post the link to the ZIP file here.

Share via

BSOD while playing games

8 answers