BSOD - Critical Process Died...

Yea I can appreciate that, good luck by the way, I hope you do well! The hardware on the system is fine 100% and checks out under different test conditions... so what happens now?

- - - Updated - - -

Anybody?

@jmatt It comes as part of the Ten Forums Win10PEUSB suite of tools, which I ran in the first week my PC crashed! Still, I'm gonna do it again just for the hell of it, hey it won't hurt right!? Happy Easter by the way! ;-)

- - - Updated - - -

I just ran rebooted off a USB an run the "one click solution" and nothing, crashed again as before. Its a shame there's no reg repair usb bootable I could run or that just may fix it...

Allo, sorry for the late reply, been mad busy... ok so, I'll go on a hunt for usb bootable registry repair software, OCCT wouldn't be much help right now so no point. I'll let yer know what I find...

Allo! Soooo, after hunting high an low, the general consensus is that other than loading in a registry hive from a damaged installation into regedit on a working installation for editing, there doesn't appear to be Bootable Registry Repair software in existance!? The only other software that may have worked was 'Scanreg.exe/Scanregw.exe' - but they were phased out with Windows XP I think...

@jmatt Yea tried all those things in different ways...

@philc43

@axe0

Y'know I got to thinking today, Occam's Razor could help me here, he says his the problem-solving principle is that "entities should not be multiplied without necessity", or more simply, the simplest explanation is usually the right one. Now, keeping this in mind, I went back to WinDbg an loaded up the Memory.Dmp file again an had a look, one thing kept nigglein me! NTDLL... why is this causing problems... then BANG I got it - it 'IS' the problem, so I decided to search for the file on the damaged installation - look what I found!!! It's the file, or the different copies of the same file but different sizes... locations... can you help?

There's nothing out of the ordinary with multiple copies of the same file, they're just different versions of the same file. This is the same for many other Windows files.

If ntdll.dll is the problem, it means you have an underlying problem which means you have a hardware problem. Here's why. In your previous thread you ran SFC a few times to fix corruption, in this post SFC reported that it found corruption and repaired them. If you believe ntdll.dll is the problem then run SFC again, SFC checks the integrity of ntdll.dll and 'informs' you if it detected problems. If SFC reports problems again, then you have an underlying problem. Unless you installed a bogus update on that installation since the post where SFC reported fixing corruption there is no other explanation for any corruption reported by SFC at this point. The only other possibility would've been corruption in the registry, but that's already exempted due to past actions.