BSOD and Display stop responding

Discussion in 'Hardware' started by zoldun, Aug 20, 2014.

  1. zoldun

    zoldun Private E-2

    Copuld anybody help me fix this its really starting to annoy me .... every since i bought this computer i got display driver but ive been keeping the information that i get on BSOD and such.

    I get alot of Display driver has stopped responding when i try to livestream or play games but it will also happens when i just look at the web browser.

    BSOD #1 error
    0x0000007E - Atikmdag.sys (i think there connected)

    BSOD #2 error
    0x0000007E

    BTW the temp is usualy around 65 - 75*C (when i game)
    and the CPU usage around half when i run a high game
    i use like 6 usb item and use 600PSU

    Does anybody see a link on these? i really want to get my pc stable its really bugging me i cant do long time gaming cuz it will crash randomly and such.

    Thanks in advance,
    Zoldun
     
  2. satrow

    satrow Major Geek Extraordinaire

    Display driver has stopped responding = a TDR problem: http://msdn.microsoft.com/en-us/library/windows/hardware/ff570087(v=vs.85).aspx TDR troubleshooting: http://www.sysnative.com/forums/blogs/usasma/23-stop-0x116-0x117-troubleshooting.html

    0x7E can be triggered by a large range of issues:
    So, it does look like your graphics card or drivers are likely to be the problem, though it's possible that something else is interfering.

    Follow these instructions carefully: http://www.sysnative.com/forums/bso...ctions-windows-8-1-8-7-and-windows-vista.html and then reply with your details and attach the zipped folder back here and we'll see what we can discover.
     
  3. zoldun

    zoldun Private E-2

    ok i will give that a whirl
     
  4. zoldun

    zoldun Private E-2

    Here are the zip files when u said details what do you mean ? and its been giving me display driver stop responding since i got it.

    Is there anyway i can make sure its is/not a fecked GPU ... originally i was told it might be a PSU problem but that didnt change anything after upgrading.
     

    Attached Files:

  5. zoldun

    zoldun Private E-2

    · OS - Windows 8.1, 8, 7, Vista ? Windows 7
    · x86 (32-bit) or x64 ? 64
    · What was original installed OS on system? Windows 7 home prem
    · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM version
    · Age of system (hardware) around 1 year and a half
    · Age of OS installation - have you re-installed the OS? few months

    · CPU
    · Video Card - 2048MB ATI AMD Radeon HD 7800 Series (ATI AIB)
    · MotherBoard - ASUSTeK COMPUTER INC. P8Z77-V LX (LGA1155)
    · Power Supply - Power station - 600WATT

    · System Manufacturer
    · Exact model number (if laptop, check label on bottom) umm im not sure Asus i think

    · Laptop or Desktop? Desktop
     
  6. satrow

    satrow Major Geek Extraordinaire

    2 crash dumps that were Driver Verified yet they point to the Windows kernel, frequently indicative of a hardware problem. Please turn off Driver Verifier now, it's designed to stress the machine and usually only used for 24-48 hours.

    Almost all the dumps point to hardware (mostly graphics-related) or memory corruption (could be corruption of drivers whilst loaded in memory).

    The easiest way to test your graphics card is to loan it out to a friend/colleague to test for a few hours/days, ensure s/he has a decent quality PSU with sufficient wattage.

    Your PSU is from Novatech, yes? They would not normally stock rubbish PSUs, it's possible that it's a bad example. Are all the signs/symptoms the same as they were prior to the PSU change?

    There are some problems reported by BEX (with WOW and Skype), these are often security/DEP-related.

    You need to update to SP1 and install all security updates subsequently.

    There's a Hotfix available that might be relevant to the usbvideo.sys crash: http://support.microsoft.com/kb/979538 (probably only useful if you don't update to SP1).

    There are 2 problem drivers installed, update or uninstall them ASAP:
    xusb21.sys Thu Aug 13 23:10:17 2009 (4A848F49)
    XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
    http://www.carrona.org/drivers/driver.php?id=xusb21.sys

    RTCore64.sys Mon Mar 11 05:32:06 2013 (513D6C56)
    RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys

    BSOD BUGCHECK SUMMARY
    Code:
    [font=lucida console]
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Aug 20 20:56:35.302 2014 (UTC + 1:00)
    System Uptime: 0 days 7:15:58.223
    BugCheck C4, {91, f, fffff880033e00c0, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4944 )
    BUGCHECK_STR:  0xc4_91
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Aug 20 13:38:57.986 2014 (UTC + 1:00)
    System Uptime: 1 days 23:44:56.908
    BugCheck 1000007E, {ffffffffc0000005, fffff88010383dbb, fffff88005fe9328, fffff88005fe8b80}
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Aug 16 11:11:01.645 2014 (UTC + 1:00)
    System Uptime: 0 days 0:02:02.566
    BugCheck 1000007E, {ffffffffc0000005, fffff8800279601a, fffff880035a1958, fffff880035a11b0}
    Probably caused by : usbvideo.sys ( usbvideo!LoadPowerLineFrequency+2ce )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Aug 15 00:33:12.982 2014 (UTC + 1:00)
    System Uptime: 0 days 10:49:40.903
    BugCheck C4, {91, f, fffffa8021940a10, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4944 )
    BUGCHECK_STR:  0xc4_91
    PROCESS_NAME:  Battle.net.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Aug 12 18:15:44.714 2014 (UTC + 1:00)
    System Uptime: 0 days 2:36:43.635
    BugCheck 3B, {c0000005, fffff96000285d7c, fffff8800953eff0, 0}
    Probably caused by : win32k.sys ( win32k!GreDeleteWnd+14 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  OBS.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jul 29 06:38:53.613 2014 (UTC + 1:00)
    System Uptime: 0 days 15:59:50.534
    BugCheck 1A, {41790, fffffa8005739000, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  rundll32.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jul  8 02:32:03.085 2014 (UTC + 1:00)
    System Uptime: 2 days 10:10:38.866
    BugCheck 1A, {5003, fffff70001080000, 90e, 91000001214}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3690c )
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  SearchFilterHo
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Jun 25 23:38:21.344 2014 (UTC + 1:00)
    System Uptime: 1 days 2:03:10.264
    BugCheck 1A, {41790, fffffa80059f2920, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  OBS.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jun 22 19:03:19.805 2014 (UTC + 1:00)
    System Uptime: 0 days 0:00:15.742
    BugCheck 1000007E, {ffffffff80000003, fffff8800276aaf5, fffff8800357df78, fffff8800357d7d0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jun 22 16:32:47.382 2014 (UTC + 1:00)
    System Uptime: 2 days 20:41:03.793
    BugCheck 124, {0, fffffa801c3a5028, be200000, 5110a}
    Probably caused by : GenuineIntel
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    
    [/font]
     
  7. zoldun

    zoldun Private E-2

    when i click delete existing settings it said no settings were changed in driver verifier.

    So you suggest i try upgrad to sp1 and security and Test the GPU ?

    TBH it seems to point to the GPU ive had display has crashed ever since first day i got it and i thought it might be currupted and reformatted my pc a few times but didnt help ... i duno if that sorts that or not.

    But ill try upgrading and look into tersting another GPU or something

    Thanks for your help satrow
     
  8. satrow

    satrow Major Geek Extraordinaire

    Try this:
    The easiest way to test the GPU is in a different, known good, computer with a decent PSU (a 7850 is fine on 450W). Swap GPUs if you can, your 600W should power almost any GPU. A few hours stress testing them should give you a clear result.

    If you're stuck with the duff GPU while waiting for a replacement, update or remove those 'bad' drivers, that should reduce the chances of a memory corruption BSOD, it won't affect the chances of a hardware BSOD.

    After the removal/updating of those drivers, you might get it stable enough to install SP1 (and updates) ready for your new card - just don't game/watch videos etc while it's downloading/updating though.
     
  9. plodr

    plodr Major Geek Super Extraordinaire

    You should have contacted the place you purchased the computer. You may have a hardware problem because a new computer should not crash on Day 1.
     
  10. zoldun

    zoldun Private E-2

    I can because i opened the case and changed the PSU i apparently voided the warrenty i still do not get that you are not even allowed to just make sure evrything is connected fine.

    I have been using DVI instead of the HDMI and its been crashing a hell of a lot less its only crashed once while with playing games and whatnot ... so i get the feeling it might be the HDMI socket or the GPU itself.

    Just wanted to say thanks for the help
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds