Question BSOD - Memory Error in Dump - Before & After RAM Replacement

[Linkedchainz]

Good Morning!

I started BSODing randomly one day playing... world of warcraft(classic 2004)?
So I presumed it to be ram since my system is ~5 years old and ive only been running on 32gb ram all this time - gpu/cpu at a very light overclock for a few years as well
I'm definitely not a technician and unsure of what I'm looking at! the new ram seems to be BSODing more which leads me to believe there must be an underlying issue
Memtest86 passed, Win mem diag failed, Intel Proccessor Diagnostic Tool passed - Potentially PSU??? any tools to check?

Diagnostic tools
HWiNFO64
CPU-Z
RivaTunerStatistics

Win 10
mobo: Z590 Pro Wifi(MS7D09)
cpu: i9-10900f
gpu: Nvidia GeForce 3070
Ram prior(4 years usage)😀DR4-3600 CL16-19-19-39 1.35V xmp (G.Skill TridentZ Neo) - 16 gb sticks on slot 2 / 4
Ram now(1 week usage): DDR4-3600 CL18-22-22-42 1.35V xmp (G.Skill Ripjaws V Series) - 32gb sticks on all slots
PSU: Corsair RM1000x 2021 80+ Gold

Dump files / Reliability History below in google drive
https://drive.google.com/drive/folders/1GCK5LkYHdq3ESBSv35SIh4YimGyCvAUJ?usp=sharing

 

[Ralston18]

32gb x 4 ? Meaning 128gb RAM - correct?

Double check the motherboard's supported RAM and supported RAM configurations. Verify via the motherboard's QVL.

Was the new RAM a matched set for dual channel use?

Source(s) for the RAM?

Was the new RAM installed by following the installation procedures in the motherboard's User Guide/Manual? (Some motherboards require that the first physically installed RAM be placed in a specific slot. Commonly DIMM_A2.)

Look in Reliability Monitor for error codes, warnings, or informational events being captured just before or at the time of the BSODs.

 

[Linkedchainz]

32gb x 4 ? Meaning 128gb RAM - correct?

Double check the motherboard's supported RAM and supported RAM configurations. Verify via the motherboard's QVL.

Was the new RAM a matched set for dual channel use?

Source(s) for the RAM?

Was the new RAM installed by following the installation procedures in the motherboard's User Guide/Manual? (Some motherboards require that the first physically installed RAM be placed in a specific slot. Commonly DIMM_A2.)

Look in Reliability Monitor for error codes, warnings, or informational events being captured just before or at the time of the BSODs.

128 yes 4 slots all 32 w/ DDR4-3600 CL18-22-22-42 1.35V xmp (G.Skill Ripjaws V Series)
https://www.amazon.com/dp/B0884TNHNC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

I DID install Dimm_A1 first, would.. turning it off and unslotting/reslotting "fix" the input error?
I find it weird my system ran fine with 2 slots for a few years then BSOD, then with brand new ram still bsod

reliability monitor is attached in the google drive if needed - as well as a few dump files(last 5 perishes)

event viewer commonly has the below errors
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000009696, 0xfffff40060a4f3a0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\022425-10625-01.dmp. Report Id: 5653dccc-4794-4604-bc16-802d34f5b6c6.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

[Ralston18]

PSU: Original to build - thus being ~ 5 years old. Correct?

PSU may be at or nearing its' designed in EOL (End of Life) and starting to falter and fail.

Setting aside concerns about the installed RAM specs for the moment, simply consider that the additional power demands of the added RAM (even though may not seem to be all that much) may have hit some threshold wattage value that the PSU simply cannot keep up with.

Especially at peak times.

It is also likely that much of that new RAM is simply going unused. Check actual RAM useage via Task Manager and Resource Monitor.

As for reslotting the RAM etc. I simply do not know. The first place to look and to read is in the Motherboard's User Guide/Manual.

Again, go to the manufacturer's website to ensure that the installed new RAM is 1) suppported, and 2) correctly configured.

Take a closer look in Reliability Monitor and Event Viewer for details about the BSODs.

The minidumps may or may not prove useful and there are other members here that are much more well-versed in reading and understanding the minidump files. I will defer to those members who wish to post and comment.

 

[Bob.B]

128 yes 4 slots all 32 w/ DDR4-3600 CL18-22-22-42 1.35V xmp (G.Skill Ripjaws V Series)
https://www.amazon.com/dp/B0884TNHNC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

I DID install Dimm_A1 first, would.. turning it off and unslotting/reslotting "fix" the input error?
I find it weird my system ran fine with 2 slots for a few years then BSOD, then with brand new ram still bsod

reliability monitor is attached in the google drive if needed - as well as a few dump files(last 5 perishes)

event viewer commonly has the below errors
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000009696, 0xfffff40060a4f3a0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\022425-10625-01.dmp. Report Id: 5653dccc-4794-4604-bc16-802d34f5b6c6.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Assuming you bought the 4 stick kit and not 2 kits of 2 sticks use just 2 sticks in slot A2 and B2.....test.

 

[Linkedchainz]

Good Morning!

I started BSODing randomly one day playing... world of warcraft(classic 2004)?
So I presumed it to be ram since my system is ~5 years old and ive only been running on 32gb ram all this time - gpu/cpu at a very light overclock for a few years as well
I'm definitely not a technician and unsure of what I'm looking at! the new ram seems to be BSODing more which leads me to believe there must be an underlying issue
Memtest86 passed, Win mem diag failed, Intel Proccessor Diagnostic Tool passed - Potentially PSU??? any tools to check?

Diagnostic tools
HWiNFO64
CPU-Z
RivaTunerStatistics

Win 10
mobo: Z590 Pro Wifi(MS7D09)
cpu: i9-10900f
gpu: Nvidia GeForce 3070
Ram prior(4 years usage)😀DR4-3600 CL16-19-19-39 1.35V xmp (G.Skill TridentZ Neo) - 16 gb sticks on slot 2 / 4
Ram now(1 week usage): DDR4-3600 CL18-22-22-42 1.35V xmp (G.Skill Ripjaws V Series) - 32gb sticks on all slots
PSU: Corsair RM1000x 2021 80+ Gold

Dump files / Reliability History below in google drive
https://drive.google.com/drive/folders/1GCK5LkYHdq3ESBSv35SIh4YimGyCvAUJ?usp=sharing

just did some testing with ram sticks, event viewer showing me a new failed bugcheck with all correct rams in corresponding dimms, memory is supported QVL,



PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 0000000000e666da, page frame number
Arg3: 0040000000000000, current share count
Arg4: 0000000000000000, 0

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1203

Key : Analysis.Elapsed.mSec
Value: 2226

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x4e

Key : Bugcheck.Code.TargetModel
Value: 0x4e

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0x4E_7_nt!MiPfnReferenceCountIsZero

Key : Failure.Hash
Value: {d4c4fdf2-bb42-a5bb-4f52-718a7a31638a}


BUGCHECK_CODE: 4e

BUGCHECK_P1: 7

BUGCHECK_P2: e666da

BUGCHECK_P3: 40000000000000

BUGCHECK_P4: 0

FILE_IN_CAB: 022425-13406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

FAULTING_THREAD: ffffbe0501c4c580

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System
SYMBOL_NAME: nt!MiPfnReferenceCountIsZero+1c02c5

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.5486

STACK_COMMAND: .process /r /p 0xffffbe04f66b7040; .thread 0xffffbe0501c4c580 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1c02c5

FAILURE_BUCKET_ID: 0x4E_7_nt!MiPfnReferenceCountIsZero

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d4c4fdf2-bb42-a5bb-4f52-718a7a31638a}