0x0000007B = INACCESSIBLE_BOOT_DEVICE. I don't think it's related to Active System Console, because IASC doesn't touch storage driver or boot file. I suggest you check the following:
1. What's your HDD configuration? Check if the boor order in BIOS is correct.
2. Are you using a RAID configuration? If yes, check if the boot VD is set correctly.
3. Check if the HDD itself has bad sectors.
Sorry but do not agree.
I installed ASC on two different servers and the problem occurred in the same way on the two servers.
The only thing that comes to mind is that on these two machines had previously installed "Intel Server Manager 8:40" buid 22.214.171.124.
I removed the "Intel Server Manager 8:40. Then I rebooted the server. Then I installed ASC 4.4. Then I rebooted the server and at this point appeared 0x0000007B.
Now I need to know how to disable lemodifiche made by the ASC setup to restart the server
What's your hard drive configuration? Any RAID configuration?
ISM 8.40 is quite old, and I don't think it's designed to manage a S5000PAL server.
Only thing I can think of is if the RAID or storage driver is getting overwritten by IASC 4.4, somehow. What version of megasr.sys is on your system, pre-IASC install?
Unfortunately, the ASC_x86.exe is a monolithic file, so I can't tell what files it replaces.
The 2 servers are configured with a RAID 5 with an LSI 8704ELP and the other with intel SRCSAS144E.
Both use the msas2k3.sys driver ver 126.96.36.199 a 32 bit.
The strange thing is that I have 4 machines with S5000PAL, two with 32-bit OS and two with 64 bit OS.For machines with 64-bit OS,ISM 8:40 was not installed because is not compatible, and the installation of ASC 4.4 work fine, without problem.
on the machine with 32-bit OS ISM 8.40 was installed and after removing the ISM 8.40 e installing ASC 4.4 the both machiene make a crah.
In one of the two machine i make an "in-place upgrade" folowing http://support.microsoft.com/kb/816579/en-us but the problem is not solved.
P.S. sorry for my english
I'll see if I can test it here. At the same time, what's the problem with "in-place upgrade"? Did the upgrade complete successfully? Did you load proper RAID driver?
The problem with "in-place upgrade is that after passing the part of the installation CD, when the machine is restarted yet since the error 0x0000007B.
Regarding the RAID driver, I installed the correct driver.
I did some tests today and was able to duplicate your problem. It's related to ISM 8.4, not IASC 4.4. Here is what I did:
1. Test was done with a S5000PSL board with SROMBSAS18E (same chip as SRCSAS144E)
2. Fresh install of Windows 2003 R2 w/ SP2 32-bit. Installed chipset and NIC driver.
3. Installed ISM 8.4 (local install, server + agent). Reboot. Confirmed ISM was running properly.
4. Reboot again. Uninstalled ISM 8.4. Reboot.
5. At this point the server is still running well. However, reboot manually again, and I encountered this 0x7B BSOD.
Apparently during the first reboot after uninstalling ISM 8.4, the uninstallation program did some "clean up" of system files those were in use when ISM was running. Because the platform is not supported, some important system files or registry got corrupted and causes the 0x7B error.
I'll do more research and see if I can find a fix, but I can't promise anything. One good lesson learned here is, never install management software on an unsupported system. It might seem to run, but it well totally ruin your system some day.
1 of 1 people found this helpful
I was able to find a fix today.
First let me explain the cause of the issue. During installation, ISM 8.4 installed a PCI hotplug driver (PCICONF), which is not supported on S5000PAL. When ISM 8.4 is uninstalled, the driver file was removed after the first reboot, however the uninstaller failed to clear the registry entry of that driver. So in the next boot, Windows thinks a driver required for booting is missing, and gives the 0x7B BSOD. Again this is the downside of installing ISM on an unsupported platform.
This issue is very similar to the issue documented in http://support.microsoft.com/kb/811408, so we can also use the solution, with a little tweak. The solution is for Windows XP, but it also works for Windows Server 2003.
Follow the steps described in Method 1 of KB811408. You'll need a Windows Server 2003 installation CD.
In step 2, you only need to rename and copy the file system. We will not touch software, SAM, security and default.
In step 9, go to the following registry key:
Skip step 10 and go to step 11. Below is the screenshot of that registry key to be deleted:
Skip steps 12~16, and go to step 17. Complete the remaining steps.
This should bring your Windows Server 2003 back online.
Only today I was able to try your solution and I say this with great admiration that is fully functional.
Thank you very much.
One last question,
if I have a machine working with ISM 8.4 how do I remove it??
I proceed as follows:
1) Uninstall ISM 8.4.
2) reboot the machine
3) removal of "UpperFilters" in CurrentControlSet, ControlSet001, ControlSet002
4) reboot the machine again.
is that correct??
Many many thanks.
Nice investigation, Edward!
The you're correct, that should prevent the 0x7b BSOD.
Many thanks Edward.
You were very kind and also very good at finding the subuzione to my problem.
Until next time.