Jump to content

BSOD - Code 9F

Dkob
By Dkob
in Troubleshooting
 Share
Go to solution Solved by Bjoolz,
3 hours ago, Dkob said:

All of the drives said they had good health, but if you need it I will leave this here. It is going to expire in a week.

I've never used paste bin, but hopefully this link works: https://pastebin.com/z3FMAn0A .

I think I omitted the information on the other drives, so hopefully everything still looks alright, but if I need to do it again I can

The health is unfortunately not reliable as it's up to the manufacturer how much a drive has to fail before it triggers a warning. Where you before would see a single error recorded in certain serious attributes cause a Warning or Bad status, you now could see hundreds without any change. This has been pushed really far over the years. You need to know which parameters to check for in the list below the general information. 

 

There are no errors recorded here. No CRC errors either which is usually what you see with bad cables. Looking at data from Backblaze (Cloud storage company that has gone through thousands of drives), about 20% of HDDs fail with no sign of failure in SMART. 

 

3 hours ago, Dkob said:

With regards to this, I wrote up a huge thing but didn't want to waste your time if the issue was only the HDD and I should just test new SATA cables.

I will ask a couple questions however. 1. Is it possible to see time signatures in the minidumps for when these crashes happened, if so did 9F and Video_Scheduler_Internal_Error happen simultaneously? 2. If they DID happen simultaneously, is it possible that 9F may have caused Video_Scheduler_Internal_Error ?

You can only get one crash at a time. Once one error is reported, everything halts and you BSOD. The only timestamp is the date in the name of the file. 

 

If it still crashes with a different cable then test removing the drive completely. 

Posted

Hey guys,

I tried posting this to the Microsoft forums with the dump files and the guy basically just told me to bring it to a shop... Let's see if you guys can give me an answer I'm more happy with!

 

