BSOD while streaming on DisplayPort attached monitor?


  1. Posts : 127
    Windows 7 Ultimate x64
       #1

    BSOD while streaming on DisplayPort attached monitor?


    Hello & thank you in advance for your assistance.

    A month ago I installed a new Sapphire HD Radeon 7790 1GB DDR5 Dual-X OC GPU & began experiencing BSOD issues with driver atikmdag.sys. Would quite often go as long as a week between BSOD.

    The BSOD seems to be associated with DisplayPort attached monitor. Have two monitors attached via Dual DVI which work fine. Can stream no problem. The third monitor which is attached via DisplayPort seems to be the culprit. Streaming The Mentalist on CBS.com last night on that monitor & it crashed right away. Watched Mentalist on another monitor with ease.

    Have been working my way thru AMD Article Number: 27116 attempting to resolve this myself. Several driver versions with same results. Always use the AMD uninstall utility (restart), Driver Sweeper (restart) & CCleaner for good measure before installing next driver. BIOS is current as are Windows 7 updates. Have a 500W PSU, the GPU came overclocked from the factory & I did down clock for a short time which did not help. The GPU runs cool in the low 40's, the new PSU runs about 20 degrees hotter than the Dell OEM PSU. But it was crashing before with the cooler running 360W Dell PSU. Sapphire recommends a 500W PSU for this GPU even tho the 7790 uses less energy than the ATI Radeon 4850 it replaced.

    Purchased a new SSD & this past weekend performed a clean install of Windows, went very well. Windows found all the drivers, even for the new Sound Card. The Intel Driver Update Utility says there are newer Chipset Drivers avail (RAID drivers too?). But I had the newer Chipset drivers before the fresh install of Windows & it was crashing then.

    So I have no idea where to go from here. Suppose replacing the displayport cable then contacting Sapphire for a replacement GPU are the next steps.

    Here is a paste from the memorydump file to go along with the SF Diagnostic ZIP:


    Code:
    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    
    FAULTING_MODULE: fffff80002a07000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  516d7857
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA0000001
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8800485a9ac to fffff80002a7cbc0
    
    STACK_TEXT:  
    fffff880`02ffd738 fffff880`0485a9ac : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02ffd740 fffff880`0486e947 : 00000000`00000000 fffff880`02ffdab8 fffffa80`0c0a9ba0 fffff880`0560c48b : atikmdag+0x239ac
    fffff880`02ffd780 fffff880`048b60e4 : 00000000`00000000 fffffa80`0cbe8af0 fffffa80`0c0a9410 fffffa80`0c156000 : atikmdag+0x37947
    fffff880`02ffd7b0 fffff880`048b750e : fffffa80`0c156f40 fffff880`0486c569 fffffa80`0c052cb0 fffffa80`0c156000 : atikmdag+0x7f0e4
    fffff880`02ffd830 fffff880`048b764d : fffffa80`0c067840 fffff880`02ffd9b1 00000000`00000000 00000000`00000000 : atikmdag+0x8050e
    fffff880`02ffd8b0 fffff880`048b772a : fffffa80`0c0a9410 fffffa80`0c037000 00000000`00000000 fffffa80`0c0a9bb8 : atikmdag+0x8064d
    fffff880`02ffd8f0 fffff880`048b784d : fffffa80`0c037000 00000000`00000000 fffffa80`00000000 fffff880`0486e1b9 : atikmdag+0x8072a
    fffff880`02ffda10 fffff880`048bf141 : fffffa80`0c0381b0 fffff880`02ffdaf9 fffffa80`0c037000 fffff880`00000002 : atikmdag+0x8084d
    fffff880`02ffda60 fffff880`048b4ae0 : fffffa80`00000000 fffffa80`0c037000 00000000`00000001 00000000`00000001 : atikmdag+0x88141
    fffff880`02ffdb60 fffff880`0485c536 : fffffa80`0b53a140 fffffa80`0a467540 00000000`003e4ab9 00000000`00000000 : atikmdag+0x7dae0
    fffff880`02ffdb90 fffff880`04206fcf : fffff880`02fd5180 00000000`00000000 00002e51`fce51ab2 fffff880`02fe00c0 : atikmdag+0x25536
    fffff880`02ffdbc0 fffff800`02a78a1c : fffff880`02fd5180 fffff880`02ffdc70 fffffa80`0a467540 fffff880`02fe00c0 : atikmpag+0x6fcf
    fffff880`02ffdbf0 fffff800`02a748a2 : fffff880`02fd5180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!KeSynchronizeExecution+0x5ec
    fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiCpuId+0x6d2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+239ac
    fffff880`0485a9ac cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+239ac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    Last edited by newpgm; 23 Oct 2013 at 16:10.
      My Computer


  2. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #2

    Well it's a bit odd that I would come across this info now after a month and a half but - apparently there is an issue with the 20 pin on displayport cables. The infamous pin 20 issue.
    To be fully compliant a displayport cable must not have pin 20 wired through.
    The monitor is feeding power down pin 20, and the video card is feeding power out as well and the some video cards don't like it, (the power feed is to provide power to active converters, DP to VGA, HDMI etc.)


    This thread is pretty close to mine:
    How a Bad DisplayPort Cable Can Ruin Ruin Your Day
    For about 2 months I've been struggling with a BSoD error related to atikmpag.sys on my Windows 7, core i7, 2x 5870 Crossfire system.

    First, I assumed it was a driver issue. At the time I think the 12.1 Catalyst drivers had just been released. So, I rolled back to 11.10 or so. BSoDs continue anywhere from every couple of days to as often as every couple hours.I formatted my system partition and reinstalled Windows to try to fix.

    Guess what? BSoDs continue!

    Finally, after all of this, I decide on replacing the DisplayPort cable as the last possible point of failure. I should have mentioned that I'm running 1 native DisplayPort and 2 DVI ports. I replaced it with one from Accell off Newegg and it's been over a month without any further BSoDs. I've heard of plenty of issues out there with DisplayPort adapters, but never thought I'd have an issue with a straight DisplayPort cable distributed with a Dell monitor. Having a Windows BSoD from a bad display cable was definitely an eye-opener for me.
    Last edited by newpgm; 23 Oct 2013 at 16:11.
      My Computer


  3. Posts : 1,007
    Winndows 7 32 bit
       #3

    newpgm said:
    Well it's a bit odd that I would come across this info now after a month and a half but - apparently there is an issue with the 20 pin on displayport cables. The infamous pin 20 issue.
    To be fully compliant a displayport cable must not have pin 20 wired through.
    The monitor is feeding power down pin 20, and the video card is feeding power out as well and the some video cards don't like it, (the power feed is to provide power to active converters, DP to VGA, HDMI etc.)


    This thread is pretty close to mine:
    How a Bad DisplayPort Cable Can Ruin Ruin Your Day
    For about 2 months I've been struggling with a BSoD error related to atikmpag.sys on my Windows 7, core i7, 2x 5870 Crossfire system.

    First, I assumed it was a driver issue. At the time I think the 12.1 Catalyst drivers had just been released. So, I rolled back to 11.10 or so. BSoDs continue anywhere from every couple of days to as often as every couple hours.I formatted my system partition and reinstalled Windows to try to fix.

    Guess what? BSoDs continue!

    Finally, after all of this, I decide on replacing the DisplayPort cable as the last possible point of failure. I should have mentioned that I'm running 1 native DisplayPort and 2 DVI ports. I replaced it with one from Accell off Newegg and it's been over a month without any further BSoDs. I've heard of plenty of issues out there with DisplayPort adapters, but never thought I'd have an issue with a straight DisplayPort cable distributed with a Dell monitor. Having a Windows BSoD from a bad display cable was definitely an eye-opener for me.
    Hi newpgm,

    Thanks for sharing this information with us. It is quite unusual to find a BSOD like this caused by the display port cable.

    I would definitely keep this in my mind as last option to check for troubleshooting this BSOD.

    Thanks again and if you have any queries in future feel free to reach out to us.
      My Computer


  4. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #4

    SandeepP said:
    Hi newpgm,

    Thanks for sharing this information with us. It is quite unusual to find a BSOD like this caused by the display port cable.

    I would definitely keep this in my mind as last option to check for troubleshooting this BSOD.

    Thanks again and if you have any queries in future feel free to reach out to us.
    Sorry I should have updated this thread.

    Even completely removing the DP attached monitor did not fix the BSOD, it came back eventually.

    Determined the Sapphire 7790 had to be at fault. Amazon refunded & I replaced it with an EVGA GeForce GTX 760 2GB GDDR5. Quite a bit more $$ but so far well worth it.

    Seems to have fixed all problems with BSOD, warm start & wake from sleep.

    thanks to all that input.
      My Computer


  5. Posts : 1,007
    Winndows 7 32 bit
       #5

    newpgm said:
    SandeepP said:
    Hi newpgm,

    Thanks for sharing this information with us. It is quite unusual to find a BSOD like this caused by the display port cable.

    I would definitely keep this in my mind as last option to check for troubleshooting this BSOD.

    Thanks again and if you have any queries in future feel free to reach out to us.
    Sorry I should have updated this thread.

    Even completely removing the DP attached monitor did not fix the BSOD, it came back eventually.

    Determined the Sapphire 7790 had to be at fault. Amazon refunded & I replaced it with an EVGA GeForce GTX 760 2GB GDDR5. Quite a bit more $$ but so far well worth it.

    Seems to have fixed all problems with BSOD, warm start & wake from sleep.

    thanks to all that input.
    Hi newpgm,

    Thanks for the update. So it confirms once more that it was a faulty video card that causes this issue. Normally this BSOD is caused to due the driver or the graphic card failure on the system.

    Thanks for the update. If you have any further queries, please feel free to contact us.
      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 02:37.
Find Us