| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 104583 | 2009-11-01 21:30:00 | WinNT Stop 7B Inaccessible Boot Device | inphinity (7274) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 826289 | 2009-11-01 21:30:00 | Hey All, We have an old machine still running NT4 Workstation. It runs a custom application which doesn't work on newer OSes for some bizarre reason, hence still using NT4 on it. However, the other day I pulled the HDD out, and created an image of it with Acronis Backup & Recovery 10, which we periodically do so we can restore the machine if the drive fails or anything. However, after putting the HDD back in the PC (no hardware changes at all), it BSODs on bootup with Stop 7B, Inaccessible Boot Device. Now, I've seen this plenty of times before when changing hardware (replacing motherboard, imaging to a new PC etc) and being related to disk controller drivers. But I'm totally stumped whats caused it here. I've tried restoring the backup image we just took, and it gets the same error. Any suggestions? Thanks in advance. |
inphinity (7274) | ||
| 826290 | 2009-11-01 21:36:00 | Is the hdd the boot drive in the BIOS?? Is the virus option in the BIOS disabled? | Speedy Gonzales (78) | ||
| 826291 | 2009-11-01 21:58:00 | Yes and Yes, and no BIOS changes were made in between it working, and it not working. I am getting the feeling that perhaps somehow connecting the drive in a different PC has stuffed the MBR or something, and that this has happened as soon as the machine booted, prior to the backup being done. Plausible? | inphinity (7274) | ||
| 826292 | 2009-11-01 22:14:00 | When you pulled the hdd out, what did you install it in (this is probably why it crashed). Whatever you installed it in, isnt in the case you took the hdd out of. ie: Its got a different CPU in it? And one site says this: Acronis Universal Restore Images of computers running Microsoft Windows cannot simply be restored to different hardware as Windows will typically fail at boot time with a STOP: 0x0000007B error screen if the proper Microsoft Hardware Abstraction Layer (HAL) and/or storage drivers are not installed in the operating system at boot time. Acronis Universal Restore is designed to overcome this problem. Universal Restore[7] is an add-on utility for True Image Echo versions running under Windows, and is designed to replace the HAL and inject updated storage drivers embedded within the image during the recovery process, allowing an image of a machine to be restored to different hardware. In other words, the system you installed the hdd in (and backed up), doesnt match (ie: drivers / hardware / cpu), the system you removed the hdd from.. Result a crash. |
Speedy Gonzales (78) | ||
| 826293 | 2009-11-01 22:38:00 | I didn't try to boot from the drive, or restore it or anything, I simply plugged it in to the IDE controller, ran Acronis and created a backup image on to a USB drive. So yes the backup was done in a PC with different hardware, but that shouldn't automagically screw the HAL? And we ahve Universal Restore as part of the license, and using this hasn't resolved the issue :( Thanks for the input though :) |
inphinity (7274) | ||
| 826294 | 2009-11-01 23:18:00 | Bent pin/s on H.D.D. socket? have a look, repair carefully with needle nosed pliers, don't repeatedly bend pins to correct orientation. | zqwerty (97) | ||
| 826295 | 2009-11-02 19:15:00 | Thanks for the suggestion :) Checked that, and no problem there. Hrmm this is a pain lol. | inphinity (7274) | ||
| 826296 | 2009-11-02 22:40:00 | A bit of an avoidance solution than actually fixing it, but what about running it in a VM? Not cloning the drive to a VM, but clean installing just NT4 and the weird app. :) | jwil1 (65) | ||
| 826297 | 2009-11-02 22:52:00 | Check the drive for bad/reallocated sectors Possibly during your cloning (which would have had to read all the data) a sector may have failed. Just coincidentally it probably corrupted something and is now causing your BSOD. Under normal operating condiditions, this sector was probably never read and thus never showed up as faulty. Which is why people should always do a full test of their entire drive periodically! |
Agent_24 (57) | ||
| 826298 | 2009-11-02 23:37:00 | Just ran chkdsk with the /f /r options on the drive, no file system errors or bad sectors found. Also tried restoring the image to another known-good IDE drive and same problem continues. I also tried now converting the image to a VMWare disk, but that BSODs with the same error! |
inphinity (7274) | ||
| 1 2 3 | |||||