AtiHDMI.sys BSoD'ing randomly on sounds  


  1. Posts : 2
    Windows 7 RTM
       #1

    AtiHDMI.sys BSoD'ing randomly on sounds


    Hey guys (and girls),
    I've recently put my new system together and since then i've been experiencing several Blue Screen of Deaths.
    First i thought it was on the video driver, as windows crashed alot when alt-tabbing back into games, but my most recent crash was when i clicked on " next song" in windows media player. I've read a bit on it on the net, and it seems that updating the sounddriver should fix it, but as the crashes are random i'd like some extra advice so that i'm sure i'm not missing anything.

    The BSoD tells me that it was ATIHDMI.sys that crashed
    My system:
    Intel i7 920 not overclocked
    6 gb OCZ ddr3 1600 mhz ram
    Ati HD4890 1gb ddr5
    2x Samsung 1TB spinpoint in raid0
    Foxconn Flamingblade motherboard
    Hansol 17 inc crt display and a 42 inch full HD LG tv connected trough HDMI

    Running Win7 RTM fully updated

    I've zipped the Dumps in this post


    Thanks alot in advance!

    Edit:
    When windows crashes it takes atleast 1 or 2 restarts before Intel Matrix Storage Manager sees my Raid partitions as valid boots
    Last edited by Daredha; 20 Sep 2009 at 14:08. Reason: Forgot something
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    hi

    the last dump from 9/20/09 was caused by the ati driver again. here are the details
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\K\Desktop\092009-32947-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
    Debug session time: Sun Sep 20 13:34:23.937 2009 (GMT-4)
    System Uptime: 3 days 12:47:28.937
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffa800fbe0000, 0, fffff8800448f420, 0}

    Unable to load image \SystemRoot\system32\drivers\AtiHdmi.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AtiHdmi.sys
    *** ERROR: Module load completed but symbols could not be loaded for AtiHdmi.sys

    Could not read faulting driver name
    Probably caused by : AtiHdmi.sys ( AtiHdmi+3420 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa800fbe0000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800448f420, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
    fffffa800fbe0000

    FAULTING_IP:
    AtiHdmi+3420
    fffff880`0448f420 488b040a mov rax,qword ptr [rdx+rcx]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: audiodg.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff880085351a0 -- (.trap 0xfffff880085351a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00007fff719b3800 rbx=0000000000000000 rcx=fffffa80098c00e0
    rdx=000000000631ff1c rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800448f420 rsp=fffff88008535338 rbp=fffffa80098c00b4
    r8=0000000000000010 r9=0000000000000001 r10=aa00008000100000
    r11=fffffa80098c00b4 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    AtiHdmi+0x3420:
    fffff880`0448f420 488b040a mov rax,qword ptr [rdx+rcx] ds:00bb:fffffa80`0fbdfffc=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002b461e4 to fffff80002ac6f00

    STACK_TEXT:
    fffff880`08535038 fffff800`02b461e4 : 00000000`00000050 fffffa80`0fbe0000 00000000`00000000 fffff880`085351a0 : nt!KeBugCheckEx
    fffff880`08535040 fffff800`02ac4fee : 00000000`00000000 00000000`00000000 00000000`00270600 fffff880`04f883d0 : nt! ?? ::FNODOBFM::`string'+0x42907
    fffff880`085351a0 fffff880`0448f420 : fffff880`044a6666 00000000`00000000 fffffa80`0fbdff90 fffffa80`0fbdffd0 : nt!KiPageFault+0x16e
    fffff880`08535338 fffff880`044a6666 : 00000000`00000000 fffffa80`0fbdff90 fffffa80`0fbdffd0 fffffa80`07df38c0 : AtiHdmi+0x3420
    fffff880`08535340 00000000`00000000 : fffffa80`0fbdff90 fffffa80`0fbdffd0 fffffa80`07df38c0 fffffa80`07df9b40 : AtiHdmi+0x1a666


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    AtiHdmi+3420
    fffff880`0448f420 488b040a mov rax,qword ptr [rdx+rcx]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: AtiHdmi+3420

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AtiHdmi

    IMAGE_NAME: AtiHdmi.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49d61bf0

    FAILURE_BUCKET_ID: X64_0x50_AtiHdmi+3420

    BUCKET_ID: X64_0x50_AtiHdmi+3420

    Followup: MachineOwner
    ---------

    Im going to do a quick look at them all to see if they have anything in comman.

    since it seems like you had video driver problems before and this is hdmi related again, im suspicous.

    Ken
      My Computer


  3. Posts : 2
    Windows 7 RTM
    Thread Starter
       #3

    Thanks allot for your quick reply, i'm looking forward to any results you can find (as i'm pretty new to dumps, never occurred on my old xp machine)
      My Computer


 

  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:11.
Find Us