BSOD ntoskrnl.exe+3f5e40 problem

[IsaccoColbacco]

Hi, I have been having this problem for some time,
now this BLUESCREEN has been appearing to me for months and I don't know what to do, so I ask you for help.
I am attaching the latest BSOD dmp files.

 

 

042421-10218-01.dmp 042321-11046-01.dmp

[Radium_Angel]

Ok, hang tight Mate, I'll poke through them and see what stands out.

 

Your full system specs, please

[Radium_Angel]

Ok, I'm going to post relevant parts of the crashes, and then my thoughts below.

___

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000001, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000005, error status (normally i/o status code)
Arg3: ffffc18c7ac88080, current process (virtual address for lock type 3, or PTE)
Arg4: fffffe3ffaa46000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
PROCESS_NAME:  WmiPrvSE.exe

IMAGE_NAME:  memory_corruption

___

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: ffff9700074f2320
Arg3: 0000000000000029
Arg4: 000000000000002a
PROCESS_NAME:  firefox.exe

IMAGE_NAME:  memory_corruption

 

___

You have bad RAM.

Run MemTest86 and test your RAM.

Also, turn off XMP if you have it enabled. Causes more issues than it solves.

[IsaccoColbacco]

CPU Amd Ryzen 5 1600 Six-core processor (NOT overclocked)

MOBO AsRock AB350 Pro4

GPU Nvidia GeForce GTX 1060 6 GB

RAM Corsair Vengeance LPX 8x2 GB DDR4 3000 Mhz

SSD Samsung SSD 850 EVO 250 GB

PSU Seasonic Core 650GM 650W

[IsaccoColbacco]

24 minutes ago, Radium_Angel said:

Also, turn off XMP if you have it enabled. Causes more issues than it solves.

I don't know if it's already disabled on my MOBO

Here some screenshot of my Mobo BIOS:

As you see, in my XMP setting I can choose only Auto or Xmp 2.0 Profile 1

 

[Radium_Angel]

22 minutes ago, IsaccoColbacco said:

I don't know if it's already disabled on my MOBO

Here some screenshot of my Mobo BIOS:

As you see, in my XMP setting I can choose only Auto or Xmp 2.0 Profile 1

Set to suto, and test with MemTest86

[IsaccoColbacco]

1 hour ago, Radium_Angel said:

Set to suto, and test with MemTest86

Ok, so I did a quick test with Memtest86 with both RAM

Here the result

 

I made only 2 passes and count me 64 errors (1st pass 18, 2nd pass 46). I think I should made a better test with every single RAM stick in the first mobo slot.

This test surprised me because I have already had problems with the RAM in the past, 
and I had already changed it for this. After almost two years am I forced to switch RAM again?

[Radium_Angel]

2 hours ago, IsaccoColbacco said:

Ok, so I did a quick test with Memtest86 with both RAM

Here the result

 

I made only 2 passes and count me 64 errors (1st pass 18, 2nd pass 46). I think I should made a better test with every single RAM stick in the first mobo slot.

This test surprised me because I have already had problems with the RAM in the past, 
and I had already changed it for this. After almost two years am I forced to switch RAM again?

That's not good, either your RAM is bad...again, or your mobo is defective, causing RAM issues.

[IsaccoColbacco]

2 hours ago, Radium_Angel said:

That's not good, either your RAM is bad...again, or your mobo is defective, causing RAM issues.

Ok, so I made a better test tonight, first I tried only the first RAM in the second slot, after one pass it detected 18 errors

 

Then I tried the second RAM in the same slot, it give me 0 errors after one pass:

 

So I think one stick of RAM is broken, now I'm using only the good one, I hope I don't have any other BSODs, thank you for your invaluable help, it has saved me so much time.

I will update the topic if there is any news.

I hope Corsair accept me a second warranty change

[Codingale]

On 4/24/2021 at 5:47 PM, IsaccoColbacco said:

I will update the topic if there is any news.

Let me know, just started having stability issues and BSOD with the exact same error messages and found this thread. About to run a mem test as well just to be safe so rip both of us at the same time if so. I too have Corsair memory.

[Codingale]

Know it's a bit old and OP hasn't posted but leaving this here for anyone else in the future:
Turns out my 2 new modules weren't playing well with the old ones at 3000MHz and I had to turn it down to 2400 MHz. Also updated BIOS so there's that.