Re: 0x00007b Windows 7
Lora Ceasor
An old computer from a client with a Windows XP broke down (PSU or Mother Board) and there is a newer machine where that system can work. However, I cannot access the system anymore. I have got the BSOD 0x0000007b. This could mean there is an issue with drivers after swapping a disk like that.
The BSOD 0x0000007b error is a classical one.It happens because your the BIOS of your newer machine is set to AHCI mode and your drive is missing the AHCI drivers.The error occurs once Windows switches over to the preloaded drivers in the boot process.
But apart from that as far as I remember Windows XP does not respond in a flexible way to a new environment by updating all drivers.I remember Acronis offering a duplicating software involving an extra feature that would update all drivers on the copy target.
Change E: to the drive letter of the old PC.So once you select "load hive", you will have to specify e:\windows\system32\config\system
Then it will ask for a name which can be anything. I usually just use X because its short as possible.
I think it was the HARDWARE key, but its been a decade so don't quote me on that. Also this is why you want to have a back up of the original, so you can try breaking changes without risking the original.
Options so far are try the recovery partition option (win 7 prem OA) on a Win 8 shipped mobo and lose all user data if it works? There is this backup routine but I haven't found the restore instructions assuming the system recovery will work.
Popping in a spare (MBR style) 1.0 TB HD from the parts cupboard with old win7pro install from an older ASUS mobo+AMD X2+Nvidia vid card booted right up to login screen. (Wow). I needed to sort out video and network drivers, but I could move around in Windows.
Popping in That downloaded DVD above and custom installing windows 7 prem to another empty partition on that drive from within win 7 pro (borrowed) bypassed the UEFI trap, and gave me a clean Win 7 prem install. But Activation failed using the COA on the Case of the H8-1223, giving me 30 days to play. The newer H8-1559 mobo may have tripped up the activation. A phone call in to MS "may" fix that.
So following the removal of certain rootkits (such as Rootkit.Boot.SST.a, which is associated with the Windows Recovery rogue), you may find that your Windows boot configuration data has been totally corrupted. Worse yet, the usual steps to remedy (such as those described in my earlier post about TDL4 and the resulting blue screen) all fall apart when you reach the bootrec /RebuildBCD command, which returns the message:
Thanks to Bitt Faulk for the final line, which restores the correct Windows loading screen as well. You will need to replace the en-US entry with something different representing your region if you are not in the US.
Sweet fix, However, wouldnt boot back up after i restarted, looking for \Windows\system32\winload.exe , so i ran through a startup and repair from a windows 7 cd and if by magic it boots back into windows. also the Rootkit.Boot.SST is now not detected by tdsskiller.
@DJ Dougiefresh , I just had the same experience and did the same thing. Using the guidance from this site and then doing the win 7 disk it came up fine. It didnt work just doing the win 7 disk without the above fix, so its complicated but it works.
Thank you, it worked! I used TDSSKiller which could only detect suspicious activity in the MBR but had no option to remove it. After applying your steps I was unable to boot into Windows but doing Startup repair fixed it. TDSSKiller no longer detects the rootkit.
Like DJ, I also followed the steps above, and all the commands completed OK. Because I had a Dell Vostro 3550 laptop, it had two partitions. After rebooting, the \Windows\system32\winload.exe error was because while Dell had the C:\boot folder and the BCD info, Windows 7 was on the D partition while using the Windows recovery tool, thus we should have entered:
Thank you. Solution work great. Thanks to ChrisB also. My laptop was a Dell Inspiron also and had to do the substitution for the system drive. Tried other solutions and this is the only one that worked. Life saver.
It kinda worked. I got a scree that said it could not find winload.exe maybe i mistyped however I was able to do a repair right after and it fixed it when befor repair would not work. I got the windows anamation back too.
The other option is to simply take the computer to an experienced tech. Some problems are too risky for the average user to deal with on their own, and this certainly qualifies I would say. In fact, many of the things I post about here on my blog qualify! ?
I too knew there was a way to do this, but have never found a successful tutorial until now. I was also to the point of a reimage, and started this procedure and when I got to the c:\Boot line, it said file not found and I got the clue the boot folder was missing. i used a command prompt to copy the boot folder from the recovery partition and tried to unsuccessfully boot. I got through the whole process with only a typo in the long string of numbers and letters and it booted miraculously. Thanks again !!!
Ok. I have an Asus P4P800e mb with a Pentium 4 3.2 ghz CPU, 4 gb ram. I tried to install Windows 2000 on an ssd, but it would not install and I got a bsod. I then installed Windows 2000 on a hard drive. This worked fine.
I have basically the same motherboard with windows 98 booting from an SSD. I don't know why, but I believe some SSDs are just better with legacy IDE modes . I use a Kingston 120GB A400 with all my retro builds.
Error "0x0000007B" means inaccessible boot device.
Access the BIOS, go to the IDE Configuration section and switch the Onboard IDE operation mode from "Enhanced Mode" to "Compatible mode". Then try the installation again.
Well I could tell you more about it if I had it here, but it is in the repair shop right now. The graphics is Intel GMA 950, and Windows XP Media Center Edition was the original OS and that is still what is on the computer.
A 0x7B bugcheck after a boot.ini modification and Safe Mode, that reads like the boot.ini mod. + Safe Mode gives the equivalent of a Clean Boot but, MSConfig had previously been used to temporarily disable a startup entry that has since been uninstalled/removed, resulting in any boot attempt crashing because a file (likely a driver marked as Boot/System) required under those parameters, is missing.
Anyone know of a good download site for Windows XP media center start disc? If I could get a good boot disc I could go to the C: prompt and type in bootcfg.exe and make the changes to start windows normally. Or, I may just take the computer to shop and explain what I think needs to be done. You would think a repair shop has a good boot disc. Thanks.
Several Dell E310 users have reported success with this adapter and a x16 HD6450 low profile card. A cheaper and 4x faster setup than the x1 card. But IMHO the money spent is better put towards a new PC.
Several Dell E310 users have also reported success with this adapter and a x16 HD6450 low profile card. A cheaper and 4x faster setup than the x1 card. But IMHO the money spent is better put towards a new PC.
Well, thanks for your help. Yep, time is one thing I do have a lot of now. But my background is radio repair and not computers. I guess I do have more knowledge of computers than your average bear though.
So that is the way this story ends. Like most everybody else on the internet who could not figure out how to resolve a Stop 0x7B, I now join their ranks. I want to thank you all for your help on this! It is much appreciated!
Trying to upgrade to ArcGIS 10.4.1 on Windows 10, MacBook Pro bootcamp (mid 2012). Everything went smoothly, until I attempted to open ArcGIS Map, whereby I received the following message: "The application was unable to start correctly (0xc000007b). Any ideas???
Those instructions should work with all versions of Windows. Did you have problems getting to the folder? Easiest way is hold the "windows" key down while typing E, this will open the Windows Explorer file browser. Type %APPDATA% (with the percent characters) in the path box and you're there.
But, on my desktop PC where 10.4 was loaded correctly, the 10.4 folder (and files) are is present. Is this some odd change of configuration of 10.4? Or, an installation problem when 10.3 is already resident?
03c5feb9e7