[SOLVED] BSOD c000021a, no dump - Windows 7 x64

R

rvnlord

Member
Joined
Mar 11, 2015
Posts
14
Hello again,

Recently, on my second old PC I am experiencing problem which drives me mad.
Moreover I got no logs at all

This is BSOD:

stop: c000021a {fatal system error}
the windows subsystem system process terminated unexpectedly with a status of 0xc0000005
(0xfc0931b2f 0x00b9eb90).
The system has been shut down.

1. I got Minidumps enabled, to be sure I crashed it on purpose once and there was a minidump file, but not with this bsod, this bsod generates no dump file which is weird.
2. In event viewer I got one line, system shut down unexpectedly, time.
3. I have no idea how can I diagnose it having absolutely no logs
4. RAM is ok
5. SMART shows no errors
6. I ran chkdsk /r /f
7. I did many other common things which I probably forgot to mention.

Would be grateful for help.
Tell me how and I can provide you whatever log you need.
 
Hello again,
thanks for the answer, unfortunately there is nothing that can help me in the post you linked, I tried countless other things but still bluescreen appears (randomly). I simply receive bsod, no dump - only information in the event viewer that "system shutdown unexpectedly". I would be grateful for further help, especially for information how can I gather any useful log in this case.

Bsod can appear when system was 8 hours idle, or after 10 minutes of watching a movie, completely randomly.
 
This bug check in most if not all cases is caused by a critical Windows component corruption (.dll, piece of the file system, etc). 9/10 times I've seen this bug check, a repair with the OS disc was necessary, or a reformat.

But anyway, as said above, without a dump there's no way to know for sure.
 
From what I can see, the linked post is related to the situation when dumps are not being produced at all, but as I mentioned in my first post, dumps are being produced (I crashed system on purpose to check that they work). Only THIS particular Bluescreen produces no dump file. So my question remains, how can I log anything at all from this crash?
 
1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

3. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Ensure all of that is in place.

If it is, just try a repair of Windows. If it fails, you'll have to reformat. That's just how this bug check goes.
 
Alright, I came back home and indeed it is all in place, I followed the steps (again dumps are working, but not for this bsod).
So your suggestion is repair from OS disc, if all is idd in place, and by that you mean repair installation? It will mess my customization and it will require to decrypt entire partition.

You are the experts, so can you tell me, if this particular BSOD should produce dump at all? (I read somehwere on MS forum that this one doesn't). Or is there a reason why it can't save dump to a file in this particular case (like I don't know, RAM failure)? I say again: dumps ARE working, just not in this case.
 
Thanks for help, but I refuse to think that my only way to go is repair install. I don't have logs so I think it is hardware problem. I think PC cannot access its resources due to RAM, PSU or Connection Failure, what else can cause that? You are the experts, so I am asking you how can I get more information about this problem? It seems to be nothing at all in the logs. I am here to fix the problem, not reinstall my entire system... Anyway, thanks for your help, I know that you spent your time trying to figure this out and as always I am grateful.
 
I would like to find out what causes this, if I repair install I will never know. Could you give me some ideas where else to look?
 
Without a dump file it's pretty much impossible.
The cause is almost certainly OS corruption, as Patrick has said, meaning the only option is a repair/clean install.
 
I would like to find out what causes this
Click to expand...

Me too, but without a dump there's no way to know.

All I know is, when this bug check is thrown it implies your OS is corrupt, and it either needs to be repaired or installed. That's it.
 
It crashed again, but this time sth actually appeared in the event log, what is weird, according to the event log, it happened 2 seconds after the crash

Code: 
Faulting application name: csrss.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc115
Nazwa moduล‚u powodujฤ…cego bล‚ฤ…d: sxs.dll, wersja: 6.1.7601.17514, time stamp: 0x4ce7c9cc
Exception code: 0xc0000005
Fault offset: 0x0000000000011b2f
Faulting process id: 0x30c
Faulting application start time: 0x01d07c236a4fd313
Faulting application path: C:\Windows\system32\csrss.exe
Faulting module path: C:\Windows\system32\sxs.dll
Report Id: 5265eb0f-e880-11e4-960e-d43d7ef137da

I am writing to let you know asap, I am going to try to do something with it tommorow, because it is very late here right now.
 
Because this is a user-mode dump, from the Client/Server Runtime Subsystem process.

Interesting considering that when this process appcrashes, so does the system with an 0xF4 bug check, so not sure why you're not getting kernel dumps.

Code: 
0:010> knL
 # Child-SP          RetAddr           Call Site
00 00000000`029ffa88 00000000`76efe892 ntdll!ZwWaitForSingleObject+0xa
01 00000000`029ffa90 00000000`76efead5 ntdll!RtlReportExceptionEx+0x1d2
02 00000000`029ffb80 000007fe`fcbe3423 ntdll!RtlReportException+0xb5
03 00000000`029ffc00 00000000`76ea3e50 csrsrv!CsrpReportToWerSvcThread+0x23
04 00000000`029ffc30 00000000`00000000 ntdll!RtlUserThreadStart+0x25

Basically ntdll is starting a user thread, and csrss is reporting. ntdll shortly thereafter reports an exception occurred, and then hangs on the ZwWaitForSingleObject function because the state was never set to Signaled as the exception likely occurred and csrss inevitably crashed or hung due to being the sole reason for the exception.

Overall, this kinda just proves OS corruption, and that the issue is probably csrss.

Again, repair or reinstall.
 
Last edited:
may be your Eset antivirus is the problem, because you have Acronis running you may quickly revert to an running system. :cool3:
 
I don't think I ever said there wasn't?

A repair should be attempted with the OS disc first, and if it fails, a reinstall is the only remaining option.

I'm not sure why I need to keep conveying this.
 

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

Back
Top