Windows 10: BSOD on print preview, PAGE_FAULT_IN_NONPAGED_AREA, cdd.dll

While inside an Autodesk Revit 2017 file the computer will crash every time we have a specific file open and we try to do a print preview. BSOD occurs shortly after it generates the preview.

Stop Code: PAGE_FAULT_IN_NONPAGED_AREA
What Failed: cdd.dll
(image attached with BSOD screen)

• BSOD only occurs in 1 specific Revit file when generating a print preview. (doesn't matter which printer is selected for use, error still occurs).
• BSOD does not occur when we are on a different computer generating a print preview on the same file that continuously crashes the computer I am posting about.
• BSOD does not occur on the offending computer when we are in other Revit files and are generating a print preview.

Any help is greatly appreciated. Let me know if there is any other information is needed and I will be happy to supply what I can.
Thanks

:)

 

Windows 10 BSOD - SYSTEM_SERVICE_EXCEPTION (win32kbase.sys+4d8be)

Another BSOD today with the same BSOD info. - SYSTEM_SERVICE_EXCEPTION

I was browsing with chrome, RAM ran out and my external monitor and laptop screen went black and then BSOD appeared.

I checked the memory.dmp file, and found that cdd.dll could be the cause of BSOD.

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: taskhostw.exe

FOLLOWUP_IP:

cdd!CddW32kCloseProcess+2f

fffff961`5bb82a4f 4981c6801b0000 add r14,1B80h

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: cdd!CddW32kCloseProcess+2f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cdd

IMAGE_NAME: cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d7cd

IMAGE_VERSION: 10.0.10586.0

STACK_COMMAND: .cxr 0xffffd000272cace0 ; kb

BUCKET_ID_FUNC_OFFSET: 2f

FAILURE_BUCKET_ID: 0x3B_cdd!CddW32kCloseProcess

BUCKET_ID: 0x3B_cdd!CddW32kCloseProcess

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_cdd!cddw32kcloseprocess

FAILURE_ID_HASH: {7a4e0392-a57c-b837-f9c0-ee576eb31f80}

Followup: MachineOwner

---------

 

BSOD - Memory Management and other errors on newly installed Windows 10

Was one of the BSoDs PAGE_FAULT_IN_NONPAGED_AREA?

 

Just in case it helps I also used the Log Collector V2 Beta to collect info. Please see attached.

 

The first 4 dumps point to cdd.dll as the cause which is unlikely as it's a system file that has not been changed in a while. The lasty says memory_corruption in win32k.sys, again unlikely.

You have 64GB of RAM so I would start by removing half the ram and running for awhile and see if a BSOD occurs. If not, swap theinstalled and removed ran and run some more to see if it occurs. If it does then one of the two 16GB DIMMS currently install is defective. You can swap them out ione at a time with the removed DIMMs to try to find the bad one or you can run memtest76+ as follows:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

If removing ram doesn't help then I'd try Driver Verifier:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 beta log collector and upload the resulting zip file.

 

Rich thanks for the response. I'll check to see if it still crashes on the revit file with different combinations or RAM as suggested. It has been unfailing to crash when on this one particular (large) file. That may allow me to narrow down the RAM sticks pretty quickly. I'll post the results as soon as I am able to.
Thanks for your help and suggestions.

 

Has to be something local to your system since the file works okay on a different system, so as you say, it makes an excellent test vehicle.