- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Proliant 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
Forums
Discussions
Discussions
Discussions
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
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
02-11-2003 10:25 AM
02-11-2003 10:25 AM
Proliant 370
Event ID: 4188
The Compaq System Management Driver has detected that the system
encountered an NT bugcheck prior to this boot. The
bugcheck data was: STOP: 0x000000DE (0x00000002, 0xE1619594, 0xFFFFFFFF, 0xE224CA48).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 10:30 AM
02-11-2003 10:30 AM
Re: Proliant 370
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 10:34 AM
02-11-2003 10:34 AM
Re: Proliant 370
It started 1/15/03 then 1/30/30 and 2/11/03
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 12:47 PM
02-11-2003 12:47 PM
Re: Proliant 370
If you don't want to call Microsoft on this one, you could always try to anaylze the memory dump (if one was created). The easiest way would be to use DUMPCHK.EXE and PSTAT.EXE. Those will give you the module that initiated the bugcheck, and then you can take it from there.
You can find info on these pretty much anythere on the web.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2003 01:30 PM
02-27-2003 01:30 PM
Re: Proliant 370
ML370 G3, NT4 SP6, Smart Array 532. First Reboot appeared 14 days after isntallation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2003 01:50 PM
02-27-2003 01:50 PM
Re: Proliant 370
Is you server patched via Microsoft? I will get back to you on what patch may be the problem. I just don't remember the exact numer at this time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2003 11:20 AM
03-08-2003 11:20 AM
Re: Proliant 370
is Q328970 for IE 5.5 SP2