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

[Heeco]

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.

 

[ICIT2LOL]

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 off hold 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

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

http://www.sevenforums.com/tutorials/433-disk-check.html

 

[Arc]

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know the results.
_______________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 116[/B][/COLOR], {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

 

[ICIT2LOL]

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??

 

[Arc]

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.

 

[Heeco]

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)

 

[Arc]

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

Let us know what happened for the furmark test.

 

[Heeco]

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.

 

[Arc]

OK.

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

 

[Heeco]

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.

 

[Arc]

Sadly I have to report that the bluescreens are still occuring

Report it following the Blue Screen of Death (BSOD) Posting Instructions.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Heeco]

I added it in the attachements.
Again I want to thank you for all your time you are putting in to this.
I really appreciate it

 

[Arc]

Something I am seeing there is very wrong. Can you please follow the procedure for one more time?

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:
  
  

Actually the crash dump is reporting a driver bug for 314.22 WHQL which should not be there. I hope one uninstall-reinstall should fix the issue.

Dont forget to uninstall all the elements of display driver present in the list, and accept all the offered restarts during the process.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffff8000364ccc0, 0}

*** 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+1bb8c5 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff8000364ccc0
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80004884FB0

LAST_CONTROL_TRANSFER:  from fffff8000351a4fa to fffff800034c3bc0

STACK_TEXT:  
fffff800`04879008 fffff800`0351a4fa : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`0364ccc0 : nt!KeBugCheckEx
fffff800`04879010 fffff800`03568615 : 00000000`00000000 fffffa80`07c4b920 00000000`00000003 fffffa80`09a39000 : nt! ?? ::FNODOBFM::`string'+0x4884
fffff800`04879050 fffff800`0358672d : fffff800`04879000 fffff800`0487f000 fffffa80`09736110 00000000`00409c18 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`04879080 fffff800`035875cb : 00000000`00000001 fffff800`04879100 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x4d
fffff800`048790b0 fffff880`04a2d8c5 : 00000000`00000000 fffff800`04879140 fffffa80`07c49000 fffffa80`09a39000 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`048790e0 00000000`00000000 : fffff800`04879140 fffffa80`07c49000 fffffa80`09a39000 fffffa80`09a39368 : nvlddmkm+0x1bb8c5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1bb8c5
fffff880`04a2d8c5 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nvlddmkm+1bb8c5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c

FAILURE_BUCKET_ID:  X64_0xc4_91_nvlddmkm+1bb8c5

BUCKET_ID:  X64_0xc4_91_nvlddmkm+1bb8c5

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc4_91_nvlddmkm+1bb8c5

FAILURE_ID_HASH:  {9994d4f4-30b0-b0b6-a11a-88205d1277ef}

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04872000 fffff880`0531d000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Heeco]

I have reinstalled 314.22 WHQL , I have done every step correctly.
So let's hope a reinstall fixed the issue.

 

[Heeco]

It just happend again sadly
Same error and everything.

 

[Heeco]

Hmm , had 3 crashes today they all followed eachother up really fast (all withing 1 hour)
also what did you mean with

Something I am seeing there is very wrong

?

 

[Arc]

Hmm , had 3 crashes today they all followed eachother up really fast (all withing 1 hour)
also what did you mean with

Something I am seeing there is very wrong

?

I described it there .....

Actually the crash dump is reporting a driver bug for 314.22 WHQL which should not be there. I hope one uninstall-reinstall should fix the issue.

But it would be better if you post the data again. Without seeing those, nothing can be said about a BSOD.

 

[ICIT2LOL]

Arc this seems to be dragging out a bit do you think some malware scanning might be in order??

I was thinking of even going slightly extreme with the Kaspersky rescue disk??

 

[Arc]

Arc this seems to be dragging out a bit do you think some malware scanning might be in order??

I was thinking of even going slightly extreme with the Kaspersky rescue disk??

Please guide Heeco through the process.

You know John, I have suggested the 314.22 WHQL to a large number of persons to teat the stability of the GPU; because that driver never fails at its own. Earlier one time only I noticed this behavior with this driver, here: http://www.sevenforums.com/bsod-hel...rrior-online-stop-0x000000c4.html#post2637976
I suggested the OP to contract with the game developer .... but he never reported any further issue there. Also I remember this post ....

I see that I was running 314.22 a while ago. Never any issues.

So I am very curious to know what is the actual situation, and what is causing the bug.

 

[ICIT2LOL]

Yes Arc it is one of those times you wish you were sitting in front of the machine and have a chance to delve inside it.
Me I am really throwing out the bait hoping something will bite if only to eliminate a specific bait