📎 AI Summary:
The user "pickle875" inquires about crashes and uploads a dump file for analysis. "Kemical" analyzes the crash, identifying it as likely caused by the "cpuz138_x64.sys" driver, associated with CPU-Z, and suggests uninstalling related system applications. "Pickle875" confirms they have removed CPU-Z, and "Kemical" asks to post new dump files if crashes continue. The overall tone is troubleshooting-focused with a collaborative effort to resolve the issue.
The user "pickle875" inquires about crashes and uploads a dump file for analysis. "Kemical" analyzes the crash, identifying it as likely caused by the "cpuz138_x64.sys" driver, associated with CPU-Z, and suggests uninstalling related system applications. "Pickle875" confirms they have removed CPU-Z, and "Kemical" asks to post new dump files if crashes continue. The overall tone is troubleshooting-focused with a collaborative effort to resolve the issue.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {841ec60, f, 1, fffff8033ffb1b57}
*** WARNING: Unable to verify timestamp for cpuz138_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz138_x64.sys
Probably caused by : cpuz138_x64.sys ( cpuz138_x64+2104 )
Followup: MachineOwnerthis is down to either CPU-z or a third part system application which diagnoses your pc's spec. I can't remember the actual name of the app but it's usually called something like 'Systemcare' or similar. Anyway try removing said app and see if the bsod stops.