Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000ddbc5840, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
Followup: MachineOwner
Hi,
as your probably aware Bugcheck EF means a critical system process died and the dump file is being rather vague as to the actual cause. However after looking through your dump files you do have one or two possible suspects.
Did you know your running RAM from two different manufacturers? Whilst this isn't always a huge problem especially if the timings are the same I would still remove one set and see if it helps any.
I found drivers relating to 'Hardlock' and Aladdin Security systems? If you check the support site you can see driver support seems to have stopped at Vista
Hardlock Downloads
See if removing this application helps with the bsod.
If the bsod continues then run the verifier
In order to run the verifer you will also need a
recovery disk/USB. This is just in case the verifier causes a blue screen loop on start up. If it does you can then use the recovery disk/usb to boot into the recovery console, enable safe mode and then turn the verifier off. Hopefully by that point the culprit will have been caught and written on the dump file.
Here's a guide on the verifier and it's uses:
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista - Windows Crashes, BSOD, and Hangs Help and Support
Windows 10 looks like it needs updating too. Have you considered trying the Anniversary update?
How to get the Windows 10 Anniversary Update
Post any dumps you might get from the verifier. Any problems post back.