Screen turns black, sound loops. Reboot required. Getting desperate

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Home premium 64bit
       #1

    Screen turns black, sound loops. Reboot required. Getting desperate


    Hey guys .

    I have been looking to fix this issue for 3weeks now, and I have ran out of ideas.
    I'll describe the issue; My screen will turn black and sound will loop ( if sound is playing) my pc becomes unresponsive (num luck led doesn't light up anymore). After that my pc will reboot automaticly.
    https://www.youtube.com/watch?v=JrScZBj9hJ0 (Video of same issue)

    If I make my way back to my desktop I am greeted with a short description of a BlueScreen.
    I will add my dump file to the attachments. It says its because of my drivers but I tried multiple drivers and the issue persist. Also the crashes seem completly random somethimes during games , sometimes right after startup, sometimes while idling.

    Other things I tried ;
    -Different Hard drive
    -Different GPU
    -Different Mobo
    -Different PSU
    -Different Drivers
    -Fresh windows install
    -Monitor Temps
    -Memtest ( Memtest froze after 7 passes )

    Thank you for reading, I hope you guys are able to help me out I am becoming desperate.
    Last edited by Heeco; 23 Apr 2014 at 08:47.
      My Computer


  2. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #2

    Hello and welcome Heeco mate just what were the temps on the machine you said you tested them but we need an idea of what range they were in.

    You have also tried reseating all cards and sticks?.

    You might try this too while you are at it


    SLOTCLEANING

    Now as for the slotsto clean them use a strip of old credit card about 1/2 inch wide nip thecorners off one end - preferably round them offhold a piece of thin lint free clothover the end dab on some form of alcohol - iso propyl alcohol (what we swab theskin with before an injection) is good and GENTLYswipe along the slots.

    This can also be donefor the GPU slot/s.


    The memtest crashing is a worry depending on how many sticks you have I might suggest testing them one at a time.

    If you like I personally would also run these is safe mode

    https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    https://www.sevenforums.com/tutorials/433-disk-check.html
      My Computer


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

    Hi Heeco.

    Yours a display/graphics related issue.

    Install the NVIDIA DRIVERS 314.22WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update
      • GeForce Experience

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    When the suggested driver is properly applied, stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark
    Monitor the temperature during Furmark.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    _______________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800978e010, fffff8800f9fd0dc, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9a30dc )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800978e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f9fd0dc, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+9a30dc
    fffff880`0f9fd0dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f8eba49)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`024f2a48 fffff880`040fd140 : 00000000`00000116 fffffa80`0978e010 fffff880`0f9fd0dc ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`024f2a50 fffff880`040d0867 : fffff880`0f9fd0dc fffffa80`08d03000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`024f2a90 fffff880`040fcf4f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0978e010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`024f2b40 fffff880`041cc03d : fffffa80`08ccc320 00000000`00000080 00000000`00000000 fffffa80`08cea410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`024f2bc0 fffff800`0371a2ea : 00000000`050a5eb3 fffffa80`08d1a060 fffffa80`0667fb30 fffffa80`08d1a060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`024f2c00 fffff800`0346e8e6 : fffff800`035f8e80 fffffa80`08d1a060 fffff800`03606cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`024f2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9a30dc
    fffff880`0f9fd0dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f8eba49)],0
    
    SYMBOL_NAME:  nvlddmkm+9a30dc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f05a000 fffff880`0fca3000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
        CheckSum:         00C19112
        ImageSize:        00C49000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  4. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #4

    Thanks Arc am still not much good with the dumps so my post was very basic. Mind you the reseating and stuff is worth a try and I am wondering why the memtest when AWOL??
      My Computer


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

    Hi John.

    The bugcheck code stop 0x116 indicates that the problem is with the graphics environment. So the areas you have to search for are .... according to priority ....

    • Display driver
    • GPU
    • System temperature (+ age + dust allocation + a lot of other things like thermal paste, broke fan etc)
    • Adequacy of the power supply

    Memory failure may cause any issue theoretically, including display failure. But I have never seen any memory caused display failure is reported as stop 0x116.
      My Computer


  6. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #6

    Hey arc and ICit2lol,

    Thanks for the responses, I really appreciate it.
    I will install the NVIDIA DRIVERS 314.22WHQL later when I am at home.
    As for my Temperatures they seem normal (screenshot from yesterday, while browsing internet)
      My Computer


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



    Fine. You need not to worried about the temps at all.

    Let us know what happened for the furmark test.
      My Computer


  8. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #8

    So , I have installed those drivers.
    And I have used the Furmark burn-in test for 10 minutes.
    The lowest temp was 42° and the highest 72°.
    I didn't see any artifacting or other graphical errors.
      My Computer


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

    OK. :)

    Now use the computer normally. Observe if the BSODs are still occurring or not. Report us in case.
      My Computer


  10. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #10

    Sadly I have to report that the bluescreens are still occuring
    I might also add that I never see an actual bluescreen. I only see the dump file that was created after.
      My Computer


 
Page 1 of 2 12 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 21:08.
Find Us