Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, ffffe0011e2fb0e0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2e974 )
Followup: MachineOwner
Hi,
you have a number of different dump files. Some ( 0xC000021A ) were caused by the loss of the user mode subsystem usually caused by mismatched system files, device drivers or third party applications.
Also present was Bugcheck 154 mean an exception in the store was not handled properly leading to a crash.
The above, Bugcheck 7A means data could not be read into memory and a further error code tells us this was because the link to the HDD could be suspect. Unless you have been actually inside your machine I doubt your cables are faulty although we can run some tests to determine either way.
Please run a chkdsk:
Link Removed
All these different issues as well as the date of the machine leads me to believe this could be a compatibility issue with Windows 10. Did you check that your laptop is Windows 10 compatible?
Drivers for laptops are almost always supplied by the manufacture apart from some gpu drivers and I checked the Acer support page for your model, a Acer Aspire 7540 and only Windows 7 drivers are available:
Link Removed
Try running these scans and see if they clear things up a little:
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.
If the bsod's continue try clearing the Store cache by running the app on this solution page:
Solution Details
Ultimately I think you would be better off returning to Windows 7. Can you restore the machine to factory defaults as this might take you back to Windows 7?