You have a myriad of driver related faults apart from memory issue.
Along with memory module tweaking go for a clean install.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, The blue screens I'm getting are Kernel Security Check Failure, MEMORY_MANAGEMENT, and before I was getting Page fault in nonpage area, Attempt writes on read-only memory and system exception blue screens.
My PC is fairly new and all are built by me.
MSI RTX 3080 10G
4x G skill triden z 8GB 3600
ROG strix x-570 e motherboard
seasonic prime px 850w 80+ Platinumryzen 7 5800x
samsung 860 evo pro 2TB ssd SATA 3
Samsung 970 evo 500gb ssd NVME(boot drive)
samsung 970 evo plus 2TB ssd NVME
Please help me as I don't even know where to start to fix these blue screens as they happen randomly while I play my games or while I just watch youtube or scroll the web.
I am currently trying to remove 1 ram card at a time to see if it is a hardware issue. My pc is fairly new and I built it myself about 9 months ago.
while im using only 2 of the 8gb ram cards i updated the BIOS to the newest version for my motherboard and everything was okay for like 8 hours until i played some games and got another BSOD which the Stop code was MEMORY_CORRUPTION and another one after the next day which was DPC_WATCHDOG_VIOLATION. After updating my bios i have tried to replug my SATA cables from my ssd and change ports on the motherboard for it. Im not sure what else to do to fix it. After starting up a game and closing the game after then leaving the pc running i got another BSOD (CRITICAL_PROCESS_DIED)
**
Bugcheck Analysis
**
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff3012cf71970
Arg3: 0000080000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1515
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1525
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: 374
Key : Analysis.Init.Elapsed.mSec
Value: 8568
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Bugcheck.Code.DumpHeader
Value: 0x1a
Key : Bugcheck.Code.Register
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : MemoryManagement.PFN
Value: 80000000
FILE_IN_CAB: 103122-9234-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41792
BUGCHECK_P2: fffff3012cf71970
BUGCHECK_P3: 80000000000
BUGCHECK_P4: 0
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: APT2_WinStore.
STACK_TEXT:
ffff8705926c7008 fffff804
74ec5f2a : 000000000000001a 00000000
00041792 fffff3012cf71970 00000800
00000000 : nt!KeBugCheckEx
ffff8705926c7010 fffff804
74e38a66 : 0000000000000000 00000000
00000000 000000000000010f fffff301
2cf71970 : nt!MiDeleteVa+0x153a
ffff8705926c7110 fffff804
74e38b7b : fffff37900000000 ffffcc0b
6d60c700 ffff870500000000 ffff8705
926c7580 : nt!MiWalkPageTablesRecursively+0x776
ffff8705926c71b0 fffff804
74e38b7b : fffff379bcc04b38 ffffcc0b
6d60c700 ffff870500000001 ffff8705
926c7590 : nt!MiWalkPageTablesRecursively+0x88b
ffff8705926c7250 fffff804
74e38b7b : fffff379bcc04000 ffffcc0b
6d60c700 ffff870500000002 ffff8705
926c75a0 : nt!MiWalkPageTablesRecursively+0x88b
ffff8705926c72f0 fffff804
74e0b7db : 0000000000000000 ffffcc0b
6d60c700 ffff870500000003 ffff8705
926c75b0 : nt!MiWalkPageTablesRecursively+0x88b
ffff8705926c7390 fffff804
74ec47c1 : ffff8705926c7530 ffffcc0b
00000000 0000000000000002 ffffcc0b
00000000 : nt!MiWalkPageTables+0x36b
ffff8705926c7490 fffff804
74eceac0 : 0000000000000001 ffff8705
00000000 ffffcc0b6d60c550 ffffcc0b
52a3f080 : nt!MiDeletePagablePteRange+0x4f1
ffff8705926c77a0 fffff804
74f26e17 : 00000000259ee5ed 00000000
00000000 ffffcc0b00000000 fffff804
00000000 : nt!MiDeleteVad+0x360
ffff8705926c78b0 fffff804
7528aaac : ffff870500000000 00000000
00000000 ffff8705926c7a10 00000259
edde0000 : nt!MiFreeVadRange+0xa3
ffff8705926c7910 fffff804
7528a585 : 000000734ef0f3d8 00000000
00000000 0000000000000000 00000000
00000000 : nt!MmFreeVirtualMemory+0x4ec
ffff8705926c7a60 fffff804
7500aab8 : ffffcc0b52a3f080 ffffcc0b
52a3f080 00000257f43bb360 00000000
00000020 : nt!NtFreeVirtualMemory+0x95
ffff8705926c7ac0 00007ffa
01d4d484 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiSystemServiceCopyEnd+0x28
000000734ef0f158 00000000
00000000 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 0x00007ffa`01d4d484
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
**
Bugcheck Analysis
**
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8002f4fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
Either you specified an unqualified symbol, or your debugger
doesn't have full symbol information. Unqualified symbol
resolution is turned off by default. Please either specify a
fully qualified symbol module!symbolname, or enable resolution
of unqualified symbols by typing ".symopt- 100". Note that
enabling unqualified symbol resolution with network symbol
server shares in the symbol path may cause the debugger to
appear to hang for long periods of time when an incorrect
symbol name is typed or the network symbol server is down.
For some commands to work properly, your symbol path
must point to .pdb files that have full type information.
Certain .pdb files (such as the public OS symbols) do not
contain the required information. Contact the group that
provided you with these symbols if you need this command to
work.
Type referenced: TickPeriods
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1983
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1975
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: 374
Key : Analysis.Init.Elapsed.mSec
Value: 10000
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 110122-9203-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8002f4fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: opera.exe
STACK_TEXT:
fffff80034ca3e18 fffff800
2ec597fe : 0000000000000133 00000000
00000000 0000000000000501 00000000
00000500 : nt!KeBugCheckEx
fffff80034ca3e20 fffff800
2ead2973 : 0000c4063abfa752 fffff800
2c40b180 0000000000000000 fffff800
2c40b180 : nt!KeAccumulateTicks+0x18462e
fffff80034ca3e80 fffff800
2ead245a : fffff8002f4f38c0 fffff800
34c9b9d0 fffff80033ae1600 00000000
00005001 : nt!KeClockInterruptNotify+0x453
fffff80034ca3f30 fffff800
2ea08a45 : fffff8002f4f38c0 00000000
00000000 0000000000000000 fffff14a
f0934438 : nt!HalpTimerClockIpiRoutine+0x1a
fffff80034ca3f60 fffff800
2ebfab9a : fffff80034c9b9d0 fffff800
2f4f38c0 00000000c1d00000 00000000
00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff80034ca3fb0 fffff800
2ebfb107 : 0000000000000000 00000000
00000000 0000000000000099 00000000
00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff80034c9b950 fffff800
2eaa9a9c : 0000000000000000 00000000
00000000 fffff80034c9bb30 fffff800
509cd76c : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff80034c9bae0 fffff800
2eaa9a68 : ffffe68f91bccd20 fffff800
2c40b180 000000004d52564e 00000000
00000cbe : nt!KxWaitForSpinLockAndAcquire+0x2c
fffff80034c9bb10 fffff800
50b71ace : fffff80034c9bbf8 00000000
00000000 fffff80034c9bc60 00000000
00000050 : nt!KeAcquireSpinLockRaiseToDpc+0x88
fffff80034c9bb40 fffff800
34c9bbf8 : 0000000000000000 fffff800
34c9bc60 0000000000000050 ffffe68f
91bc0000 : nvlddmkm+0x8f1ace
fffff80034c9bb48 00000000
00000000 : fffff80034c9bc60 00000000
00000050 ffffe68f91bc0000 fffff800
50b9c6e6 : 0xfffff800`34c9bbf8
SYMBOL_NAME: nvlddmkm+8f1ace
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 8f1ace
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
---------
**
Bugcheck Analysis
**
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff908a98539080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000, The process object that initiated the termination.
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2406
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22939
Key : Analysis.IO.Other.Mb
Value: 1
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 3
Key : Analysis.Init.CPU.mSec
Value: 405
Key : Analysis.Init.Elapsed.mSec
Value: 8312
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.DumpHeader
Value: 0xef
Key : Bugcheck.Code.Register
Value: 0xef
Key : CriticalProcessDied.ExceptionCode
Value: 98573080
Key : CriticalProcessDied.ImageName
Value: coremessaging.dll
Key : CriticalProcessDied.ImageOffset
Value: 33989
Key : CriticalProcessDied.ImageSize
Value: f2000
Key : CriticalProcessDied.ImageTimestamp
Value: d3dfbbe6
Key : CriticalProcessDied.Process
Value: svchost.exe
Key : CriticalProcessDied.Symbol
Value: coremessaging.dll!Map__uint__uint::Insert
Key : CriticalProcessDied.WERReportId
Value: bf443045-dd63-4e69-96e1-5eaf3fe19d12
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 110122-9109-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: ef
BUGCHECK_P1: ffff908a98539080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: svchost.exe
CRITICAL_PROCESS: svchost.exe
ERROR_CODE: (NTSTATUS) 0x98573080 - <Unable to get error code text>
CRITICAL_PROCESS_REPORTGUID: {bf443045-dd63-4e69-96e1-5eaf3fe19d12}
IMAGE_NAME: coremessaging.dll
MODULE_NAME: coremessaging
FAULTING_MODULE: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffff385512d78f8 fffff800
317080d2 : 00000000000000ef ffff908a
98539080 0000000000000000 00000000
00000000 : nt!KeBugCheckEx
fffff385512d7900 fffff800
315f4e13 : 0000000000000000 fffff800
310062c5 0000000000000002 fffff800
310061ef : nt!PspCatchCriticalBreak+0x10e
fffff385512d79a0 fffff800
313d6290 : ffff908a00000000 00000000
00000000 ffff908a98539080 ffff908a
985394b8 : nt!PspTerminateAllThreads+0x1abb27
fffff385512d7a10 fffff800
313d608c : ffff908a98539080 00000000
00000000 0000000000000000 fffff800
3148e2aa : nt!PspTerminateProcess+0xe0
fffff385512d7a50 fffff800
3120aab8 : ffff908a98539080 ffff908a
98573080 fffff385512d7b40 ffff908a
98539080 : nt!NtTerminateProcess+0x9c
fffff385512d7ac0 00007ff8
a462d644 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiSystemServiceCopyEnd+0x28
000000826d67fb28 00000000
00000000 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 0x00007ff8`a462d644
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_98573080_coremessaging.dll!Map__uint__uint::Insert_IMAGE_coremessaging.dll
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f60a9b6e-4b0f-4a5d-afe7-25f1e1586cd6}
Followup: MachineOwner
---------
You have a myriad of driver related faults apart from memory issue.
Along with memory module tweaking go for a clean install.