Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - whocrashed points to cdd.dll and kernel


06 Aug 2013   #11

Windows 7 Home Premium x64
 
 

You can just remove it Asus Bloatware are known to cause BSOD with Windows 7, especially that OLD!
Remove it as you would any other software then follow through with | Drivers - Clean Left over Files after Uninstalling

To make sure it's gone.

EDIT:


It was pointed out to me that it is better to update the driver rather then to remove it
seeing it will be automatically installed on reboot.

Click the link below:
Updated Version : 2009/12/07

Choose Windows 7 64bit
Attachment 280120

Scroll down and find:
Attachment 280121




My System SpecsSystem Spec
.

06 Aug 2013   #12

Win7 Home Premium 64bit 6.1.7601 Service Pack 1
 
 

I found and downloaded the appropriate ATK 0110 from the link above and went to the folder for 64 (instead of 32) and Windows 7 and double clicked on the file AsAcpiIns.exe which caused a bsod (possibly because I was listening to a radio program when attempting the install). Anyway I restarted the computer and went back and re-ran AsAcpiIns.exe and it ran without error (basically a cmd window opened briefly and closed and it was done).

I don't know if it worked. Do you know how to check where that driver would be listed? I found by typing "driverquery" into a command prompt I get a list of installed drivers which shows (briefly):


HTML Code:
Module Name  Display Name           Driver Type   Link Date             
============ ====================== ============= ======================
1394ohci     1394 OHCI Compliant Ho Kernel        11/20/2010 2:44:56 AM 
ACPI         Microsoft ACPI Driver  Kernel        11/20/2010 1:19:16 AM 
AcpiPmi      ACPI Power Meter Drive Kernel        11/20/2010 1:30:42 AM 
adp94xx      adp94xx                Kernel        12/5/2008 3:54:42 PM  
adpahci      adpahci                Kernel        5/1/2007 10:30:09 AM  
adpu320      adpu320                Kernel        2/27/2007 4:04:15 PM  
AFD          Ancillary Function Dri Kernel        12/27/2011 7:59:20 PM 
agp440       Intel AGP Bus Filter   Kernel        7/13/2009 4:38:43 PM  
aliide       aliide                 Kernel        7/13/2009 4:19:47 PM  
amdide       amdide                 Kernel        7/13/2009 4:19:49 PM  
AmdK8        AMD K8 Processor Drive Kernel        7/13/2009 4:19:25 PM  
AmdPPM       AMD Processor Driver   Kernel        7/13/2009 4:19:25 PM  
amdsata      amdsata                Kernel        3/18/2010 5:45:17 PM  
amdsbs       amdsbs                 Kernel        3/20/2009 11:36:03 AM 
amdxata      amdxata                Kernel        3/19/2010 9:18:18 AM  
AppID        AppID Driver           Kernel        11/20/2010 2:14:37 AM 
arc          arc                    Kernel        5/24/2007 2:27:55 PM  
arcsas       arcsas                 Kernel        1/14/2009 11:27:37 AM 
AsyncMac     RAS Asynchronous Media Kernel        7/13/2009 5:10:13 PM  
atapi        IDE Channel            Kernel        7/13/2009 4:19:47 PM  
b06bdrv      Broadcom NetXtreme II  Kernel        2/13/2009 2:18:07 PM
.....
etc.

The ATK / ASUS ACPI driver is not on this list, right? Does this mean it is gone?
My System SpecsSystem Spec
06 Aug 2013   #13

Windows 7 Home Premium x64
 
 

The way to really look for it in MSINFO32.
Start> RUN> "MSINFO32" without the quotes then hit [Enter].

In MSINFO32;
Press Ctrl+F and search for; ASACPI

If it doesn't find it it's gone.
My System SpecsSystem Spec
.


06 Aug 2013   #14

Win7 Home Premium 64bit 6.1.7601 Service Pack 1
 
 

Ok so it's still there in MSINFO32. How do I tell if the version listed is the old (broked/bsod cause) version or the new one I just downloaded and (hopefully) installed?


HTML Code:
mtsensor	ATK0110 ACPI UTILITY	c:\windows\system32\drivers\asacpi.sys	Kernel Driver	No	Manual	Stopped	OK	Normal	No	No
Should I just go to that path c:\windows\system32\drivers path and delete it? What will that break?
My System SpecsSystem Spec
06 Aug 2013   #15

Windows 7 Home Premium x64
 
 

Don't just delete it.

You can browse to "C:\Windows\system32\drivers" and look in its properties.

Attachment 280141*this is just an example, you should look for asacpi.sys
My System SpecsSystem Spec
06 Aug 2013   #16

Win7 Home Premium 64bit 6.1.7601 Service Pack 1
 
 

