Error occurred with code 9F
Error occurred with code 9F
Hey there, I posted my files to the Microsoft forums but the person suggested I visit a shop instead. Hopefully you can help me find a solution I’m more comfortable with! I searched for answers to the blue screen code (9f), but haven’t found a fix that works for me. I recently got a new computer and it ran smoothly for a while. Recently, after what might have been a Windows update, I keep seeing these random BSODs. I thought they’d only happen during gaming, but nothing seems to trigger them. I had the issue during an update, with just my desktop open and no program running, and I also experienced it when gaming. Error Code: 9f Important Info: My system is a desktop OS – Windows 11 Education 64-bit, x64 processor, AMD Ryzen 7 7700 8-core, ASUS TUF Gaming graphics card, MSI MAG B650 motherboard, and a CORSAIR RMX power supply. I reinstalled Windows using the media creator and the activation key from my school. The OS was originally mine, and I’ve restored it now. Most components are new (from August 2023), except two old HDDs. My Windows is on a newer NVMe SSD, not an older one. When I reinstalled, I wiped the hard drives completely. I used the original drivers and a BIOS update. I checked for updates and was fully current. I ordered a RAM replacement because I also received code 119. After swapping RAM to 5600MHz, I changed the speed setting after the blue screen appeared. I tried XMP/EXPO but don’t know which option works best. Another thing: when I searched for dump files in “C:/Windows/MiniDump” on Oct 15, there were none – only old files from a few weeks prior. Here’s the link to the drive: https://drive.google.com/drive/folders/1...drive_link. When I ran perfmon /report, it didn’t finish and kept saving for about ten minutes before I went to “C:/PerfLogs” and found the report.html. Thanks for taking the time to read this, Dan!
We focused on the Driver_Power_State_Failure (9F) incidents first. All these issues seem linked to your Seagate Barracuda HDD (ST2000DM008-2FR1 for multiple units). This crash usually stems from a driver problem, though SATA drivers are now outdated and embedded in the OS, increasing hardware vulnerability. The cable might be the culprit too. You can share a report from CDI if needed. The unusual case was a Video_Scheduler_Internal_Error tied to the GPU. If games ran on the HDD, the drive could have frozen, causing DirectX to crash.
Thank you for reviewing my update! Your insights are much more helpful than before. I'm preparing a detailed post to maximize your assistance, so you have more resources at hand. I hadn't considered inspecting my SATA cables yet; I pulled a few from an older machine and it might point to a hardware problem. I plan to replace them with new ones and see if that resolves the issue. All drives reported good health, but if needed, I'll leave this note here. It will expire in a week. I haven't used paste bin before, but I found this link: https://pastebin.com/z3FMAn0A in case you need it. I might have missed details about the other drives, so everything should still be fine unless I repeat the process. Regarding my previous post, I wrote something extensive but didn’t think you’d want to waste time if the problem was limited to the HDD. I’ll ask a few questions though.
1. Can I check for time signatures in minidumps around the crash moments? If yes, did 9F and Video_Scheduler_Internal_Error occur at the same time?
2. If they did happen together, could 9F have triggered Video_Scheduler_Internal_Error? I’m really grateful for your help! I’ll order new cables and mark this as a solution if it fixes the issue after a week of use.
Thanks again!
Dan
The health data isn't consistent because failure thresholds depend on the manufacturer. Previously, a few critical attributes would trigger warnings or bad statuses, but now hundreds appear without any issue. This situation has evolved significantly over time. It's important to identify which parameters should be monitored in the details below. No errors are logged here, and there are no CRC errors, which typically indicate faulty cables. Analyzing data from Backblaze—a company handling thousands of drives—shows around 20% HDD failures with SMART indicators still active. Only one crash occurs at a time. When an error is detected, the system stops completely and displays a BSOD. The only recorded timestamp is the date in the file name. If the drive fails again with another cable, try removing it entirely.
If someone finds this discussion, I deleted my hard drive and it stopped the BSOD. That’s the fix I’m confident about.