Occasional DRIVER_POWER_STATE_FAILURE

Koushirou · 11 Apr 2021

zbook said:

Please post a share link for the memory dump.

Code:

LastWriteTime         Size (MB) FullName             
-------------         --------- --------             
4/11/2021 11:07:23 AM    817.82 C:\WINDOWS\MEMORY.DMP

Perform these steps in sequence:

a) Use the built-in troubleshooter:
In Device Manager, double-click Xbox 360 Controller for Windows.
Select Troubleshoot, and then follow the steps provided.

b) Remove and then redetect the controller:
Right-click Xbox 360 Controller for Windows, and then select Uninstall.
In the Action menu, select Scan for hardware changes.

c) Try updating the driver:
Double-click Xbox 360 Controller for Windows.
On the Driver tab, select Update Driver.

Here's your requested file:
MEMORY.DMP - Google Drive

I'm sorry, I can't find the troubleshooter in Device Manager as you mentioned in first step.
Double clicking Xbox 360 Controller in Device Manager will only show me its properties.
I've done step b & c a few times before though. I'll do it again per your instruction.
I'm starting to feel this is more related to hardware compatibility problem, since this PC quite old.
Or is it possible the gamepad itself that causing driver error?
This one still on warranty so I can ask for replacement..
Thanks!

Koushirou · 25 Apr 2021

zbook said:

Please post a share link for the memory dump.

Code:

LastWriteTime         Size (MB) FullName             
-------------         --------- --------             
4/11/2021 11:07:23 AM    817.82 C:\WINDOWS\MEMORY.DMP

Perform these steps in sequence:

a) Use the built-in troubleshooter:
In Device Manager, double-click Xbox 360 Controller for Windows.
Select Troubleshoot, and then follow the steps provided.

b) Remove and then redetect the controller:
Right-click Xbox 360 Controller for Windows, and then select Uninstall.
In the Action menu, select Scan for hardware changes.

c) Try updating the driver:
Double-click Xbox 360 Controller for Windows.
On the Driver tab, select Update Driver.

Koushirou said:

Here's your requested file:
MEMORY.DMP - Google Drive

I'm sorry, I can't find the troubleshooter in Device Manager as you mentioned in first step.
Double clicking Xbox 360 Controller in Device Manager will only show me its properties.
I've done step b & c a few times before though. I'll do it again per your instruction.
I'm starting to feel this is more related to hardware compatibility problem, since this PC quite old.
Or is it possible the gamepad itself that causing driver error?
This one still on warranty so I can ask for replacement..
Thanks!

Hello,
Just now I've got a BSOD with new message Kernel Security Check Failure.
Below is the log:
VEDA-(2021-04-25_23-21-09).zip - Google Drive

This happened after I'm finished playing games and browse the internet with MS Edge.
To prevent any BSOD, I've always uninstalled the gamepad device after game session. But, I usually postponed the last "Restart to take effect" step.
Its been fine with this method until today.
So, whats with the new BSOD?
Is this still related to the Xbox controller driver? Or more spesifically because I postponed the restart step?
So far I've done the SFC & DISM check with no error found.

Thanks again for your help!

zbook · 25 Apr 2021

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

philc43 · 25 Apr 2021

So, whats with the new BSOD?
Is this still related to the Xbox controller driver? Or more spesifically because I postponed the restart step?
So far I've done the SFC & DISM check with no error found.

This latest crash does not appear to be related to the Xbox Controller. However, if you removed the device but did not restart the system it might leave certain processes running in the background and could lead to the buffer overrun you experienced.

Code:

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

I would try restarting the PC after removing the controller just to tidy up any leftover services that may be running.

Koushirou · 25 Apr 2021

zbook said:

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

Hi,
Thanks, but I'd like to stick with "provide with logs when BSOD happen" method.
I'll reach you when I finally have a spare time and decided to troubleshoot with the driver verifier.

philc43 said:

This latest crash does not appear to be related to the Xbox Controller. However, if you removed the device but did not restart the system it might leave certain processes running in the background and could lead to the buffer overrun you experienced.

Code:

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

I would try restarting the PC after removing the controller just to tidy up any leftover services that may be running.

Hello,
Thank you for the read and analysis!
Yeah, from now on I'll make sure to do a proper reboot after uninstall. Hope this will work well.

Have a good day everyone!