BSODs, ntoskrnl.exe, fltmgr.sys, cdd.dll ???

[smilingbounder]

Need help with this. I used a program called "WhoCrashed" to read the .dmp files that were created after the BSODs.

Crash reports as follows:







On Thu 6/30/2011 11:04:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-25687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x18 (0xFFFFFA80018A8C90, 0xFFFFFA8006DB5D10, 0x1, 0x200000000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Tue 6/28/2011 7:55:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062811-27312-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x200DD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF960007400DD, 0xFFFFF88002466FE8, 0xFFFFF88002466850)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 6/15/2011 6:49:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061511-21968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800021C660, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Wed 6/15/2011 6:41:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061511-22937-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3B07)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001110B07, 0x0, 0x200000028)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 6/11/2011 6:46:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-22312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFF8A20F3F96F4, 0x0, 0xFFFFF800031A12D0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

[zigzag3143]

Need help with this. I used a program called "WhoCrashed" to read the .dmp files that were created after the BSODs.

Crash reports as follows:







On Thu 6/30/2011 11:04:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-25687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x18 (0xFFFFFA80018A8C90, 0xFFFFFA8006DB5D10, 0x1, 0x200000000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Tue 6/28/2011 7:55:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062811-27312-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x200DD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF960007400DD, 0xFFFFF88002466FE8, 0xFFFFF88002466850)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 6/15/2011 6:49:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061511-21968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800021C660, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Wed 6/15/2011 6:41:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061511-22937-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3B07)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001110B07, 0x0, 0x200000028)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 6/11/2011 6:46:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-22312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFF8A20F3F96F4, 0x0, 0xFFFFF800031A12D0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

sorry but we need the actual DMP files





To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[smilingbounder]

Ok, done. Attached the zip of the minidump files to this post.

 

[zigzag3143]

Ok, done. Attached the zip of the minidump files to this post.

There are several different codes and all blame drivers. Lets start by runing driver verifier to see if we cant id which

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.