random BSOD Windows 10

[SHADY16]

so every so often i get a random BSOD and i cant figure out what it is, this is what comes up  The bugcheck was: 0x000000d1 (0x0000000000b85380, 0x0000000000000002, 0x0000000000000008, 0x0000000000b85380 not sure if thats enough also get this message too driver_irql_not_less_or_equal

[sebfro]

Found an article on it for microsoft: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1--driver-irql-not-less-or-equal

 

That propably won't make sense, try this one and see if it works:

https://support.microsoft.com/nb-no/help/14238/windows-10-troubleshoot-blue-screen-errors

[DrMikeNZ]

This can be caused by an unstable overclock, if you are overclocked then drop it back.

Also, check your minidump with bluescreenview to see what caused the crash. Then reinstall that driver.

http://www.nirsoft.net/utils/blue_screen_view.html

[SHADY16]

Just now, DrMikeNZ said:

This can be caused by an unstable overclock, if you are overclocked then drop it back.

Also, check your minidump with bluescreenview to see what caused the crash. Then reinstall that driver.

http://www.nirsoft.net/utils/blue_screen_view.html

my pc is not overclocked at all everything is stock

[SHADY16]

4 minutes ago, DrMikeNZ said:

This can be caused by an unstable overclock, if you are overclocked then drop it back.

Also, check your minidump with bluescreenview to see what caused the crash. Then reinstall that driver.

http://www.nirsoft.net/utils/blue_screen_view.html

also it says it is related to this ntoskrnl.exe

[KyonEXE]

When I got random BSOD I ran a mem86+ test and found a bad RAM stick.  But I googled that .exe and it has to do with "system services such as hardware virtualization, process and memory management."

[KyonEXE]

Oh, and always check for windows and driver updates, they fix things too

[SHADY16]

9 minutes ago, KyonEXE said:

Oh, and always check for windows and driver updates, they fix things too

all my drivers are up to date.i also just ran a memtest and my ram is good, so if its a bad overclock then my system is having issues at stock clocks

[KyonEXE]

Mmm, it could be a windows installation if that's a windows service.  Maybe run a chkdsk /f /r, then when it reboots from that run a sfc /scannow.  These are command prompt commands so hit your windows key type cmd and right click that and run as administrator.