- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- BSOD on BL460c
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 08:03 AM
тАО12-01-2008 08:03 AM
Re: BSOD on BL460c
- SystemRom├п┬╝ BIOS)├г ├г 2008.09.29
- SmartArrayE200i 1.80
- NC373i 4.6.16.0
- HP PSP 8.1
- Quad-Core Intel Xeon, 3000 MHz
All servers have experienced a blue screen at one point in time and they happen at different times over the last couple of months. They will work fine for a month or so and then BSOD with a STOP: 0X0000000A, STOP: 0X000000D0, or a STOP: 0X0000008E for no reason at all. There was not a high load during the time of the BSOD. Also, all of these servers were migrated to blades using the HP SMP-P2P software from DL385 G1's.
I have tried the protectnonpagedpool registry key and have updated all drivers to the latest and greatest, but two servers blue screened over the weekend.
Has anyone had any luck with the storport driver fix?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 08:12 AM
тАО12-01-2008 08:12 AM
Re: BSOD on BL460c
According to the article this problem should have been corrected with
Version 6.2.0.32 (or later)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 03:11 PM
тАО12-01-2008 03:11 PM
Re: BSOD on BL460c
HP has suggested that I update my STORPORT driver to the following-
Windows 2003 SP1 Storport.sys 5.2.3790.3148
Windows 2003 SP2 Storport.sys 5.2.3790.4303
http://support.microsoft.com/kb/950448/en-us
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 03:24 PM
тАО12-01-2008 03:24 PM
Re: BSOD on BL460c
We are using storport.sys version 5.2.3790.3959 and experiencing the issue.
Feels a bit hit and miss updating the storport.sys drivers as it dosn't specifically mention the problems we are having. New storport driver resolves a clustering error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 03:33 PM
тАО12-01-2008 03:33 PM
Re: BSOD on BL460c
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 04:48 PM
тАО12-01-2008 04:48 PM
Re: BSOD on BL460c
Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x0000000100060049, 0x0000000000000002, 0x0000000000000000, 0xFFFFFADF900AC743))
>>>>>>
2: 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: 0000000100060049, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffadf900ac743, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000100060049
CURRENT_IRQL: 2
FAULTING_IP:
storport!RaidXrbSetDataBufferAddress+2b
fffffadf`900ac743 488b4848 mov rcx,qword ptr [rax+48h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: cqmgstor.exe
LAST_CONTROL_TRANSFER: from fffff8000102e5b4 to fffff8000102e890
STACK_TEXT:
fffffadf`8cecc258 fffff800`0102e5b4 : 00000000`0000000a 00000001`00060049 00000000`00000002 00000000`00000000 : nt!CmpDelayCloseWorker+0xa7
fffffadf`8cecc260 00000000`0000000a : 00000001`00060049 00000000`00000002 00000000`00000000 fffffadf`900ac743 : nt!CmpDelayDerefKCBDpcRoutine+0x50
fffffadf`8cecc268 00000001`00060049 : 00000000`00000002 00000000`00000000 fffffadf`900ac743 fffffadf`9cd27b10 : 0xa
fffffadf`8cecc270 00000000`00000002 : 00000000`00000000 fffffadf`900ac743 fffffadf`9cd27b10 00000000`00000000 : 0x1`00060049
fffffadf`8cecc278 00000000`00000000 : fffffadf`900ac743 fffffadf`9cd27b10 00000000`00000000 00000000`00000000 : 0x2
fffffadf`8cecc280 fffffadf`900ac743 : fffffadf`9cd27b10 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffadf`8cecc288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidXrbSetDataBufferAddress+0x2b
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!RaidXrbSetDataBufferAddress+2b
fffffadf`900ac743 488b4848 mov rcx,qword ptr [rax+48h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: storport!RaidXrbSetDataBufferAddress+2b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 471c86a8
FAILURE_BUCKET_ID: X64_0xD1_storport!RaidXrbSetDataBufferAddress+2b
BUCKET_ID: X64_0xD1_storport!RaidXrbSetDataBufferAddress+2b
Followup: MachineOwner
---------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 05:14 PM
тАО12-01-2008 05:14 PM
Re: BSOD on BL460c
Unfortunately you can't disable the Insight Storage Agents without shutting down the underlying Foundation Agents required for monitoring.
You could potentially set all the storage related Management agents to Inactive through the System Control Panel but i'm not sure that this would rectify the issue.
E.g." Fibre Array, IDE, iSCSI, Drive Array, SCSI, SAS, Storage information and Remote Alerter" etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2008 01:52 PM
тАО12-09-2008 01:52 PM
Re: BSOD on BL460c
1. Update to PSP v8.15a
2. Update all firmware to FW Maintenance CD v8.30 baseline
3. Update Storport drivers from Microsoft - http://support.microsoft.com/kb/950448/en-us
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2008 03:00 PM
тАО12-09-2008 03:00 PM
Re: BSOD on BL460c
I've decided to do the exactly the same thing during our next outage, so fingers crossed the issue will go away.
I've also been having a look at http://support.microsoft.com/kb/244617
Blade user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2008 10:28 PM
тАО12-09-2008 10:28 PM
Re: BSOD on BL460c
According to our trial & error excercise, what I've noticed is, if you set Driver Verifier against some specific drivers, BSOD seems to have stopped. Those drivers are hpeaadsm.sys, ql2300.sys, storport.sys and hpciss2.sys. From this, I'm guessing that there are something wrong with the combination of these 4(or some of these) drivers under a certain conditions in terms of the root cause of BSOD.
I keep this testing to re-produce BSOD using several blades to clarify the real cause with help from Microsoft and hp, but if someone can provide similar data or any related information, it would be very helpful.
O. Terai