Question Got a critical structure corruption BSOD

[Hoogers]

Weeks ago I bought new RAM to install into my computer, replacing the one stick of 8 GB RAM I had with 2 new 8 GB sticks for 16 GB RAM. Since then I've had random BSODs. The first time, I got one that said EVENT TRACING FATAL ERROR. About a week later I got another one but I forgot what error it was. Wasn't doing anything in particular, the first time I was on google chrome and the second I was in file explorer. It's been about 2 weeks now without a problem since but now while on google chrome I got yet another one saying CRITICAL STRUCTURE CORRUPTION. I'm worried it's the RAM I just bought but I can't tell, because it seems that it's either a driver or hardware issue. Any help?

This was the dump file for the most recent BSOD:

Spoiler

CRITICAL_STRUCTURE_CORRUPTION (109)
Arg1: a3a023e6ed00454e, Reserved
Arg2: 0000000000000000, Reserved
Arg3: aadd8054af109b9c, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

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: a3a023e6ed00454e

BUGCHECK_P2: 0

BUGCHECK_P3: aadd8054af109b9c

BUGCHECK_P4: 101

PG_MISMATCH: 800000000

MEMORY_CORRUPTOR: ONE_BIT

CPU_COUNT: 8

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x109

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-03A7H49

ANALYSIS_SESSION_TIME: 02-24-2020 20:50:30.0173

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
fffffb8534816d98 0000000000000000 : 0000000000000109 a3a023e6ed00454e 0000000000000000 aadd8054af109b9c : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME: 2020-02-25T04:31:08.000Z

OSBUILD: 18362

OSSERVICEPACK: 657

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: 2005-04-22 18:40:32

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: 2325

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner

 

[Colif]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

especially if you weren't getting BSOD before you swapped ram

 

[Abhinav2005]

This problem generally occurs due to Windows Driver Corruption or RAM problem.
After running Memtest86,if your test fails then it's your RAM problem. If your test passed then follow the steps:-
Create a bootable Pendrive and repair your system using Windows Repair Tool.
Or you can backup all you IMPORTANT things and do a clean install. This can be due to virus or malware.

After doing,use your system until you get another Stop Code.

 

[Hoogers]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

especially if you weren't getting BSOD before you swapped ram

I ended up flashing my BIOS and updating them and after doing that I went through the Windows Memory Diagnostic again with both RAM sticks and it came up with no problem this time. Is it possible my old BIOS version wasn't that compatible with the RAM I bought which caused problems? It used to be a 2015 version but now it's a more recent 2018 version. I think the RAM I bought actually came out sometime after 2015.

 

[Hoogers]

This problem generally occurs due to Windows Driver Corruption or RAM problem.
After running Memtest86,if your test fails then it's your RAM problem. If your test passed then follow the steps:-
Create a bootable Pendrive and repair your system using Windows Repair Tool.
Or you can backup all you IMPORTANT things and do a clean install. This can be due to virus or malware.

After doing,use your system until you get another Stop Code.

I startes memtest and so far it finished pass 1 of 4 with 229 cumulative error counts. Does that mean faulty ram then?

 

[NotWD]

I startes memtest and so far it finished pass 1 of 4 with 229 cumulative error counts. Does that mean faulty ram then?

Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

 

[Hoogers]

I also just realized all the errors are coming from test 13, the hammer test. From some searching I'm seeing that's where people usually get errors and there's even a section on the memtest website about test 13 only errors. Should I replace the sticks regardless?

 

[Colif]

Max error count you want in memtest is 0. Any higher is a sign you need new ram

BIOS updates can help motherboard work with ram but won't overcome faulty ram itself.

I would rma the sticks and get a new set. Failing memtest is a valid reason for replacement.

 

[Abhinav2005]

I startes memtest and so far it finished pass 1 of 4 with 229 cumulative error counts. Does that mean faulty ram then?

RAM is your problem. Time to get a new RAM. Or if under warranty so a RMA.

 

[Abhinav2005]

RAM is your problem. Time to get a new RAM. Or if under warranty go for RMA.