New
#1
BSODs, ntoskrnl.exe, fltmgr.sys, cdd.dll ???
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.