Windows 7 The Horrors of the 0x9f

Arkade

New Member
Hello, I'm getting some rather Annoying Bluescreens now, Specifically the 0x9f. But get this. The driver all the BSODS reference is the kernal.


Dump FileCrash TimeBug Check StringBug Check CodeParameter 1Parameter 2Parameter 3Parameter 4Caused By DriverCaused By AddressFile DescriptionProduct NameCompanyFile VersionProcessorCrash AddressStack Address 1Stack Address 2Stack Address 3Computer NameFull PathProcessors CountMajor VersionMinor VersionDump File Size
112312-17737-01.dmp11/23/2012 11:23:49 AMDRIVER_POWER_STATE_FAILURE0x0000009f00000000`00000003fffffa80`067a5440fffff800`03f02518fffffa80`02d57520ntoskrnl.exentoskrnl.exe+7efc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.17944 (win7sp1_gdr.120830-0333)x64ntoskrnl.exe+7efc0 C:\Windows\Minidump\112312-17737-01.dmp8157601921,960
112412-23166-01.dmp11/24/2012 2:48:21 PMDRIVER_POWER_STATE_FAILURE0x0000009f00000000`00000003fffffa80`06c69060fffff800`026fa518fffffa80`08035010ntoskrnl.exentoskrnl.exe+7efc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.17944 (win7sp1_gdr.120830-0333)x64ntoskrnl.exe+7efc0 C:\Windows\Minidump\112412-23166-01.dmp81576011,036,544


View attachment 112312-17737-01.dmpView attachment 112412-23166-01.dmp
 
Un-install the AICharger app - it's blamed in both BSOD's

Remove RivaTuner/EVGA Precision/MSI Afterburner - it's known to cause BSOD's also.
 
Un-install the AICharger app - it's blamed in both BSOD's

Remove RivaTuner/EVGA Precision/MSI Afterburner - it's known to cause BSOD's also.

I cannot remove Precision as it's 1 never caused a BSOD and 2 is the only way i've forcefully OC'ed both GPU's. Also the Ai charger has been installed for years and never caused an issue so without explanation, i don't see how it could be cauisng the bsods.(other than for example when i enter S3, and Ai Charger is charging the device, and i remove it before waking the PC. It would make sense, so i just shouldn't remove anything using the charger while in S3,)
 
1. How do you know it's never caused BSODs? How do you know it won't cause BSODs in the future?
2. Just for now, uninstall it. You can reinstall it if the problem is fixed.

same applies for the AI charger.
 
1. How do you know it's never caused BSODs? How do you know it won't cause BSODs in the future?
2. Just for now, uninstall it. You can reinstall it if the problem is fixed.

same applies for the AI charger.

I've never had BSOD issues till this week. I Also regularly game on this machine, So i don't want to downclock my GPU's just because we want to guess. I'm going to test my Ai Charger theory and get back to you guys.
 
If a small bit of sewage gets clogged in a drain, no harm done.
If another small bit of sewage gets clogged up in the same place, still no harm done.
BUT
If small bits of sewage KEEP getting clogged up in the same place, A LOT of harm will be done.

Just a suggestion.
 
If a small bit of sewage gets clogged in a drain, no harm done.
If another small bit of sewage gets clogged up in the same place, still no harm done.
BUT
If small bits of sewage KEEP getting clogged up in the same place, A LOT of harm will be done.

Just a suggestion.
i hear ya, but lets try thinking. I don't want to act without an explanation for why? If no one can explain why Precision is causing my BSOD's than why should i remove it. I'd rather farm information and learn why than just remove it without knowledge.
 
It's your system and you're free to do with it what you want.
Good luck to you.
 
Past experience (other BSOD anlalysts) -

remember, minidumps, system info and all that, they're not conclusive. Even if the minidump says "Probably caused by: <something>.exe", it doesn't necessarily mean that <something>.exe is the actual problem - the minidump just says that <something>.exe is most likely the root of the problem. Apply that to this situation - even though it says "caused by: ntoskrnl.exe" it's not necessarily true.

May I also point out:
ntoskrnl.exe gives a variety of errors, so it's not conclusive either.
 
Past experience (other BSOD anlalysts) -

remember, minidumps, system info and all that, they're not conclusive. Even if the minidump says "Probably caused by: <something>.exe", it doesn't necessarily mean that <something>.exe is the actual problem - the minidump just says that <something>.exe is most likely the root of the problem. Apply that to this situation - even though it says "caused by: ntoskrnl.exe" it's not necessarily true.

May I also point out:
ntoskrnl.exe gives a variety of errors, so it's not conclusive either.
I hear ya, but i would have liked someone to be able to try and get me closer to the cause. Whoever said Ai charger was right. I tested my theory and it apparently is the issue, so thank whoever pointed that out. i Also just found it funny that it references the kernel. I'm to used to seeing Nvidia driver crashes. or my cousin famous Paged Fault In Non-Paged Area.
 
Back
Top