Question BSOD once in a month

[walvis33]

I had random shutdowns when:
every fan and lighting was still running but i had no picture on monitor;
system froze and it needed hard shutdown to fix;
and today i received a blue screen, dump is shown below

nothing is/was overclocked (RAM at 3000mhz);
i tested my GPU in kombustor for ~2 hours before and my RAM in memtest for 10+ hours and got no error in both programs;
every game and program runs well and i haven't got my GPU running above 75C in Furmark and CPU at 70C in Aida64 stress test, it just does it randomly.

first random shutdown was when i just installed windows and i was idle, even RAM was at stock;
second was when i was on windows login screen and it just froze;
today i was playing ps3 emulator and got blue screen 10 minutes after closing it.

this pc was build in december and still has everything under warranty and i can possibly replace something

specs:
Gigabyte B450M DS3H (Bios is F40, stock)
Ryzen 5 2600
RX580 Sapphire Pulse
G Skill SniperX F4-3200 CL16 8GB x2 running @3000mhz
be quiet! pure power 11 500w

memorydump:

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

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff90000000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000006, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on S0UND

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 3

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  50

BUGCHECK_P1: fffff90000000000

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 6

READ_ADDRESS:  fffff90000000000

MM_INTERNAL_CODE:  6

BLACKBOXBSD: 1 (!blackboxbsd)



BLACKBOXNTFS: 1 (!blackboxntfs)



BLACKBOXPNP: 1 (!blackboxpnp)



BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffffcf0f2f3db7f0 -- (.trap 0xffffcf0f2f3db7f0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=fffff90000000000

rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037a8c46d0 rsp=ffffcf0f2f3db988 rbp=0000000000000004
 r8=fffff90000000000  r9=fffff97cbe400000 r10=0000000000000002
r11=fffff97cbe5f27f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MI_READ_PTE_LOCK_FREE:
fffff803`7a8c46d0 488b01          mov     rax,qword ptr [rcx] ds:fffff900`00000000=????????????????
Resetting default scope

STACK_TEXT: 
ffffcf0f`2f3db448 fffff803`7aa5860a : 00000000`00000050 fffff900`00000000 00000000`00000000 fffff97c`be400000 : nt!KeBugCheckEx
ffffcf0f`2f3db450 fffff803`7a8c9c7c : fffff97f`ffffffff fffff803`7a923726 fffff900`00000000 00000000`00000000 : nt!MiInPagePageTable+0x1603fa
ffffcf0f`2f3db5a0 fffff803`7a8c8fae : 00000000`00000000 00000000`00000000 00000000`00000001 fffff900`00000000 : nt!MiUserFault+0x7dc
ffffcf0f`2f3db650 fffff803`7a9d041e : ffffa680`5930b180 00000000`00000088 00000000`00000400 ffffd10d`3d4ab040 : nt!MmAccessFault+0x14e
ffffcf0f`2f3db7f0 fffff803`7a8c46d0 : fffff803`7a8199b4 ffffd10d`3d4ab040 fffff803`7a915039 ffffa680`5930b180 : nt!KiPageFault+0x35e
ffffcf0f`2f3db988 fffff803`7a8199b4 : ffffd10d`3d4ab040 fffff803`7a915039 ffffa680`5930b180 00000000`00000000 : nt!MI_READ_PTE_LOCK_FREE
ffffcf0f`2f3db990 fffff803`7a8198c2 : 00000000`00000001 00000000`00000000 00000000`00000001 fffff803`7ad8f240 : nt!MiMappingHasIoTracker+0x44
ffffcf0f`2f3db9c0 fffff803`cc10b94e : 00000000`00000000 ffffd10d`3d4ab180 fffff803`cc10e188 00000000`00000004 : nt!MmUnmapIoSpace+0x62
ffffcf0f`2f3dbaf0 fffff803`7afbeecd : ffffd10d`3d4ab040 fffff803`7aef7e90 00000000`00000400 fffff803`7ac65a20 : kerneld+0xb94e
ffffcf0f`2f3dbb30 fffff803`7a8f43b5 : ffffd10d`2796f9a0 fffff803`7aec5600 ffffd10d`3d4ab040 ffffd10d`3d4ab040 : nt!IopLoadUnloadDriver+0xc703d
ffffcf0f`2f3dbb70 fffff803`7a86bcd5 : ffffd10d`3d4ab040 00000000`00000080 ffffd10d`2788f040 00000000`00000080 : nt!ExpWorkerThread+0x105
ffffcf0f`2f3dbc10 fffff803`7a9c9998 : ffffa680`59679180 ffffd10d`3d4ab040 fffff803`7a86bc80 ffffcf0f`2f3dbcd0 : nt!PspSystemThreadStartup+0x55
ffffcf0f`2f3dbc60 00000000`00000000 : ffffcf0f`2f3dc000 ffffcf0f`2f3d6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  kerneld+b94e

MODULE_NAME: kerneld


IMAGE_NAME:  kerneld.x64


STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b94e

FAILURE_BUCKET_ID:  AV_R_INVALID_kerneld!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7e10fa66-c5e3-20c3-421e-2ac8750f89c9}

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

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

