I'm running windows 10 build 14393 on a laptop.

Some backstory: I've been getting very frequent BSODs with the error being "kernel security check failure"- about once every 2 days. I think I finally narrowed the issue down to being caused by my new usb 3 hub. I unplugged the hub and got no BSODs for about a week- at least until today.

Today I got a BSOD but instead the error was "Page Fault in nonpaged area" (a message that I've never seen on this computer before). The file concerned was cdd.dll. What could be causing this type of BSOD?

My ram is new (got it around the same time as the USB hub- 2 months ago). However, this is the first time I've gotten the page fault error message in the 2 months with the new ram, and the "kernel security check failure" errors kept occurring when I put the old ram in as a test. Memtest also completed 1 pass fine. Other than that, no hardware has been "changed" per-se, but I did open my laptop and put it back together to replace the screen which had broken.

If you'd like to read the above paragraphs in bullet form:

  • 2 months ago: Replaced screen
  • 2 months ago: Changed RAM
  • 1.6 months ago: Started using new USB hub
  • 1.5 months ago: Started getting BSODs "Kernel security check failure" fairly regularly.
  • 1 month ago: Put the old ram back in
  • 1 month ago: Memtest completed successfully
  • 1 month ago: Continued to receive kernel security check failure BSODs
  • 1 week ago: Stopped using USB hub
  • 1 week ago: stopped receiving kernel security check failure BSOD
  • Today: got a BSOD "page fault in nonpaged area" with the file being cdd.dll
  • Today: chkdsk completed succesfully
  • A quick Google search lists faulty hardware or software being the cause of a "page fault in nonpaged area" BSOD. The most common hardware is RAM. It'll be painful, but try removing one RAM chip at a time and testing that way. Memtest can't catch everything. – Kaizerwolf Aug 30 '17 at 13:09
  • yeah, I saw that. That's why I ran the old ram in it for a week, and mentioned that this is the first BSOD of it's type i've gotten having had the ram for 2 months – Blaine Aug 30 '17 at 13:12
  • also seemed like the problem can refer to a ram issue, but if a file is listed (like cdd.dll), it could mean that the issue was only in ram because that driver called it? – Blaine Aug 30 '17 at 13:12
  • Unless I'm mis-reading, you have not reinstalled the new RAM. Perhaps there's an issue with your old RAM? – Kaizerwolf Aug 30 '17 at 13:16
  • I assume the output of your analysis with windbg confirms the failure is with cdd.dll file? – Ramhound Aug 30 '17 at 13:34

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.