Windows 10: BSOD only when I have my 2 ram sticks in

I recently came across my first ever BSOD loop and don’t know what to afterwards, during the process I couldn’t get anything to work even when I went to system restore it would BSOD during. Fast forward a bunch of troubleshooting and I decide to launch my pc with 1 ram stick, and no BSOD, play some YouTube and couple other light browser tasks with discord open. I’ve tested both sticks using the windows memory diagnostic by themselves and no errors come up, I’ve been using my pc since with 1 stick no fault but when I use the other I get the stop code KMODE_EXCEPTION_NOT_HANDLED , and a couple o

:)

 

BSOD when using 2 ram sticks

I followed the guide to set driver verifier up and let it run for 6 hours. Never got a BSOD, so no dump files. After updating my BIOS and setting the ram to auto mode (so not in XMP mode) it seems stable. Ran memtest86 4 times and has not errored yet. I plan to run OCCT for 2 hours tonight to see if it fails (already did 3 sessions of 1 hour each no issues). So, I am not sure if the Ram is bad and cannot run at the specs they say or if my MB has as issue with the Ram.

But for now, seems like the issues was BIOS needed updating and Ram will not run in XMP mode. I may buy new ram soon and see if it has the same problem.

UPDATE: After running OCCT for 1 hour I did get another BSOD. There was no dump for it as it froze on the BSOD and did not restart. I force restarted and it booted to BSOD twice. Then the OS loaded and withing minutes it BOSD again. Then it would not boot up, so I removed 1 stick of Ram and it booted back up. I have put the 2 dumps in shared folder OneDrive (I moved the other files into folder named old). Out of the 5 BSOD there is only 2 dumps.

Thanks for all your help.

 

BSOD when use 2 stick of RAM

Is it just one of the sticks that causes the BSOD - or can it be either one?
In most cases, this is due to a bad stick of RAM - but that's not the only possibility.
For example, it can be a problem with the slot that the stick plugs into (sometimes they break when inserting the sticks)
It can also be other damage/problems with the motherboard that cause this.

Only 1 memory dump (from 20 May) is present in the uploaded reports.
If you are using a disk cleaning app, please stop using it while we're troubleshooting

Your BIOS/UEFI version P3.70 dates from November of 2019
Please visit the ASRock support site for your motherboard to see if there is a later, stable version.
If so, please download and install it.
While you're at the support site, also download and install the latest version of the AMD chipset/motherboard drivers. Some of yours date from 2015.

You have version 1809 of Windows 10. Please update to version 1909.
Once that's done, then ensure that you manually check for (and get) ALL available Windows Updates

There are many BSOD's and Live Kernel Events listed in the WER section of the MSINFO32 reports.
Do you turn your system off by holding the power button down?
Do you get shutdowns without the BSOD?