but as its so rare, can you run this as well - https://www.sysnative.com/forums/pages/bsodcollectionapp/

 

[walvis33]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

but as its so rare, can you run this as well - https://www.sysnative.com/forums/pages/bsodcollectionapp/

i did run this program:
https://drive.google.com/open?id=1FaBM6IPoDo8BbesYJzBLKZcOt0UY_lQX

if still needed i will upload a minidump when next crash happens

 

[Colif]

lol. any chance you can run it in English? I can't read that, sorry

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://anhydrousdormouse.htmlpasta.com/

File information:	050120-16359-01.dmp (Apr 30 2020 - 18:53:36)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:	*** WARNING: Unable to verify timestamp for kerneld.x64
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 8 Hour(s), 14 Min(s), and 48 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/B450M-DS3H-rev-10#kf
There is a BIOS update available for your system. You are using version F40 and the latest is version F50. Note: There are special update instructions that must be followed carefully. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit: Results for 2 dumps below: https://tantaloushold.htmlpasta.com/

Spoiler

File information:	050320-16453-01.dmp (May 2 2020 - 20:44:54)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:	*** WARNING: Unable to verify timestamp for kerneld.x64
Probably caused by:	kerneld.x64 (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 14 Min(s), and 47 Sec(s)

File information:	050120-16359-01.dmp (Apr 30 2020 - 18:53:36)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:	*** WARNING: Unable to verify timestamp for kerneld.x64
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 8 Hour(s), 14 Min(s), and 48 Sec(s)

 

[walvis33]

i got another blue screen, after overclocking memory to 3200/CL14 with 1.4 volts, had 0 errors in 4 memtest86 passes and crashed during my test in GTA 5, with the same error as before.

i did run it with english language, but after overclocking (received the same bsod error):
https://drive.google.com/open?id=1FaBM6IPoDo8BbesYJzBLKZcOt0UY_lQX

this time it didn't create event for it in Event Viewer and instead wrote:

The winlogon notification subscriber <SessionEnv> was unavailable to handle a critical notification event.

maybe it's caused by overclocking now; but how can it pass memtest86 4 times without errors?
and again, first time when i had a system crash was that same error with stock RAM (2133 cl15).

latest minidump:
https://drive.google.com/open?id=1WuaNhzo1ovIhmmaLOtr3nU_Rl178IKAF

another minidump i found in windows/minidump:
https://drive.google.com/open?id=1ZYNwcu_CRJM5ayin1k8YVDn05-YyDM8s

 

[walvis33]

i did some experiments; im 95% sure this is my RAM... but i'm confused how it easily passes all the memtest86 tests? i will be waiting for confirmation
this RAM is not on QVL and i can't replace it quickly, maybe it'll stay for another 6 six months there.

if this caused by RAM:
will this create problems for other components/degrade my pc's health or i just need to get over blue screens during this time?

 

[Colif]

Overclocking can cause BSOD so I should have said to remove any, I had just assumed you didn't have one.

If ram isn't on QVL and its a Ryzen CPU, then thats another good reason. They really picky about ram.

As for damages, I don't think so. Its always possible that restarts could damage the boot drive.
It can corrupt files, so you might need to install windows as well.

So you can't return ram and get sticks that are on motherboard list?

 

[walvis33]

i can't return it if it's not faulty.

when RAM was overclocked bsods appeared more often. for now i think this is RAM, but i need to be 100% sure, because i'm still confused with memtest results and it's general behavior.

i think behavior is weird because these crashes are completely random; i can do any test and play any game with 100% load at all components without ANY errors, and get blue screens when nothing is running and 99% of my ram is free.

i reset bios with all the RAM speeds for now.