New Comp, constant crashing after installing drivers. (atdcm64a.sys)

Page 1 of 3 123 LastLast

  1. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    New Comp, constant crashing after installing drivers. (atdcm64a.sys)


    This is my first time building a PC and it starts to crash after installing the AMD drivers. I have tried to install the drivers from multiple source, the motherboard drivers CD, the graphic card CD, download from the AMD website. The crashing starts after a few minutes from installing the drivers and will continue to crash a few minutes after the reboot. I ran verifier.exe and found out the the possibility of the atdcm64a.sys error but i dont know how to solve it.

    Thank you for your time :)
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard, Evan :)

    Most probably you have installed an old ATI driver of January 2010. You should upgrade it , go to AMD Support & Drivers to get the updates.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {20e, fffff880071bc432, fffff9803aa10e10, 0}
    
    Unable to load image \??\D:\Drivers\ALL in 1\AMD\Win7-64_Win7_Vista64_Vista(8.70a_WHQL)\Bin64\atdcm64a.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atdcm64a.sys
    *** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
    Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 000000000000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized
        to STATUS_NOT_SUPPORTED.
    Arg2: fffff880071bc432, The address in the driver's code where the error was detected.
    Arg3: fffff9803aa10e10, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_20e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  20e
    
    FAULTING_IP: 
    atdcm64a+2432
    fffff880`071bc432 89442478        mov     dword ptr [rsp+78h],eax
    
    FOLLOWUP_IP: 
    atdcm64a+2432
    fffff880`071bc432 89442478        mov     dword ptr [rsp+78h],eax
    
    IRP_ADDRESS:  fffff9803aa10e10
    
    DEVICE_OBJECT: 0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  InstallManager
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800031683dc to fffff80002ce1640
    
    STACK_TEXT:  
    fffff880`0854b418 fffff800`031683dc : 00000000`000000c9 00000000`0000020e fffff880`071bc432 fffff980`3aa10e10 : nt!KeBugCheckEx
    fffff880`0854b420 fffff800`0317247a : fffff800`031669f0 fffff880`071bc432 fffff980`3aa10e10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0854b460 fffff800`03173483 : 00000000`0000020e 00000000`00000000 fffff980`3aa10e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0854b4b0 fffff800`03174115 : 00000000`00000001 fffffa80`06cf1a02 fffff980`3aa10e10 fffff800`03169e56 : nt!VfErrorReport1+0x63
    fffff880`0854b550 fffff800`031681e0 : fffff980`3aa10fb8 fffffa80`08781e80 00000000`00000000 fffff800`03176e3f : nt!VfPnpVerifyNewRequest+0x45
    fffff880`0854b580 fffff800`03180b33 : fffffa80`06cf1aa0 fffffa80`08781e80 fffff980`3aa10e10 fffffa80`087cc240 : nt!VfMajorVerifyNewRequest+0x70
    fffff880`0854b5d0 fffff800`03180d86 : fffff880`00000001 fffffa80`00000001 fffffa80`00000001 fffff880`071bc432 : nt!IovpCallDriver1+0x483
    fffff880`0854b680 fffff800`03184bb2 : fffff980`3aa10e10 00000000`00000002 fffff980`3aa10e10 fffff800`02f4d4cc : nt!VfBeforeCallDriver+0x186
    fffff880`0854b6e0 fffff880`071bc432 : fffff980`3aa54ee0 00000000`00000002 fffffa80`086586f0 fffffa80`06db7ae0 : nt!IovCallDriver+0x502
    fffff880`0854b740 fffff980`3aa54ee0 : 00000000`00000002 fffffa80`086586f0 fffffa80`06db7ae0 00000000`00000000 : atdcm64a+0x2432
    fffff880`0854b748 00000000`00000002 : fffffa80`086586f0 fffffa80`06db7ae0 00000000`00000000 fffff880`0854b7a0 : 0xfffff980`3aa54ee0
    fffff880`0854b750 fffffa80`086586f0 : fffffa80`06db7ae0 00000000`00000000 fffff880`0854b7a0 fffff880`0854b790 : 0x2
    fffff880`0854b758 fffffa80`06db7ae0 : 00000000`00000000 fffff880`0854b7a0 fffff880`0854b790 00000000`00000000 : 0xfffffa80`086586f0
    fffff880`0854b760 00000000`00000000 : fffff880`0854b7a0 fffff880`0854b790 00000000`00000000 fffff980`3aa10e10 : 0xfffffa80`06db7ae0
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  atdcm64a+2432
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atdcm64a
    
    IMAGE_NAME:  atdcm64a.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b4e8192
    
    FAILURE_BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432
    
    BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm atdcm64a
    start             end                 module name
    fffff880`071ba000 fffff880`071c4000   atdcm64a T (no symbols)           
        Loaded symbol image file: atdcm64a.sys
        Image path: \??\D:\Drivers\ALL in 1\AMD\Win7-64_Win7_Vista64_Vista(8.70a_WHQL)\Bin64\atdcm64a.sys
        Image name: atdcm64a.sys
        Timestamp:        Thu Jan 14 07:59:38 2010 (4B4E8192)
        CheckSum:         00016432
        ImageSize:        0000A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    I ran the AMD Automatic Detect and Install software but it saids I already had the latest drivers installed...

    P.S ok ignore that i just tried to open the AMD VISION engine control center and it cant be opened.
    i will post an update after i download and install a driver

    P.S.S for some reason, i got the unable to load detection driver while trying to install the latest driver, may i ask how to fix it?
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    You are to get the ATI DSM dynamic driver only, not the entire crystelite control center .
      My Computer


  5. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #5

    Er... I got the Unable to load detection drivers error when attempting to install the driver, btw how do you download only the ATI DSM dynamic driver, doesnt seem like i can find it at the AMD website
    Does save mode prevent you from installing drivers cause im in save mode to prevent any crashing just my journey to fix my comp
    Last edited by Evanescents; 23 Aug 2012 at 11:16. Reason: Adding information
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Download and install Driver Sweeper .
    Boot into Advanced Boot Options, and select safe mode (without networking).
    Search for Driver Sweeper in your start menu.
    Select all ATI component and clean them.
    Now try to reinstall the driver.

    You install the downloaded latest version of your graphics driver, try to disable the Crystalite control center during installation .
      My Computer


  7. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #7

    Ok did exactly as told, wipe out the ATI component with Driver Fusion (updated version of Driver Sweeper) then reinstalled the latest version. Crashing still happens after a few minutes...

    Thank you again for all your time
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Can you upload the new dump please ?
      My Computer


  9. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #9

    I dont see any new dump... I think it's because the crash is a screen turn complete white (or colorful) crash and not a BSOD so i dont think that it saved any dumps.
      My Computer


  10. Posts : 16
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #10

    After a few more tries of uninstalling and installing my drives, I've managed to have my computer stayed up for the whole night without crashing. If my comp didnt crash for the next few days, I will change this thread to solved.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 03:58.
Find Us