Frequent BSODs and other weird shenanigans after upgrading.

[mahoutsukai]

I recently changed my motherboard, CPU as well as my RAM and for some reason my system kept getting BSOD's after a few hours of use. Things such as MEMORY_MANAGEMENT, CRITICAL STRUCTURE CORRUPTION as well as ATTEMPTED WRITE READONLY MEMORY kept popping up randomly and after the first blue screen it just entered a BSOD Loop. Is it my motherboard or is it my RAM? any help would be very appreciated.

AsRock B450-HDV/Ryzen 5 3500x
Patriot 2133 2x4 DDR4.

 

Sorry if my post isnt clear since english isnt my first language. 

 

Edit: I forgot to mention, for some reason after a few days of upgrading, my PC just doesnt turn on at all while my Keyboard and mouse's RGB is still on for some reason. Turns out the power button my case is busted, and for some reason my PSU too. But for some reason after reassembling it, my PC basically came back like nothing had happened with the same case and everything. Should I consider changing PSU as well? thanks. (Currently still using the Cooler Master 500w V2 that magically came back to life.)

[Radium_Angel]

If you can post the crash dump files from the BSoDs, I can read them and tell you what is going on, but it sounds like bad RAM.

Do you have XMP turned on the BIOS? That seems to cause many issues, if so, turn that off.

[mahoutsukai]

8 minutes ago, Radium_Angel said:

If you can post the crash dum030221-55859-01.dmpp files from the BSoDs, I can read them and tell you what is going on, but it sounds like bad RAM.

Do you have XMP turned on the BIOS? That seems to cause many issues, if so, turn that off.

I dont think so, I've only had this motherboard for a few days now and I didnt touch the BIOS at all. Here's the crash dump files, I finally figured out how to actually get them. 
 

Edit: For some reason 2 of them are 0B, sorry for that.

030221-49468-01.dmp 030221-40281-01.dmp 030221-54250-01.dmp 030221-40109-01.dmp

[Radium_Angel]

ok, give me a few to look them over

[Radium_Angel]

Ok, I'm going to post the relevant parts of the crash dump, then at the end, I'll let you know my thoughts.

___

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: ffffc13ffef61558
Arg3: 0000000000040000
Arg4: 0000000000000000

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffc13ffef61558

BUGCHECK_P3: 40000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  smss.exe
 

SYMBOL_NAME:  ONE_BIT

MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 

The other crash dump is identical.

I suspect rather stongly you have bad RAM.

You can easily verify this by using a program that runs from a USB stick called "MemTest86"

 

As to the not turning on, then turning on, I would say it sounded like a short in the case, or a poorly connected power switch.

[mahoutsukai]

1 minute ago, Radium_Angel said:

Ok, I'm going to post the relevant parts of the crash dump, then at the end, I'll let you know my thoughts.

___

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: ffffc13ffef61558
Arg3: 0000000000040000
Arg4: 0000000000000000

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffc13ffef61558

BUGCHECK_P3: 40000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  smss.exe
 

SYMBOL_NAME:  ONE_BIT

MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 

The other crash dump is identical.

I suspect rather stongly you have bad RAM.

You can easily verify this by using a program that runs from a USB stick called "MemTest86"

 

As to the not turning on, then turning on, I would say it sounded like a short in the case, or a poorly connected power switch.

Ah, Ok thanks  I did test my RAM before posting tho, but I did so using Windows Memory Diagnostic. It didnt detect any error at all which lead me to posting the thread. 

[Radium_Angel]

6 minutes ago, mahoutsukai said:

Ah, Ok thanks  I did test my RAM before posting tho, but I did so using Windows Memory Diagnostic. It didnt detect any error at all which lead me to posting the thread. 

WMD is useless, only MemTest86 will find if the RAM is good or not.