New build BSOD problem!!

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 13,354
    Windows 7 Professional x64
       #11

    Good thing you enabled Driver Verifier, because it is now pointing to your Realtek Audio Drivers. See if you can find an update:
    Code:
    Timestamp:        Wed Oct 21 10:27:48 2009 (4ADF1A64)
    It is recommended to download drivers from the computer manufacturer's website. However, if you can't find them, you can download some generic drivers directly from Realtek: Realtek

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Memdump3.zip\072710-21340-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50
    Debug session time: Tue Jul 27 05:43:15.839 2010 (GMT-4)
    System Uptime: 0 days 0:00:23.524
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D5, {fffff9800bbc8d60, 0, fffff880064ba1ee, 0}
    
    Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    
    Could not read faulting driver name
    Probably caused by : RTKVHD64.sys ( RTKVHD64+b61ee )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
    Memory was referenced after it was freed.
    This cannot be protected by try-except.
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff9800bbc8d60, memory referenced
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg3: fffff880064ba1ee, if non-zero, the address which referenced memory.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b50e0
     fffff9800bbc8d60 
    
    FAULTING_IP: 
    RTKVHD64+b61ee
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xD5
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88003721290 -- (.trap 0xfffff88003721290)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8
    rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002
     r8=0000000000000000  r9=fffff880064ba1ee r10=0000000000000000
    r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    RTKVHD64+0xb61ee:
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002efde54 to fffff80002e7d600
    
    STACK_TEXT:  
    fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx
    fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877
    fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e
    fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee
    fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    RTKVHD64+b61ee
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  RTKVHD64+b61ee
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: RTKVHD64
    
    IMAGE_NAME:  RTKVHD64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4adf1a64
    
    FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee
    
    BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
    Memory was referenced after it was freed.
    This cannot be protected by try-except.
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff9800bbc8d60, memory referenced
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg3: fffff880064ba1ee, if non-zero, the address which referenced memory.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS:  fffff9800bbc8d60 
    
    FAULTING_IP: 
    RTKVHD64+b61ee
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xD5
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88003721290 -- (.trap 0xfffff88003721290)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8
    rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002
     r8=0000000000000000  r9=fffff880064ba1ee r10=0000000000000000
    r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    RTKVHD64+0xb61ee:
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002efde54 to fffff80002e7d600
    
    STACK_TEXT:  
    fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx
    fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877
    fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e
    fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee
    fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    RTKVHD64+b61ee
    fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  RTKVHD64+b61ee
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: RTKVHD64
    
    IMAGE_NAME:  RTKVHD64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4adf1a64
    
    FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee
    
    BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm RTKVHD64
    start             end                 module name
    fffff880`06404000 fffff880`065ee080   RTKVHD64 T (no symbols)           
        Loaded symbol image file: RTKVHD64.sys
        Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
        Image name: RTKVHD64.sys
        Timestamp:        Wed Oct 21 10:27:48 2009 (4ADF1A64)
        CheckSum:         001FA0EE
        ImageSize:        001EA080
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  2. Posts : 18
    Windows 7 professional
    Thread Starter
       #12

    I've never been so happy to get blue screens. I dunno what driver verifier does, but the motherboard fans have been louder than usual. It really feels like my desktop is being tasked to the max. Anyway, there have been four more bsods. You will notice that they are similar and they seem to highlight the same drivers. After reading your email, I proceeded to uninstall the ati hdmi audio driver and update it to the version 6.0.1.6121. I had no issues with the replacement windows legacy drivers (which replaced it after installation) but when I tried to run the catalyst manager setup for the update I had 2 sets of bsods. One set of two just after the restart before the installation completed and another when I tried to update my amd chipset after I ran driveragent and according to it my usb controllers and ATISMBus were outdated (running the windows drivers). Dunno if I really know what those mean though..
    Anyway that's the story. If the manufacturers installer is causing the bsod then maybe I should stick with the windows drivers?
    Here are the dumps.
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #13

    Now it's pointing to atdcm64a.sys as the cause, which is definitely ATi-related. If you have the Catalyst Control Center installed, be sure to remove it.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Minidumps4.zip\072710-26020-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50
    Debug session time: Tue Jul 27 19:47:19.844 2010 (GMT-4)
    System Uptime: 0 days 0:34:05.530
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {20e, fffff88008df8432, fffff9801aa8aea0, 0}
    
    Unable to load image \??\C:\ATI\Support\9-9_vista64_win7_64_dd_ccc_wdm_enu\Driver\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
    ---------
      My Computer


  4. Posts : 18
    Windows 7 professional
    Thread Starter
       #14

    Should I uninstall the ati hdmi audio driver as well (The one mentioned in the former bsod)?
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #15

    Yep, go right ahead.
      My Computer


  6. Posts : 18
    Windows 7 professional
    Thread Starter
       #16

    Hi again!
    It's been a while. The good news is: it seems the system has been stable all this while. I kept it running for a week, and there was not a single BSOD until, well... 5 minutes ago. Pointing to something like NETIO.sys. I've kept driver verifier on all this while, restarted the system once and kept it going for a week straight, until this showed up. I don't know if it's time to turn verifier off because it supposedly induces more crashes. Any advice? Here's the dump:
      My Computer


  7. Posts : 13,354
    Windows 7 Professional x64
       #17

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
      My Computer


  8. Posts : 18
    Windows 7 professional
    Thread Starter
       #18

    2 new memdumps. Is there no end?
    I really appreciate your time in helping me deal with these annoyances. I had already uninstalled daemon tools as well as spdt.sys (unwittingly installed by a colleague). I hope my hardware is okay.
    When would you consider a safe time to deactivate Driver Verifier?
    Thanks.
      My Computer


  9. Posts : 18
    Windows 7 professional
    Thread Starter
       #19

    There was another one just a minute ago: A constant symptom seems to be Google chrome malfunctioning.. if that helps.

    Thanks a bunch!
      My Computer


  10. Posts : 18
    Windows 7 professional
    Thread Starter
       #20

    It's raining dumps. Here's the latest one.
      My Computer


 
Page 2 of 3 FirstFirst 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 19:32.
Find Us