Atapi.sys and Netio.sys BSOD.

I'll try that and report back.

Alright - I tried new RAM again and it still crashed. I have a few dumps to analyze.

Below is the analysis of the latest dump (7/24):
BugCheck 9F, {3, fffffa8004c88060, fffff80004000518, fffffa8005920260}

Probably caused by : atapi.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004c88060, Physical Device Object of the stack
Arg3: fffff80004000518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8005920260, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: fffffa8003cbecb0

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000e00000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE: FFFFF80004006FB0

STACK_TEXT:
fffff800`040004c8 fffff800`02b3d8d2 : 00000000`0000009f 00000000`00000003 fffffa80`04c88060 fffff800`04000518 : nt!KeBugCheckEx
fffff800`040004d0 fffff800`02ad885c : fffff800`04000600 fffff800`04000600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04000570 fffff800`02ad86f6 : fffff800`02c7e140 00000000`00610c8f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`040005e0 fffff800`02ad85de : 000000e7`03a62a40 fffff800`04000c58 00000000`00610c8f fffff800`02c4c468 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04000c30 fffff800`02ad83c7 : 00000048`32828fc1 00000048`00610c8f 00000048`32828f52 00000000`0000008f : nt!KiTimerExpiration+0x1be
fffff800`04000cd0 fffff800`02ac58ca : fffff800`02c48e80 fffff800`02c56cc0 00000000`00000000 fffff880`00dcef78 : nt!KiRetireDpcList+0x277
fffff800`04000d80 00000000`00000000 : fffff800`04001000 fffff800`03ffb000 fffff800`04000d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7600.16385

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_image_atapi.sys

FAILURE_ID_HASH: {b0247292-b47c-68ac-304c-7f9dfc271ed4}

Followup: MachineOwner
---------

Here's the analysis of 7/15:
BugCheck 9F, {3, fffffa8003956680, fffff80000b9c518, fffffa8003dcba10}

Probably caused by : atapi.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003956680, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8003dcba10, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: fffffa8003996920

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000e1a000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE: FFFFF80000BA2FB0

STACK_TEXT:
fffff800`00b9c4c8 fffff800`02b388d2 : 00000000`0000009f 00000000`00000003 fffffa80`03956680 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ad385c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`02ad36f6 : fffff800`02c79140 00000000`0023f978 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02ad35de : 00000055`a219a2c8 fffff800`00b9cc58 00000000`0023f978 fffff800`02c47188 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ad33c7 : 0000001a`e16456c1 0000001a`0023f978 0000001a`e1645612 00000000`00000078 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02ac08ca : fffff800`02c43e80 fffff800`02c51cc0 00000000`00000000 fffff880`11d75db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7600.16385

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_image_atapi.sys

FAILURE_ID_HASH: {b0247292-b47c-68ac-304c-7f9dfc271ed4}

Followup: MachineOwner
---------

OH yeah - forgot that step. My bad. Attached is the log.

I ran Windows Driver Verifier and got it to crash again. Here is the resulting dump (and attached. It's really a .dmp but I renamed it .log so I could upload it):

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : atapi.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005823060, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffff9801c458dc0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: fffffa80039b3710

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000fe7000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE: FFFFF80000BA2FB0

STACK_TEXT:
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


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7600.16385

FAILURE_BUCKET_ID: X64_0x9F_VRF_3_IMAGE_atapi.sys

BUCKET_ID: X64_0x9F_VRF_3_IMAGE_atapi.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_vrf_3_image_atapi.sys

FAILURE_ID_HASH: {4bc8c658-c45f-b4db-70cc-6d78491ef9f9}

Followup: MachineOwner

I attached the proper data 2 weeks ago and no one responded. Here it is again with the latest dump.

I am happy to report that I found the problem causing all of my stability issues - we had AVG 2012 and as soon as we updated our server/clients to AVG 2013 - the crashes stopped!

Thank you for all your help and time!