Resetting the PC fails after earlier BSOD critical process died message


KSV

Joined
Dec 23, 2020
Messages
6
Reaction score
2
After the recent (20H2) Windows 10 upgrade, my computer started misbehaving. I tried varous tricks like using a restore point but I obtained BSOD Critical Process Died message repeatedly. The system checked the hardware and found no problem. Using one of the suggestions given on a related post, I created a USB windows recovery drive using an older computer (Win10). This starts, but none of the recovery/troubleshoot/restore options have succeeded. Using the command prompt, I could see that the file structure on the C: drive was intact.

I posted a thread and received some tips about Windows activation. When all the tips available in the Windows forum failed I tried to reset this PC using a USB Win10 CD and taking the 'delete files route'. After 'recovering this PC 71%' I received the blue screen 'There was a problem resetting your PC. No changes were made'. But now with the command prompt I cannot even see the C: drive. The 512Gb storage drive still passes the Dell Support Assistant diagnostic run.

The computer is a Dell XPS 13 9360, past its warranty by 6 months..

What else can I try, short of installing a fresh Windows 10? Any tips would be appreciated.
 
Ad

Advertisements

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,178
Reaction score
2,255
Sounds like you're pretty much on top of things.
Keep in mind
But now with the command prompt I cannot even see the C: drive.
When booting using an external resource the drive partition letters are rarely if ever the common lettering you are used to seeing.

The error can be vague but will often be caused by damaged / corrupted system files or a bad area holding critical information regarding partitioning.
Not sure what you could do further to advance the diagnostic process.
I would lean towards the drive itself and consider a replacement.
On the bright side it doesn't look like a big job to replace it.
Dell XPS 13 (9360) SSD Replacement - YouTube

The only other thing I would probably try is booting with a Linux Live Distro and see if that might reveal anything of consequence and possibly give you a means to backup any critical data
Linux Mint 20 "Ulyana" - MATE (64-bit) - Linux Mint
 
Ad

Advertisements

KSV

Joined
Dec 23, 2020
Messages
6
Reaction score
2
Thank you for the tips.

I have ordered a replacement drive. In the meantime, I have been trying various tips available in the forum. The latest is that I now obtain 'No boot device found'. One thread suggests going to the USBCD/Troubleshoot/command prompt and then executing
diskpart
list disk
It showed Disk 0 as 476 Gb (the XPS hard drive)

list volume
This showed two volumes C (100Mb), E (476Gb) and two more presumably from the USB CD F Windows RE (506 Mb) and D ESD-USB) (7799 Mb)

I also tried
bootrec /fixboot
The operation completed successfully.

bootrec /fixboot
Access is denied

Another dead end! I do not know how to overcome this one. I shall keep trying.

I also tried Ubuntu, which I had installed earlier on an ancient computerto replace Win 7, and which works without trouble. On the XPS, Ubuntu complained about RST. Apparently, the XPS came with a RAID configuration and I am not sure whether I should reset RST. For the present I am trying various strands to fix Win10.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top