BSOD - ntoskrl.exe problem, error 0x0000009f

sizza · 17 Apr 2013

Hi
Firstly, many thanks for running this amazing forum! Judging by the number of posts and responses you give, this is a vital service!

So... I assembled PC a few weeks ago using a second hand intel motherboard and i3 but all all else new bits and all seemed ok for several weels but a couple of days the BSOD struck, and has been every day since. According to the minidump report ntoskrl.exe could be the culprit but from reading posts this could be for any number of reasons. I've done a bit of digging, and things that might be helpful are:

- I am using AVG antivirus 2012 free (but it ran with no BSOD for several weeks)
- I did have mismatched memory (2x1GB and 2x2GB) but I'm now (4x2GB) and BSOD has happened again
- I have an OEM version of Windows 7 pro which seemed to be legit. The activation was ok (after a couple of goes)
- I have updated the graphic card driver (geforce gt430) and it was working fine in another PC i built for several months
- BSOD does seem to occur following a recovery from a standby mode.

Many thanks in advance for any help.:)

Northernsoul55 · 17 Apr 2013

Hi,
All your crash dumps point to:

Code:

 
Stop message 0x0000009F Descriptive text: DRIVER_POWER_STATE_FAILURE
Usual cause: A driver is in an inconsistent or invalid power state.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8009ad7060, fffff80000b9c518, fffffa8008ccac10}
*** WARNING: Unable to verify timestamp for MAudioFastTrackUltra.sys
*** ERROR: Module load completed but symbols could not be loaded for 
MAudioFastTrackUltra.sys
Probably caused by : MAudioFastTrackUltra.sys

These drivers need updating:

Faulting driver: MAudioFastTrackUltra.sys
Relates to: M-Audio Fast Track Ultra
Dated: Tue Jan 11 20:12:17 2011
Website: M-Audio Drivers

Faulting Driver: nvlddmkm.sys
Relates to: Nvidia Video Drivers
Dated: Fri Mar 15 01:37:00 2013
Website: Drivers - Download NVIDIA Drivers
(Update to latest driver..Choose Option 2)

The CPU seems to be slightly underclocked, are the settings defaulted?

Code:

 
 
0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i3 CPU         530  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: 2926

Run the following tests and post back any results:

Run SFC to check the integrity of all Windows 7 system files:
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Also please Run chkdsk /f/r in an elevated command prompt.
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
At the command prompt please type: chkdsk /f/r
(Note: there is a space between chkdsk and /f/r)

https://www.sevenforums.com/tutorials/433-disk-check.html

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Tip

Run these tests overnight

Cheers

Dave

sizza · 17 Apr 2013

Wow! Many thanks for your speedy and detailed reply, Dave. I'll update the drivers (indeed my unreliable spidey sense is telling me the M-audio driver is the main culprit!) and run the tests tonight. I will post how i get on.
cheers!
Simon

Northernsoul55 · 17 Apr 2013

Your M-Audio driver was blamed in every crash so your Spidey Sense is correct

Look forward to your feedback.

cheers

Dave

x BlueRobot · 17 Apr 2013

Some manufacturers underclock their CPUs intentionally to avoid crashes.

Northernsoul55 · 17 Apr 2013

Ahh thanks for the info Harry...come across a few of those lately :)

x BlueRobot · 17 Apr 2013

Northernsoul55 said:

Ahh thanks for the info Harry...come across a few of those lately :)

Your welcome Dave :)

sizza · 18 Apr 2013

A quick update! I ran the SFC and chkdsk last night with no reported problems, the first stage of the memory test was still running when I left for work this morning, 4 passes completed with no issues so far.

I got an updated driver for the M-Audio Fast Track Ultra but haven't loaded it yet, i'll do that when the tests are finished (the Windows driver "updater" was lying to me when it said previously that the one i had was the most up to date!) Having said that, i did a bit if digging and it seems this driver doesn't like the sleep/hibernate mode - lots of reports of it crashing when coming out of sleep. M-audio said they would look into it but their advice was to switch off the sleep mode option (not a popular solution judging by people's reactiosn!), and it was not clear from their website whether the latest driver release fixed this. I'll see what happens!

I tried updating the nvidia driver, and the online test (option 2) told me it was the latest driver for my card so i have not investigates that further at the moment.

And I have not done anything to the clocking (not something I have ever attempted) but i did get the motherboard and processor second hand so maybe someone else had played with it? Bluerobot's explanation seems likely though. Is it worth trying to put it back to the max speed? I'm always up for a bit of tweaking if it does not affect stability...

Many thanks again for your help, i'll post another update once i get the new driver installed.
cheers
simon

Northernsoul55 · 18 Apr 2013

Hi
Thanks for the feedback :)
Leave the clocking alone, any clocking will affect system stability. At least until we have cleared your BSOD issue.

Your Nvidia drivers are the latest version 314.22 - WHQL. Your logs also reported this driver is contributing to your BSOD's, we will need try a different driver if your BSOD's continue as i am confident your BSOD's will continue if this issue is not addressed.

Try rolling back the Nvidia driver to the last one:

http://www.vistax64.com/tutorials/165382-device-manager-roll-back-driver.html?ltr=D

Once completed monitor your situation, use the computer as normal, and see if any further BSOD'S persists.
Post back a new log if you do experience a new crash.

Cheers
Dave

sizza · 18 Apr 2013

Hi Dave
Many thanks, i will do that!

cheers
Simon