I've looked around for the solution to this blue screen code (9f), but haven't found one that works for me. Basically, I built a new computer recently and for a month or so it worked without a hitch. Recently (I'm not sure if it was after a certain Windows update), I keep getting these random BSOD. I thought it would only occur while gaming for a while, but nothing specific seems to trigger it. I've got it during a windows update, I've got it with nothing open and just my desktop, and like I said I've got it while gaming.

 

Error Code: 9f

 

Important Information:

  • This computer is a desktop
  • OS - Windows 11 Education
  • 64 bit operating system, x64 based processor
  • CPU - AMD RyzenTM 7 7700 8-Core, 16-Thread Unlocked Desktop Processor
  • GPU - ASUS TUF Gaming NVIDIA GeForce RTXTM 4070 OC Edition Gaming Graphics Card (PCIe 4.0, 12GB GDDR6X, HDMI 2.1, DisplayPort 1.4a)
  • MB - MSI MAG B650 Tomahawk WiFi Gaming Motherboard (AMD AM5, ATX, DDR5, PCIe 4.0, M.2, SATA 6Gb/s, USB 3.2 Gen 2, HDMI/DP, Wi-Fi 6E, AMD Ryzen 7000 Series Desktop Processors)
  • PSU - CORSAIR RMX SeriesTM RM750x 80 Plus Gold Fully Modular ATX Power Supply, 750W
  • RAM - CORSAIR VENGEANCE DDR5 RAM 32GB (2x16GB) 5600MHz CL36 AMD EXPO iCUE Compatible Computer Memory - Gray (CMK32GX5M2B5600Z36)
  • The OS was installed by me, I used the Windows media creation tool and then used the activation key provided by my school
  • This was the original OS and I have reinstalled it once now
  • Most of the hardware is very new (almost everything is from Aug 2023) except for two HDDs that are likely 5+ years old
  • Windows is installed on my newer NVMe SSD not on one of the old HDDs
  • When I reinstalled windows I completely wiped the system hard drives and all
  • System Manufacturer - (I'm not sure what this is asking for exactly) I'm using Windows so Microsoft? Unless you are asking if it is prebuilt. In that case, no I built this myself.

What I have tried so far:

  • Went to the motherboard's manufacturer's website and manually installed all drivers including a BIOS update
  • Checked the windows update center and I am fully up to date
  • I ordered a RAM replacement because at some point I also got code 119. Since the replacement the error code has been exclusively 9f
  • I changed my clock speed of my RAM to 5600 after the blue screen occurred
  • I turned on XMP or EXPO, I forget which one this motherboard offers, but I can figure it out if whoever answers needs that information. I turned this on after the blue screen occurred

Another Interesting Note

When I looked for the dump files in "C:/Windows/MiniDump" from a BSOD yesterday (Oct 15) there were no dump files. The ones I found were from a couple of weeks ago.

 

Link to drive

https://drive.google.com/drive/folders/1jQNmf6DVrnkI57ntzowvMrvzUOuTLQ5r?usp=drive_link 

Note: When I ran perfmon /report it did not ever "finish" the report and let me save so after like 10 minutes I went to "C:/PerfLogs" and got the report.html from there

 

Thanks for anyone who took the time to read this,

Dan

 

Edit: I thought of this just after I posted (and to be honest I'm not sure how helpful it is) but when I get the BSOD the Stop Code is DRIVER_POWER_STATE_FAILURE. Just in case that means anything. I just wanna give as much information as possible about the problem and be done with it! ;(

Link to comment
https://linustechtips.com/topic/1536061-bsod-code-9f/
Share on other sites
Link to post
Share on other sites
Posted

You had one crash that weren't like the others so we'll deal with the Driver_Power_State_Failure (9F) crashes first. They all point to your Seagate Barracuda HDD (ST2000DM008-2FR1 if you have more than one). This crash is often a driver issue, but there aren't really SATA drivers anymore as it's just baked into the OS which makes hardware more likely. Possibly the cable. 

 

You can also provide a report from CDI in case we spot anything wrong with the drive. Use pastebin for the information and link it here.

 

The odd one out was a Video_Scheduler_Internal_Error which is GPU related. If you have games on the HDD it's possible that the drive froze and DirectX crashed. 

 

 

Link to comment
https://linustechtips.com/topic/1536061-bsod-code-9f/#findComment-16170690
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Thanks for taking the time to look through my post! You have already given a much better answer than I have gotten previously.

I'm writing a lot but I want to be as informative as possible with my post so that you have a bit more to work with...

16 hours ago, Bjoolz said:

You had one crash that weren't like the others so we'll deal with the Driver_Power_State_Failure (9F) crashes first. They all point to your Seagate Barracuda HDD (ST2000DM008-2FR1 if you have more than one). This crash is often a driver issue, but there aren't really SATA drivers anymore as it's just baked into the OS which makes hardware more likely. Possibly the cable. 

I've never thought about checking my SATA cables, but I did actually pull a few of these from an old computer from before the time of these drives, so it may be some kind of hardware issue there. I will try getting brand new SATA cables and seeing if that helps.

16 hours ago, Bjoolz said:

You can also provide a report from CDI in case we spot anything wrong with the drive. Use pastebin for the information and link it here.

All of the drives said they had good health, but if you need it I will leave this here. It is going to expire in a week.

I've never used paste bin, but hopefully this link works: https://pastebin.com/z3FMAn0A .

I think I omitted the information on the other drives, so hopefully everything still looks alright, but if I need to do it again I can.

16 hours ago, Bjoolz said:

The odd one out was a Video_Scheduler_Internal_Error which is GPU related. If you have games on the HDD it's possible that the drive froze and DirectX crashed. 

With regards to this, I wrote up a huge thing but didn't want to waste your time if the issue was only the HDD and I should just test new SATA cables.

I will ask a couple questions however. 1. Is it possible to see time signatures in the minidumps for when these crashes happened, if so did 9F and Video_Scheduler_Internal_Error happen simultaneously? 2. If they DID happen simultaneously, is it possible that 9F may have caused Video_Scheduler_Internal_Error ?

 

I am incredibly thankful for the time you have spent on this! I will order the new SATA cables and if I do not get the issue for a week of use, I will mark your reply as the solution. Thanks again.

- Dan

Link to comment
https://linustechtips.com/topic/1536061-bsod-code-9f/#findComment-16171474
Share on other sites
Link to post
Share on other sites
Posted
  • Solution
3 hours ago, Dkob said:

All of the drives said they had good health, but if you need it I will leave this here. It is going to expire in a week.

I've never used paste bin, but hopefully this link works: https://pastebin.com/z3FMAn0A .

I think I omitted the information on the other drives, so hopefully everything still looks alright, but if I need to do it again I can

The health is unfortunately not reliable as it's up to the manufacturer how much a drive has to fail before it triggers a warning. Where you before would see a single error recorded in certain serious attributes cause a Warning or Bad status, you now could see hundreds without any change. This has been pushed really far over the years. You need to know which parameters to check for in the list below the general information. 

 

There are no errors recorded here. No CRC errors either which is usually what you see with bad cables. Looking at data from Backblaze (Cloud storage company that has gone through thousands of drives), about 20% of HDDs fail with no sign of failure in SMART. 

 

3 hours ago, Dkob said:

With regards to this, I wrote up a huge thing but didn't want to waste your time if the issue was only the HDD and I should just test new SATA cables.

I will ask a couple questions however. 1. Is it possible to see time signatures in the minidumps for when these crashes happened, if so did 9F and Video_Scheduler_Internal_Error happen simultaneously? 2. If they DID happen simultaneously, is it possible that 9F may have caused Video_Scheduler_Internal_Error ?

You can only get one crash at a time. Once one error is reported, everything halts and you BSOD. The only timestamp is the date in the name of the file. 

 

If it still crashes with a different cable then test removing the drive completely. 

Link to comment
https://linustechtips.com/topic/1536061-bsod-code-9f/#findComment-16171620
Share on other sites
Link to post
Share on other sites
Posted
  • Author
22 hours ago, Bjoolz said:

If it still crashes with a different cable then test removing the drive completely. 

Well that didn't take very long... Ordered a brand new cable and it crashed with the Driver_Power_State_Failure (9F) error again. Going to try to just remove both my hard drives and see if I encounter it again. Just figured I would update this thread.

Link to comment
https://linustechtips.com/topic/1536061-bsod-code-9f/#findComment-16172756
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×