Code:
BugCheck F4, {3, fffffa8008d219a0, fffffa8008d21c80, fffff800039cc350}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
From the call stack, the process referenced a memory address, which caused the thread to have a page fault, although, the page fault couldn't handed and processed by the thread as a result of some kind of I/O error.
Code:
6: kd> !process fffffa8008d219a0 3
GetPointerFromAddress: unable to read from fffff800038fd000
PROCESS fffffa8008d219a0
SessionId: none Cid: 02c8 Peb: 7fffffd3000 ParentCid: 02b8
DirBase: 1d5596000 ObjectTable: fffff8a00ed363d0 HandleCount: <Data Not Accessible>
Image: csrss.exe
VadRoot fffffa800a9a4f80 Vads 319 Clone 0 Private 2743. Modified 25193. Locked 0.
DeviceMap fffff8a000008b30
Token fffff8a00ed2e060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 465848
QuotaPoolUsage[NonPagedPool] 52400
Working Set Sizes (now,min,max) (4468, 50, 345) (17872KB, 200KB, 1380KB)
PeakWorkingSetSize 9750
VirtualSize 176 Mb
PeakVirtualSize 335 Mb
PageFaultCount 197972983
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 3024
*** Error in reading nt!_ETHREAD @ fffffa8008d72b50
Code:
STACK_TEXT:
fffff880`095dee38 fffff800`03a53d22 : 00000000`000000f4 00000000`00000003 fffffa80`08d219a0 fffffa80`08d21c80 : nt!KeBugCheckEx
fffff880`095dee40 fffff800`03a0008b : ffffffff`ffffffff fffffa80`09420060 fffffa80`08d219a0 fffffa80`08d219a0 : nt!PspCatchCriticalBreak+0x92
fffff880`095dee80 fffff800`03980144 : ffffffff`ffffffff 00000000`00000001 fffffa80`08d219a0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`095deed0 fffff800`036c4e93 : fffffa80`08d219a0 fffff800`c0000006 fffffa80`09420060 00000000`02940c00 : nt!NtTerminateProcess+0xf4
fffff880`095def50 fffff800`036c1450 : fffff800`0371081f fffff880`095dfa38 fffff880`095df790 fffff880`095dfae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`095df0e8 fffff800`0371081f : fffff880`095dfa38 fffff880`095df790 fffff880`095dfae0 00000000`02941910 : nt!KiServiceLinkage
fffff880`095df0f0 fffff800`036c5282 : fffff880`095dfa38 00000000`00013600 fffff880`095dfae0 00000000`029413e8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`095df900 fffff800`036c3dfa : 00000000`00000000 000007fe`fd56d8c0 00000000`77888d01 00000000`00013600 : nt!KiExceptionDispatch+0xc2
fffff880`095dfae0 00000000`77789c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02941330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77789c12
Code:
6: kd> !error fffff800`c0000006
Error code: (NTSTATUS) 0xc0000006 (3221225478) - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.
Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.
Test each RAM stick and every motherboard DIMM slot available.
No code has to be inserted here. It is a RAM, a bad RAM.
But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.