Bsod playing games, Google Chrome. Error 0x050

Hi! I've been recently encountering blue screens associated with 0x50 error! I have recently replaced my ram, my motherboard(rma'd), and my hard drive. I would like to know what is causing the problem. Any Assistance is deeply appreciated!

Hey there!

Code:

BugCheck 50, {fffff82002c0d348, 0, fffff80002a78b40, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceCopyEnd+0 )

Followup: MachineOwner

Code:

BugCheck 50, {fffff82002a8ec52, 8, fffff82002a8ec52, 5}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1ba )

Followup: MachineOwner

Code:

BugCheck 116, {fffffa80088f0400, fffff8800ffa3c84, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+91dc84 )

Followup: MachineOwner

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: Drivers - Clean Left over Files after Uninstalling

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Laith said:

Hey there!

Code:

BugCheck 50, {fffff82002c0d348, 0, fffff80002a78b40, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceCopyEnd+0 )

Followup: MachineOwner

Code:

BugCheck 50, {fffff82002a8ec52, 8, fffff82002a8ec52, 5}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1ba )

Followup: MachineOwner

Code:

BugCheck 116, {fffffa80088f0400, fffff8800ffa3c84, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+91dc84 )

Followup: MachineOwner

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: Drivers - Clean Left over Files after Uninstalling

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Unfortunately, I still am encountering the same bsod, even after doing all of that. Using blue screen view, I always see it is caused by ntoskrnl.exe+748c0, (when i double click to see all the details), and the red highlighted address is always ntoskrnl.exe+ee7aa. Furthermore, desktop manager and explorer.exe sometimes crashes. I recall that had a relation with some windows update I read about. I do have all windows updates, the important ones at least, none of the optional.

Run the other tests. While you are at it run MemTest86+, not MemTest86 but MemTest86+.

Laith said:

Run the other tests. While you are at it run MemTest86+, not MemTest86 but MemTest86+.

K, thanks for the assist! I have ran all the prior test at one time, so all that's left is to run memtest86+
Will get back to you! Weird if it's ram since Corsair just sent me a new pair of dominators..

I think it might be the RAM. It's not kinda weird if something happend when the RAM transported to your house.

Well either the previous DIMM slots were failing or one of the sticks were loose.

Laith said:

Well either the previous DIMM slots were failing or one of the sticks were loose.

No, I didn't switch from A2 to B1. It's A2 and B2 still. But all I did was switch their positions and reseated them. However, now the memok! led is on, however I took it as an ok sign; usually memok! is taken as a means to see if the PC will past post or not/if memory is compatible. Still as of now, my computer has not bsod. Strange.

Really is, but as long as it dosen't BSOD your fine.