G
gazdgls
Hi,
My laptop has been crashing, randomly but frequently, with "Something went wrong with your PC" for some time now and the consistent event log is 6008: The previous system shutdown at 09:03:17 on 22/02/2020 was unexpected.
The thing is; there was no shut down at 9:03, the laptop was running fine, as far as I could tell, and there aren't any logs for that time.
This first started after the December Windows updates, eventually I reinstalled windows and it was fairly stable until the January updates. That time I got away with just restoring back to before the update but in since February it's been much worse.
I've just done a complete PC reset, files and all, and even that crashed a few times in the windows set up configuration.
It has crashed in safe mode but as the problem is intermittant under normal start up it is difficult to really debug.
I only charge it when shut down and have scanned the disks, run clean-up software, driver updates (Drive Booster, which also crashes) so I guess it's hardware and will take it to the shop next week.
I just wanted to know if anyone had seen the specific issue here, where the system seems to be responding to a phantom crash?
I'm running Windows 10 Home 1903, OS build 18362.535 on an Asus UX360CA.
Many thanks,
Gareth
[NB: The other warnings in the image I get a lot of too, but they don't usually cause crashes.
For completness they are:
10016 The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user LAPTOPGAZ\Gaz SID (S-1-5-21-467970153-2783959590-3152162492-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
37: The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.]
Continue reading...
My laptop has been crashing, randomly but frequently, with "Something went wrong with your PC" for some time now and the consistent event log is 6008: The previous system shutdown at 09:03:17 on 22/02/2020 was unexpected.
The thing is; there was no shut down at 9:03, the laptop was running fine, as far as I could tell, and there aren't any logs for that time.
This first started after the December Windows updates, eventually I reinstalled windows and it was fairly stable until the January updates. That time I got away with just restoring back to before the update but in since February it's been much worse.
I've just done a complete PC reset, files and all, and even that crashed a few times in the windows set up configuration.
It has crashed in safe mode but as the problem is intermittant under normal start up it is difficult to really debug.
I only charge it when shut down and have scanned the disks, run clean-up software, driver updates (Drive Booster, which also crashes) so I guess it's hardware and will take it to the shop next week.
I just wanted to know if anyone had seen the specific issue here, where the system seems to be responding to a phantom crash?
I'm running Windows 10 Home 1903, OS build 18362.535 on an Asus UX360CA.
Many thanks,
Gareth
[NB: The other warnings in the image I get a lot of too, but they don't usually cause crashes.
For completness they are:
10016 The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user LAPTOPGAZ\Gaz SID (S-1-5-21-467970153-2783959590-3152162492-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
37: The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.]
Continue reading...