Hello everyone. I seem to get random BSODs playing Dead Space (2023). They can happen after any length of playtime. Nothing in particular during gameplay seems to trigger them. I have made no recent software or hardware changes besides installing Dead Space. Any help would be greatly appreciated! My specs: Windows 10 Enterprise (Version 10.0.19044 Build 19044) Intel i5-10600KF CPU @ 4.10GHz, 5001 Mhz MPG Z490 GAMING PLUS (MS-7C75) NZXT Kraken X52 CORSAIR Dominator Platinum RGB 16GB (2x8GB) DDR4 3200 MSI RTX 3080 GAMING X TRIO 10GB SAMSUNG 970 EVO PLUS 1TB What I have tried so far: Updating GPU drivers Updating Windows Reinstalls of game and launcher Here is the minidump file: https://www.mediafire.com/file/jov1or8x3196ptn/013123-8765-01.dmp/file ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffffff8b4c015a, memory referenced. Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff8041862813b, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Type Value: Read Key : Analysis.CPU.mSec Value: 1624 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1633 Key : Analysis.IO.Other.Mb Value: 17 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 24 Key : Analysis.Init.CPU.mSec Value: 546 Key : Analysis.Init.Elapsed.mSec Value: 25831 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Bugcheck.Code.DumpHeader Value: 0x50 Key : Bugcheck.Code.Register Value: 0x50 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 013123-8765-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 50 BUGCHECK_P1: ffffffff8b4c015a BUGCHECK_P2: 0 BUGCHECK_P3: fffff8041862813b BUGCHECK_P4: 2 READ_ADDRESS: fffff80418cfb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffffff8b4c015a MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe TRAP_FRAME: ffffc00d8cf37150 -- (.trap 0xffffc00d8cf37150) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000800 rbx=0000000000000000 rcx=00000000000000fa rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8041862813b rsp=ffffc00d8cf372e0 rbp=ffffc00d8cf37400 r8=00000000ffffffff r9=7fff8506c3938cc0 r10=7ffffffffffffffc r11=ffffc00d8cf372c0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!ObpCreateHandle+0xfdb: fffff804`1862813b 48837f6000 cmp qword ptr [rdi+60h],0 ds:00000000`00000060=???????????????? Resetting default scope STACK_TEXT: ffffc00d`8cf36ea8 fffff804`18436e57 : 00000000`00000050 ffffffff`8b4c015a 00000000`00000000 ffffc00d`8cf37150 : nt!KeBugCheckEx ffffc00d`8cf36eb0 fffff804`18242250 : ffff8506`bc400340 00000000`00000000 ffffc00d`8cf371d0 00000000`00000000 : nt!MiSystemFault+0x1d6bd7 ffffc00d`8cf36fb0 fffff804`18409cd8 : 00000000`00000000 ffffc00d`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400 ffffc00d`8cf37150 fffff804`1862813b : 00000000`00000001 ffffc00d`00000000 ffff8506`c56fafa0 ffffc00d`8cf375b0 : nt!KiPageFault+0x358 ffffc00d`8cf372e0 fffff804`1863e8a8 : 00000000`00000000 ffffc00d`8cf375f0 ffff950d`3ef19020 00000000`00000000 : nt!ObpCreateHandle+0xfdb ffffc00d`8cf374f0 fffff804`18630d86 : ffff950d`2f803c90 ffff950d`24c3d350 ffff950d`24c3d350 ffff950d`2f803c90 : nt!ObInsertObjectEx+0x488 ffffc00d`8cf37780 fffff804`186310be : ffff8506`e1245b80 ffff950d`24c3d350 ffffc00d`8cf37928 00000000`000000a0 : nt!EtwpAddUmRegEntry+0x176 ffffc00d`8cf37830 fffff804`18646db4 : ffff8506`e1245b80 00000000`00000000 00000000`00000000 00000000`000000a0 : nt!EtwpRegisterUMGuid+0x19e ffffc00d`8cf378f0 fffff804`1840d9f5 : 00000000`0000000f 00000000`00000000 00000000`000000a0 000000c9`ee37dbf8 : nt!NtTraceControl+0x314 ffffc00d`8cf37990 00007ffa`e9cf0914 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 000000c9`ee37dbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`e9cf0914 SYMBOL_NAME: nt!ObpCreateHandle+fdb MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2486 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: fdb FAILURE_BUCKET_ID: AV_R_(null)_nt!ObpCreateHandle OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {48c202f8-a564-ab26-552e-c82ebfe1b64e} Followup: MachineOwner
its unstable system memory, check the V. numbers on your ddr sticks, then match them to this table 3.20 Micron 4Gbit Rev.A Presumed 3.21 Micron 4Gbit Rev.B Confirmed 3.22 Micron 4Gbit Rev.E* Speculated 3.22 Micron 4Gbit Rev.F* Confirmed 3.31 Micron 8Gbit Rev.B Confirmed 3.33 Micron 8Gbit Rev.D Presumed 3.34 Micron 8Gbit Rev.E Speculated 4.14 Samsung 4Gbit D-die (4x16) Confirmed 4.23 Samsung 4Gbit D-die Confirmed 4.24 Samsung 4Gbit E-die Confirmed 4.31 Samsung 8Gbit B-die Confirmed 4.49 Samsung 16Gbit M-die Speculated 4.40 Samsung 16Gbit A-die Speculated 5.29 Hynix 4Gbit MFR Confirmed 5.20 Hynix 4Gbit AFR Confirmed 5.21 Hynix 4Gbit BJR Speculated 5.39 Hynix 8Gbit MFR Confirmed 5.30 Hynix 8Gbit AFR Presumed 5.31 Hynix 8Gbit "BFR"??? Speculated 5.32 Hynix 8Gbit CJR Presumed 8.20** Nanya 4Gbit Rev.A Speculated 8.30** Nanya 8Gbit Rev.A Speculated If your ram is Nanya, get rid of it.
application 0xc7's, random startup bsods that may be fine on the next on. my dominator nanya's weren't throwing kernel bsods, but didn't pass tm5, and large 7z files would throw crc errors on extraction. Ops crash was provoked by an svhost doing something with the ntkrnlmp(NT Kernel Multiprocessor) driver.
