STOP 0x00000007B error after installing new RAID controller
- From: "Matthias Claes" <matthias(-dot-)claes@stadsbader(-dot-)com>
- Date: Wed, 16 Aug 2006 15:22:25 +0200
Our HP Proliant ML350 had a HP Smart Array 532 controller.
There are 5 disks connected to the controller 2x RAID1 + 3x RAID5.
Windows Server is installed on the RAID1 volume.
This weekend, the controller failed.
Because the SA-532 is retired by HP, we had it replaced with a Smart Array
642.
The new controller is recognized upon boot, it finds the RAID volumes and
starts to boot Windows Server.
The Windows startup screens comes up (I even have the chance to press F8 if
I want to), fior a split second
and then a stop error occurs:
STOP: 0x00000007B (0XF68C2A98, 0xC00000034, 0x00000000, 0x00000000)
I know this has something to do with Windows to being able to find the
driver for the new card (or not being able to find the old card).
However, because the old card is broken, I was not able the driver for the
SA-642 in the OS while it was still running.
Is there a way to fix this situation?
Matthhias Claes
Stadsbader-Flamand NV
matthiasclaes-at-hotmail-dot-com
(de server is our Exchange server, so our corporate mail is down right now)
.
- Follow-Ups:
- Re: STOP 0x00000007B error after installing new RAID controller
- From: Miha Pihler [MVP]
- Re: STOP 0x00000007B error after installing new RAID controller
- Prev by Date: Re: connect two dcs
- Next by Date: Re: SBS 2003 migration from a server to new server w/ same OS
- Previous by thread: Re: Cannot add Server to a Domain!
- Next by thread: Re: STOP 0x00000007B error after installing new RAID controller
- Index(es):
Relevant Pages
|
Loading
