近來郵件主機(Windows Server 2008 R2-Exchange Server 2010)會不定時的發生藍底白字,然後觸發了HP的ASR機制重啟。
雖然最近有更換記憶體,但這問題在更換記憶體前就已經發生。
更換記憶體前後,頻率並沒有甚麼太大的差異。
從產生的DMP解析看來,似乎是HpCISSs2.sys這檔案引起的。GOOGLE了一下,這個檔案應該是Raid用的驅動。
公司有兩台一樣的G7主機,但是用途不一樣,另外一台滿正常的沒甚麼問題。
比較了兩台的HpCISSs2.sys檔案,版本不太一樣。藍白的這台是較為新版的6.28.0.64,正常的這台是6.26.0.64。
目前,想嘗試將該驅動降舊版的,不知道這樣對資料是不是會有問題?
另外,有前輩或朋友有遇到類似的問題嗎?
以下是ASR重啟後,跳出的警告視窗訊息
問題簽章:
問題事件名稱: BlueScreen
作業系統版本: 6.1.7601.2.1.0.272.7
地區設定識別碼: 1028
與問題相關的其他資訊:
BCCode: d1
BCP1: 0000000000000010
BCP2: 000000000000000A
BCP3: 0000000000000000
BCP4: FFFFF8800103CA85
OS Version: 6_1_7601
Service Pack: 1_0
Product: 272_3
以下是DMP檔的解析內容
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: 0000000000000010, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800103ca85, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cc5100
0000000000000010
CURRENT_IRQL: a
FAULTING_IP:
HpCISSs2+5a85
fffff880`0103ca85 498b7520 mov rsi,qword ptr [r13+20h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff800018188c0 -- (.trap 0xfffff800018188c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=00000254dfc703db rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800103ca85 rsp=fffff80001818a50 rbp=fffff88001037000
r8=ffffffffffffffff r9=0000000000000ec8 r10=fffff88001059970
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
HpCISSs2+0x5a85:
fffff880`0103ca85 498b7520 mov rsi,qword ptr [r13+20h] ds:0001:00000000`00000020=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001a893a9 to fffff80001a89e00
STACK_TEXT:
fffff800`01818778 fffff800`01a893a9 : 00000000`0000000a 00000000`00000010 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
fffff800`01818780 fffff800`01a88020 : fffffa80`18e0b148 fffff880`0460da08 fffffa80`3ae7f7a0 fffffa80`18e9c008 : nt!KiBugCheckDispatch+0x69
fffff800`018188c0 fffff880`0103ca85 : fffffa80`18e9c008 fffffa80`18e9c008 fffffa80`21a9d8f0 00000000`00000fbc : nt!KiPageFault+0x260
fffff800`01818a50 fffffa80`18e9c008 : fffffa80`18e9c008 fffffa80`21a9d8f0 00000000`00000fbc fffffa80`37d24060 : HpCISSs2+0x5a85
fffff800`01818a58 fffffa80`18e9c008 : fffffa80`21a9d8f0 00000000`00000fbc fffffa80`37d24060 00000000`00000000 : 0xfffffa80`18e9c008
fffff800`01818a60 fffffa80`21a9d8f0 : 00000000`00000fbc fffffa80`37d24060 00000000`00000000 00000000`00000001 : 0xfffffa80`18e9c008
fffff800`01818a68 00000000`00000fbc : fffffa80`37d24060 00000000`00000000 00000000`00000001 00001f80`00000a04 : 0xfffffa80`21a9d8f0
fffff800`01818a70 fffffa80`37d24060 : 00000000`00000000 00000000`00000001 00001f80`00000a04 fffff800`01818bf0 : 0xfbc
fffff800`01818a78 00000000`00000000 : 00000000`00000001 00001f80`00000a04 fffff800`01818bf0 fffff800`01c07e80 : 0xfffffa80`37d24060
STACK_COMMAND: kb
FOLLOWUP_IP:
HpCISSs2+5a85
fffff880`0103ca85 498b7520 mov rsi,qword ptr [r13+20h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: HpCISSs2+5a85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HpCISSs2
IMAGE_NAME: HpCISSs2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 526e7e66
FAILURE_BUCKET_ID: X64_0xD1_HpCISSs2+5a85
BUCKET_ID: X64_0xD1_HpCISSs2+5a85
Followup: MachineOwner
2018/1/24補充一下:
自發文至今天止,共20天沒有再發生類似的問題。
期間也並沒有做任何的驅動更新或其他硬體變更,至少到現在都沒再發生了。
滿弔詭的。
2018/3/16補充:
自2018年2月份開始,一樣的問題再度發生,目前已先將Raid卡驅動降版本測試再觀察是否還會再發生。
建議可以先使用SPP更新一下,有時候是配對上的問題