BSOD Repair Loop Critical_Process_Died

Hi, I've been wrestling with this problem for last 2 days and I don't seem to be able to find an answer anywhere hence I'm posting here. Firstly, I can't generate the dumpfile as I can't access windows at all. I can't access it through any boot options including safe mode.

I've recently upgraded from Windows 7 to 10 through the microsoft updater.

The only major thing I did before this happened was installing the AMD CCC and rebooting, which caused this loop. I actually reinstalled it as switchable graphics wasn't working.

Things I've tried -
1. Automatic Repair - doesn't work. txt file in srt folder says the OS version is not compatible even if I use the Windows 10 usb.

2. chkdsk /f /r - it fixed a bunch of things, there seemed to be a lot of problems but now it says that there is no problems and no further action is required.

3. Fixing and rewriting bcd files - This was the interesting part because my computer some how changed the C:\ to D:\ and created a new C:\. I've reassigned it so that original C:\ is renamed back to C:\ and removed the new C:\ partition which only had the boot files in it and reformed all the bcd files in original C:\

4. I can't run sfc /scanow. It doesn't work with any commands I found over the internet.

5. Other things I found were that if I tried to reset the computer while keeping the files, it doesn't allow me to do it.
Also, I found out that some of my drivers were missing by using devcon - graphics (both integrated intel, dedicated radeon m6740) some sound cards, single usb driver.
Also when I installed thne integrated intel graphics driver through pnputil, when I restart the computer, the driver disappears and comes up with code 28 again.

I don't mind doing a fresh install but only if I am able to access my current hd files and create a backup, which hopefully should be possible because I can access the files through cmd prompt in WindowsRE.

axe0 said:

Hi jban0811,

Welcome to the 10forums.

What I want to try first is a clean boot, this to see if a program is interfering with the boot.

Please try to access the command prompt in the advanced options when you are in the recovery options.
When you have the command prompt open type the following commands:
start msconfig
start taskmgr.exe

In the msconfig, go to the services tab, check 'hide microsoft services' and disable every other service

In the taskmanager, go to the startup tab and disable everything.

Go back to msconfig, click apply, click ok and reboot the system.

Hi, I've tried to do as you said. I can't get into msconfig from X: because it doesn't exist and in C:\windows\system32, it says i don't have sufficient privileges to run system configuration even though the cmd is running as Administrator: X:\windows\SYSTEM32\cmd.exe

Also in the taskmanager it doesn't seem to have the startup tab and it looks like the older taskmanagers, not the one from windows 10.

Thanks!

axe0 said:

I just found a possible way,

In command prompt enter the following commands
Bootrec /fixMBR
bootrec /fixBoot
bootrec /rebuildBCD

And try the repair again.

In most cases when the hard drive is locked the master boot file has been corrupted, these commands should fix that.

I've tried it. but still the same message with msconfig telling me to run this utility as a user in the admin group. and everything else seems to be the same.

axe0 said:

Do you have some restore points created?

unfortunately I don't. I upgraded to windows 10 just a few days ago so any points are from windows 7

axe0 said:

In command prompt enter the following commands to see the drive partitions

Code:

diskpart
list disk
select disk X (choose the hard drive of windows)
list partition

Please make a photo of the partitions and post it here

I will type it out

Partition ### Type Size Offset
Partition 1 Primary 440 GB 200 MB
Partition 2 Primary 20 GB 440 GB
Partition 3 Primary 4063 MB 461 GB

Partition 1 is the C: with everything in it
Partition 2 is what came with the laptop on purchase as the recovery
Partition 3 is HP_Tools, not sure what it's for