Personally I agree with you about 10. But some people love it.
So i just remembered i could check crashlogs and ive got a plethora of reoccurring errors and warnings.
For starters i get the same 4 warnings all in a row at the same time regarding the cpu. (im assuming for each core)
Kernel-Processor-Power (Microsoft-Windows-Kernel-processor-power) event id: 37
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 23 seconds since the last report. (for the other 3 errors instead of saying processor 0, itll say processor 1, 2 etc)
The next thing i get is a critical.
The source is Kernel-Power, event id: 41
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
finally this is the other error i get, this is the one thats quite frequent. other than that, there arent many other errors.
The source is DistributedCOM and the event id 1005
DCOM got error "1084" attempting to start the service dps with arguments "Unavailable" in order to run the server:
Now for the error above, the number slightly changes as does the event number, although the rest of the error is exactly the same.
Sorry to kinda dump this all in one message, any ideas or thoughts? I dug up a little info on the power error. Supposedly thats a power supply issue, that error is exactly when my laptop shut off today. which leads me to believe its my battery thats the issue. even though i said this happened while plugged in as well, its quite possible that it being plugged in is irrelevant because the battery would still be active, just charging. Previously i suspected the battery to be the culprit even before i made this post but i kind of came up with my own conclusion that it was not because after running cfg -energy in CMD nothing checked out wrong for power. But, knowing that upfront diagnostics may not always find the errors behind the problem, i decided to check crash logs. seems like ive got a lot of valuable information here that could determine the exact cause of the shut downs.