Ok properties says the current file was created Thursday, ‎May ‎14, ‎2009, ‏‎9:26:24 AM and is version 1043.5.0.0

I am having a hard time finding out if there is a newer version than what is installed. I found this (ASUSTeK Computer Inc. -Support- Drivers and Download ATK_package) but it says the ATK utilities are specific to Notebook and so that's a little confusing if this is the right place to be looking or not.

This site (Drivers and Download (M4A77TD PRO) [Official Site - Main Page]) shows an ATK0110 utility for my motherboard with a date of 2009.12.07 so that would be slightly newer than 5/14/2009 but still really old. Should I download and install this?

Again my neverending thanks for your patience and help with this.
My System SpecsSystem Spec
07 Aug 2013   #17

Windows 7 Home Premium x64
 
 

No don't download anything not from the OEM's (Original Equipment Manufacturer) website.

Since updating, did you have any issues?
My System SpecsSystem Spec
07 Aug 2013   #18

Win7 Home Premium 64bit 6.1.7601 Service Pack 1
 
 

Yeah still having issues.

I updated asacpi as directed above but the system was still doing bsod. I went to the system32/drivers folder and deleted asacpi entirely and it does not appear to be reinstalling itself as your earlier post indicated it might. It is gone I have rebooted a few times.

I read elsewhere that MS Security Essentials can cause BSOD so I removed it and installed Avast for antivirus instead.

I got a couple more bsod's today and I've attached the minidump files. The first one probably does not have driver verifier on but the later ones should.

Here is what whocrashed reports:

Quote:
On Wed 8/7/2013 10:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-25599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50073B08, 0x8570000011DF6882, 0xFFFFF6FC50073B01)
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 Wed 8/7/2013 10:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1B88E)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50073B08, 0x8570000011DF6882, 0xFFFFF6FC50073B01)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 8/7/2013 2:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-7410-02.dmp
This was probably caused by the following module: unknown_module_00000000`00000002.sys (Unloaded_Unknown_Module_00000000`00000002+0x17)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00928D7E0, 0xFFFFF8A00928D868, 0x5080304)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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.
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: unknown_module_00000000`00000002.sys .
Google query: unknown_module_00000000`00000002.sys BAD_POOL_HEADER



On Wed 8/7/2013 2:48:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-7410-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x1296EA, 0x2, 0x12A7B5)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.



On Tue 8/6/2013 9:46:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080613-11154-01.dmp
This was probably caused by the following module: asacpi.sys (ASACPI+0x19A0)
Bugcheck code: 0xC9 (0x22F, 0xFFFFF88003FDF9A0, 0xFFFFF980176FECF0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: asacpi.sys .
Google query: asacpi.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
My System SpecsSystem Spec
07 Aug 2013   #19

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by jamestcoop View Post
Yeah still having issues.

I updated asacpi as directed above but the system was still doing bsod. I went to the system32/drivers folder and deleted asacpi entirely and it does not appear to be reinstalling itself as your earlier post indicated it might. It is gone I have rebooted a few times.

I read elsewhere that MS Security Essentials can cause BSOD so I removed it and installed Avast for antivirus instead.

I got a couple more bsod's today and I've attached the minidump files. The first one probably does not have driver verifier on but the later ones should.
Please check your RAM.
RAM - Test with Memtest86+
*Read and follow carefully.
If no errors were found make sure your Intel 520 Series SSD is up to date with the latest firmware
Intel® Solid-State Drive Toolbox
F.A.Q
My System SpecsSystem Spec
08 Aug 2013   #20

Win7 Home Premium 64bit 6.1.7601 Service Pack 1
 
 

Ok I installed intel's ssd tool and everything there appears up to date.

I ran memtest86+ for 2 more passes today with no errors. I will run it overnight to get the complete 7 passes as recommended in the article you reference above.

In meantime, here are a few more minidump files attached as a zip archive.

Can I ask how it is you figured out what was the offending driver before? Is there a tutorial you might link me to with more information about reading windbg, whocrashed, and other dump/crash tools? Thanks again for all the help!
My System SpecsSystem Spec
Reply

 BSOD - whocrashed points to cdd.dll and kernel




Thread Tools



Similar help and support threads for2: BSOD - whocrashed points to cdd.dll and kernel
Thread Forum
Solved BSOD's, WhoCrashed says ntoskrnl.exe BSOD Help and Support
BSoD while playing Saints Row IV. WhoCrashed claims ntoskrnl.exe BSOD Help and Support
Solved Randoms BSOD since ~1 week. WhoCrashed - ntoskrnl.exe and ntkrnlmp.exe BSOD Help and Support
so i installed whocrashed BSOD Help and Support
New Windows kernel mode flaw points to future attack vectors News

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:25 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33