Sometimes DRIVER_POWER_STATE_FAILURE errors like " blue screen"hardware related may be caused by damage random access memory(RAM). If you are experiencing random computer reboots, sound signals when booting or other computer malfunctions (in addition to BSOD errors 0x9F), then it is very likely that there is memory corruption. In fact, almost 10% of application crashes on Windows OS are caused by memory corruption.
If you've recently added new memory to your computer, we recommend temporarily removing it to make sure it's not causing the DRIVER_POWER_STATE_FAILURE error. If this action resolves the BSOD, then this is the source of the problem, and therefore the new memory is either incompatible with some of your hardware or damaged. In this case, you will need to replace new memory modules.
If you did not add new memory, the next step is to run a diagnostic test on your computer's existing memory. A memory test will scan for hard memory failures and intermittent errors that could be causing your 0x9F Blue Screen of Death.
Although latest versions Windows contains a utility for testing RAM, I highly recommend using Memtest86 instead. Memtest86 is a testing tool software BIOS-based, unlike other test programs run in Windows environment. The advantage of this approach is that the utility allows you to check ALL operating memory for DRIVER_POWER_STATE_FAILURE errors, while other programs cannot check memory areas occupied by the program itself, the operating system and other running programs.
This post will help you fix stop error: Driver_power_state_failure in Windows 8 | 7. This particular Blue screen error is also known with a bug check code 9f or 0x0000009f , below are the steps to fix it. The most common cause of this error is out of date driver software of your installed hardware. Another cause is out of date BIOS or a recent change in hardware | Software. DRIVER_STATE_POWER_FAILURE is a blue screen error that occurs when there is a change in power state, i.e. when you shutdown, restart or put your computer to sleep, hibernation etc. So, while this process is running all of the hardware installed in your computer are directed to change their power state to lose power (to shutdown), but when there is a fault in a particular device driver, the corresponding device does not respond as Windows wants it to and hence you face this STOP error.
Here are a few ways that you can fix this BSOD:
Method 1: Updating Driver Software
Alternatively
Method 2: Using Driver Verifier
Before starting this procedure, it is recommended that you create a system restore point , so that you can fall back on it if something goes wrong.
This process will help you pin point the exact driver that might be causing this blue screen error. Remember, if the Driver verifier find an issue your computer might throw a BSOD again. That is why we made a system restore point, so that we can simply run system repair and get the computer to it’s previous state.
For more information on Driver Verifier you can look at this support article by Microsoft
Method 3: Updating BIOS
Updating your Computer’s BIOS is a critical process and need a fair bit of understanding on your part. It is always recommended that you only update your BIOS if highly necessary. Over the years motherboard / Computer manufacturers have made it easier for any user to update the BIOS, but still, it is a difficult process and if not done correctly, can brick your system and make it unusable. So, if you choose to update your BIOS, please do it at your own risk.
If you still face an issue, please write to us using the comments section.
In today's article we will analyze another blue screen, the screen of death - 0x0000009F. This critical failure can manifest itself in operating rooms. Windows systems XP, Vista, Windows 7, Windows Server 2008/2012, Windows 8/8.1 and even Windows 10. In general, no one is immune from this problem.
Typically, the cause of the blue screen of death 0x0000009F is a malfunctioning driver that causes the operating system to become unstable as soon as its power mode changes, for example, when the computer enters sleep or standby mode, when rebooting the PC, and the like.
To the great regret of a huge number of users, such a driver may turn out to be almost any driver in the operating system, which makes finding the “culprit” a rather difficult task. Note, not impossible, but extremely difficult. So, let's see what you can do when you encounter Blue Screen of Death 0x0000009F.
Well, the first solution that we highly recommend you do is update operating system. Installing the latest updates available at the moment can, so to speak, “settle down” the situation on your computer. Update your Windows OS and see if this problem goes away.
Additionally, Microsoft has released several fixes for the error in various situations - check out the list:
If any of the things described suit your case, download and install. Well, if not... well, you’ll have to sweat a little, trying to figure out which driver causes the blue screen of death 0x0000009F. So, we will identify the culprit driver using a long-proven method - using the BlueScreenView program. This program is capable of reading crash dumps generated after blue screens of death and showing users the items that were involved in the incident.
BlueScreenView is free program, so download it from some trusted source and then use it for its intended purpose - no installation required. As soon as you launch BlueScreenView on your computer, you will see something like the following window:
At the top of the window, all available mini memory dumps on your computer will be located in the C:\WINDOWS\MiniDump directory. Of course, your system settings may not be set to create mini-memory dumps, so you will need to go to the program settings and set the C:\WINDOWS\ directory (full and automatic dumps are stored here). As soon as you set the directory, a list with all available dumps will appear at the top of the window.
You need to select one of them - for us it is DRIVER_POWER_STATE_FAILURE - and look at the bottom of the window, in which the elements that caused a critical failure will be highlighted in red. They are often the ones that cause faulty drivers. All you need to do is search the Internet for information on the driver you found and use your findings to further solve the problem. Unfortunately, there is no other way.
We hope that this material helped you in solving the blue screen of death 0x0000009F.
Found a typo? Select the text and press Ctrl + Enter
Today we will look at:
Error code 0x0000009F with an accompanying blue screen may occur on different versions Windows (from XP to “seven” and higher), and the most difficult thing in solving this problem is that there is no single algorithm for solving this problem, so you have to go through all possible options. To make your life easier, we have compiled possible solutions problems when error 9f() in Windows 7 and other versions of this operating system shows its signs, and you need to do something about it.
The main source of this problem is a non-working driver for one of the connected devices. This driver may be installed correctly, however various reasons it could have crashed, causing it to be unable to process incoming requests.
Typically, this occurs when the computer frequently turns off due to network outages or prolonged overload. There are also cases when, during a standard exit from hibernation or sleep modes, error 0x0000009F also made itself felt by the appearance of a blue screen.
If none of these points suits you personally, then follow the further instructions.
As we said earlier, the 9f error problem occurs due to a broken driver. It follows from this that this driver must be replaced with a working version.
The easiest and most effective way to do this is to use special utility to install, remove or update drivers. We recommend that you use the application DriverPack Solution, which is constantly updated, and when analyzing your operating system, finds and flags all drivers that are outdated, broken or missing.
You can learn more about it from our article.
We hope this information was useful to you, and now you understand how to respond to error 9f with blue screen in Windows 7 and more. If you still have or have new questions, ask them in the comments, and we will answer them.
Often error 0x0000009f appears on computers with Windows 7, 8 and 10. In addition to the code on the blue screen of death, there is an indication of DRIVER POWER STATE FAILURE 0x0000009f, which translates as “Power driver failure.” Therefore, knowing the cause of the BSOD, you can fix the blue screen of death with code 0x0000009f on any version of the Microsoft operating system.
The blue screen of death with code 0x0000009f occurs when the computer wakes from sleep mode, as well as when system settings are changed and software is installed that affect the device’s power plan. Therefore, if you encounter the DRIVER POWER STATE FAILURE error and code 0x0000009f, you should familiarize yourself with the following methods to solve it.
In order to fix the DRIVER_POWER_STATE_FAILURE problem, it is worth updating the software responsible for powering the device. Often included with a laptop and motherboard There is software for setting up the power supply. This is ACPI. You need to reinstall or update them.
To do this we do the following:
IMPORTANT! If the blue screen of death appears on a computer and not on a laptop, then in the “Device Manager” you need to open the “Computer” branch. Here we select “ACPI”.
We update or completely reinstall the driver that matches the version and bitness of the operating system.
If the driver has been damaged and you don’t know the reason for this, then you need to first check the system for viruses and then run . To do this we launch command line with Administrator rights and enter the command “sfc /scannow”.
After checking the system for file integrity, you should reboot the system.
Also affects the power supply fast start systems. To change this situation, you need to do the following:
On the official Microsoft forum, they recommend solving BSOD 0x0000009f motherboard(BIOS).
If the methods described above did not help solve the problem, you need to roll back the system to an earlier state when the error had not yet been observed.