Share via

Driver Power state failure

Anonymous
2024-03-24T06:54:01+00:00

Just tonight, I started seeing these BSOD codes. I just rebuilt this computer almost from scratch a few months ago apart from the SSD, NVME, and GPU and everything has been running rather well until just now.

The first error pointed to a driver called cpuz158_x64 which I presume came with the CPUz tool and I removed it entirely. The 2nd crash which just happened a few minutes ago, just left a hex code as the driver: (0xfffff804`4f016c30). I am using WhoCrashed to view a basic view on the dmp files, but I could use an expert's help figuring out whats going on here.

Here are the dump files: dmpdump.zip

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-24T08:29:01+00:00

    The information that was posted about the V2 log collector was incorrect.

    The log collector was created to improve the BSOD troubleshooting.

    Initially the DM log collector was used for Windows 7 and 8 and 10.

    Then the V2 log collector was developed to improve the troubleshooting for Windows 10.

    There are thousands of threads with the use of log collectors.

    And there are multiple forums that regularly use log collectors to collect important files to improve the troubleshooting.

    Was this answer helpful?

    0 comments No comments
  2. DaveM121 891.6K Reputation points Independent Advisor
    2024-03-24T08:07:30+00:00

    Collector v2 will just create a collection containing your dump files and a lot of other system information files, it will not produce any other result that would differ from analysing minidump files.

    That cpuz driver usually associated to CPUID or iCUE is known to cause BSOD's

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-03-24T07:49:03+00:00

    I already figured that one out by reading the dump myself but what of the other dmp that was point to the cpuz driver. Seems strange to have 2 drivers go corrupt at the same time.

    Is there any value in running collector v2 for more information?

    I also have to wonder if this is related to my other question on the windows 23H2 update failing due to some kind of driver error.

    Was this answer helpful?

    0 comments No comments
  4. DaveM121 891.6K Reputation points Independent Advisor
    2024-03-24T07:33:35+00:00

    Hi, I am Dave, I will help you with this.

    Your minidump files indicate it is the Bluetooth driver causing your system to crash.

    Go to the support page for your PC, then from there, download and re-install the version of Bluetooth drivers they provide.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-03-24T07:32:54+00:00

    Please run the V2 log collector > post a share link into this thread using one drive, drop box, or google drive

    https://www.tenforums.com/bsod-crashes-debugging/

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    Make sure that share links are available without sign in.

    Was this answer helpful?

    0 comments No comments