Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffffe0016f6b9000, ffffd00027375c60, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )
Followup: MachineOwner
Hi Shinigami,
of the three dump files posted two were bugcheck EF (critical process died) and the above means the Store caught an unexpected exception.. Unfortunately the dumps were rather vague as to what the initial cause could be although os corruption is likely candidate. I'm also not quite convinced your system is windows 10 ready..
my OS is corrupt. I cannot click the windows icon, I cannot uninstall applications, etc. I'm hoping there's a solution that's not "buy/build another computer" or "buy a new os"
If you simply cannot do anything then it's a little difficult to advise you on what to do next, normally I would advice running a set of scans:
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.
I would then suggest running the driver verifier. This is a windows app which will stress drivers on start up to see if any will crash. The only thing is if your going to use this app with Windows 10 you also need to create a recovery disk/USB. The reason you might need this is because sometimes the verifier can cause a bsod start up loop. If this happens you then use the recovery disk/USB to boot from, enter safe mode and turn the verifier off. The driver responsible should hopefully be caught in the dump file.
Recovery disk/USB:
Creating a recovery drive - Windows Help -
Guide on using Driver verifier:
How do I fix a Blue Screen in Windows using Driver Verifier?
Now the trouble is your system is unresponsive so you might not be able to do the things i suggested. In this case would suggest either trying system restore and go back to a time when things worked or try a RESET.
How to Reset Your Windows 10 PC
If that still fails to work then I'd consider going back to Windows 7 or you could try a clean install of Windows 10? You'll need to download the iso and burn it to either disk or USB:
Link Removed
Don't worry about activation as it will activate automatically.
Post any new dump files.
with your issue!
