Windows 7 BSOD Atapi.sys DRIVER_POWER_STATE_FAILURE (9f)

H0lyD1ver

New Member
This machine had Win XP 32-bit and was running smoothly (no crashes). I ran the compatibility test and it passed and I did a fresh install of Win 7 x64 and now it crashes. Attached are all the dumps and data. Any help would be greatly appreciated.

I've run driver verifier and the latest dump is a result of it crashing while in the Driver Verification mode.

By the way, I tried running RAMMon but both 32-bit and 64-bit version files gave me an error when I tried to run them.
 

Attachments

  • CPUZ.zip
    303.4 KB · Views: 323
  • DAN2014-Tue_08_12_2014_102323_96.zip
    1 MB · Views: 394
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8005823060, fffff80000b9c518, fffff9801c458dc0}

Probably caused by : atapi.sys

Followup: MachineOwner
The above dump file and Bugcheck is the most prolific out of those sent. Only one other (same Bugcheck) mentioned your gpu driver. The Bugcheck tells us that you have a device thats sitting in a IRP for too long and this could be down to system corruption, faulty device or driver.

avgldx64.sys Thu Nov 08 02:24:03 2012: AVG Anti Virus known on occasion to cause the odd issue. Please remove for this period of bugtesting and install MSE as it's far more stable. (you can always re-install AVG later)
http://www.microsoft.com/en-gb/security/pc-security/mse.aspx

viahduaa.sys Mon Mar 28 12:27:35 2011: Via Audio driver. Later 2012 version here:
http://download.viatech.com/DriverDownloadSubmitAjaxSvl

I don't think your system is recognising your GPU correctly because under Dxdiag it has this for your card:

---------------
Display Devices
---------------
Card name: RDPDD Chained DD

Try running the system file checker. Find command prompt, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results.
If it turns up with corruption it couldn't cure then again in a admin command prompt type this:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.
 
Thank you for your response.

I was getting crashes before I installed AVG because I had seen that, so I don't think that's the issue. It was also crashing before I installed the graphics card.

The link to the Via Audio Driver doesn't work.

The SFC test found no violations. I'll reinstall the 7600GS driver.
 
Last edited:
The results from the Checkdisc scan are attached. Microsoft Essentials didn't find anything. I'm downloading the Audio Driver. I'll let you know what I find. 7600GS driver (gfx) has been re-installed.
 

Attachments

  • chkdsk.jpg
    chkdsk.jpg
    125.3 KB · Views: 521
Not to tale Kemical's thread away from him but your name seemed familar.
Just looked it up, I saw you here before:

http://www.sevenforums.com/bsod-help-support/332190-atapi-sys-netio-sys-bsod.html

Ah yes, Seven Forums...
I had a bad experience over there, Thedoctor44, I got banned because of how I debugged.
That's a different story if you're ever interested.
Arc is giving you a hard time I see, quite the attitude.

I'll see if I can be of use.

Could we possibly get a Kernel memory dump?
It'd be more useful.

  1. Go the Start
  2. Right click My Computer
  3. Select Properties
  4. Click Advanced system settings
  5. Click on the Advanced tab
  6. Select Settings under Startup and Recovery
  7. Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

Code:
C:/Windows/memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.
 
I installed the latest audio driver yesterday and when I came in this morning the machine was locked up again (black screen, no response when trying to connect via remote desktop).

Here is a link to the memory.dmp:
https://www.dropbox.com/s/8lbm4g2jhghkp9d/MEMORY.zip

Yeah - I hadn't seen a response over there and then when I posted a new dump (somewhat incorrectly) finally when they did respond it wasn't very helpful.
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8005823060, fffff80000b9c518, fffff9801c458dc0}

Probably caused by : atapi.sys

Followup: MachineOwner

Hi,
H0yD1ver could you run chkdsk again but this time use the GUI method and make sure both boxes are ticked. If you notice your last chkdsk was run without the F parameter which fixes broken sectors and the like.
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

Atapi.sys can also be a target for malware. Try downloading and running Malwarebytes:
https://www.malwarebytes.org/

Could you also post a new dxdiag now you installed the drivers again. Thanks. ( I have feeling it might be connected with the bsod but we'll see)

Please post any new dump files
 
I've been doing a bit of poking around at first it sounded like a disk issue but digging futher into the devices your nvidia driver might be causing problems.

Code:
0: kd> !dpcs
CPU Type      KDPC       Function
3: Normal  : 0xfffff88002fd99e8 0xfffff80002ba4a90 nt!PpmPerfAction
3: Normal  : 0xfffffa8005812118 0xfffff88000c0bf78 ataport!IdePortCompletionDpc
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
3: Normal  : 0xfffffa80061c10c8 0xfffff880111b060c nvlddmkm

Code:
0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)

You have some DPCs which isn't good, I noticed your Nvidia driver was still waiting on a DPC
Despite the fact that the IRQL is at Dispatch/DPC level.

