CRITICAL_PROCESS_DIED after registry change

Hi everyone, today I made a change in the registry of my Windows 10 computer in order to install a software that otherwise couldn’t be installed on my D drive (see here for details: Solved: Install LabView 2019 on hard drive other than C: - NI Community) and now my computer is stuck in a BSOD reporting “CRITICAL_PROCESS_DIED”. I’ve tried everything, from startup repair to uncountable prompt commands but stil can’t solve the problem. The worst thing is that I even made a backup of the registry before making any change, and I even used a command to load it up (something like “Reg import <backup_location>”), which succeeded but didn’t help.

I would be glad if any of you could help me.

PS: of course I could neither change the language of my OS or dump any log as suggested in the rules of this section, since I can’t access Windows even in safe mode. Sorry.

System Restore says there are no Restore Points to get back to. Also what kind of 3rd party softwares do you suggest?

Find several flash drives that you can format (> or = 8 GB).

Find a working Windows computer.

On the working Windows computer create tools that be used on the problematic computer.



Create a bootable Sea Tools flash drive.

https://www.seagate.com/content/dam/...lsBootable.zip

SeaTools Bootable | Seagate US


Move the flash drive to the problematic computer and boot to the flash drive.

Run the Sea Tools Long Generic test > take pictures > post a share link into this thread using one drive, drop box, or google drive

If the drive fails the Long Generic test then plan to back up files and replace the drive.


(The prior flash drive can be repurposed or another flash drive can be used)

Create a bootable Windows 10 Media Creation Tool (MCT) (Windows 10 iso).

Download Windows 10 ISO File

https://www.microsoft.com/en-us/soft...d/windows10%20



Move the flash drive to the problematic computer and boot to the flash drive.

Open Windows Recovery Environment (RE) > startup repair > report whether it does or does not create a srttrail



Open command prompt > type

notepad

notepad

notepad

bcdedit /enum all

bcdedit | find "osdevice"

C:
dir

D:
dir

E:
dir

(to copy type:)
ctrl +a
ctrl +c

(to paste into notepad type:)
ctrl +v

(save to a flash drive > move the drive to a working computer > post a share link into this thread using one drive, drop box, or google drive

Ok I've tried running Sea Tools first but it doesn't matter which one of the first 2 icons (that appear on startup) I choose, in the end everything turns quickly to a screen displaying the current time and waiting for my keyboard input. Still, if the purpose of this was to test if the drive is good, being it an SSD (never moved from its position, so neither dropped) that has always worked like a charm up to now I wouldn't suspect it to be faulty. I can detach it, plug it in a working machine and try to test via Data Lifeguard Diagnostics (by Western Digital) if you think there really might be an hardware issue.

Regarding the second diagnostic phase I will leave here the results:

https://1drv.ms/f/s!ArIMqaZlxDRqhJYm...8nicw?e=Ce6ayI

I've detached all my other drives in order for them not to be "contaminated" by some strange actions of the recovery softwares (I'm also sure there are no booting partitions or important SO-related stuff on them because I've made sure not to have them connected when I installed Windows 10 on my machine in the first place), so if the purpose of this was to find out in which partion the OS is, I guess it's C now and there won't be any ambiguty from now on, right?

Good night and thanks to everyone!

The Windows 10 iso was able to boot without problems.


See if the computer can run either:

Sea Tools bootable or Sea Tools Legacy: Long Generic test

SeaTools | Support Seagate US

For test results or error messages or codes > take pictures > post a share link into this thread using one drive, drop box, or google drive

What happened with the startup repair?

What registry editing was performed?

zbook said:

The Windows 10 iso was able to boot without problems.


See if the computer can run either:

Sea Tools bootable or Sea Tools Legacy: Long Generic test

SeaTools | Support Seagate US

For test results or error messages or codes > take pictures > post a share link into this thread using one drive, drop box, or google drive

What happened with the startup repair?

What registry editing was performed?

Startup repair indeed created a "srttrail", I'm posting it here:

https://1drv.ms/t/s!ArIMqaZlxDRqhJYq...p5lJg?e=MIK434

The registry editing was...

1. Remove "WOW6432Node" in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node

2. In HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer set NIDIR64 = D:\Program Files\National Instruments

...as described here: Solved: Install LabView 2019 on hard drive other than C: - NI Community

- - - Updated - - -

dalchina said:

No comment on my suggestion to use off-line registry editing?

doing it right away, just give me some time, sorry

Also quick update: I'm watching the registry on my working laptop and that "WOW6432Node" looks full of much stuff that has nothing to do with LabVIEW, so to delete it looks like a terrible advice to give. Could it be the problem?