BSOD when opening firefox error 0x000000d1

[Brett636]

I am getting this BSOD error when attempting to open firefox or applications such as chkdsk. The error code is as follows

0x000000d1 (0000000000000000, 0000000000000000A, 00000000000000008,00000000000000000) The two middle codes may be switched as I am typing this off of memory. Anyways, the system will boot fine, but will eventually hang if you leave it alone long enough in normal mode. In safe mode the computer lasts longer, but over time you can only move the mouse and attempting to open any files or even click the start button will get you no where. When attempting to open my firefox browser the system will hang up and the BSOD will appear in both safe mode and normal mode. I can post this through Google Chrome only. The system specs are as follows:

AMD Phenom II X6
Asus MOBO M4A89TD Pro/USB3
4 GB memory
dual sapphire radeon HD5770 video cards in a crossfire setup
2 WD 600GB Velocirpator HD in Raid 0 setup


So far I have removed one of the video cards, and reinstalled the video drivers, allowed memtest86+ to run for nearly 24 hours with no errors. Attempted to run chkdsk, malwarebytes, and combofix.exe to fix a google redirect virus issue, and everytime the system either hangs or I get the BSOD error listed above. If I have forgotten anything or if some other information is necessary please don't hesitate to ask. I will post the remaining information that i have gathered by following the BSOD posting guidelines, but I was not able to generate a system health report. Probably because to post this I had to run in safemode to get the computer to run long enough to get this post written out and the dump information gathered.

I appreciate any and all help I can get with this issue and look forward to resolving it quickly!

 

[Brett636]

I was able to bootup in normal mode and generate the system health report. I am reposting the original zip file in the previous post but containing the system health report as well.

 

