Windows 10: BSOD caused by ntoskrnl exceptions

Hello to anyone that is willing to help my name is Glenn,

My pc was assembled by professionals but it got really hot so a month ago I took my cpu cooler off and noticed that they left the plastic on the cpu cooling block, So I fixed that issue after emailing the people that did it. But now another month later im beginning to have BSOD's and randomely at that. Im not sure if it has anything to do with the CPU plastic or me actually doing something wrong when I re applied cooling paste and the cooling block itself.

It happens irregularly but usually when a game is running either active or in the background (When multitasking) I hope you guys can tell me if this is a driver issue or maybe an old bios driver issue or just a faulty CPU.

I reinstalled my windows 3 times with an actual OS image.




:)

 

BSOD Bad_Pool_Caller Win10 on Dell Inspiron

Here is some info that may help. May be your network driver. One of the posts suggest a program that will give more info on what crashed. Hope this helps you.

BSOD caused by ndis.sys, NETIO.SYS and ntoskrnl.exe - [Solved] - Windows 10

 

BSOD ntoskrnl, plz help!

Hello, I'm having bsod when I launch benchmark with sisoft sandra.

I got 2 different bsod DRIVER_CORRUPTED_XPOOL and DRIVER_OVERRAN_STACK_BUFFER all with the same driver ntoskrnl.

what to do?

i'm using win10 64bit.

thank you

 

The 5/12 dump doesn't have any useful info in it. The 5/6 dump indicates a problem with your Nvidia card or driver nvlddmkm.sys.
Code: BugCheck 3B, {c0000005, fffff807b90a63b7, ffffd1002ffe7ba0, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : memory_corruption[/quote] Driver Description: nVidia Video drivers
Driver Update Site: Download Drivers | NVIDIA

You have the newest avauilable driver, 382.05, so try doing a complete uninstall and reinstall as follows:

 

Driver Description: nVidia Video drivers
Driver Update Site: Download Drivers | NVIDIA

You have the newest avauilable driver, 382.05, so try doing a complete uninstall and reinstall as follows:[/quote] I have already done this and that bsod was rare and I didnt recieve it before. however I do keep getting with like intervals of 7 days at times bsods with either Service exceptions or Thread exceptions.

 

There were only two dumps in the zip you uploaded.

Are you running any disk cleaners like CCleaner? If so that may be deleting additional dumps.

I don't see anything in the Event Viewer log either.

With the over heating, try this:
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

If that doesn't show anything then try this:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

 

Yeah I have CCleaner but its because I reinstalled my pc that the other dumps are gone ;(
Ill try and run driver verifier either today or tomorrow thank you for responding!

Update: I also updated my bios today my motherboard is an MSI Z170A M7 Gaming. I had version 1.b and I now have the updated 1.h which also has NVME compatibility fixes. Maybe this was the cause of the BSOD's.

Im currently running driver verifier how long should I try it? A day?
I dont really notice a difference running this.

 

Did you follow the instructions at the link I gave you for Driver Verifier. It tells you how to set it up and how long (MAX) to run it.

Good news about the BIOS, that could very well resolve this.

 

Yeah I was running a pretty old one, I just thought I mightve broken something when I reinstalled the CPU cooler without the plastic or during the reseating of the gpu but I dont think I hit anything or something like that maybe that the CPU cooler got seated too tight but I was very carefull with that aswell.

Yeah I did the driver verifier settings correctly and rebooted, But I dont notice my pc running sluggish due to it.

 

Let it run for up to 48 hours, see if we get a Driver Verifier induced BSOD and dump.

Use it like you normally do.

 

I havent had any bsod's yet, But my gpu temperature did go up a bit. Is this due to driver verifier or could it be related?

 

No, verifier does not put any additional load on the GPU.

You have a NVIDIA GeForce GTX 980 Ti. All I can suggest is check to make sure the fan(s) are turning properly and the airflow inside the case is good.

 

I have a scythe fuma cpu cooler which blocks all airflow.

The gpu is not dusty and I have my fans at 100% which is noticeable about. Maybe it's broken.

 

Hello Ztruker,

So today I had a bsod again and im hoping you can tell me why

Attachment 137229

 

Dump shows a
Code: BugCheck 3B, {c0000005, fffff80364a7e2af, ffffcc8053cceab0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+3ff )[/quote] Code: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80364a7e2af, Address of the instruction which caused the bugcheck Arg3: ffffcc8053cceab0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.[/quote] In the thread trace I see this:
Code: ffffcc80`53cce108 fffff80b`67367d67*** WARNING: Unable to verify timestamp for e2xw10x64.sys *** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys e2xw10x64+0x7d67[/quote] This belongs to your Killer E2400 Gigabit Ethernet Controller dated 14/09/2016. You could check to see if there is a newer version available: Support