- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- SA532 to SA641 BSOD
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
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
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
11-13-2012 07:32 AM
11-13-2012 07:32 AM
SA532 to SA641 BSOD
a SA532 has failed on a server and upon replacing it with a SA641(which incidentally uses THE SAME DRIVER!) the server BSODS with 0x0000007B (0xF789EA94) which is a boot driver issue as i know that error very well.
OS is win2003 standard
now the important parts:
1) the controller IS BROKEN, so i can't boot and plug the 641 so that it can "detect the driver".
2) a "repair install" is not an option as it breaks installed software, there's too much software installed that can't simply be reinstalled, the installation HAS TO BOOT as is.
3) theres no replacement 532 controller at hand or in a timeframe that's allowable.
4) safe mode, LKG fails the same as is the case with all 7B errors
i need to be able to FORCE the system to boot from the 641 somewhat, no idea how to do this from recovery console and since they use the same driver there's nothing to replace.
I'm extremely annoyed as SA are supposed to be driver-unified and replaceable between them