- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: ML150 G5 BLUE SCREEN AT LOGON
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-16-2010 03:04 AM
тАО01-16-2010 03:04 AM
ML150 G5 BLUE SCREEN AT LOGON
I have an ML150 G5, running Windows Server 2003 on an RAID 1 array. The onboard RAID controller is LSI SAS1064E.
Yesterday, i tried to do a remote desktop connection to the server, i put the credentials and when I pressed connect, rdc stopped responding.
Eversince, I restart the server, try to login normally (no rdc) and then there is a blue screen with the following error code
STOP: 0x0000008E (0xX000005, 0x808BC9DD, 0xB9283900, 0x00000000)
When i start windows in safe mode, the system starts, but when i start it in last good known configuration, then it doesnt go to the logon screen but it gets blue for 1sec and then it restarts.
I then noticed that on server startup, at the RAID array startup there is the message "failed or degraded volume detected: Volume (00:001) is currently in state DEGRADED" and when I go to LSI Logic Config Utility the primary drive is failed.
Does this has to do with the blue screen??
Can you please help me figure it out?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2010 01:02 PM
тАО01-16-2010 01:02 PM
Re: ML150 G5 BLUE SCREEN AT LOGON
what happens now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2010 12:10 PM
тАО01-17-2010 12:10 PM
Re: ML150 G5 BLUE SCREEN AT LOGON
Every time I start windows normally and try to logon, after i put the username and password i have a blue screen.
Any other suggestion??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2010 08:47 PM
тАО01-17-2010 08:47 PM
Re: ML150 G5 BLUE SCREEN AT LOGON
Boot from Windows PE Live CD, backup needed data to USB drive and reinstall OS.
Also I recommend to update firmware for RBSU and RAID controller to latest version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 09:22 AM
тАО01-18-2010 09:22 AM
Re: ML150 G5 BLUE SCREEN AT LOGON
You think the blue screen has to do with the failed drive?
Also, why should I reinstall windows on the server, instead of replacing the drive and rebuilding the array?
What is rsbu?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 10:50 PM
тАО01-18-2010 10:50 PM
Re: ML150 G5 BLUE SCREEN AT LOGON
1.remove failed drive
2.run full memory diagnostics or install healthy modules
3.if memory is ok, try to start win
4.if successfully started, install drive and rebuild array, if not - backup data and reinstall OS (or you may try to find corrupted system files and replace it)
5.update firmware
RBSU - Rom Based Setup Utility (BIOS)
p.s. is any usefull error message in iml log before the accident?