Windows 10: I get a BSOD once a day due to memory corruption and im not sure what causes this

i have 32gb of ram and an i9 9900k processor


this is what is says in windbg


SYSTEM_SERVICE_EXCEPTION 3b
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80683eb5b57, Address of the instruction which caused the bugcheck
Arg3: ffff800f2d19da00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80683eb5b57

BUGCHECK_P3: ffff800f2d19da00

BUGCHECK_P4: 0

EXCEPTION_CODE: NTSTATUS 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!MiFindEmptyAddressRangeDownTree+17
fffff806`83eb5b57 48 ???

CONTEXT: ffff800f2d19da00 -- .cxr 0xffff800f2d19da00
rax=ffff800f2d19e560 rbx=0000020000000000 rcx=ffff9d0c266b36d8
rdx=0000000000000000 rsi=ffff9d0c266b36d8 rdi=00007ffffffeffff
rip=fffff80683eb5b57 rsp=ffff800f2d19e3f0 rbp=ffff800f2d19e5f0
r8=00007ffffffeffff r9=0000000000000000 r10=0000020000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000010000
r14=00007ff56e080000 r15=00007fffffff0000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!MiFindEmptyAddressRangeDownTree+0x17:
fffff806`83eb5b57 48 ???
Resetting default scope

BUGCHECK_STR: 0x3B_c000001d

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-OBF6H0I

ANALYSIS_SESSION_TIME: 02-01-2020 18:27:23.0735

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff80683eb5af5 to fffff80683eb5b57

STACK_TEXT:
ffff800f`2d19e3f0 fffff806`83eb5af5 : ffff9d0c`2dffc080 ffff9d0c`266b33f0 00000000`20646156 fffff806`83b6f06d : nt!MiFindEmptyAddressRangeDownTree+0x17
ffff800f`2d19e480 fffff806`83dd9395 : 00000000`00100000 00000000`000000a9 00000000`00000018 00000000`00000000 : nt!MiFindEmptyAddressRangeDown+0xd5
ffff800f`2d19e4f0 fffff806`83dd8983 : ffff9d0c`18584000 ffff800f`2d19e840 ffff800f`2d19e808 ffff800f`2d19e818 : nt!MiMapViewOfDataSection+0x7d5
ffff800f`2d19e660 fffff806`83e0539e : 00000000`00000000 ffff800f`2d19ea80 00000000`00000004 ffff9d0c`266b3080 : nt!MiMapViewOfSection+0x343
ffff800f`2d19e7b0 fffff806`8385f70f : ffff800f`2d19eac0 00000000`00040086 ffff800f`00000001 ffff800f`2d19eac0 : nt!MiMapViewOfSectionExCommon+0x1c6
ffff800f`2d19e930 fffff806`83e0208a : 00000000`00000000 ffff9d0c`2284f350 00007ffc`1e7c0000 00000000`001f0000 : nt!MmMapViewOfSectionEx+0x6f
ffff800f`2d19e9b0 fffff806`83e04353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiMapCfgBitMapSection+0xb6
ffff800f`2d19ea50 fffff806`83e0429e : 00000000`00000000 00000200`00000000 00000000`00000000 ffff9d0c`266b3080 : nt!MiCfgInitializeProcess+0x83
ffff800f`2d19eac0 fffff806`83e038a8 : 00000000`00000000 00007ff6`2f780000 00000000`00000000 00000000`00010000 : nt!MiMapProcessExecutable+0xe6
ffff800f`2d19eb60 fffff806`83e3556d : 00000000`000022b4 ffff800f`2d19f260 00000000`000022b4 00000000`00000000 : nt!MmInitializeProcessAddressSpace+0x1d4
ffff800f`2d19ed50 fffff806`83e2f937 : 00000000`2dffc000 ffff800f`2d19f260 00000000`00000000 00000000`00000000 : nt!PspAllocateProcess+0xf45
ffff800f`2d19f1e0 fffff806`839d2d15 : 00000000`00000002 00000000`00000af8 00000000`00000000 00000000`00000001 : nt!NtCreateUserProcess+0x6f7
ffff800f`2d19f990 00007ffc`1e85d934 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000026`c347d6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1e85d934


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
4 errors : !nt fffff80683eb5340-fffff80683eb5b58
fffff80683eb5340 *87 db 74 15 48 8b 4b 08 48 85 c9 0f 85 a7 63 13 ..t.H.K.H.....c.
fffff80683eb5350 00 48 8b cb e8 27 c2 97 *fd 8b c6 4c 8d 5c 24 70 .H...'.....L.\$p
...
fffff80683eb5b50 *89 f8 33 d2 48 8b f1 48 *8f 4c 24 20 4d 8b f9 44 ..3.H..H.L$ M..D

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xffff800f2d19da00 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_STRIDE

TARGET_TIME: 2020-02-02T02:24:39.000Z

OSBUILD: 18362

OSSERVICEPACK: 592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1972-08-21 17:24:00

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 1cc2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_stride

FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup: memory_corruption
---------

:)

 

BSODs with corrupt pagefile - Is That Possible?

Past couple of days I have been having random BSODS. A few examples of the messages was - Memory management / IRQL less than or equal to/ Thread could not be activated/ Page Pool something or other.

First BSODS I have had on this relatively new system so decided to take everything back to stock and test each part. I'm on Windows 7 Ultimate 64bit BTW.

HDtune error check - fine
Memtest86 - 10 passes fine
Prime 95 - 7hrs overnight fine
Graphics card - furmark/3DMark fine

Go to play a bit of WOW last night and it locks up straight away with memory management issue. So I looked into it a bit and read that it could possibly be a virtual memory/pagefile issue and that if it is corrupted it may cause these issues.

I then set the pagefile to zero and enabled clear pagefile on shutdown in the registry. When it rebooted I let the amount be set by Windows and disabled the registry entry for clearing it on shutdown and will see how it goes.

I had never heard of this issue before causing BSODS, is it common and what should be the next step if I get another one today with the new pagefile in place?

 

BSOD - I'm very frustrated


Memory corruption doesn't necessarily mean hardware, it is more often caused by drivers passing data to the wrong memory address but a memory test is still suggested to ensure it is not the cause.

With memory corruption the most occuring causes are:

• Drivers,
• Memory,
• SSD (firmware more often than the SSD itself bad),
• HDD,
• GPU, in this case we should see some DirectX stuff back in the stacks or similar drivers.

Then there is also the possibility that the

• CPU,
• SATA/IDE controller,
• mainboard &
• PSU,

can cause memory corruption, though most of these are pretty rare occuring when we see memory corruption.
I've seen only once the PSU causing memory corruption because of a loose cable, a few times the CPU and a few times the mainboard.

 

What causes a Physical Memory Dump?

The cause is listed on the blue screen, when booting press F8 and select the option that says "don't reset on BSOD's", not sure what it's called.