BSOD Page Fault In NonPaged Area

Garlotch

Reputable
Jun 27, 2014
31
0
4,530
Hey, I have been having this Blue Screen Of Death, it's happened about 5 times in the last day or so. The error message (or whatever you call it) It gives me is:

cdd.dll
PAGE_FAULT_IN_NONPAGED_AREA

I'm running a laptop. Originally windows 8 with win8 hard drive format, but i sort of tricked the HDD into formatting into NTFS, so I could load win7 on there, which I am currently running now.

4 Gb Ram.

Intel i3 Quad Core CPU

500 gb HDD Space

Intel Graphics HD 4000 GPU

Anyone have any ideas on how I could fix this?
 
Solution
See if there are any updates for this anvsnddrv.sys. Looks it belongs to AnvSoft Virtual Audio Device whatever this is

AVG can also cause this 0x50 stop error

See if theres an update for Virtualclone
Windows 8 IS NTFS. You may have tricked the UEFI BIOS, if you want to call it that, but you didn't need to. All you needed to do was a clean install and set the BIOS to legacy instead of AHCI, or actually, 7 supports AHCI and UEFI too so either way a clean install using the custom method with a delete and recreation of the target partition should have been fine.

I'd reinstall using the clean method. It's likely to be a bad installation or possibly a hardware issue. The file cdd.dll is a Windows System file and is unlikely to be the cause of your BSOD. It was probably the process that happened to be loading when the crash happened. You might run whocrashed and post the crash report here.
 

Garlotch

Reputable
Jun 27, 2014
31
0
4,530
I ran a scan, here what it showed me:

EDUKrUI.png


What do you make of this?
 

Garlotch

Reputable
Jun 27, 2014
31
0
4,530
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: GARLOTCH-LAPTOP
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV, SAMSUNG ELECTRONICS CO., LTD., SAMSUNG_NP1234567890
CPU: GenuineIntel Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4162686976 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 5/11/2014 6:01:51 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\110514-23696-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF9600079DC51)
Bugcheck code: 0x50 (0xFFFFF900C018D7A0, 0x0, 0xFFFFF9600079DC51, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 5/11/2014 6:01:51 a.m. GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdd.dll (cdd+0xDC51)
Bugcheck code: 0x50 (0xFFFFF900C018D7A0, 0x0, 0xFFFFF9600079DC51, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 5/11/2014 2:18:12 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\110514-23680-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6373)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000106373, 0xFFFFF880067D6030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 4/11/2014 7:40:49 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\110414-35833-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2328C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960003028C9, 0xFFFFF88009B88110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 19/09/2014 11:07:04 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-44366-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6373)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A6373, 0xFFFFF8800611C030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 

Garlotch

Reputable
Jun 27, 2014
31
0
4,530
Yeah It was definitely the AnyVideoConverter, something weird going on there, I tried uninstalling it multiple times, each time it would shutdown my PC and give me the BSOD. But i went into Safe Mode, and did it from there, which seemed to work. Thanks guys! Problem solved.

P.S If I get any new crashes, i will make another thread.

God bless you all, thanks Paul mate :)