BSOD at least twice a month - uncertain cause

I am experiencing BSODs at least twice a month. I started archiving the minidump files in a Dropbox folder (link shared at the end).

I do not know what is causing these BSODs

Things I have tried
1) running memtest numerous times (screenshots in dropbox link) - no errors on any runs
2) reinstalling Windows 10 twice - still experiencing problems

I cannot pinpoint what incites a BSOD and half the time the BSOD occurs when the computer is idle.

Also, I would like to know why my Windows minidump folder automatically deletes the minidumps (I do not use CCleaner)

Please see the attached zip and the dropbox link (for my latest 4 BSOD minidumps + snapshots of passed memtest tests)

Dropbox: Dropbox - BSOD - Simplify your life

Hello LeoBloom,

Old mini-dump files seem to be automatically deleted by the system clean-up actions that are now built into the W10 OS. I have found that if they are automatically deleted after about 2 days but I have not yet found the scheduled event that does this so I have not found a way to disable it.

The recent mini-dumps that I have been through do point to memory corruption. I would repeat the test using our recommended Memtest86+ tool.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.

only 1 dump file. were there other BSODs?

When did the crashes start?

I had another BSOD earlier today - the error read MEMORY_MANAGEMENT and it happened when I was watching a YouTube video (beta logger attached + see Dropbox Link for newest minidump)

I also did another MemTest run (this time with Passmark version) x10 tests with no errors (a few days prior to today's BSOD)

Dropbox - BSOD - Simplify your life

This latest crash dump continues to show there are memory problems. The analysis of the crash shows you have had a one bit flip.

Code:

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: ffffcb8018d3f188
Arg3: 0000000010000000
Arg4: 0000000000000000


FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT


The PTE (page table entry) shows errors:

3: kd> dt nt!_MMPFN ffffcb8018d3f188
   +0x000 ListEntry        : _LIST_ENTRY
   +0x000 TreeNode         : _RTL_BALANCED_NODE
   +0x000 u1               : <unnamed-tag>
   +0x008 PteAddress       : ???? 
   +0x008 VolatilePteAddress : ???? 
   +0x008 PteLong          : ??
   +0x010 OriginalPte      : _MMPTE
   +0x018 u2               : _MIPFNBLINK
   +0x020 u3               : <unnamed-tag>
   +0x024 NodeBlinkLow     : ??
   +0x026 Unused           : ??
   +0x026 Unused2          : ??
   +0x027 ViewCount        : ??
   +0x027 NodeFlinkLow     : ??
   +0x028 u4               : <unnamed-tag>
Memory read error ffffcb8018d3f1af

Arg 3 and 4 show the bit flip when data was passed between a low and high address.
It would be worth checking that all your cables are connected properly to the hard disks in case there are any errors being introduced while writing/reading to virtual memory but it is generally thought this is a sign of faulty memory.

The only way of testing for sure is to remove two sticks at a time and retest, keep doing this with different combinations of 2 sticks until you find the one that causes the error.

Got it - does it specifically have to be combinations of 2 RAM sticks at a time or is it better to do 1 at a time?

Would something like 10 passes w/ 1 stick per slot (alternating by putting in a new stick per new slot for a total of 4 tests) be sufficient?

I suggested 2 sticks at a time to keep the dual memory configuration, by testing I meant to just use the system as normal and wait to see if it crashes. I realise this could take several weeks of testing as the bsod is infrequent.

1) Please uninstall iObit with the applicable uninstall tool:
http://forums.iobit.com/forum/advanc...y-remove-iobit

2) For startup and recovery system failure:
a) Change kernel to automatic memory dump
b) Uncheck automatic restart
c) reboot to keep settings

With automatic restart checked it can be easy to miss bsod.
With automatic restart unchecked it should display a bsod windows with bugcheck and : (
Sometimes it may display a misbehaving driver in the form *.sys
At the beginning of a bsod it typically displays a % counter.
If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

@philc43
OK - I ran the memtest anyway on two sticks I will call 1 and 3 which are in slots 1' and 3' --- this resulted in 22 passes with no errors on MemTest86+ v5.01. I will use the computer normally for a period of 1 month and report back any BSOD. If no BSOD, I will take out sticks 1 and 3, and I will place sticks 2 and 4 in slots 2' and 4' and follow again for a month
@zbook
I have changed kernel to automatic memory dump and I have unchecked automatic restart. Is it necessary to uninstaller IOBit? I occasionally use the unlocker software (though very rarely)