Windows 10: Analyze my dump file and identify the BSOD problem

Pls, anyone can analyze my dump file to indentify wht the problem is?Thxdump file link download: https://drive.google.com/file/d/1BUmmEoEu4nE88M5haMdPchHzdenYRcKx/view?usp=drive_link

:)

 

Help analyzing BSOD dump files - DRIVER_POWER_STATE_FAILURE

Hello,

I have been receiving blue screens of death related to DRIVER_POWER_STATE_FAILURE. I have not been able to identify which driver is causing this and I was wondering if someone would analyze my dump files to gain more information regarding this BSOD error.
The full dump and minidump has been included here: Dump Files – Google Drive

So far I have ran the follow commands but the BSOD still occurs.

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

 

[BSOD] need help for analyze dump file

Hello,

I am having crashing issues when using software that allows control with virtual gamepads. (ParsecSoda) I need help analyzing the DUMP file of the BSOD in question please. Here is the code: DRIVER_IRL_LESS_OR_NOT_EQUAL file: wdf01000.sys. Here the dump file: https://www.mediafire.com/file/ue7bo5brexyos82/Dump_Windows_10.rar/file

I really need to know the source of the problem because the problem being that it can be related to several causes.

 

Need help analyzing dump file.

If your computer crashes, how can you find out what happened, fix the issue and it prevent it from happening again? You may find the small memory dump file useful in this situation. The small memory dump file contains
the smallest amount of useful information that could help you identify why your computer crashed. The memory dump file contains the following information:

• The Stop message, its parameters and other data
• A list of loaded drivers
• The processor context (PRCB) for the processor that stopped
• The process information and kernel context (EPROCESS) for the process that stopped
• The process information and kernel context (ETHREAD) for the thread that stopped
• The Kernel-mode call stack for the thread that stopped

To create a memory dump file, Windows requires a paging file on the boot volume that is at least 2 megabytes (MB) in size. On computers that are running Microsoft Windows 2000, or a later version of Windows, a new memory
dump file is created each time that a computer crash may occur. A history of these files is stored in a folder. If a second problem occurs and if Windows creates a second small memory dump file, Windows preserves the previous file. Windows gives each file
a distinct, date-encoded file name. For example, Mini022900-01.dmp is the first memory dump file that was generated on February 29, 2000. Windows keeps a list of all the small memory dump files in the %SystemRoot%\Minidump folder.

The small memory dump file can be useful when hard disk space is limited. However, because of the limited information that is included, errors that were not directly caused by the thread that was running at the time of
the problem may not be discovered by an analysis of this file.