Sunday, January 06, 2013 6:52 PM
Situation: The plant had it's post-holiday break start-up this am and one of the PC's went into Startup Repair mode. I was called in and found that the file "PSHED.dll was corrupt." After ~6 hours, I am unable to boot the PC. The PC is a HP desktop with 4 GB RAM, only a year or so old. Runs Win7 Enterprise x64; the load on it is relatively light. (I work as an on-site IT Support guy, Tier-2.)
What I've done:
- Tried to boot to Safe Mode - no luck.
- Restore to previous point in time - no luck.
- Tried the steps in How to Recover from an Infinitely Looping Startup Reapir Loop without Reinstalling Windows - no luck.
- Tried the steps in Windows Vista Boots to a Black Screen with only the Mouse Cursor - no luck.
- From Cmd prompt within WinRE, ran bootrec.exe /fixmbr, and bootrec.exe /rebuildbcd - no luck.
- Created a System Repair CD on my laptop and booted to it - no luck doing all the above.
- Over-wrote the corrupt PSHED.dll with a copy from my laptop and rebooted - no luck.
About half the time on boot-up from the CD I can "find" an OS, other times not. When the OS is found in WinRE, I can get to the drives and folders, so could pull off the user data, but I'd like to repair the PC if possible - better chance of learning from the experience. My limiting factor is the entire plant startsd up tomorrow monring at 6 am and I need to have this on-line by 11 am that same day - allowing time to reimage it and transfer over the user data.
Question: Is there anything else I can try? (We don't have the install media; we just download the images as needed.)
Monday, January 07, 2013 8:19 PMAfter more work with the computer, we found the HDD was bad. Still ... if anyone has some thoughts on the original question for future refererence, I'd really like to hear them.
Tuesday, January 08, 2013 7:07 AMModerator
The file PSHED.DLL is part of the component that enables hardware errors to be generated.
So, please check whether this issue still occurred after changing the HDD.
TechNet Community Support
- Marked As Answer by RV2011 Tuesday, January 08, 2013 10:53 AM
Tuesday, January 08, 2013 10:55 AMThanks, we did. We disconnected all possible cables and took out the RAM, then added them back in one-by-one to see if any was the problem. Each bootup was successful.