Windows 10: Had BSODS for months most caused by ntoskrnl.exe

Hey, i have had Blue screens for ages now, in blue screen view it says most of the blue screens are caused by ntoskrnl.exe heres the info Attachment 135281. Thanks

:)

 

Frequently receiving BAD_POOL_HEADER BSODs on Windows 10

Greetings, fellow Windows folks!

For months now, I've been receiving many BSODs on my laptop. All of them, however, BAD_POOL_HEADER
BSODs occur the most frequently, and more specifically so caused by ntoskrnl.exe.

Here is a link to a screenshot of the latest BSOD entry: http://puu.sh/wrRqR.png

................................ and another to my latest 5 entries caused by ntoskrnl.exe: BSOD Dumpies.zip

Thanks for further help and info!

~

***Post moved by the moderator to the appropriate forum category.***

 

BSOD APC_INDEX_MISMATCH ntoskrnl.exe+142940

I had a BSOD. Bug Check String APC_INDEX_MISMATCH , cause by driver ntoskrnl.exe caused by address ntoskrnl.exe+142940. Adive on the fix for this. XPS 15 9950 RUNNING Windows 10 Pro.

 

ntoskrnl is not the problem - it is usually another driver but bluescreen view just reports what it sees.

I've had a look through the driver modules loaded and the only older ones I can see are:

LGSHidFilt.Sys Thu May 30 16:16:33 2013 (51A76D51) - a Logitech gaming driver
Hamdrv.sys Mon Mar 30 14:28:42 2015 (55194F8A) - a LogMeIn Hamachi driver

If you can find newer drivers it would be worth updating them

 

Hey, thanks for helping i have uninstalled hamachi because i don't use it anymore so if it was the problem its gone now and the logitech driver has no updates. I'll let you know if my computer blue screens again.

 

Just crashed again here's the information that i got from the collector thing : Attachment 136029

 

One of your recent crashes suggested the graphics driver might be a cause:

Code: BugCheck 50, {ffffffff8d486824, 2, fffff80659f8e481, 2} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Could not read faulting driver name Probably caused by : nvlddmkm.sys ( nvlddmkm+7e481 )[/quote] Your current driver is dated Thu Feb 23 07:38:50 2017. There will be more recent ones you can install:

Please update the NVidia driver. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

 

I updated the driver but i'm still getting blue screens i'm starting to think its not a software problem and its a hardware one *Sad any way here's the log collector information : Attachment 136804

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.