BSOD with error PAGE_FAULT_IN_NONPAGED_AREA in CNG.SYS
-
Monday, February 18, 2013 7:55 AM
Hi everybody,
since this weekend I had several BSOD on two Server 2008 R2 machines.
Error was in all cases the same:
Bugcheck code: 0x50 (0xFFFFFA8080E00000, 0x0, 0xFFFFF880016BF6B2, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA
Analysing the dump files with WinDbg shows cng.sys as reason:
STACK_COMMAND: kb
FOLLOWUP_IP:
cng!SHA256Update+a6
fffff880`0148d6a2 488b4710 mov rax,qword ptr [rdi+10h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: cng!SHA256Update+a6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cng
IMAGE_NAME: cng.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fc987bf
FAILURE_BUCKET_ID: X64_0x50_cng!SHA256Update+a6
BUCKET_ID: X64_0x50_cng!SHA256Update+a6
Followup: MachineOwner
I already tried sfc /scannow (no errors). System are both updated and hardware is ok.
Does anybody know why this is happening and can help me find out the cause?
Any help appreciated...
All Replies
-
Monday, February 18, 2013 10:26 AM
Hi,
Bug checkcode: 0x50 is recorded for this BSOD.Have a look at below link and troubleshoot it accordingly.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
Below info is for your reference.
- Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
- Another common cause is the installation of a faulty system service.
- Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Regards, Ravikumar P
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Monday, February 25, 2013 4:43 AM
-
Monday, February 18, 2013 11:23 AM
Maybe it is a service that causes the BSOD.
Try disabling Non-Microsoft services from MSConfig.One at a time if possible so you'll be able to check which one has been corrupted.
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Monday, February 25, 2013 4:43 AM
-
Monday, February 18, 2013 1:05 PM
It could be caused by faulty Memory or device drivers.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
Boot the server in safe mode and perform the clean boot and check.
Troubleshooting the BSOD issues please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers, check this web site.
http://support.microsoft.com/common/international.aspxThanks
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Monday, February 25, 2013 4:43 AM
.png)
