7 HP x64 - Startup Repair Loop, NoRootCause

ThrashZone · 05 Jan 2016

I thought it was third time's the charm

TVeblen · 06 Jan 2016

One thing I thought I'd mention is that is somewhat common for the Startup Repair loop to be caused by bad RAM. We most often see it when someone puts incompatible RAM in a system.

You could try running the PC on one stick of RAM. If that doesn't work, switch it for the other stick of RAM. Or you can run Memtest86+ - Advanced Memory Diagnostic Tool on one or both sticks of RAM for at least 3 passes.

And of course, check to see if the owner recently upgraded his RAM!

And it is always a good idea in these cases to disconnect all additional and external hard drives, disable (in BIOS) the onboard sound and LAN, and disconnect all USB connected devices. The goal is to do the diagnostics with just the bare minimum hardware connected to simplify the system.

Hope that helps

Anak · 06 Jan 2016

Thank you essenbe, and Layback Bear for your kind words, I am about due for an eye exam.

7 HP x64 - Startup Repair Loop, NoRootCause-7f-now-where-did-i-put-those-glasses_-_.jpg

And back to topic...

TZ, running a second or a third time would depend on how Alexx's ram works, if Alexx follows TVeblen's suggestion(s). I've brought stubborn operating systems back from just resetting the ram, and running a Last Known Good Configuration option would still be a good idea.

If the ram is okay, then take a closer look at the partition table.

Code:

The partition table does not have a valid system partition.

Repair Action: Partition Table Repair
Result: Completed successfully. Error Code 0x0
Time Taken = 2356ms.

Layback Bear · 06 Jan 2016

alexx2 do you have any news for us?
Please keep us informed.

alexx2 · 08 Jan 2016

Hi guys, really appreciate all the replies. I have both my Saturday and Sunday free this week, so I will be doing my best to get through all of your suggestions. I will post back any and all results as soon as I can!

Thanks again everyone,
Alexx

alexx2 · 10 Jan 2016

Hi all,

I'll give you a run down of what has been done now.

1 - different RAM chucked into DIMM 1 (as somewhat suggested by - TVeblen), same result.
2 - Removed all peripherals (i.e. went back to wired keyboard mouse, removed wireless card, DVD drive removed, second HDD removed, swapped GPU to a GT310) as i've heard additional drivers could cause issues? Still same result., being startup repair launches.
3 - Entering Last Known Good Config results in startup repair.
4 - Reinserted original RAM and run a memtest, 6 times, all passed. No issues with RAM.

I will be working on both of essenbe's entries and ThrashZone's tonight after work.

Hopefully something will prevail!

Again all of this help is greatly appreciated for this very annoying and stubborn issue.

Alexx

Layback Bear · 11 Jan 2016

Thank for keeping us update.

Anak · 11 Jan 2016

I'd sure like to see the volumes on this machine; Alexx, can you get to an elevated CMD prompt on your buddies machine?

If you can, type diskpart , then touch enter.

Type, list volume, then enter.

Can you get a screenshot to upload here or describe what you see?

If you do see any volumes that are unhealthy, please note description and mention in your next post.

What I'd like to see is if all volumes and their partitions are healthy, here's what I show on mine:

7 HP x64 - Startup Repair Loop, NoRootCause-diskpart.png

If you can't get a normal CMD prompt, I believe you can also use the CMD prompt at the bottom of the Advanced Boot Options screen.

Jess086 · 04 Jan 2017

Having the same problem... last thing installed was a windows update on the 31st Dec