- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Proliant ML 370.
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
тАО01-03-2003 01:54 PM
тАО01-03-2003 01:54 PM
Proliant ML 370.
The following error messages are from 9:00 pm 1/2/03
****************************************************
The previous system shutdown at 8:59:37 PM on 1/2/03 was unexpected.
0000: d3 07 01 00 04 00 02 00 ??.......
0008: 14 00 3b 00 25 00 1f 00 ..;.%...
0010: d3 07 01 00 05 00 03 00 ??.......
0018: 01 00 3b 00 25 00 1f 00 ..;.%...
****************************************************
The computer has rebooted from a bugcheck.
The bugcheck was:
0x0000000a (0x00000028, 0x00000002, 0x00000000, 0x8012f268).
Microsoft Windows NT [v15.1381]. A full dump was not saved.
****************************************************
The Compaq System Management Driver has detected that
the system encountered a bugcheck prior to this boot.
The bugcheck data was:
STOP: 0x0000000A (0x00000028, 0x00000002, 0x00000000, 0x8012F268).
0000: 00 00 00 00 09 00 50 00 ......P.
0008: 00 00 00 00 5c 10 35 c4 ....\.5??
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
****************************************************
The following errors occured at 11:53 AM on 1/2/03
****************************************************
The previous system shutdown at 11:53:53 AM on 1/2/03 was unexpected.
0000: d3 07 01 00 04 00 02 00 ??.......
0008: 0b 00 35 00 35 00 b5 01 ..5.5.??.
0010: d3 07 01 00 04 00 02 00 ??.......
0018: 10 00 35 00 35 00 b5 01 ..5.5.??.
****************************************************
The computer has rebooted from a bugcheck.
The bugcheck was:
0x0000000a (0x00000009, 0x00000002, 0x00000001, 0x80108f92).
Microsoft Windows NT [v15.1381].
A full dump was not saved.
****************************************************
The Compaq System Management Driver has detected that
the system encountered a bugcheck prior to this boot.
The bugcheck data was:
STOP: 0x0000000A (0x00000009, 0x00000002, 0x00000001, 0x80108F92).
0000: 00 00 00 00 09 00 50 00 ......P.
0008: 00 00 00 00 5c 10 35 c4 ....\.5??
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
It is a simple file and print server. Not sure what changed other than the Redmond patches.
Any ideas would be appreciated.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2003 02:46 PM
тАО01-03-2003 02:46 PM
Re: Proliant ML 370.
If you are running NT4 SP6a and applied the SRP. You will need to go to Microsoft.com and search for this article "Q305228". Basically depending on which array contorlller you have, your CPQARRAY.SYS driver has to be at a certain version level or these STOP 0A errors can occur after applying the Security Rollup Package. The Article mentioned previously gives all the details.
Good Luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2003 06:21 PM
тАО01-03-2003 06:21 PM
Re: Proliant ML 370.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2003 05:25 AM
тАО01-06-2003 05:25 AM
Re: Proliant ML 370.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2003 01:42 PM
тАО02-17-2003 01:42 PM
Re: Proliant ML 370.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2003 03:08 PM
тАО02-17-2003 03:08 PM
Re: Proliant ML 370.
I have same problem after applying critical updates on Proliant ML330 PIII 1.26 GHz server with 640 MB of RAM. Raid 5
The server has been running one year without problem but since I applied critical updates in Jan 2003 rebooted 4 times
The Compaq System Management Driver has detected that the system encountered a bugcheck prior to this boot. The bugcheck data was: STOP: 0x00000024 (0x00190201, 0xF0A405B0, 0xF0A403EC, 0x80133632).
Did you find any solutions?
I did all updates again check NIC etc but still keeps rebooting
Any help appreciated
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2003 03:19 PM
тАО02-17-2003 03:19 PM
Re: Proliant ML 370.
After removing MS Hotfix 328310, my system has been stable. I did not apply the updated fix to above patch, since I am still annoyed that is appears to have caused all the problems.
Good luck.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2003 04:31 PM
тАО02-17-2003 04:31 PM
Re: Proliant ML 370.
I found and remove MS Hotfix 328310, will let you know if my system will be stable.
I'm runnig these hotfixes Q304158,305929,312895,313829,318138,320206,
323172,326830,329115
Please let me know if should I remove any of them as well
Thank you Bob
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2003 08:09 AM
тАО02-24-2003 08:09 AM
Re: Proliant ML 370.
There is a fix now for the Hotfix 328310 bug, it's essentially a replacement download. It's not yet on the Critical Updates downloads, you have to "update" it - but found just installing this "update" takes care of the security issue. You can check it out here:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS02-071.asp
The download (for English) here:
http://microsoft.com/downloads/details.aspx?FamilyId=E5606A46-364E-4585-9EDB-63654007E685&displaylang=en
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 10:06 AM
тАО04-29-2003 10:06 AM
Re: Proliant ML 370.
Did removing Q328310 fix your problem? I am experiencing something similar also on multiple ML370G3 servers.