BSoD involving 0x000000ef and ntoskrnl.exe

[TheRetroReplay]

I need some serious help, my computer has blue screened 13 times today, I used BlueScreen View to see the issue and they all have a bug check of 0x000000ef and caused by driver ntoskrnl.exe

It happens mostly when loading up programs and applications, I did a RAM check and with Windows Diagnostic Tool and there were no results, ran Scan Disk which found nothing and ran Check Disk too which found nothing

==================================================
Dump File : 090415-20421-01.dmp
Crash Time : 9/4/2015 10:34:14 PM
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffe000`ee1b5840
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14e240
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16463 (th1.150819-1946)
Processor : x64
Crash Address : ntoskrnl.exe+14e240
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090415-20421-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 281,352
Dump File Time : 9/4/2015 10:38:05 PM
==================================================

This is the latest one to happen any and all help will be very much appreciated

For what's inside the computer I have
MotherBoard: Gigabyte GA-78LMT-USB3 (rev. 5.0)
Processor: AMD FX-8320
Graphics Card: AMD Radeon R7 260X
8GB DDR3 of RAM (single stick)

 

[KevinS200]

do you happen to have windows 8.1 by any chance?

 

[TheRetroReplay]

do you happen to have windows 8.1 by any chance?

Yes, I had it before upgrading it to Win 10

 

[KevinS200]

There has been problems with it, go ahead and read this and see if this fixes it for you.
http://www.reviversoft.com/blog/2013/04/critical-process-died/

 

[itmoba]

Given the log dump, I'm about 99% sure that it's a hardware problem. I suggest you use the Inquisitor live-cd to run a thorough test, though another good alternative is the Phoronix live-distribution -- I'm pretty sure that Tom's uses Phoronix (though not the live-cd version).

 

[TheRetroReplay]

Given the log dump, I'm about 99% sure that it's a hardware problem. I suggest you use the Inquisitor live-cd to run a thorough test, though another good alternative is the Phoronix live-distribution -- I'm pretty sure that Tom's uses Phoronix (though not the live-cd version).

That's an issue, I've run hardware diagnostics and everything passes, I've even booted in safe mode and didn't run into issues

 

[itmoba]

Did you run your tests Inquisitor or Phoronix, or have you only used the software that ships with Microsoft Windows?

 

[pjs312]

Given the log dump, I'm about 99% sure that it's a hardware problem. I suggest you use the Inquisitor live-cd to run a thorough test, though another good alternative is the Phoronix live-distribution -- I'm pretty sure that Tom's uses Phoronix (though not the live-cd version).

Unlikely, I've been having this problem too and I don't have any hardware problems. I started having this problem on the 29th and its been happening once a day since then, all the reports of ntoskrnl.exe+14e240 are from the past week with Windows 10.

 

[huynie]

Given the log dump, I'm about 99% sure that it's a hardware problem. I suggest you use the Inquisitor live-cd to run a thorough test, though another good alternative is the Phoronix live-distribution -- I'm pretty sure that Tom's uses Phoronix (though not the live-cd version).

Unlikely, I've been having this problem too and I don't have any hardware problems. I started having this problem on the 29th and its been happening once a day since then, all the reports of ntoskrnl.exe+14e240 are from the past week with Windows 10.

I'm currently troubleshooting the same BSOD. I hope we find a solution.

 

[TheRetroReplay]

Did you run your tests Inquisitor or Phoronix, or have you only used the software that ships with Microsoft Windows?

I used the one that came with Windows, I'm not sure how to get Inquisitor or Phoronix work. Strangely enough I haven't had any issues after that crash, the system has been running fine all day today

 

[johnbl]

put the actual memory dump file on a server and post a link.
All i can see is that a process exited and the address of the process.
A mini dump would help, a kernel memory dump would help a lot.

 

[TheRetroReplay]

put the actual memory dump file on a server and post a link.
All i can see is that a process exited and the address of the process.
A mini dump would help, a kernel memory dump would help a lot.

 

[itmoba]

Okay, never ever give people the actual memory.dmp file. We meant the short dump, not this one. Immediately remove the link as it contains private information about you that you probably don't want others to know. I've notified the moderators to act in the event that you don't first. You don't need to worry about forum violations, as this clearly isn't one. I'm simply trying to protect you.

 

[TheRetroReplay]

Okay, never ever give people the actual memory.dmp file. We meant the short dump, not this one. Immediately remove the link as it contains private information about you that you probably don't want others to know. I've notified the moderators to act in the event that you don't first. You don't need to worry about forum violations, as this clearly isn't one. I'm simply trying to protect you.

Link removed, thanks for letting me know, so where do I find the short dump then?

 

[johnbl]

I think your problem will be from the western digital SCSI driver from 2008 corrupting memory.
I think if you run verifier.exe (see below) it will bugcheck the system at the time of corruption and name the driver.
(or you can update the driver and see if you still have issues)


I would remove your overclock driver
C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014
and reboot the system. The debugger shows some corruptions in files in memory but it could be caused by the overclock driver (or not)

update this driver:
Western Digital SCSI Arcitecture Model (SAM) WDM driver
\SystemRoot\System32\drivers\wdcsam64.sys Wed Apr 16 01:39:08 2008
maybe look here for a update:http://wdc.custhelp.com/app/answers/detail/search/1/a_id/5419#

I would: start cmd.exe as an admin, then run
sfc.exe /scannow
then run
dism.exe /online /cleanup-image /restorehealth

if you don't find any problems, then
start cmd.exe as an admin then run
verifier.exe /standard /all
and reboot your system. This will help check your drivers for certain bugs if it finds any it will bugcheck your system and save then info in the memory dump.


-------------
debugger reports errors in the following files on your system.
these look like .dlls in the c:\windows\system32 directory
the system crashed because it looks like you had a service that created a few hundred threads and overflowed the stack, then tried to transfer
control to some random memory locations.

226 errors : ntdll (7ff8ee2135a0-7ff8ee27d002)
8 errors : KERNEL32 (7ff8ec736760-7ff8ec73676b)
7 errors : sechost (7ff8ec504a21-7ff8ec504a2b)
8 errors : KERNELBASE (7ff8eb73b428-7ff8eb73b433)


machine info:

BIOS Version FA
BIOS Starting Address Segment e000
BIOS Release Date 04/23/2013
Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
Processor Version AMD FX(tm)-8320 Eight-Core Processor
Processor Voltage 90h - 1.6V
External Clock 200MHz
Max Speed 3000MHz
Current Speed 3500MHz

 

[itmoba]

Those are located here: C:\Windows\Minidump\[SOME_FILE_NAME]
They are the same as the one from the original post. What we were asking for were the other crash reports (you said there were 13). I'm sure johnbl misspoke when (s)he asked for the actual file, or that they meant to say that they wanted a link to the file in a private message.

 

[johnbl]

yes, a link to the actual file so I can download the memory dump to my local machine and read the Binary data with my debugger. Put the files on a server like Microsoft onedrive then mark them as public and post a link.

Those are located here: C:\Windows\Minidump\[SOME_FILE_NAME]
They are the same as the one from the original post. What we were asking for were the other crash reports (you said there were 13). I'm sure johnbl misspoke when (s)he asked for the actual file, or that they meant to say that they wanted a link to the file in a private message.

 

[Alikanso]

I solved the problem by uninstalling "intel rapid storage technology" software, It was causing some sort of data management conflict thus resulting in ntoskrnl based crashes/freezes.

I have a Lenovo y500 win10 laptop (upgraded from win8.1). it was freezing frequently (more than 3 times a day) and usually they occur after waking up from sleep. It is more than 1 month now without any freezing, it stopped immediately after the uninstallation.

I hope this was helpful.