BSODs while gaming ?
BSODs while gaming ?
OS Microsoft Windows 11 Home
Motherboard Gigabyte B760 DS3H AX
CPU Intel® Core™ i5-14400F, 2500 Mhz, 10 core, 16 processori logici
RAM Patriot Memory DDR5-5600 Series 2x16
GPU AMD Sapphire Radeon RX 9060 XT
SSD KIOXIA-EXCERIA G2 SSD nvme 1tb
Recently, I've experienced several BSODs in some games, some of which use kernel-level anti-cheat, and others that are just regular games like
Monster Hunter Wilds
or
Baldur's Gate 3
, which don't even use kernel-level anti-cheat.
The BSODs have consistently been memory-related, and the crash dumps indicate that a corrupted bit was found in memory. These crashes usually occur about half an hour into gameplay, or right after closing the game.
The attached text contains the latest BSOD with the error
FAULTY_HARDWARE_CORRUPTED_PAGE
.
I’d like to point out that I’ve already run tests to check for Windows corruption and performed
MemTest86
with 4 passes.
I am pretty much desperate, can you understand the problem please?
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This BugCheck indicates that a single bit error was found in this page. This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000753, physical page number
Arg3: 00000161e8428b30, zero
Arg4: ffff9800487e5000, zero
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1578
Key : Analysis.Elapsed.mSec
Value: 9803
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 781
Key : Analysis.Init.Elapsed.mSec
Value: 28290
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001
Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2505.1.2
Key : BlackBox.SmDecompressionFailure.CompressedSize
Value: 0x753
Key : BlackBox.SmDecompressionFailure.CompressionFormat
Value: 0x0
Key : BlackBox.SmDecompressionFailure.SourceDataHash
Value: 0xc66e9518
Key : BlackBox.SmDecompressionFailure.SourceDataOffset
Value: 0x8b30
Key : BlackBox.SmDecompressionFailure.SourcePFN1
Value: 0x1c2428
Key : BlackBox.SmDecompressionFailure.SourcePFN2
Value: 0x1c2429
Key : BlackBox.SmDecompressionFailure.TargetPFN
Value: 0x706551
Key : Bugcheck.Code.LegacyAPI
Value: 0x12b
Key : Bugcheck.Code.TargetModel
Value: 0x12b
Key : Dump.Attributes.AsUlong
Value: 0x21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
Key : Failure.Hash
Value: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe
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: 0x3f7
BUGCHECK_CODE: 12b
BUGCHECK_P1: ffffffffc00002c4
BUGCHECK_P2: 753
BUGCHECK_P3: 161e8428b30
BUGCHECK_P4: ffff9800487e5000
FILE_IN_CAB: 081525-18437-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffac8e60a84080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MemCompression
STACK_TEXT:
ffff8381`1e64f168 fffff807`d7805035 : 00000000`0000012b ffffffff`c00002c4 00000000`00000753 00000161`e8428b30 : nt!KeBugCheckEx
ffff8381`1e64f170 fffff807`d78c9f53 : 00000000`00000200 ffffac8e`45ada020 00000000`c00004e0 ffffac8e`1b8a4050 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x135
ffff8381`1e64f1c0 fffff807`d741f4b9 : ffffac8e`00002000 00000000`00000001 ffffac8e`33dfd7d0 ffffac8e`45ada000 : nt!ST_STORE<SM_TRAITS>::StDmFinishPageRetrieve+0x4aa563
ffff8381`1e64f220 fffff807`d741f19a : 00000000`00000001 00000000`00000001 ffffac8e`33dfd7d0 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x109
ffff8381`1e64f290 fffff807`d74209b1 : 00000000`00000000 ffffac8e`00000002 fffff807`ffffffff 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x13a
ffff8381`1e64f350 fffff807`d742083b : ffffac8e`1b8a4000 ffffac8e`33dfd7d0 ffffac8e`45ada000 ffffac8e`33dfd7ff : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0xed
ffff8381`1e64f3f0 fffff807`d74eed27 : ffffac8e`60a840fd ffffac8e`33dfd7d0 00000000`00000000 00000000`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x2b
ffff8381`1e64f420 fffff807`d74eec5d : fffff807`d7420810 ffff8381`1e64f500 00000000`00000002 ffffac8d`e76e96b8 : nt!KeExpandKernelStackAndCalloutInternal+0xb7
ffff8381`1e64f490 fffff807`d754e8ff : 00000000`00000002 00000000`00000000 00000000`00000000 ffffac8e`5139f7f8 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff8381`1e64f4d0 fffff807`d74df560 : 00000000`00000040 fffff807`d743cb12 ffffac8e`1b8a4000 ffffac8e`5139f700 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcf
ffff8381`1e64f5a0 fffff807`d74dd769 : 00000000`00000000 ffff8381`1e64f679 00000000`00000000 00000000`40000010 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x198
ffff8381`1e64f5f0 fffff807`d74dbd20 : 00000000`00000000 00000000`00000000 ffff8381`1e64f679 ffffac8e`33dfd7d0 : nt!SmWorkItemQueue+0x9
ffff8381`1e64f620 fffff807`d741d3fa : ffffac8e`5139f700 00000000`0000000c ffffac8d`00000000 ffffac8e`33dfd7d0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0x1f0
ffff8381`1e64f6e0 fffff807`d741ce7e : 00000000`00000002 ffff8381`1e64f7b0 ffffac8e`00000002 ffffac8e`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x132
ffff8381`1e64f760 fffff807`d741bf59 : 00000000`001a5b54 00000000`00000002 00000000`00000000 00000000`00000001 : nt!MiIssueHardFaultIo+0x9e
ffff8381`1e64f7b0 fffff807`d74b0152 : ffff8000`00000000 000002c1`6da3e01e 00000000`c0033333 00000000`00000001 : nt!MiIssueHardFault+0x24d
ffff8381`1e64f8b0 fffff807`d78b37cb : 000002c1`6da231b5 000002c1`6da231b5 000002c1`6a000000 00000000`0000004e : nt!MmAccessFault+0x402
ffff8381`1e64fa20 00007ffb`1150ea1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
000000da`83cf9100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`1150ea1c
SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+135
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.26100.4946
STACK_COMMAND: .process /r /p 0xffffac8e2503a080; .thread 0xffffac8e60a84080 ; kb
BUCKET_ID_FUNC_OFFSET: 135
FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
Followup: MachineOwner
Welcome to the forums, newcomer!
I've encountered multiple BSODs. Please share your .dmp files so we can review them. The host mentioned files stored on a service similar to DropBox, and direct a link in this thread.
OS Microsoft Windows 11 Home
Motherboard Gigabyte B760 DS3H AX
CPU Intel® Core™ i5-14400F, 2500 Mhz, 10 core, 16 processori logici
RAM Patriot Memory DDR5-5600 Series 2x16
GPU AMD Sapphire Radeon RX 9060 XT
SSD KIOXIA-EXCERIA G2 SSD nvme 1tb
You didn’t specify the PSU make and model. If the PSU has been in use for some time, please note its age. BIOS version for your motherboard?
I’ve had several BSODs in certain games—some involving kernel-level anti-cheat, while others are standard titles like
Monster Hunter Wilds
or
Baldur's Gate 3
that don’t require such protection.
Where did you obtain the installer for the OS and games? Which version of Windows 11 are you currently running?
Hello, I'm currently outside my home, so I can't provide full details. For the PSU, I completed some tests and everything looks good; I'll add the information today. On other matters, I purchased a new PC two months ago, so it's brand new. Concerning the BIOS, I'm up to date with the latest versions since I already suspected this might be the issue (I'll update later). Regarding the OS source, I can't share details because I bought the computer from a technician who provided an unactivated Windows copy that I activated myself. For the Windows version, I was aware that recent builds caused problems with games using EAC or kernel-level anti-heat, but a patch was released and installed. Still, I'm unable to fill in these specifics as I'm currently outside, though I'm using the latest Windows. To try resolving the issue, I considered using an insider version, thinking it might be an OS update. Thanks for your response. This is the minidump file: https://drive.google.com/file/d/18DFrAYT...p=drivesdk
Restore all bios configurations to their original state and turn off any XMP functionality.
The dump shows a clear memory read error at a specific physical address, confirming a RAM issue. I observe that your RAM is overclocked to 5600MHz, which may not match the certification for that speed. It’s best to turn off the XMP profile so it operates at its original (SPD) rate. For DDR5 RAM, this usually means running at 4800MHz. If it remains stable at that speed, you might be overclocking excessively. Please remember that your CPU specifications state Intel only ensures stability with RAM up to 4800MHz for the i5-14400F. While some i5-14400F chips can handle higher speeds, there’s no certainty about performance.
Hello, I checked the BIOS and noticed XMP wasn't turned on. I set the RAM speed to 4800MHz but it still crashed.
It might relate to stability concerns in raptor lake. This issue was more frequent on i7/i9 processors, leading to crashes under heavy use and resulting in a recall. It's possible i5s could also be impacted.