Rather rare and random 0xc000021a BSODs

eddman · Sep 14, 2014

Once in a while I get a 0xc000021a BSOD, which seem to be happening right after boot.

Here are the latest two.

----------------
Windows 8.1 enterprise, with all updates except September update KB2984006.

P.S. The SF Diagnostic Tool doesn't work for me. It gives no results.

usasma · Sep 15, 2014

Please make the following reports and upload them with your next post:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. If possible, use the "inside Windows" flash mechanism (if your OEM provides one).

There's a good chance that this system is not compatible w/Win8 or 8.1 If that's the case, we may not be able to fix it. We will continue to offer suggestions, but it's up to you to decide if it's too much trouble to continue. If so, you may be able to find greater reliability by reverting to Win7 or even Vista.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

rsdrvx64.sys Thu Feb 12 08:01:49 2009 (49941DBD)
EldoS Corporation RawDisk Driver
http://www.carrona.org/drivers/driver.php?id=rsdrvx64.sys

Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

The drivers that are [DEL]struckout[/DEL] don't have updates available (AFAIK).
DO NOT delete them, just leave them be.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Sun Sep 14 16:27:53.242 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091514-20390-01.dmp]
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Built by: [B]9600[/B].17238.amd64fre.winblue_gdr.140723-2018
System Uptime:[B]0 days 0:03:57.020[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::OKHAJAOM::`string'+b69 )[/B]
BugCheck [B]C000021A, {ffffc001a82a91f0, 0, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]WINLOGON_FATAL_ERROR (c000021a)[/url]
Arguments: 
Arg1: ffffc001a82a91f0, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000
Arg2: 0000000000000000, Error Code.
BUGCHECK_STR:  0xc000021a_DCOM_Terminated
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: [B]0xc000021a_DCOM_Terminated_nt!_??_::OKHAJAOM::_string_[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  F7
  BIOS Release Date             07/10/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  P35-S3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep  2 17:29:03.216 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\090314-13765-01.dmp]
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Built by: [B]9600[/B].17238.amd64fre.winblue_gdr.140723-2018
System Uptime:[B]0 days 0:01:54.996[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::OKHAJAOM::`string'+b69 )[/B]
BugCheck [B]C000021A, {ffffc001631f4920, 0, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]WINLOGON_FATAL_ERROR (c000021a)[/url]
Arguments: 
Arg1: ffffc001631f4920, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000
Arg2: 0000000000000000, Error Code.
BUGCHECK_STR:  0xc000021a_DCOM_Terminated
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: [B]0xc000021a_DCOM_Terminated_nt!_??_::OKHAJAOM::_string_[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  F7
  BIOS Release Date             07/10/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  P35-S3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Sun Sep 14 16:27:53.242 2014 (UTC - 4:00)**************************
[COLOR=RED][B]rsdrvx64.sys         Thu Feb 12 08:01:49 2009 (49941DBD)[/B][/COLOR]
ElbyCDIO.sys         Mon Mar  4 04:21:51 2013 (513467AF)
vmci.sys             Fri May 17 21:19:18 2013 (5196D716)
VMNET.SYS            Thu Jul 18 15:42:50 2013 (51E8453A)
vmnetadapter.sys     Thu Jul 18 15:43:00 2013 (51E84544)
vmnetbridge.sys      Thu Jul 18 15:43:47 2013 (51E84573)
VClone.sys           Wed Jul 24 11:02:55 2013 (51EFEC9F)
vsock.sys            Wed Jul 31 22:46:10 2013 (51F9CBF2)
eamonm.sys           Thu Aug 15 10:53:50 2013 (520CEB7E)
ehdrv.sys            Thu Aug 15 10:54:11 2013 (520CEB93)
EpfwLWF.sys          Thu Aug 15 10:55:11 2013 (520CEBCF)
epfwwfp.sys          Thu Aug 15 10:55:12 2013 (520CEBD0)
epfw.sys             Thu Aug 15 10:55:18 2013 (520CEBD6)
edevmon.sys          Mon Aug 19 09:00:54 2013 (52121706)
[DEL]intelppm.sys         Thu Aug 22 04:46:35 2013 (5215CFEB)
dump_storahci.sys    Thu Aug 22 07:40:39 2013 (5215F8B7)
[/DEL]

RTKVHD64.sys         Tue Nov  5 06:39:41 2013 (5278D8FD)
Rt630x64.sys         Tue Feb 18 06:44:16 2014 (53034790)
hcmon.sys            Thu Feb 27 21:40:28 2014 (530FF71C)
nvlddmkm.sys         Mon May 19 19:08:44 2014 (537A8EFC)
idmwfp.sys           Sun Jun  8 18:40:54 2014 (5394E676)
vmnetuserif.sys      Thu Jun 12 19:45:38 2014 (539A3BA2)
VMkbd.sys            Thu Jun 12 20:20:01 2014 (539A43B1)
vmx86.sys            Thu Jun 12 21:09:56 2014 (539A4F64)
[/font]

eddman · Sep 16, 2014

There is no new BIOS update for this motherboard.

I don't know if it's a compatibility issue. I've been using W8.1 for a few months and these 0xc000021a BSODs are new to me.

I removed the rsdrvx64.sys driver altogether.

I found the SF Diagnostic Tool's result files. They were in partition D: for some reason.

usasma · Sep 16, 2014

What may happen is that an update to Windows may change how a function works with the hardware on your system. This is how incompatibilities are exposed (and may not be evident at first). The point here is that you may get frustrated trying to fix this - and the fix for that would be to revert to an earlier version of Windows.

FWIW - I had a Lenovo x61t tablet that I installed Win8 on (it's BIOS dated from 2008).
The ability of the OS to work with the BIOS was greatly increased in Win8, so that's why I single out older BIOS's
The tablet had some "quirks" that I tried to fix. As time went on the quirks got worse and worse. I finally took the computer with me when I visited Microsoft and had the people there try to help me. We were unable to fix it, even with the assistance of some of the greatest technical minds that I have ever known.
Finally I gave up and reverted to Win7 - and the system works without problems!

If the BSOD issues continue, please run Driver Verifier according to these instructions: Driver Verifier Settings

I have had issues with Virtual Machine software, and suggest that you uninstall it in order to test the system. Feel free to reinstall it once the system is stabilized.

The WER section of MSINFO32 shows Power Policy issues with combase.dll
Are there any particular things related to power policy that stick out in your mind?
Try changing the power policies to low-performance settings (powercfg.cpl) and see if that helps

Another possibility is the network connection. Please try a new cable, and if possible, try another network connection.

eddman · Sep 16, 2014

usasma said:
What may happen is that an update to Windows may change how a function works with the hardware on your system. This is how incompatibilities are exposed (and may not be evident at first).

If so, then It could very much be possible. I'll revert back to windows 7 as a last resort, if need be.

usasma said:
If the BSOD issues continue, please run Driver Verifier according to these instructions: Driver Verifier Settings

Later, I suppose.

usasma said:
I have had issues with Virtual Machine software, and suggest that you uninstall it in order to test the system. Feel free to reinstall it once the system is stabilized.

I need VMware for testing purposes. I'm not sure if I can uninstall it, for now.

usasma said:
The WER section of MSINFO32 shows Power Policy issues with combase.dll
Are there any particular things related to power policy that stick out in your mind?
Try changing the power policies to low-performance settings (powercfg.cpl) and see if that helps

I don't know what to tell you. Sometimes the computer has problems going into sleep or hibernating. It gets stuck, with monitor turned off but the system still working, fans spinning. As a result I tend not to use them.

usasma said:
Another possibility is the network connection. Please try a new cable, and if possible, try another network connection.

Never thought bad network connection could cause BSODs. Is windows really that sensitive?!

In any case, thank you very much for helping me. There are people who wouldn't do such stuff unless there was a lot of money involved, yet you do it for free.

usasma · Sep 16, 2014

A story from my own experience.....

Years ago one of my son's computers was hit by a lightning strike.
The strike came through the network cable (from the cable modem)
It fried (we found out later on) the 56k telephone modem - which wasn't connected and we didn't use.

This damage caused BSOD's which took me weeks to troubleshoot.
When I started removing parts to troubleshoot the BSOD's we found that it was this device.

We'll continue to work with you on this until you decide that you've had enough.
Just zip up and upload the memory dumps (the contents of C:\Windows\Minidump) as they occur.

Good luck!

eddman · Nov 18, 2014

I encountered a 0x00000024 (NTFS related) BSOD while updating windows.

usasma · Nov 19, 2014

The STOP 0x24 is about the file system (NTFS) on the hard drive.
Try running chkdsk /r /f from an elevated (Run as administrator) Command Prompt
Try running hard drive diagnostics on ALL hard drives: Hard Drive Diagnostic Procedure

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Tue Nov 18 17:29:18.147 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111914-30718-01.dmp]
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Built by: [B]9600[/B].17328.amd64fre.winblue_r3.140827-1500
System Uptime:[B]3 days 5:28:47.304[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!FsRtlAcquireFileForCcFlushEx+51 )[/B]
BugCheck [B]24, {b500190637, ffffd00020e66d48, ffffd00020e66550, fffff8000dc7d089}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000024]NTFS_FILE_SYSTEM (24)[/url]
Arguments: 
Arg1: 000000b500190637
Arg2: ffffd00020e66d48
Arg3: ffffd00020e66550
Arg4: fffff8000dc7d089
PROCESS_NAME:  MRT.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]0x24_nt!FsRtlAcquireFileForCcFlushEx[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  F7
  BIOS Release Date             07/10/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  P35-S3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Tue Nov 18 17:29:18.147 2014 (UTC - 5:00)**************************
lvrs64.sys           Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys          Mon Oct 22 22:12:08 2012 (5085FCF8)
ElbyCDIO.sys         Mon Mar  4 04:21:51 2013 (513467AF)
vmci.sys             Fri May 17 21:19:18 2013 (5196D716)
VMNET.SYS            Thu Jul 18 15:42:50 2013 (51E8453A)
vmnetadapter.sys     Thu Jul 18 15:43:00 2013 (51E84544)
vmnetbridge.sys      Thu Jul 18 15:43:47 2013 (51E84573)
VClone.sys           Wed Jul 24 11:02:55 2013 (51EFEC9F)
vsock.sys            Wed Jul 31 22:46:10 2013 (51F9CBF2)
eamonm.sys           Thu Aug 15 10:53:50 2013 (520CEB7E)
ehdrv.sys            Thu Aug 15 10:54:11 2013 (520CEB93)
EpfwLWF.sys          Thu Aug 15 10:55:11 2013 (520CEBCF)
epfwwfp.sys          Thu Aug 15 10:55:12 2013 (520CEBD0)
epfw.sys             Thu Aug 15 10:55:18 2013 (520CEBD6)
edevmon.sys          Mon Aug 19 09:00:54 2013 (52121706)
intelppm.sys         Thu Aug 22 04:46:35 2013 (5215CFEB)
exfat.SYS            Thu Aug 22 07:40:18 2013 (5215F8A2)
dump_storahci.sys    Thu Aug 22 07:40:39 2013 (5215F8B7)
RTKVHD64.sys         Tue Nov  5 06:39:41 2013 (5278D8FD)
Rt630x64.sys         Tue Feb 18 06:44:16 2014 (53034790)
hcmon.sys            Thu Feb 27 21:40:28 2014 (530FF71C)
nvlddmkm.sys         Mon May 19 19:08:44 2014 (537A8EFC)
idmwfp.sys           Thu Sep 25 11:44:24 2014 (54243858)
vmnetuserif.sys      Wed Oct 29 16:33:20 2014 (54514F10)
VMkbd.sys            Wed Oct 29 17:05:33 2014 (5451569D)
vmx86.sys            Wed Oct 29 17:51:42 2014 (5451616E)
[/font]

Rather rare and random 0xc000021a BSODs

eddman

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

eddman

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

eddman

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

eddman

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One