BSOD - whocrashed points to cdd.dll and kernel

Hi. Thank you all for your help.

My computer has been getting BSOD memory dump errors for a couple of weeks now and I have tried many tools to pin down the error but at this point I need some expert guidance.

Steps I've taken so far:
Booting to safe mode and restoring to an earlier configuration before bsod started.
Uninstalling nvidia graphics card driver updates since after that driver update is when the problems first appeared (this could be synchronicity and not related).
Uninstalling and reinstalling everything but the OS.
Formatting the ssd and reinstalling a fresh copy of win7 using an older nvidia graphics driver that I knew to work for months without problems in the past.
Ran Memtest86+ for 3 passes with 0 errors reported in memory

Utilities for error checking I already installed:
WhoCrashed
NirSoft tools
Win Debugger utilities (windbgx64)
Driver Verifier

I still get the bsod. Most recently while playing Warframe but it's not always while gaming. Additionally the computer won't come back from sleep mode some times. When it does bsod it won't always restart correctly (the blue/on light will light up but nothing displays on the monitor and there is no sound of windows starting up so I am thinking it isn't getting past POST).

WhoCrashed seems to point to CDD.DLL and the kernel as the culprits but from what I've read they probably (hopefully) are fine and those were the services that were requesting information from the broken utility/driver when the bsod happens.

I've attached the memory dump file. Is there any other information you need?

Thanks in advance!!!!!!!!!!!!!!!!!!

I would start by running Driver Verifier, following this tutorial | Driver Verifier - Enable and Disable

Post back with the new dump files!

Ok I started Driver Verifier selecting everything but Windows components.

I put the computer to sleep while I went to run an errand. When I came back I moved the mouse, it came out of sleep mode, and about 1 second later bsod memory dump.

After the bsod the screen goes blank and is not responsive so I restarted the computer with the restart button on the tower. After restart I selected windows in safe mode with networking and after the windows splash screen loaded but before I could log in there was another bsod memory dump.

Attached is the new dump and other compressed files.

Thanks again for all your help!!

jamestcoop said:

Ok I started Driver Verifier selecting everything but Windows components.

I put the computer to sleep while I went to run an errand. When I came back I moved the mouse, it came out of sleep mode, and about 1 second later bsod memory dump.

After the bsod the screen goes blank and is not responsive so I restarted the computer with the restart button on the tower. After restart I selected windows in safe mode with networking and after the windows splash screen loaded but before I could log in there was another bsod memory dump.

Attached is the new dump and other compressed files.

Thanks again for all your help!!

The latest dump wasn't included in the last file you uploaded.

This one:

"On Mon 8/5/2013 1:41:22 AM GMT your computer crashed

You can upload it separately, you'll find it in a folder called minidump:

C:\Windows\minidump\
Look for a file from 8/5/2013.
If you're having issues uploadig | Screenshots and Files - Upload and Post in Seven Forums

Sorry I thought I followed the instructions correctly but I guess not.

Since then it has BSOD'ed another 3-4 times and I've included the new SF zipped folder and the more recent mini dump file in this post.

This is really frustrating! Thanks again for your help in figuring this out :)

Driver Verifier wasn't enabled.

Follow this tutorial instead | Using Driver Verifier to identify issues with Drivers

Here are some more. Driver verifier was on this time I hope!

On Tue 8/6/2013 6:48:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080613-11466-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50051288, 0x81800000BE9C3882, 0xFFFFF6FC50051281)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/6/2013 6:48:18 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x16F9B2)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50051288, 0x81800000BE9C3882, 0xFFFFF6FC50051281)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 311.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 311.06
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation MEMORY_MANAGEMENT



On Tue 8/6/2013 2:19:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080613-8096-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x5001, 0xFFFFF780C0000000, 0x4F82, 0x4F83FFFFFFF6)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/6/2013 5:05:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-9375-01.dmp
This was probably caused by the following module: ???????????.sys (Unloaded_???????????+0x1A)
Bugcheck code: 0x1A (0x5005, 0xFFFFF70001080000, 0xBC9, 0x1E54)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ???????????.sys .
Google query: ???????????.sys MEMORY_MANAGEMENT



On Tue 8/6/2013 4:10:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-10062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002FC1328, 0x0, 0xFFFFFA8006A50800)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/6/2013 2:16:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-7519-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xDB5, 0xDB300001B62)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/6/2013 2:15:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-10108-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x2474, 0x2462000048E0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Remove ATK0110 ACPI Utility:

Code:

ASACPI.sys   Mon Mar 28 05:30:36 2005

Driver Reference Table - ASACPI.sys