[SOLVED] W10 AMD BSOD Critical Process Died - No Boot

R

Reemul

Active member
Joined
Apr 6, 2018
Posts
25
Location
Brisbane, Australia
Hello

Pretty sure PC updated after being turned off for weeks.
Also received 0x000021a, but now only getting Critical Process Died.
Its stuck in a loop, crash, reboot, recovery console.
It showed a restore point, but I thought I better backup before restoring, so I removed the HDD to another PC, backed up, and returned it - restore point no longer available.
Safe mode gives same Critical BSOD.
I can only run programs from command prompt - sysnativefilecollectionapp - not working

Spec
W10 17134 Home
x64
Original OS OEM
3 years old
OS same
AMD Ryzen 2600x (1 Year old)
MSI A320M Gaming Pro (updated Bios - no effect)
Nvidia GTX1050 (tried old AMD card - no effect)
SP 2x 8Gb 2133 DDR4 (tried just using individual stick - no effect
Casecomm 550W (have tried other PS - no effect)
Partitions - 100Mb EFI Fat32
450Mb NTFS
1862Gb NTFS - Windows

Ran memtest & hdd test & malwarebytes ok

I tried to run SFC /scannow from the command prompt, but get "windows resource protection could not perform the requested operation.

Tried again with sfc /scannow /offwindir=d:\windows /offbootdir:e:\ but same error resource error.
I assigned e: to the efi partition - not sure on syntax of drive lettering. D is windows partition.

I tried DISM /image:d:\ /cleanup-image /scanhealth but get error 2 - Cannot find file specified.
Not sure if I have the options right there.
Log from X: View attachment dism.log.

Thanks for help in advance.

Reemul
 
Please show me the SMART status of the HDD:

GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:



  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
    info_failing.png
 
Can you upload a kernel dump for your 0xc000021a crash please?

C:\Windows > upload MEMORY.DMP somewhere and paste the link here.
 
Hello

I've found some dumps files. I've had a quick look in Windbg but none of these dmp's pertain to 0x021a
The 0x21a BSOD only appeared a couple times.

There is a 8gb memory.dmp file a couple days old. Wow they compress well.
MEMORY.zip - Google Drive

There is a series of dumpXXXX.tmp files in the c:. I renamed them to .dmp & they did contain data.
DUMP3f99.dmp - Google Drive
DUMP5e7b.dmp - Google Drive

Thanks
 
Code: 
Bugcheck code 000000EF
Arguments ffffc38f`6b097580 00000000`00000000 00000000`00000000 00000000`00000000

We have a critical system process that terminated, therefore Windows bugchecked.

Code: 
PROCESS ffffc38f6b097580
    SessionId: 0  Cid: 0234    Peb: 874afa6000  ParentCid: 0228
    DirBase: 209d00000  ObjectTable: ffffe68d7025ac80  HandleCount:  28.
    Image: csrss.exe
    VadRoot ffffc38f6b236690 Vads 17 Clone 0 Private 102. Modified 2. Locked 0.
    DeviceMap ffffe68d6ce020e0
    Token                             ffffe68d7025a060
    ElapsedTime                       00:00:00.258
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         10840
    QuotaPoolUsage[NonPagedPool]      2512
    Working Set Sizes (now,min,max)  (289, 50, 345) (1156KB, 200KB, 1380KB)
    PeakWorkingSetSize                259
    VirtualSize                       2101288 Mb
    PeakVirtualSize                   2101288 Mb
    PageFaultCount                    305
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      130

As usual with 0xEF, the Client/Sever Runtime Subsystem was the terminating process.

Code: 
7: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff9801`bcea1938 fffff802`be214151 nt!KeBugCheckEx
01 ffff9801`bcea1940 fffff802`be133e19 nt!PspCatchCriticalBreak+0xfd
02 ffff9801`bcea19e0 fffff802`be010e88 nt!PspTerminateAllThreads+0x15887d
03 ffff9801`bcea1a50 fffff802`be010c49 nt!PspTerminateProcess+0xe0
04 ffff9801`bcea1a90 fffff802`bdc50743 nt!NtTerminateProcess+0xa9
05 ffff9801`bcea1b00 00007ff8`79a001a1 nt!KiSystemServiceCopyEnd+0x13
06 00000087`4ad6fb68 00000000`0000002c 0x00007ff8`79a001a1
07 00000087`4ad6fb70 ffffffff`ffffffff 0x2c
08 00000087`4ad6fb78 00000000`c0000034 0xffffffff`ffffffff
09 00000087`4ad6fb80 0000024e`17180200 0xc0000034
0a 00000087`4ad6fb88 00000000`00000009 0x0000024e`17180200
0b 00000087`4ad6fb90 0000024e`172041f0 0x9
0c 00000087`4ad6fb98 00000001`00000002 0x0000024e`172041f0
0d 00000087`4ad6fba0 00000000`00000000 0x00000001`00000002

This is really simple OS corruption - how it occurred, IDK. Bad update? So many possibilities.

The only thing I can recommend is to repair Windows with the DVD and if it's not working/no restore point, your best bet is just to do a reset or refresh.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top