Different BSODs in ntoskrnl.exe, (Codes: 0x3b - 0xc5 - 0x124)

Hello!

I am currently experiencing several different BSODs in random intervals. The file BluwScreenViewer points its finger at is ntoskrnl.exe, which, from what i read online, should mean that it's a driver issue.

I still don't know which driver, though. (Or if it actually is a Driver that is at fault here.)

I already did a clean install of the GPU and the Chipset Driver (The Chipset one was probably the culprit that caused my BSODs without any error showing which had me going mad for weeks), ran the windows memory check and tried different security solutions.

I am currently using a paid subscription of Bitdefender Internet Security 2015. Over the last few weeks i switched to Trend Micro and Kaspersky for a couple of days each, just to see if that does anything to improve the situation. (I used special removal tools from the vendors after using any of them and before installing new ones, just to make sure i don't add more problems)

So far, no luck.

I would really appreciate any help here. I don't really know enough about this to narrow it down further.

Collection file with the dmp files attached.

I just ran 1 pass of Memtest and it didn't find any Errors. I will leave it running over night and see if multiple passes run into any problems. Just one question: If i let it run over night and it runs into some trouble, let's say in the 2nd pass and i only notice the next morning after several hours, is there any risk of doing any damage to the PC ?

I usually don't like to leave the PC running over night. Just want to make sure i don't fry anything by accident.

In any case, if memtest doesn't find anything i will enable DV tomorrow and see if i can single out the offending driver.

Thank you for your quick response, Arc!

Alright, i let Memtest run over night for a total of around 15 hours to get the 8 passes and it showed no errors.

First thing i did then was to enable DV and it crashed the System not even 5 minutes after rebooting. Although it showed no errors, this is what happened:





Are there any logs i could post? There are no new dump files, since this wasn't a bluescreen (I think. Usually windows tells me after rebooting from a bsod) so i have no idea where i would look for any logs of this error.

Golden said:

Slyve said:

Are there any logs i could post? There are no new dump files, since this wasn't a bluescreen (I think. Usually windows tells me after rebooting from a bsod) so i have no idea where i would look for any logs of this error.

Have a look in C:\Windows\Minidump for any recent .dmp files.

I did, but the most recent one is the one from yesterday, which is already included in the archive in the first post. The error that occurred today after i enabled DV didn't create any new dump files, unfortunately.

Just in case i am wrong, i am attaching the most recent dump file to this post.

Golden said:

Thats fine.

From your images/photo's, it appears to be a video-related problem. Assuming you have the latest driver, can you check that the video card is free of dust and dirt, and that the fan is spinning.

Can you confirm the temperature of the card at idle using something like HWInfo?

I am using HWInfo already, with all relevant Info provided via the Gadget, the Idle Temperature of the GPU is around 30°C (32°C right now) and at slightly above 60°C while under heavy load.

I just cleaned the whole PC last week. Even then there was little dust. I bought a new tower a couple of months back which seems to be a lot better at keeping dust out than any tower i had before.

The Driver is the most recent that is provided by AMD. I uninstalled it clean with a tool called Dissplay Driver Uninstaller v. 14.0.0.1 in safe mode, rebooted and then installed the most recent one again.

Unless I am missing something, i think the Driver should be working fine.

Edit: Sorry, i got something mixed up, i am not using HWInfo, i am using OpenHardwareMonitor + the Gadget.

Just crashed again with a DRIVER_CORRUPTED_EXPOOL bsod.

Dump file is attached.

From what i read so far, this seems to make it pretty clear that a driver is at fault here, but i am unsure how to proceed. The article i am reading says, if DV fails to pinpoint the driver i should "use the Global Flags utility to enable the special pool by pool tag."

I have no idea what that is. I will read some more and see if i can find something that i can understand, but if someone has some more ideas as to figuring out which driver is banging up my system with tools that aren't as intimidating, I'd be pretty grateful!