Code:
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`00b9c4c8 fffff800`02af38d2 : 00000000`0000009f 00000000`00000003 fffffa80`05823060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a8e85c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`02a8e6f6 : fffff800`02c34140 00000000`00e98b15 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02a8e5de : 0000022b`ec5c0ad3 fffff800`00b9cc58 00000000`00e98b15 fffff800`02c01528 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a8e3c7 : 000000ae`80fc53c1 000000ae`00e98b15 000000ae`80fc53d7 00000000`00000015 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a7b8ca : fffff800`02bfee80 fffff800`02c0ccc0 00000000`00000000 fffff880`111b060c : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

It seems it has tried to drain the DPC queue but failed to do so.

Code:
0: kd> !irp fffff9801c458dc0
Irp is active with 5 stacks 1 is current (= 0xfffff9801c458e90)
No Mdl: No System Buffer: Thread 00000000:  Irp stack trace. 
     cmd  flg cl Device   File     Completion-Context
>[ 16, 2]   0 e1 fffffa8005823060 00000000 fffff88000e0957c-fffff88000e093c4 Success Error Cancel pending
           \Driver\atapi    ACPI!ACPIDeviceIrpDeviceFilterRequest
            Args: 00000000 00000001 00000004 00000000
[ 16, 2]   0 e1 fffffa80057399b0 00000000 fffff880018f27d0-fffffa8005888cd0 Success Error Cancel pending
           \Driver\ACPI    CLASSPNP!ClasspStartNextPowerIrpCompletion
            Args: 00000000 00000001 00000004 00000000
[ 16, 2]   0 e1 fffffa8005888790 00000000 fffff88000eaff50-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00000000 00000001 00000004 00000000
[ 16, 2]   0 e1 fffffa80058882c0 00000000 00000000-00000000    pending
           \Driver\partmgr
            Args: 00000000 00000001 00000004 00000000
[  0, 0]   0  0 00000000 00000000 00000000-fffffa8006c71c50   

            Args: 00000000 00000000 00000000 00000000

Code:
0: kd> !devstack fffffa80058882c0
  !DevObj           !DrvObj            !DevExt           ObjectName
> fffffa80058882c0  \Driver\partmgr    fffffa8005888410 
  fffffa8005888790  \Driver\Disk       fffffa80058888e0  DR0
  fffffa80057399b0  \Driver\ACPI       fffffa80039c5d50 
  fffffa8005823060  \Driver\atapi      fffffa80058231b0  IdeDeviceP2T0L0-2
!DevNode fffffa800573d900 :
  DeviceInst is "IDE\DiskST3250824A______________________________3.AAH___\5&3731d328&0&0.0.0"
  ServiceName is "disk"

Code:
0: kd> !DevNode fffffa800573d900
DevNode 0xfffffa800573d900 for PDO 0xfffffa8005823060
  Parent 0xfffffa8005726900   Sibling 0xfffffa800573e900   Child 0000000000  
  InstancePath is "IDE\DiskST3250824A______________________________3.AAH___\5&3731d328&0&0.0.0"

Code:
0: kd> !devnode fffffa8005726900
DevNode 0xfffffa8005726900 for PDO 0xfffffa800571b940
  Parent 0xfffffa8005706d90   Sibling 0xfffffa800580ad90   Child 0xfffffa800573d900  
  InstancePath is "PCIIDE\IDEChannel\4&269ed2a3&0&0"

We can see the IRP pending stems from a PCI device which is for your Nvidia card.

Code:
0: kd> lm vm nvlddmkm
start             end                 module name
fffff880`11085000 fffff880`11d8f000   nvlddmkm   (no symbols)          
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Jan 31 07:45:04 2013 (510A2100)
    CheckSum:         00CEDB22
    ImageSize:        00D0A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your driver is very outdated, I suggest you update your driver.
 
I forgot about that...
I didn't check which GPU model you had, the Geforce 7 series are old and don't supply new drivers, given you appear to have the latest driver I can't see it being that.
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8005823060, fffff80000b9c518, fffff9801c458dc0}

Probably caused by : atapi.sys

Followup: MachineOwner

Hi,
H0yD1ver could you run chkdsk again but this time use the GUI method and make sure both boxes are ticked. If you notice your last chkdsk was run without the F parameter which fixes broken sectors and the like.
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

Atapi.sys can also be a target for malware. Try downloading and running Malwarebytes:
https://www.malwarebytes.org/

Could you also post a new dxdiag now you installed the drivers again. Thanks. ( I have feeling it might be connected with the bsod but we'll see)

Please post any new dump files

1. Ran chkdsk: 465 large file records processed, 0 bad file records processed, 34 EA records processed, 76 reparse records processed.
2. Ran Malwarebytes and it didn't find anything.
3. Attached is the new dxdiag.
 

Attachments

  • DxDiag8-18.txt
    24.4 KB · Views: 415
Thanks for that. Your GPU is now appearing correctly in the dxdiag so re-installing the driver must have helped. How is the machine running currently? You haven't posted any dump files although if you do have any always post them as it gives us more to go on.
 
It's still freezing regularly, and when it does that it's not giving me dumps to analyze. I left it on over the weekend, and when I came back I couldn't remote in or get anything to show up when I accessed the workstation's keyboard/mouse.
 
Back
Top