Your crash dumps are not showing any finite probable cause.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If memtest comes to be free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88005829750, 1, fffff800030cec58, 1}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PfpPrefetchSharedStart+d8 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88005829750, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800030cec58, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f11100
GetUlongFromAddress: unable to read from fffff80002f111c0
fffff88005829750 Nonpaged pool
FAULTING_IP:
nt!PfpPrefetchSharedStart+d8
fffff800`030cec58 48897808 mov qword ptr [rax+8],rdi
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: wmpnscfg.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88002ca7550 -- (.trap 0xfffff88002ca7550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005829748 rbx=0000000000000000 rcx=fffff80002e7b990
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030cec58 rsp=fffff88002ca76e0 rbp=fffff8a00ccf7000
r8=fffffa800cf93b50 r9=0000000000000000 r10=fffff88003365960
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!PfpPrefetchSharedStart+0xd8:
fffff800`030cec58 48897808 mov qword ptr [rax+8],rdi ds:fffff880`05829750=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c72ac8 to fffff80002cd9b80
STACK_TEXT:
fffff880`02ca73e8 fffff800`02c72ac8 : 00000000`00000050 fffff880`05829750 00000000`00000001 fffff880`02ca7550 : nt!KeBugCheckEx
fffff880`02ca73f0 fffff800`02cd7cae : 00000000`00000001 fffff880`05829750 fffffa80`00000200 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x45252
fffff880`02ca7550 fffff800`030cec58 : fffffa80`07a12de0 00000000`00000001 00000002`00000000 00000000`00060001 : nt!KiPageFault+0x16e
fffff880`02ca76e0 fffff800`031394b4 : fffffa80`068e7300 00000035`9310d9cc 00000000`00000005 fffffa80`0ca7e060 : nt!PfpPrefetchSharedStart+0xd8
fffff880`02ca7710 fffff800`03139a0f : 00000035`9310d9cc fffffa80`0ca7e060 fffff8a0`0ccf7000 00000000`c00000ce : nt!PfSnPrefetchScenario+0x54
fffff880`02ca7980 fffff800`0303970f : 00000000`00000000 00000000`fc0d39bf fffffa80`0c3979b0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`02ca7a50 fffff800`02fc901c : fffffa80`0cf93b50 fffffa80`0c3979b0 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x4c0c0
fffff880`02ca7a80 fffff800`02cca9f5 : fffff880`03364180 00000000`00000000 fffff800`02fc8ed4 fffffa80`0cf93b50 : nt!PspUserThreadStartup+0x148
fffff880`02ca7ae0 fffff800`02cca977 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`02ca7c20 00000000`77b2c520 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0018fe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b2c520
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PfpPrefetchSharedStart+d8
fffff800`030cec58 48897808 mov qword ptr [rax+8],rdi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!PfpPrefetchSharedStart+d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd
FAILURE_BUCKET_ID: X64_0x50_nt!PfpPrefetchSharedStart+d8
BUCKET_ID: X64_0x50_nt!PfpPrefetchSharedStart+d8
Followup: MachineOwner
---------
RST in SCSI mode
Quote