[writhziden]

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\123111-32573-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`03257e70
Debug session time: Sat Dec 31 11:08:29.390 2011 (UTC - 7:00)
System Uptime: 2 days 15:17:19.670
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a1183c5e74, 0, fffff800030b90d9, 5}

Unable to load image \SystemRoot\system32\drivers\NISx64\1105000.07F\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS

Could not read faulting driver name
Probably caused by : SRTSP64.SYS ( SRTSP64+3764a )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a1183c5e74, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030b90d9, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c20e0
 fffff8a1183c5e74 

FAULTING_IP: 
nt!MmCopyToCachedPage+179
fffff800`030b90d9 410fb601        movzx   eax,byte ptr [r9]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  PING.EXE

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800c1ca090 -- (.trap 0xfffff8800c1ca090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f8a0094630100400 rbx=0000000000000000 rcx=0000007ffffffff8
rdx=fffff98025dc0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030b90d9 rsp=fffff8800c1ca220 rbp=fffff8800c1ca280
 r8=0000098000000000  r9=fffff8a1183c5e74 r10=fffff98025dc0000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmCopyToCachedPage+0x179:
fffff800`030b90d9 410fb601        movzx   eax,byte ptr [r9] ds:fffff8a1`183c5e74=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031097a1 to fffff8000308a5c0

STACK_TEXT:  
fffff880`0c1c9f28 fffff800`031097a1 : 00000000`00000050 fffff8a1`183c5e74 00000000`00000000 fffff880`0c1ca090 : nt!KeBugCheckEx
fffff880`0c1c9f30 fffff800`030886ae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40d4b
fffff880`0c1ca090 fffff800`030b90d9 : fffff6fc`c0325638 fffff800`030b65fe 00000000`00000ffc fffff880`0c1ca270 : nt!KiPageFault+0x16e
fffff880`0c1ca220 fffff800`030b658e : fffff980`25dc0000 fffff8a1`183c5e74 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x179
fffff880`0c1ca410 fffff800`030b62f4 : fffffa80`097d9010 fffff8a1`183c5e74 fffff880`0c1ca550 00000000`0000018c : nt!CcMapAndCopyInToCache+0x20e
fffff880`0c1ca500 fffff880`012bd098 : 00000000`0004018c fffffa80`0898a700 fffff880`0c1ca5f0 fffffa80`0004018c : nt!CcCopyWrite+0x194
fffff880`0c1ca590 fffff880`010a2132 : fffffa80`0898a7f0 fffff880`010a5732 fffff880`0004018c 00000000`00040101 : Ntfs!NtfsCopyWriteA+0x208
fffff880`0c1ca780 fffff880`010a5c2a : fffff880`0c1ca850 fffffa80`0f024d78 fffff8a1`183c5e00 00000000`00040100 : fltmgr!FltpPerformFastIoCall+0xf2
fffff880`0c1ca7e0 fffff880`010c37fe : 00000000`0004018c 00000000`00000000 fffffa80`0898a7f0 fffff880`0c1ca950 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0c1ca820 fffff800`0339e68e : fffffa80`0898a864 00000000`00000000 fffffa80`04ed8de0 fffffa80`0898a864 : fltmgr!FltpFastIoWrite+0x1ce
fffff880`0c1ca8c0 fffff800`03089813 : fffff8a1`183c5e00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad
fffff880`0c1ca9c0 fffff800`03085db0 : fffff880`02c6764a 00000000`00000010 00000000`00000086 fffff880`0c1cabf8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c1cabc8 fffff880`02c6764a : 00000000`00000010 00000000`00000086 fffff880`0c1cabf8 fffff8a0`145f1e50 : nt!KiServiceLinkage
fffff880`0c1cabd0 00000000`00000010 : 00000000`00000086 fffff880`0c1cabf8 fffff8a0`145f1e50 fffff880`0c1cac20 : SRTSP64+0x3764a
fffff880`0c1cabd8 00000000`00000086 : fffff880`0c1cabf8 fffff8a0`145f1e50 fffff880`0c1cac20 fffff8a1`183c5e74 : 0x10
fffff880`0c1cabe0 fffff880`0c1cabf8 : fffff8a0`145f1e50 fffff880`0c1cac20 fffff8a1`183c5e74 00000000`0004018c : 0x86
fffff880`0c1cabe8 fffff8a0`145f1e50 : fffff880`0c1cac20 fffff8a1`183c5e74 00000000`0004018c fffff8a0`145f1ea0 : 0xfffff880`0c1cabf8
fffff880`0c1cabf0 fffff880`0c1cac20 : fffff8a1`183c5e74 00000000`0004018c fffff8a0`145f1ea0 00000000`00000000 : 0xfffff8a0`145f1e50
fffff880`0c1cabf8 fffff8a1`183c5e74 : 00000000`0004018c fffff8a0`145f1ea0 00000000`00000000 00000000`00000086 : 0xfffff880`0c1cac20
fffff880`0c1cac00 00000000`0004018c : fffff8a0`145f1ea0 00000000`00000000 00000000`00000086 fffff880`00000005 : 0xfffff8a1`183c5e74
fffff880`0c1cac08 fffff8a0`145f1ea0 : 00000000`00000000 00000000`00000086 fffff880`00000005 00000000`0000002b : 0x4018c
fffff880`0c1cac10 00000000`00000000 : 00000000`00000086 fffff880`00000005 00000000`0000002b fffff8a0`1d291b60 : 0xfffff8a0`145f1ea0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SRTSP64+3764a
fffff880`02c6764a ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  SRTSP64+3764a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SRTSP64

IMAGE_NAME:  SRTSP64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4b160164

FAILURE_BUCKET_ID:  X64_0x50_SRTSP64+3764a

BUCKET_ID:  X64_0x50_SRTSP64+3764a

Followup: MachineOwner
---------
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\010712-21637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0241e000 PsLoadedModuleList = 0xfffff800`0265be70
Debug session time: Sat Jan  7 08:30:06.032 2012 (UTC - 7:00)
System Uptime: 0 days 0:09:36.532
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026c60e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800038b3320 -- (.trap 0xfffff800038b3320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80051b0730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800038b34b8 rbp=0000000000063062
 r8=0000000000000000  r9=fffffa80051b03c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000248db29 to fffff8000248e5c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`038b34b8 fffff880`01949955 : fffff800`0260b080 fffff800`02616c40 fffffa80`04f94600 fffff880`0199ef24 : 0x0
fffff800`038b34c0 fffff800`0260b080 : fffff800`02616c40 fffffa80`04f94600 fffff880`0199ef24 fffffa80`051b0730 : ahcix64s+0x4955
fffff800`038b34c8 fffff800`02616c40 : fffffa80`04f94600 fffff880`0199ef24 fffffa80`051b0730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`038b34d0 fffffa80`04f94600 : fffff880`0199ef24 fffffa80`051b0730 00000028`00000000 fffff800`0260b080 : nt!KiInitialThread
fffff800`038b34d8 fffff880`0199ef24 : fffffa80`051b0730 00000028`00000000 fffff800`0260b080 fffff800`02616c40 : 0xfffffa80`04f94600
fffff800`038b34e0 fffff880`01996228 : fffffa80`04f94600 00000000`00000001 00000000`00000000 00000000`00000002 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`038b3510 fffff800`0249a12e : fffff800`038b3600 00000000`00000002 00000000`00000000 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`038b3570 fffff800`02499c76 : fffffa80`04f94b30 00000000`0000905c 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`038b35e0 fffff800`0249a34e : 00000001`57a3eca3 fffff800`038b3c58 00000000`0000905c fffff800`0260be08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`038b3c30 fffff800`02499b57 : fffff800`02608ec1 fffffa80`0000905c fffffa80`03ff7060 00000000`0000005c : nt!KiTimerExpiration+0x1be
fffff800`038b3cd0 fffff800`02496d8a : fffff800`02608e80 fffff800`02616c40 00000000`00000000 fffff880`00da14c0 : nt!KiRetireDpcList+0x277
fffff800`038b3d80 00000000`00000000 : fffff800`038b4000 fffff800`038ae000 fffff800`038b3d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff800038b3320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`01949955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\010912-28594-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`0328fe70
Debug session time: Mon Jan  9 12:53:23.766 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:51.685
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa0e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800044ab320 -- (.trap 0xfffff800044ab320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8005206730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044ab4b8 rbp=0000000000076113
 r8=0000000000000000  r9=fffffa80052063c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c1b29 to fffff800030c25c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`044ab4b8 fffff880`0196a955 : fffff800`0323f080 fffff800`0324ac40 fffffa80`04fea600 fffff880`01809f24 : 0x0
fffff800`044ab4c0 fffff800`0323f080 : fffff800`0324ac40 fffffa80`04fea600 fffff880`01809f24 fffffa80`05206730 : ahcix64s+0x4955
fffff800`044ab4c8 fffff800`0324ac40 : fffffa80`04fea600 fffff880`01809f24 fffffa80`05206730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`044ab4d0 fffffa80`04fea600 : fffff880`01809f24 fffffa80`05206730 00000028`00000000 fffff800`0323f080 : nt!KiInitialThread
fffff800`044ab4d8 fffff880`01809f24 : fffffa80`05206730 00000028`00000000 fffff800`0323f080 fffff800`0324ac40 : 0xfffffa80`04fea600
fffff800`044ab4e0 fffff880`01801228 : fffffa80`04fea600 00000000`00000021 00000000`00000000 fffff800`0323ce80 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`044ab510 fffff800`030ce12e : fffff800`044ab600 00000000`00000000 00000004`40290088 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`044ab570 fffff800`030cdc76 : fffffa80`03f61460 00000000`00004909 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`044ab5e0 fffff800`030ce34e : 00000000`addbbffa fffff800`044abc58 00000000`00004909 fffff800`0323f3a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`044abc30 fffff800`030cdb57 : 00000000`36a226e1 00000000`00004909 00000000`36a226cf 00000000`00000009 : nt!KiTimerExpiration+0x1be
fffff800`044abcd0 fffff800`030cad8a : fffff800`0323ce80 fffff800`0324ac40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`044abd80 00000000`00000000 : fffff800`044ac000 fffff800`044a6000 fffff800`044abd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff800044ab320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`0196a955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\010912-28969-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`03295e70
Debug session time: Mon Jan  9 13:02:03.073 2012 (UTC - 7:00)
System Uptime: 0 days 0:07:38.992
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033000e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff80000b9c320 -- (.trap 0xfffff80000b9c320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8005200730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff80000b9c4b8 rbp=00000000000d1795
 r8=0000000000000000  r9=fffffa80052003c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c7b29 to fffff800030c85c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`00b9c4b8 fffff880`01910955 : fffff800`03245080 fffff800`03250c40 fffffa80`04ff0600 fffff880`01965f24 : 0x0
fffff800`00b9c4c0 fffff800`03245080 : fffff800`03250c40 fffffa80`04ff0600 fffff880`01965f24 fffffa80`05200730 : ahcix64s+0x4955
fffff800`00b9c4c8 fffff800`03250c40 : fffffa80`04ff0600 fffff880`01965f24 fffffa80`05200730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`00b9c4d0 fffffa80`04ff0600 : fffff880`01965f24 fffffa80`05200730 00000028`00000000 fffff800`03245080 : nt!KiInitialThread
fffff800`00b9c4d8 fffff880`01965f24 : fffffa80`05200730 00000028`00000000 fffff800`03245080 fffff800`03250c40 : 0xfffffa80`04ff0600
fffff800`00b9c4e0 fffff880`0195d228 : fffffa80`04ff0600 00000000`00000013 00000000`00000000 fffff800`00b9c768 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`00b9c510 fffff800`030d412e : fffff800`00b9c600 00000000`00000000 00000000`40ee1288 00000000`00000013 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`00b9c570 fffff800`030d3c76 : fffffa80`049ff5b0 00000000`000072ee 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030d434e : 00000001`1194bfc8 fffff800`00b9cc58 00000000`000072ee fffff800`03247048 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030d3b57 : 00000000`55e65ed3 00000000`000072ee 00000000`55e65e18 00000000`000000ee : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030d0d8a : fffff800`03242e80 fffff800`03250c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff80000b9c320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`01910955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\010912-19609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`0329ce70
Debug session time: Mon Jan  9 13:28:33.070 2012 (UTC - 7:00)
System Uptime: 0 days 0:16:11.350
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033070e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800044ab320 -- (.trap 0xfffff800044ab320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80051e7730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044ab4b8 rbp=00000000000d1795
 r8=0000000000000000  r9=fffffa80051e73c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030ceb29 to fffff800030cf5c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`044ab4b8 fffff880`01961955 : fffff800`0324c080 fffff800`03257c40 fffffa80`04fcb600 fffff880`01809f24 : 0x0
fffff800`044ab4c0 fffff800`0324c080 : fffff800`03257c40 fffffa80`04fcb600 fffff880`01809f24 fffffa80`051e7730 : ahcix64s+0x4955
fffff800`044ab4c8 fffff800`03257c40 : fffffa80`04fcb600 fffff880`01809f24 fffffa80`051e7730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`044ab4d0 fffffa80`04fcb600 : fffff880`01809f24 fffffa80`051e7730 00000028`00000000 fffff800`0324c080 : nt!KiInitialThread
fffff800`044ab4d8 fffff880`01809f24 : fffffa80`051e7730 00000028`00000000 fffff800`0324c080 fffff800`03257c40 : 0xfffffa80`04fcb600
fffff800`044ab4e0 fffff880`01801228 : fffffa80`04fcb600 00000000`00000011 00000000`00000000 fffff800`03249e80 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`044ab510 fffff800`030db12e : fffff800`044ab600 00000000`00000000 00000000`403a1288 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`044ab570 fffff800`030dac76 : fffff800`03271290 00000000`0000f339 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`044ab5e0 fffff800`030db34e : 00000002`42f84dab fffff800`044abc58 00000000`0000f339 fffff800`0324c9a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`044abc30 fffff800`030dab57 : 00000000`b5a831d1 00000000`0000f339 00000000`b5a831a2 00000000`00000039 : nt!KiTimerExpiration+0x1be
fffff800`044abcd0 fffff800`030d7d8a : fffff800`03249e80 fffff800`03257c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`044abd80 00000000`00000000 : fffff800`044ac000 fffff800`044a6000 fffff800`044abd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff800044ab320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`01961955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\011012-18517-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e70
Debug session time: Tue Jan 10 12:49:43.810 2012 (UTC - 7:00)
System Uptime: 0 days 0:27:58.090
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  PING.EXE

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800044a3550 -- (.trap 0xfffff800044a3550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80051e7730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044a36e8 rbp=00000000000a7944
 r8=0000000000000000  r9=fffffa80051e73c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c9b29 to fffff800030ca5c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`044a36e8 fffff880`018e9955 : fffff800`03247080 fffffa80`06bec4f0 fffffa80`04fc6600 fffff880`0193ef24 : 0x0
fffff800`044a36f0 fffff800`03247080 : fffffa80`06bec4f0 fffffa80`04fc6600 fffff880`0193ef24 fffffa80`051e7730 : ahcix64s+0x4955
fffff800`044a36f8 fffffa80`06bec4f0 : fffffa80`04fc6600 fffff880`0193ef24 fffffa80`051e7730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`044a3700 fffffa80`04fc6600 : fffff880`0193ef24 fffffa80`051e7730 00000028`00000000 fffff800`03247080 : 0xfffffa80`06bec4f0
fffff800`044a3708 fffff880`0193ef24 : fffffa80`051e7730 00000028`00000000 fffff800`03247080 fffffa80`06bec4f0 : 0xfffffa80`04fc6600
fffff800`044a3710 fffff880`01936228 : fffffa80`04fc6600 00000000`00000002 00000000`00000000 fffff800`03244e80 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`044a3740 fffff800`030d612e : fffff800`044a3830 00000000`00000001 00000000`00000000 00000000`0000003e : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`044a37a0 fffff800`030d5c76 : fffffa80`074e4b70 00000000`0001a431 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`044a3810 fffff800`030d634e : 00000003`e8384848 fffff800`044a3e88 00000000`0001a431 fffff800`032478a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`044a3e60 fffff800`030d5b57 : fffff800`03244ec2 fffffa80`0001a431 fffffa80`049d4060 00000000`00000031 : nt!KiTimerExpiration+0x1be
fffff800`044a3f00 fffff800`030d0705 : 00000000`00000000 fffffa80`06bec4f0 00000000`00000000 fffff880`00d664c0 : nt!KiRetireDpcList+0x277
fffff800`044a3fb0 fffff800`030d051c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`080b61e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  .trap 0xfffff800044a3550 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`018e9955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\011012-19983-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03249e70
Debug session time: Tue Jan 10 12:58:06.829 2012 (UTC - 7:00)
System Uptime: 0 days 0:07:20.749
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b40e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800044ab320 -- (.trap 0xfffff800044ab320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004df5730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044ab4b8 rbp=00000000000891c3
 r8=0000000000000000  r9=fffffa8004df53c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000307bb29 to fffff8000307c5c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`044ab4b8 fffff880`0194a955 : fffff800`031f9080 fffff800`03204c40 fffffa80`04b61600 fffff880`0199ff24 : 0x0
fffff800`044ab4c0 fffff800`031f9080 : fffff800`03204c40 fffffa80`04b61600 fffff880`0199ff24 fffffa80`04df5730 : ahcix64s+0x4955
fffff800`044ab4c8 fffff800`03204c40 : fffffa80`04b61600 fffff880`0199ff24 fffffa80`04df5730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`044ab4d0 fffffa80`04b61600 : fffff880`0199ff24 fffffa80`04df5730 00000028`00000000 fffff800`031f9080 : nt!KiInitialThread
fffff800`044ab4d8 fffff880`0199ff24 : fffffa80`04df5730 00000028`00000000 fffff800`031f9080 fffff800`03204c40 : 0xfffffa80`04b61600
fffff800`044ab4e0 fffff880`01997228 : fffffa80`04b61600 00000000`00000020 00000000`00000000 fffff800`044ab768 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`044ab510 fffff800`0308812e : fffff800`044ab600 00000000`00000000 00000000`405d1288 00000000`0000003d : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`044ab570 fffff800`03087c76 : fffffa80`045725b0 00000000`00006e5c 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`044ab5e0 fffff800`0308834e : 00000001`06b4fe2a fffff800`044abc58 00000000`00006e5c fffff800`031f9e08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`044abc30 fffff800`03087b57 : 00000000`527dace0 00000000`00006e5c 00000000`527dac1c 00000000`0000005c : nt!KiTimerExpiration+0x1be
fffff800`044abcd0 fffff800`03084d8a : fffff800`031f6e80 fffff800`03204c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`044abd80 00000000`00000000 : fffff800`044ac000 fffff800`044a6000 fffff800`044abd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff800044ab320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`0194a955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\011012-21715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02418000 PsLoadedModuleList = 0xfffff800`02655e70
Debug session time: Tue Jan 10 13:09:26.503 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:46.003
Loading Kernel Symbols
...............................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026c00e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff80000b9a320 -- (.trap 0xfffff80000b9a320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004d62730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff80000b9a4b8 rbp=00000000000079e0
 r8=0000000000000000  r9=fffffa8004d623c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002487b29 to fffff800024885c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`00b9a4b8 fffff880`01913955 : fffff800`02605080 fffff800`02610c40 fffffa80`04b0f600 fffff880`01968f24 : 0x0
fffff800`00b9a4c0 fffff800`02605080 : fffff800`02610c40 fffffa80`04b0f600 fffff880`01968f24 fffffa80`04d62730 : ahcix64s+0x4955
fffff800`00b9a4c8 fffff800`02610c40 : fffffa80`04b0f600 fffff880`01968f24 fffffa80`04d62730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`00b9a4d0 fffffa80`04b0f600 : fffff880`01968f24 fffffa80`04d62730 00000028`00000000 fffff800`02605080 : nt!KiInitialThread
fffff800`00b9a4d8 fffff880`01968f24 : fffffa80`04d62730 00000028`00000000 fffff800`02605080 fffff800`02610c40 : 0xfffffa80`04b0f600
fffff800`00b9a4e0 fffff880`01960228 : fffffa80`04b0f600 00000000`00000006 00000000`00000000 fffff800`02602e80 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`00b9a510 fffff800`0249412e : fffff800`00b9a600 00000000`00000000 00000000`40ca2a89 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`00b9a570 fffff800`02493c76 : fffff880`012b60e8 00000000`00001a8b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9a5e0 fffff800`0249434e : 00000000`3f2ee4c6 fffff800`00b9ac58 00000000`00001a8b fffff800`026063e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9ac30 fffff800`02493b57 : fffff800`02602ec6 fffffa80`00001a8b fffffa80`03b72060 00000000`0000008b : nt!KiTimerExpiration+0x1be
fffff800`00b9acd0 fffff800`02490d8a : fffff800`02602e80 fffff800`02610c40 00000000`00000000 fffff880`00d7f4c0 : nt!KiRetireDpcList+0x277
fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff80000b9a320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`01913955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Brett636\Windows_NT6_BSOD_jcgriff2\011112-33197-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0245a000 PsLoadedModuleList = 0xfffff800`02697e70
Debug session time: Wed Jan 11 11:36:25.190 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:36.690
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, a, 8, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800027020e0
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
+6637623833303363
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff800038b3320 -- (.trap 0xfffff800038b3320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004d32730 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800038b34b8 rbp=00000000000854d3
 r8=0000000000000000  r9=fffffa8004d323c8 r10=0000000000000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800024c9b29 to fffff800024ca5c0

FAILED_INSTRUCTION_ADDRESS: 
+6637623833303363
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`038b34b8 fffff880`018b0955 : fffff800`02647080 fffff800`02652c40 fffffa80`04b10600 fffff880`01905f24 : 0x0
fffff800`038b34c0 fffff800`02647080 : fffff800`02652c40 fffffa80`04b10600 fffff880`01905f24 fffffa80`04d32730 : ahcix64s+0x4955
fffff800`038b34c8 fffff800`02652c40 : fffffa80`04b10600 fffff880`01905f24 fffffa80`04d32730 00000028`00000000 : nt!KiInitialPCR+0x2380
fffff800`038b34d0 fffffa80`04b10600 : fffff880`01905f24 fffffa80`04d32730 00000028`00000000 fffff800`02647080 : nt!KiInitialThread
fffff800`038b34d8 fffff880`01905f24 : fffffa80`04d32730 00000028`00000000 fffff800`02647080 fffff800`02652c40 : 0xfffffa80`04b10600
fffff800`038b34e0 fffff880`018fd228 : fffffa80`04b10600 00000000`00000001 00000000`00000000 00000000`00000000 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`038b3510 fffff800`024d612e : fffff800`038b3600 00000000`000025c5 00000000`00000001 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x68
fffff800`038b3570 fffff800`024d5c76 : fffffa80`04b10b30 00000000`0000273c 00000000`00000000 fffffa80`03ba3b60 : nt!KiProcessTimerDpcTable+0x66
fffff800`038b35e0 fffff800`024d634e : 00000000`5d651c17 fffff800`038b3c58 00000000`0000273c fffff800`02647a08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`038b3c30 fffff800`024d5b57 : fffff800`02644ec1 fffff800`0000273c fffffa80`03b72060 00000000`0000003c : nt!KiTimerExpiration+0x1be
fffff800`038b3cd0 fffff800`024d2d8a : fffff800`02644e80 fffff800`02652c40 00000000`00000000 fffff880`00d7f4c0 : nt!KiRetireDpcList+0x277
fffff800`038b3d80 00000000`00000000 : fffff800`038b4000 fffff800`038ae000 fffff800`038b3d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .trap 0xfffff800038b3320 ; kb

FOLLOWUP_IP: 
ahcix64s+4955
fffff880`018b0955 488d4c2420      lea     rcx,[rsp+20h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ahcix64s+4955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ahcix64s

IMAGE_NAME:  ahcix64s.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0f64

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_ahcix64s+4955

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


[/list]

Nearly all caused by your RAID controller. Update the driver for your RAID device ahcix64s.sys.

Once that is done, update to SP1

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
​

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

 

[Brett636]

I went to your link regarding the raid controller driver ahcix64.sys and was unable to come up with a location to download it from. I went to the Asus website and found an updated raid controller driver posted on 2/10/2011 but when i downloaded it the installer was unable to locate my hard drives. Any suggestions?

 

[Brett636]

I was able to get the driver installed, now going to work on getting updated to SP1

 

[writhziden]

I went to your link regarding the raid controller driver ahcix64.sys and was unable to come up with a location to download it from. I went to the Asus website and found an updated raid controller driver posted on 2/10/2011 but when i downloaded it the installer was unable to locate my hard drives. Any suggestions?

Nevermind, see you got the driver installed. What did you do to get it to work in case someone stumbles across this thread and has similar issues?

 

[Brett636]

I went to your link regarding the raid controller driver ahcix64.sys and was unable to come up with a location to download it from. I went to the Asus website and found an updated raid controller driver posted on 2/10/2011 but when i downloaded it the installer was unable to locate my hard drives. Any suggestions?

Nevermind, see you got the driver installed. What did you do to get it to work in case someone stumbles across this thread and has similar issues?

I downloaded the most up to date RAID driver from the Asus website which came in the form of a zip file. Once I extracted the zip file I went to the first executable file I could find which wasn't getting me anywhere. I navigated further into the extracted folders and found a raid driver folder with the very file you linked too which matched my 64 bit windows 7. Along with that file was its own .exe file that I assumed was there to install the driver so I ran it and it went through its normal dialog boxes claiming to be installing the driver. I hope it got it into the right place.

I just finished with the SP1 install and am about to reboot. Lets hope this works!

I appreciate the help!

 

[Brett636]

I am still getting the same BSOD error when running firefox. After the installing SP1 I uninstalled and reinstalled firefox only to get the same problem. I haven't let it sit long enough to see if the system still freezes on its own, but I am going to assume that hasn't changed since the intial firefox browser issue still exists. What is next on the list to look at?

 

[writhziden]

I am still getting the same BSOD error when running firefox. After the installing SP1 I uninstalled and reinstalled firefox only to get the same problem. I haven't let it sit long enough to see if the system still freezes on its own, but I am going to assume that hasn't changed since the intial firefox browser issue still exists. What is next on the list to look at?

I'll need the latest dump files to determine the next course of action. If upgrading the driver did not help, I'm guessing it is an underlying issue causing the problem; it may be the memory even if memtest86+ comes up clean. What kind of memory do you have installed?

You may want to run the extended version of the Windows Memory Diagnostics Tool for at least five passes to see if Memtest86+ missed anything. I recommend letting it run overnight since it can take a long time to complete.

If your computer was working fine up until recently, backup all important data and restore to an earlier point in time using a system restore point by following the instructions in http://www.sevenforums.com/tutorials/700-system-restore.html making sure to pay close attention to the note in 8. of OPTION ONE.

The following site may also be of use as the user who originally posted there had a similar problem. Make sure to backup any important data before resetting anything involving your RAID controller. Blue screen errors kernel, ahcix64s, win32.sys and tcpip.sys in Windows 7

 

[Brett636]

Here is the latest dump file. I will attempt those other suggestions when time allows, and I look forward anything else you can suggest. Thanks again!

 

[writhziden]

Here is the latest dump file. I will attempt those other suggestions when time allows, and I look forward anything else you can suggest. Thanks again!

The dump file still lists the RAID as the cause.

Also, what kind of memory do you have? If you need help getting this information, use HWiNFO64 Download and use Save Report. Save it as an html file and choose where to save it using the Browse button that appears when you click Save Report. Then hit next and finish saving it by following the wizard for Save Report. You can upload the html file on here for us to view and give you further advice.

 

[Brett636]

I don't recall the specific type of memory I purchased when I built the computer. I ran the program from your last post and will include that information here. I ran the windows memory diagnostics for 5 passes in the extended testing mode and it found no errors.

 

[writhziden]

I don't recall the specific type of memory I purchased when I built the computer. I ran the program from your last post and will include that information here. I ran the windows memory diagnostics for 5 passes in the extended testing mode and it found no errors.

The memory is made up of two sticks of G Skill F3-14400CL7-2GBFLS Appears to be fine with your board, however Post #77 may also apply to you.

 

[writhziden]

Your motherboard memory qualified vendors list also supports the above post in a way.

1. Due to CPU spec., AMD 100 and 200 series CPUs support up to DDR3 1066Mhz. With ASUS design, this motherboard can support up to DDR3 1333MHz.
2. When overclocking, some AMD CPU models may not support DDR3 1600 or higher frequency DIMMs.

Might be worth looking into what your CPU supports for frequencies. If you are overclocking, you may be pushing it with your current RAM.

 

[Brett636]

I am not overclocking. Call me a wuss, but when I spent $300(at the time) for a new CPU I wasn't going to risk frying it by overlocking it even though i know it could probably handle some overlocking. As long as it runs my games smoothly I am not interested in squeezing that extra 5 fps when what I experience now works.

 

[writhziden]

I am not overclocking. Call me a wuss, but when I spent $300(at the time) for a new CPU I wasn't going to risk frying it by overlocking it even though i know it could probably handle some overlocking. As long as it runs my games smoothly I am not interested in squeezing that extra 5 fps when what I experience now works.

Couldn't agree more with you. I've never overclocked any of my hardware for the same reason, plus it voids the warranty for most hardware. I think that warning about going above 1333 MHz may still apply even without overclocking for some CPUs based on what Dave76 was saying, which makes sense. If it has issues with a RAM frequency during overclocking, it stands to reason it may also have issues without overclocking on some units.

 

[Brett636]

so I guess my next step is to go back to a system restore point prior to last Sunday since that is when this all began? If the RAID controller is still showing as the issue, but I have updated it (as far as I can tell) to the latest version of the drivers available, what other step regarding the RAID controller can I take?

 

[writhziden]

so I guess my next step is to go back to a system restore point prior to last Sunday since that is when this all began? If the RAID controller is still showing as the issue, but I have updated it (as far as I can tell) to the latest version of the drivers available, what other step regarding the RAID controller can I take?

Backup your important files and try resetting the RAID controller. You may have to do a clean install of Windows afterwards, but hopefully just resetting it will not erase the data. My understanding is that it most likely will, however, which is one of the many reasons RAID is recommended against.

 

[Brett636]

I'm assuming you are referring to going into the RAID controller and deleting my existing array and creating another? If this is the main cause of this issue I am not opposed to doing away with the RAID setup altogether and just running each drive separately, but would I be inviting a whole new host of problems besides having to restore my data by doing that?

 

[writhziden]

I'm assuming you are referring to going into the RAID controller and deleting my existing array and creating another? If this is the main cause of this issue I am not opposed to doing away with the RAID setup altogether and just running each drive separately, but would I be inviting a whole new host of problems besides having to restore my data by doing that?

Do you have a hardware RAID, software RAID, or hybrid RAID? I'm trying to read up on these to determine if removing your RAID setup will cause any issues. This really isn't my forte, so if you want better advice, I would suggest starting a thread in Hardware and Devices asking the same question posed in your previous post.