Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe00005fec7c0, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
Followup: MachineOwner
Hi,
and it shows a caution bubble for the Reallocated Sectors Count
HDDs keep a certain amount of semi hidden good but unused sectors as spares in case existing ones fail. The above message may mean that these 'spare's are now running low ( 10%)
Is it possible for you to take a screenshot of your SMART data?
Download an app called
Speedfan. Follow the arrows in the screenshot and you can get an online report about the state of your drive. I did mine as an example:
Try running both these scan's ( a number of times if need be) and see if any system corruption is cleaned up:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Something else you could try is to check if it's an actual driver issue by running the Driver verifier. This application will stress drivers on boot up, if a driver does blue screen then the name of said driver will be in the dump file all being well.
First however you will need to make a
Recovery disk/USB for windows 10 .
The reason you need a recovery disk/USB is because the driver verifier can on occasion cause a bsod boot loop. If this occurs you can use the recovery key to boot back into windows and turn the verifier off.
This handy guide by John Griffith is a great help:
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista - Windows Crashes, BSOD, and Hangs Help and Support should I be trying to manually update each old driver individually?
You should be able to spot them in your (what was called) Add and remove programs section.
You will have to use the drivers for Windows 8.1 or at least try and install them. If they prove stubborn try running them in compatibility mode
Sony eSupport - VPCEH12FX - Support I would try and install those SATA drivers at least.
Please post any new dump files.