The Horrors of the 0x9f

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


[TABLE]
[TR="bgcolor: E0E0E0"]
[TH]Dump File[/TH]
[TH]Crash Time[/TH]
[TH]Bug Check String[/TH]
[TH]Bug Check Code[/TH]
[TH]Parameter 1[/TH]
[TH]Parameter 2[/TH]
[TH]Parameter 3[/TH]
[TH]Parameter 4[/TH]
[TH]Caused By Driver[/TH]
[TH]Caused By Address[/TH]
[TH]File Description[/TH]
[TH]Product Name[/TH]
[TH]Company[/TH]
[TH]File Version[/TH]
[TH]Processor[/TH]
[TH]Crash Address[/TH]
[TH]Stack Address 1[/TH]
[TH]Stack Address 2[/TH]
[TH]Stack Address 3[/TH]
[TH]Computer Name[/TH]
[TH]Full Path[/TH]
[TH]Processors Count[/TH]
[TH]Major Version[/TH]
[TH]Minor Version[/TH]
[TH]Dump File Size[/TH]
[/TR]
[TR]
[TD="bgcolor: #FFFFFF"]112312-17737-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]11/23/2012 11:23:49 AM[/TD]
[TD="bgcolor: #FFFFFF"]DRIVER_POWER_STATE_FAILURE[/TD]
[TD="bgcolor: #FFFFFF"]0x0000009f[/TD]
[TD="bgcolor: #FFFFFF"]00000000`00000003[/TD]
[TD="bgcolor: #FFFFFF"]fffffa80`067a5440[/TD]
[TD="bgcolor: #FFFFFF"]fffff800`03f02518[/TD]
[TD="bgcolor: #FFFFFF"]fffffa80`02d57520[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe+7efc0[/TD]
[TD="bgcolor: #FFFFFF"]NT Kernel & System[/TD]
[TD="bgcolor: #FFFFFF"]Microsoft® Windows® Operating System[/TD]
[TD="bgcolor: #FFFFFF"]Microsoft Corporation[/TD]
[TD="bgcolor: #FFFFFF"]6.1.7601.17944 (win7sp1_gdr.120830-0333)[/TD]
[TD="bgcolor: #FFFFFF"]x64[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe+7efc0[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]C:\Windows\Minidump\112312-17737-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]8[/TD]
[TD="bgcolor: #FFFFFF"]15[/TD]
[TD="bgcolor: #FFFFFF"]7601[/TD]
[TD="bgcolor: #FFFFFF"]921,960[/TD]
[/TR]
[TR]
[TD="bgcolor: #FFFFFF"]112412-23166-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]11/24/2012 2:48:21 PM[/TD]
[TD="bgcolor: #FFFFFF"]DRIVER_POWER_STATE_FAILURE[/TD]
[TD="bgcolor: #FFFFFF"]0x0000009f[/TD]
[TD="bgcolor: #FFFFFF"]00000000`00000003[/TD]
[TD="bgcolor: #FFFFFF"]fffffa80`06c69060[/TD]
[TD="bgcolor: #FFFFFF"]fffff800`026fa518[/TD]
[TD="bgcolor: #FFFFFF"]fffffa80`08035010[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe+7efc0[/TD]
[TD="bgcolor: #FFFFFF"]NT Kernel & System[/TD]
[TD="bgcolor: #FFFFFF"]Microsoft® Windows® Operating System[/TD]
[TD="bgcolor: #FFFFFF"]Microsoft Corporation[/TD]
[TD="bgcolor: #FFFFFF"]6.1.7601.17944 (win7sp1_gdr.120830-0333)[/TD]
[TD="bgcolor: #FFFFFF"]x64[/TD]
[TD="bgcolor: #FFFFFF"]ntoskrnl.exe+7efc0[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]C:\Windows\Minidump\112412-23166-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]8[/TD]
[TD="bgcolor: #FFFFFF"]15[/TD]
[TD="bgcolor: #FFFFFF"]7601[/TD]
[TD="bgcolor: #FFFFFF"]1,036,544[/TD]
[/TR]
[/TABLE]


View attachment 112312-17737-01.dmp View attachment 112412-23166-01.dmp
 


#3
http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html

Please use the above link to submit a BSOD report - the minidumps dont tell us much.

Thanks!
Program Spewed Errors, but this is the results(nice to know it uses the current drive, not my C drive D:)

View attachment W7F_24-11-2012.zip
 


usasma

Fantastic Member
Microsoft Community Contributor
#4
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.
 


#5
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,)
 


GeneralHiningII

Honorable Member
#6
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.
 


#7
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.
 


GeneralHiningII

Honorable Member
#8
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.
 


#9
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.
 


usasma

Fantastic Member
Microsoft Community Contributor
#10
It's your system and you're free to do with it what you want.
Good luck to you.
 


#11
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.
 


#12
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.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.