Have you tested your memory 1 memory stick at a time? Which chasing the information on the Microsoft bsod bug check page :īug check 0x50 can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).Īnother possible cause is the installation of a faulty system service or faulty driver code.Īntivirus software can also trigger this error, as can a corrupted NTFS volume. Typically the address is just plain bad or it is pointing at freed memory.Īrg1: ffffb5819bfdf6c8, memory referenced.Īrg2: 0000000000000002, value 0 = read operation, 1 = write operation.Īrg3: fffff80e078edc0e, If non-zero, the instruction address which referenced the bad memory At this point the OS panics and throws a BSOD to prevent damage to the system.Īnd confirmed with a analysis of bugcheck in your dump file with

When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space. In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own. As such, if ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD. It is protected by security features and the Windows System File Checker. Ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system. Which is pointing to ntoskrnl.exe main reason for bsod (part that reacted to make it happen, not the cause of the issue)

Windows afd service