Memory dump shows a STOP 0x3B BSOD.
The stack text shows that it's possibly 3rd party software - but that could also be a sign of a hardware problem.
Previous BSOD's (frm MSINFO32) were
STOP 0x116
STOP 0x133 (2 of them)
STOP 0x139
STOP 0x1A (4 of them)
STOP 0x1E (2 of them)
STOP 0x3B (2 of them - this doesn't include the one that dates from 20 May)
STOP 0x4E (2 of them)
STOP 0xBE (3 of them)

Your TP-Link Wireless adaptor has drivers dating from 2016.
Please update them to the latest available, Windows 10 compatible version

You have a USB audio device with a driver that dates from 2016
These devices are known to cause BSOD's on some systems.
I suggest that you temporaritly remove (unplug) the device from your system and uninstall it's software.
Feel free to try it again (with updated software) once we're finished troubleshooting.

Your IOBit Advanced System Care has a driver (Monitor_win10_x64.sys) that dates from 2018 - and it may have a critical vulnerability. I strongly suggest updating Advanced System Care to the latest available version/update.

Please update:
- Realtek PCI3 Wireless drivers
- Internet Download Manager
As they also have drivers dating from 2018

- - - Updated - - -

PS - I haven't forgotten about the RAM problem, but would like to get your system updated prior to working on that.

 

BSOD when using 2 ram sticks

My computer is BSOD when I have 2 sticks of Ram put into MB slots B2&A2 (the slots the MB says to use for Dual channel). It crashes under load when gaming. So I download OCCT to test and it crashes every time I have both sticks in without fail.





I ran OCCT memory stress test and CPU stress test with 2 16 GB sticks in slots A2 & B2 (Dual channel mode was shown in BIOS)

Crashed (BSOD) in 30 seconds or less.



I ran OCCT memory stress test and CPU stress test with each Stick of Ram (1 stick at a time) in slots B2, then A2. Also 1 time each with XMP on and off.

No crashes



I ran OCCT memory stress test on a stick in B2 slot again, this time OCCT would go into "Not Responding" ever 30 secs or so then come back working (this happen like clockwork till I stopped it 12 minutes in).



I ran Memorytest86 tool from USB flash drive on each stick in slot B2 no errors. Also ran 1 stick in slot A2 with no errors.



After running the tests, I put both sticks back in to test them with Memorytest86, but when it got to "Checking CPU,Cache,Mem speeds" it hung and never went into the test. Then when I tried to reboot, the computer would start powering up, then depower, then start powering up again (it does this on repeat for 5 minutes). I had to remove 1 Ram stick to boot it, shut it back down and put the other in again than it booted with both stick is. But the boot led to a BSOD, then rebooted back to Desktop.





I have the dumps of all the crashes, but it just says "BugCheck Failed". 2 of the dumps are when it BSOD while in a game, 2 are when running OCCT Memory test, and last one is the BSOD when I added back both sticks and it booted to BSOD.



All the parts are new, so I need to figure out which piece of hardware is bad: MB, CPU, or Ram. Right now, I am thinking MB but can't confirm since I don't know how to read the mini dumps.

Below is some of the info I got from the 4 dumps:



SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the BugCheck

Arg2: fffff800382f7f0f, Address of the instruction which caused the BugCheck

Arg3: ffffb103e8306730, Address of the context record for the exception that caused the BugCheck

Arg4: 0000000000000000, zero.



IMAGE_NAME: GenuineIntel.sys

FAILURE_BUCKET_ID: IP_MISALIGNED_GenuineIntel.sys



******************************************************************************



WINLOGON_FATAL_ERROR (c000021a)

The Winlogon process terminated unexpectedly.

Arguments:

Arg1: ffff868ca60e9a40, String that identifies the problem.

Arg2: ffffffffc0000005, Error Code.

Arg3: 00007ffae6fb425f

Arg4: 000000f60bdbdf80



FAILURE_BUCKET_ID: 0xc000021a_c0000005_csrss.exe_Terminated_nt!PopTransitionSystemPowerStateEx



******************************************************************************



ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)

An attempt was made to write to readonly memory. The guilty driver is on the

stack trace (and is typically the current instruction pointer).

When possible, the guilty driver's name (Unicode string) is printed on

the BugCheck screen and saved in KiBugCheckDriver.

Arguments:

Arg1: ffffa8181955a258, Virtual address for the attempted write.

Arg2: 8a00000000200121, PTE contents.

Arg3: fffff3882909e710, (reserved)

Arg4: 000000000000000a, (reserved)





IMAGE_NAME: ntkrnlmp.exe



FAILURE_BUCKET_ID: AV_nt!MiRaisedIrqlFault



******************************************************************************



KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common BugCheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff8062a610654, The address that the exception occurred at

Arg3: fffff285c1d9f698, Parameter 0 of the exception

Arg4: fffff285c1d9eed0, Parameter 1 of the exception



IMAGE_NAME: volsnap.sys

FAILURE_BUCKET_ID: AV_volsnap!VspStorageDriverCallout





Based on this can you tell me what is the issue with this PC?