I have a Dell Inspiron E1505, 1GB RAM, Hitachi SATA 120GB HD, Windows XP SP3 Home.
The pc was working fine before the problem occur. I was operating on AC (with battery removed). During a routine shutdown, I accidentally unplug the AC cord while the computer was still saving settings. The next time I power it up, I got the BSOD with the STOP 0x00000128 error code. Here's what I've tried so far:
Tried to use Recovery Console but it rejected my Admin password as invalid and will not go into Recovery Console mode. (Incidentally, it did accept a blank password once and let me in but never again after that one time). The one time it did accept the blank password, I was able to copy a recovery system file from the Win Xp CD to the hard drive c:\windows\system32\config folder. After reboot, now I got a STOP 0x0000007b error code. The second parameter of the error code is the 0xc0000034 so I learned that this is the STATUS_OBJECT_NAME_NOT_FOUND error. I've unable to find anything on the web to address this problem.
I have created an Ultimate Boot CD for Windows (UBCD4Win) boot disk and it would boot up but will not start Windows from the UBCD disk so I cannot use any of the tools from UBCD. Starting Windows from the UBCD gave me the same x7b error.
Does anyone have other suggestions as where I can go from here? I'm tempted to reload Windows but only as a last resort. Does anyone know if repairing an installation rather than a complete reload will help? And will a repair wipe out my applications and data I have on the drive?
REPAIR you windows installation. Boot from your XP CD, choose install, allow it to scan for previous installations and prompt you and then press "R" when the menu comes up to REPAIR the existing installation. The OS will be repaired using your original CD and you will retain all of your existing device drivers, installed programs and user settings. You will need to re-patch the OS pack to the latest service pack and apply any post SP hotfixes to complete the rebuild, but the repair option is one of the most useful and overlooked options for fixing a broken Windows installation.
I have used it countless times to repair XP - read up on it if you need to, but it's your best bet out of this situation with the smallest impact on your OS.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.