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

[Slyve]

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.

 

[Arc]

BugCheck 3B, {c0000005, fffff800030106e6, fffff8800d0a5c90, 0}

[COLOR=Red]Probably caused by : Pool_Corruption[/COLOR] ( nt!ExFreePool+732 )

Followup: Pool_corruption
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not see any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Slyve]

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!

 

[Slyve]

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]

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.

 

[Slyve]

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]

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?

 

[Slyve]

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.

 

[Slyve]

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!

 

[Arc]

Uninstall BitDefender. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

See how it goes.
________________________________

BugCheck C5, {ffffffff, 2, 0, fffff80002fbe9cc}

[COLOR=Red]*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

 

[Slyve]

Uninstall BitDefender. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

See how it goes.
________________________________

BugCheck C5, {ffffffff, 2, 0, fffff80002fbe9cc}

[COLOR=Red]*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

While typing my reply, i just got another bsod which actually cited a BD related .sys file as the cause.

I just renewed my license, but i think it's still better than a broken piece of hardware.

I will remove BD with the Removal tool and see if it gets rid of the problems. Probably gonna torture the system with a round of the verifier again.

Thank you for the help! I will update if the system runs smoothly now or if the problems persist.

Edit: attached the last dump file, so everything related to the problem is here, just in case someone else runs into similar problems later.

Just noticed that the last bsod cited the exact same file you pointed out, Arc. Some part of the BD firewall. I really hope removing that thing altogether will finally end this bsod madness. This is really driving me mad.

 

[Arc]

BugCheck D1, {10, 2, 0, fffff88006c9ea6e}

*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys
[COLOR=Red]Probably caused by : bdfndisf6.sys ( bdfndisf6+ba6e )[/COLOR]

Followup: MachineOwner
---------

Follow the post #10.

 

[Slyve]

So, my PC is running absolutely fine and has been for the last 3 days.

It turns out it was indeed the BitDefender Firewall Driver that drove it into the ground. Combined with an outdated Chipset driver that caused a couple of bluescreens, which made this whole thing so hard to figure out.

When i tried removing BitDefender to see if it causes the BSODs, the Chipset driver continued to cause errors. I figured BD wasn't at fault and reinstalled it since i had a paid license, which had over 300 days left. I only found out about the chipset driver a little later and fixed it. Now it was BD that caused the BSODs and again i thought i still had to identify the real problem.

Now that i have the updated chipset driver AND removed BD, everything is running smooth!

Thank you guys very much for your Help!

 

[Arc]

You are welcome. Let us know for any further BSOD.

 

[Slyve]

You are welcome. Let us know for any further BSOD.

After about 2 weeks without BSODs, i just had one with the Error Code 124 again. This one happened while i was playing a GPU heavy game while streaming my entire screen via Chromecast (I have never done that before and was playing around with it just to see how it performs.) The BSOD occured after about 15-30 Minutes of playing. Can't say for sure because i wasn't really looking at the time when i started playing, so i had to guess)

I attached the dump file. I'd appreciate any help regarding the cause this time, because bluescreenviewer just points it's finger at the ntoskrnl.exe again.

 

[Arc]

Follow it: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

 

[Slyve]

0x124 BSOD. Possibly CPU or GPU related problem.

So, after about 3 different BSODs and some malware related troubles, i dedicded to do a fresh install of windows with just the basics.

I was able to solve 2 BSOD causes (thanks to you guys) before, this reinstall was to get completely rid of the malware (could also have been ad-ware or a virus, i really don't know, it was pretty weird and confusing and stuff just started popping up out of nowhere), just to be safe.

It worked, the only thing left are the 0x124 BSODs, almost exclusively while playing games. Mostly Europa Universalis 4, a very CPU heavy game, so i assume my CPU is the troublemaker. But since i don't have a spare CPU lying around, i can't know for sure and decided to ask here once again.

I'll attach the last 2 dump files. I uploaded them to an online analyzer (since i don't know how to open or interpret them) and it showed something related to "authentic_AMD" or something like that

Since i use both an AMD CPU and GPU, i don't know how to proceed from here.

I really hope it is the CPU, since it still got warranty. If it's the GPU, there's nothing i can do about it right now. Those little *******s are expensive.

Hope you guys know what it is based on the dump files.

 

[Arc]

BugCheck 124, {0, fffffa8007cf0038, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

It means that the AMD CPU reports a Machine Check Exception and nothing more. It may be the CPU, or the GPU or anything and everything that is stated in the guide Stop 0x124 - what it means and what to try ; and so I am asking you ... how far have you followed it from the top? What are the results?

 

[Slyve]

BugCheck 124, {0, fffffa8007cf0038, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

It means that the AMD CPU reports a Machine Check Exception and nothing more. It may be the CPU, or the GPU or anything and everything that is stated in the guide Stop 0x124 - what it means and what to try ; and so I am asking you ... how far have you followed it from the top? What are the results?

Except the last option and the BIOS update, i tried all of it.

I have never overclocked, so that option didn't apply.

Cooling seemed fine (the hottest part was the GPU at 61°C while under constant load. (I don't exactly remember the CPU Temp, but it was definitely below 60.) Tested with The Valley GPU Benchmark ( https://unigine.com/products/valley/ )

Drivers are all completely fresh from the Re-install of windows on Sunday. Directly from the Manufacturers Website (which are Gigabyte for MB Stuff and AMD for GPU Drivers)

I used the Valley Benchmark to test the GPU, HeavyLoad for the CPU and Memtest86 for the Memory (8 Passes over night.) Tested the CPU and GPU for about an hour each. I read up a little about these stress tests and they said that, if the Hardware is going to cave, it will usually do so in the first 15-30 minutes under heavy load.

On Sunday i did the Re-Install, but since i cannot reproduce the issue without the Game installed, i installed the Drivers and the Game that suffers from the Crash (Europa Universalis 4) and the Crash occured again, although kind of randomly. The first day it went fine, the day after that the BSOD happened after about 30 minutes and another one about 60 minutes later.

I also cleaned the complete PC just before i did the re-install. Only thing i couldn't do was the testing with other parts, since i don't own any, unfortunately.

As for the BIOS update, that might be worth a try, but i am a little uncertain about that. I heard that bios updates are tricky and can damage the Board is something goes wrong.

Edit: I just checked on the Gigabyte website and there doesn't appear to be a newer BIOS version for my Board.

 

[Arc]

OK. You have done a lot, but neither of them are the best in their jobs. So please consider to do the tests again.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes. Remember, memtest86 is an inferior tool than memtest86+.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts
​

Also let us know the wattage of the installed PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .