积极答复者
WIN Server2012 with Raid expansion 蓝屏问题,Windbg看是arcsas.sys引起的,这个是什么驱动。。

问题
-
请教以下问题。。
1.下面问题蓝屏代码是?
2.arcsas.sys是什么?
3.哪里有windbg解析出测蓝屏代码如何分析的具体资料,如下面显示的栈段及一些地址具体目的是什么?
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0xfffff800`f0683000 PsLoadedModuleList = 0xfffff800`f094da60
Debug session time: Fri Jun 6 10:00:08.036 2014 (UTC - 7:00)
System Uptime: 0 days 0:01:32.707
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {a42ee803, b, 1, fffff88005854c06}
Probably caused by : arcsas.sys ( arcsas!CompleteQueuedRequest+3e )
Followup: MachineOwner
---------
4: 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: 00000000a42ee803, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005854c06, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000a42ee803
CURRENT_IRQL: b
FAULTING_IP:
arcsas!CompleteQueuedRequest+3e
fffff880`05854c06 40886e03 mov byte ptr [rsi+3],bpl
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff880031f3680 -- (.trap 0xfffff880031f3680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa801c14e010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005854c06 rsp=fffff880031f3810 rbp=000000000000000e
r8=00000000a42ee800 r9=fffff880031f35d7 r10=fffff8800585fcbf
r11=fffff880031f34e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
arcsas!CompleteQueuedRequest+0x3e:
fffff880`05854c06 40886e03 mov byte ptr [rsi+3],bpl ds:00000000`00000003=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800f06fd369 to fffff800f06fe040
STACK_TEXT:
fffff880`031f3538 fffff800`f06fd369 : 00000000`0000000a 00000000`a42ee803 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx
fffff880`031f3540 fffff800`f06fbbe0 : 00000000`00000001 fffff880`000000c8 00000000`00000000 fffff880`031f3680 : nt!KiBugCheckDispatch+0x69
fffff880`031f3680 fffff880`05854c06 : 00000000`00000001 fffffa80`1c14e010 fffff880`0585fca0 fffff880`031f35ff : nt!KiPageFault+0x260
fffff880`031f3810 fffff880`05854520 : fffffa80`1c153840 fffff880`031f38a0 00000000`00000000 fffff880`031f35fb : arcsas!CompleteQueuedRequest+0x3e
fffff880`031f3840 fffff880`058548c9 : 00000000`00000100 00000000`00000001 fffff880`0585fb30 00000000`000000cd : arcsas!ResetAndInitializeAdapter+0x2e4
fffff880`031f38e0 fffff880`01916bbf : fffffa80`19d6f8e0 fffff800`f073495d fffffa80`1c07b2c8 fffffa80`1c135ee0 : arcsas!ResetAdapter+0x165
fffff880`031f39f0 fffff880`01910f4a : 00000000`00000000 fffffa80`1c135904 fffffa80`1c29ad90 fffffa80`72536152 : storport!RaCallMiniportResetBus+0x6f
fffff880`031f3a40 fffff880`0192d6d2 : fffffa80`1c135940 fffffa80`1c135940 fffffa80`1c135ee0 00000000`80040081 : storport!RaidAdapterResetBus+0x3e
fffff880`031f3a90 fffff880`01928082 : fffffa80`1c4a06e0 fffff800`00000004 fffffa80`1c4a06e0 00000000`00000001 : storport!RaidUnitHierarchicalReset+0x3e
fffff880`031f3ac0 fffff800`f06e945b : fffffa80`1c4a06e0 00000000`00000000 fffff880`0192801c fffff880`014570d8 : storport!RaidHierarchicalResetWorkRoutine+0x66
fffff880`031f3b10 fffff800`f0736391 : fffff800`f0907080 fffffa80`1912d680 fffff800`f06e93fc fffff800`f0907000 : nt!IopProcessWorkItem+0x5f
fffff880`031f3b80 fffff800`f06a5521 : 00000000`00000000 00000000`00000080 fffff800`f0736250 fffffa80`1912d680 : nt!ExpWorkerThread+0x142
fffff880`031f3c10 fffff800`f06e3dd6 : fffff880`00ec3180 fffffa80`1912d680 fffff880`00ecef40 fffffa80`1916d040 : nt!PspSystemThreadStartup+0x59
fffff880`031f3c60 00000000`00000000 : fffff880`031f4000 fffff880`031ee000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
arcsas!CompleteQueuedRequest+3e
fffff880`05854c06 40886e03 mov byte ptr [rsi+3],bpl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: arcsas!CompleteQueuedRequest+3e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: arcsas
IMAGE_NAME: arcsas.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f677204
BUCKET_ID_FUNC_OFFSET: 3e
FAILURE_BUCKET_ID: AV_arcsas!CompleteQueuedRequest
BUCKET_ID: AV_arcsas!CompleteQueuedRequest
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_arcsas!completequeuedrequest
FAILURE_ID_HASH: {7d8c031a-5355-8b2c-6a8a-30192932fa55}
Followup: MachineOwner
---------
4: kd> lmvm arcsas
start end module name
fffff880`0584d000 fffff880`0586a000 arcsas (pdb symbols) c:\symbols\arcsas.pdb\6D1C44D62ABF44EE9D50D16CFA44D38E1\arcsas.pdb
Loaded symbol image file: arcsas.sys
Image path: \SystemRoot\System32\drivers\arcsas.sys
Image name: arcsas.sys
Timestamp: Mon Mar 19 10:51:00 2012 (4F677204)
CheckSum: 0001EB4B
ImageSize: 0001D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
4: kd> .trap 0xfffff880031f3680
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa801c14e010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005854c06 rsp=fffff880031f3810 rbp=000000000000000e
r8=00000000a42ee800 r9=fffff880031f35d7 r10=fffff8800585fcbf
r11=fffff880031f34e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
arcsas!CompleteQueuedRequest+0x3e:
fffff880`05854c06 40886e03 mov byte ptr [rsi+3],bpl ds:00000000`00000003=??
答案
-
你好,
你可以运行!analyze -show Code来得到蓝屏代码。
arcsas.sys是属于Adaptec产品的Adaptec RAID 控制器驱动文件。
你可以参考下面的文章来使用windows debugger 工具。
Troubleshoot a Windows bluescreen, a.k.a bugcheck, a.k.a blue screen of death
http://blogs.msdn.com/b/ndis/archive/2006/10/26/troubleshoot-a-windows-bluescreen-a-k-a-bugcheck-a-k-a-blue-screen-of-death.aspxInterpreting a Bug Check Code
http://msdn.microsoft.com/en-us/library/windows/hardware/ff547224(v=vs.85).aspx- 已标记为答案 panDavid 2014年6月13日 2:43
全部回复
-
你好,
你可以运行!analyze -show Code来得到蓝屏代码。
arcsas.sys是属于Adaptec产品的Adaptec RAID 控制器驱动文件。
你可以参考下面的文章来使用windows debugger 工具。
Troubleshoot a Windows bluescreen, a.k.a bugcheck, a.k.a blue screen of death
http://blogs.msdn.com/b/ndis/archive/2006/10/26/troubleshoot-a-windows-bluescreen-a-k-a-bugcheck-a-k-a-blue-screen-of-death.aspxInterpreting a Bug Check Code
http://msdn.microsoft.com/en-us/library/windows/hardware/ff547224(v=vs.85).aspx- 已标记为答案 panDavid 2014年6月13日 2:43