New
#1
BSOD 0xCA_2 on multiple machines
We have multiple users in our environment that have been getting BSOD's with corrupt dump files. They all point to 0xCA_2 and they are not doing anything specific when it happens. We have full dumps enabled so it will take very long to upload/download. I have copied the results of the debugger below. If someone can give me commands to type in, I can post my findings....
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca9670
Debug session time: Mon May 21 09:15:05.809 2012 (UTC - 4:00)
System Uptime: 2 days 23:48:27.005
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck CA, {2, fffffa800be44050, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+262d1 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000002, Invalid PDO
An API which requires a PDO has been called with either an FDO,
a PDO which hasn't been initialized yet (returned to PnP in a
QueryDeviceRelation/BusRelations), or some random piece of
memory.
Arg2: fffffa800be44050, Purported PDO.
Arg3: 0000000000000000, Driver object.
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0xCA_2
DEVICE_OBJECT: fffffa800be44050
DRIVER_OBJECT: fffffa80061f3e10
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b8f2033
MODULE_NAME: iaStor
FAULTING_MODULE: fffff880010f3000 iaStor
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002bae058 to fffff80002ae0c40
STACK_TEXT:
fffff880`033bdbf8 fffff800`02bae058 : 00000000`000000ca 00000000`00000002 fffffa80`0be44050 00000000`00000000 : nt!KeBugCheckEx
fffff880`033bdc00 fffff880`011192d1 : fffffa80`062d7dc0 fffff800`02c812b8 fffffa80`0543d680 fffffa80`053ee1a0 : nt!IoRequestDeviceEjectEx+0x228
fffff880`033bdc50 fffff800`02dd79e3 : fffffa80`053ee050 00000000`00000001 fffffa80`0b4a2170 fffffa80`0543d680 : iaStor+0x262d1
fffff880`033bdc80 fffff800`02aeb001 : fffff800`02c812b8 fffff800`02dd7901 fffffa80`0543d600 fffffa80`09706d50 : nt!IopProcessWorkItem+0x23
fffff880`033bdcb0 fffff800`02d7bfee : 00000000`00000000 fffffa80`0543d680 00000000`00000080 fffffa80`0542b040 : nt!ExpWorkerThread+0x111
fffff880`033bdd40 fffff800`02ad25e6 : fffff880`031d5180 fffffa80`0543d680 fffff880`031dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd80 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd9e0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
iaStor+262d1
fffff880`011192d1 eb27 jmp iaStor+0x262fa (fffff880`011192fa)
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: iaStor+262d1
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xCA_2_iaStor+262d1
BUCKET_ID: X64_0xCA_2_iaStor+262d1
Followup: MachineOwner
---------