BSOD! Constant Crashes

Question

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: fffff38000801000 Arg3: 0000140000000000 Arg4: 0000000000000000

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1890

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3722

    Key  : Analysis.Init.CPU.mSec
    Value: 343

    Key  : Analysis.Init.Elapsed.mSec
    Value: 12345

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 78

    Key  : MemoryManagement.PFN
    Value: 140000000

FILE_IN_CAB:  122221-10265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffff38000801000

BUGCHECK_P3: 140000000000

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

STACK_TEXT:  
ffff880a`cc6c3308 fffff801`08cbff7f     : 00000000`0000001a 00000000`00041792 fffff380`00801000 00001400`00000000 : nt!KeBugCheckEx
ffff880a`cc6c3310 fffff801`08b15daf     : ffffd382`b4cf5700 00000000`00000000 fffff3f9`00000002 00000001`00200000 : nt!MiDeleteVa+0x1a9e8f
ffff880a`cc6c3410 fffff801`08b19112     : ffffd382`b4bca6c0 fffff801`08b18f51 ffff880a`cc6c37b8 00000000`00000000 : nt!MiDeletePagablePteRange+0x36f
ffff880a`cc6c3720 fffff801`08f75ab9     : 00000000`00000000 00000001`00200000 ffffd382`b4cf5080 ffffd382`b4bca6c0 : nt!MiDeleteVirtualAddresses+0x52
ffff880a`cc6c3770 fffff801`08f89a0a     : ffffd382`b4cf5080 ffffd382`b4bca6c0 ffffd382`00000000 00000000`00000000 : nt!MiDeleteVad+0x199
ffff880a`cc6c3830 fffff801`08f61cf9     : ffffd382`b49597c0 ffffd382`b49597c0 ffffd382`b4c83080 ffffd382`b4cf5080 : nt!MiCleanVad+0x42
ffff880a`cc6c3860 fffff801`08f95651     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffd382`b4cf5080 : nt!MmCleanProcessAddressSpace+0x10d
ffff880a`cc6c38e0 fffff801`08f8cdeb     : ffffd382`b4cf5080 ffffe383`e7bbe490 ffffd382`b4cf5080 00000000`00000000 : nt!PspRundownSingleProcess+0x135
ffff880a`cc6c3970 fffff801`08f99ec1     : 00000000`00000000 ffffd382`b4cf5001 ffffd382`b4c83080 00000001`0026b000 : nt!PspExitThread+0x613
ffff880a`cc6c3a60 fffff801`08c27f78     : ffffd382`000034c4 ffffd382`b4c83080 ffffd382`b4cf5080 ffffd382`b4cf5080 : nt!NtTerminateProcess+0xf1
ffff880a`cc6c3ae0 00007ffb`8ed238e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000001`0007f738 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8ed238e4

SYMBOL_NAME:  nt!MiDeleteVa+1a9e8f

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22000.376

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1a9e8f

FAILURE_BUCKET_ID:  0x1a_41792_nt!MiDeleteVa

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ad6dfca3-101b-35a8-d6e1-12de9ecbc1f5}

Followup:     MachineOwner
---------

Dumps: https://1drv.ms/u/s!AnT6RSWDFxi0glaTIf7lVjARfedN?e=K64dKK

Answer 1

Hi Isaac,

I am Dave, I will help you with this.

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

1

The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

2

If no RAM errors are found, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

https://answers.microsoft.com/en-us/windows/for...