Windows 10: BSOD error 0xc000021a crash

This morning, I needed to check my emails so tried booting up my laptop only for the BSOD saying "Your PC ran into a problem and needs to restart. We are just collecting some error info and then we will restart for you." I allow it to reach 100% but whenever it starts to restart my laptop just freezes. No matter how many times I boot my computer this always seem to happen which is why I am unable to follow the BSOD posting instructions. Is there anyway I can fix this as I need certain data that is on my hard drive?

:)

 

windows 10 pro stuck in restart loop "your pc ran into a problem and needs to restart. We are just collecting some error info, and then we'll restart for you, stop code: 0xc000021a"

You can check this thread and follow the answer provided by Likhitha
V to resolve the issue with stop code: 0xc000021a error.

Update us on the results.

 

BSOD during gaming

I got BSOD while playing games, the error message shows memory manager, after that I cannot boot into windows because of BSOD error 0xc000021a, I can only boot into it by selecting "disable driver signature enforcement" , what information I need to provide
to get help?

 

Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

 

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html But if I can not actually load Windows at all at the moment should I just skip running SeaTools?

 

Never mind I didn't read the entirety of the post

*EDIT*
Now I have read other sections of the post on SeaTools it sounds like I would need another PC to download the software which I am not able to access until the weekend.

 

You could start with chkdsk already and hope it gives some result *Smile
I would recommend to run "chkdsk /r" (without quotes) in case chkdsk finds something it could fix it.

 

Right so I did what you suggested and it appears that it seems to have got stuck at a specific point however annoyingly neither my phone or iPad want to upload the photo I took so:
"X:\windows\system32>chkdsk C: /R
The type of the file system is NTFS.
Volume label is Windows10_OS.

Stage 1: Examining basic file system structure...
840192 file records processed.
File verification complete.
9361 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage...
L: 1068850 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors...
Security descriptor verification completed.
114330 data files processed.
CHKDSK is verifying Usn Journal...
16232 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data...
Progress: 211575 of 840176 done; Stage: 25%; Total: 18%; ETA: 3:53:32"

Like I said, it has now been at this point for over 12 hours now.

 

Please keep chkdsk running, it may take some time depending on how much it has to do and the size of the hard drive.


Warning Aborting chkdsk could cause damage

 

Chkdsk has just finished so:

"X:\windows\system32>chkdsk C: /R
The type of the file system is NTFS.
Volume label is Windows10_OS.

Stage 1: Examining basic file system structure...
840192 file records processed.
File verification complete.
9361 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage...
L: 1068850 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors...
Security descriptor verification completed.
114330 data files processed.
CHKDSK is verifying Usn Journal...
16232 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data...
840176 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters...
102123574 free clusters processed.
Free space verification complete.

Windows has scanned the file system and found no problems.
No further action is required."

This seems to imply there is nothing wrong however at the end it did fail to transfer logged messages to the event log with status 50.

 

This is just 1 step of finding the cause, there are a few usual causes for this crash.

• Mismatched system files,
• User-mode driver
• system service
• 3rd party app's

To proceed, you would need recovery media or the troubleshooting options.
I would recommend the recovery media in case the recovery partition(s) get damaged.
Recovery Drive - Create in Windows 10 - Windows 10 Forums

 

But if I can not load Windows and just continuously get the BSOD or the troubleshooting screen I won't be able to create the recovery drive, will I?

 

According to your answer you don't have access to any other pc running Windows 10?

 

Yes, I do not have access to any other PC running Windows 10 at the moment.

 

Alright, lets hope the recovery partition won't get damaged.

Try following, a clean boot
In the troubleshooting options, go to advanced options and click on command prompt.
In command prompt enter
Code: start msconfig[/quote] and press enter.
In msconfig, try following





Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist.