Proteus V 15.6" - Critical_Process_Died

[666]

Hi all,

I got this laptop in October of last year and so far it has been great!

However I have recently started to experience the Critical_Process_Died message when I shutdown. The machine collects some data and then restarts.

When I start up the Control Center that monitors temperatures, controls keyboard lighting etc, everything looks fine. I am using a cooling which obviously helps. However at times the GPU temperature will jump to 99 and the GPU and CPU usages jump to between 80-90, and it is only when this happens that I receive the error message. I used a different cooling pad at work for about 4 hours this morning with no issues at all. When I used a very similar cooling pad at home the issue was back within a matter of minutes.

I did place a call with Windows and they said it was a Driver Problem with the Display Adapter (GTX 1070 8gb) and suggested rolling back to an older version, which I did not due to having zero problems at work.

It just seems strange that everything has been brilliant and now suddenly this, which seems to have coincided with a Windows update. Is anyone else experiencing this? Could it be the driver (following the Windows Update)? Could it be a problem with the GPU itself and it starting to fail? (Have Gold cover so covered). Something else I have missed?

I'm going to try with the working cooling pad for a few hours tonight and see if the issue comes back.

Any replies/assistance are greatly appreciated.

Regards

 

[ubuysa]

It would be useful to see whether a dump was written by these BSODs, if it is can you post the dump here?

That it seems to work ok at work may be a red herring. To be sure you'd need to use the laptop in exactly the same way at work (so the same applications/games/etc.) as you do at home. If it is a driver issue, and bad/wrong drivers is one of the main causes of this BSOD, then it's entirely possible that the workload mix at work doesn't use the same driver feature that causes the BSOD at home because the workloads are different.

If you suspect a recent Windows update then it's well worth backing that out to confirm whether it was that.

It's also worth checking that the Windows system files and component store are not corrupted in some way. To do that run the two commands one after the other (they both take a while to run).

To check the Windows system files run the command 'sfc /scannow' (without quotes)

To check the component store run the command 'dism /online /cleanup-image /scanhealth' (without quotes).

If either of those report errors found and corrected then you may well be ok. If either report errors found that could not be corrected I would advise a reinstall of Windows and all the drivers.

The first thing to check however is with the workload at work exactly the same as the workload at home. If it doesn't fail at work under exactly the same workload then we'll need to figure out what's different at home. My guess is that the work workload is different enough to not trigger the (probably driver) issue.