BSOD BCCode: 117, associated probably with video problem

Hi all!

I need a help with an issue which is driving me crazy!

It has been some days i am getting ramdoms BSODs whose characteristic is a sudden video signal loss with a crash pointing to the video driver.
This may happen while playing a game or just out of windows start.
sometimes it wont let me actually load windows.

Today, i turned on the computer in normal mode and it ran good for barely 3 minutes, having come to an expected shutdown while i was brwosing the net reading text.


Below i paste the info about the unexpected shutdown

It loads OK when i load Windows in safemode.

I have most current Nvidia Drivers.

I suspect it is a hardware problem with video, since last year i lost one of my laptop's videocard due to overheating. this is NOT the case now, since we are in the coldest month of the year in a cold city (Sao Paulo, Brazil)

anyways, there isnt enough evidence (by my rookie view) to support that it is an unrecoverable hardware fault.

PLease help me!

If that turns out to be the case, i will have to buy another computer.

---------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1046

Additional information about the problem:
BCCode: 117
BCP1: FFFFFA80110384E0
BCP2: FFFFF880059B019C
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070615-38859-01.dmp
C:\Users\4-PATA-2P\AppData\Local\Temp\WER-59607-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



CPU: i7 960@3.2 GHz
12Gb RAM
Nvidia 485 GTX 2Gb VRAM DDR5
2x SATA2 500Gb HD in Raid 0

Thanks in advance

I see the backtrace of a previous solved BSOD there. Appreciable job done there on it (Baidu AV).

The present issue is display/graphics related, and it is a single dump reflecting this issue, so first concentrating on the driver, which is I think 353.30 WHQL.

Uninstall the installed display driver using Display Driver Uninstaller. Then install 350.12 WHQL as a test, see how it goes.

Report us for any further BSOD.

Further troubleshooting might be needed depending on the situation.
_____________________________________________________

Code:

BugCheck 117, {fffffa80110384e0, fffff880059b019c, 0, 0}

Unable to load image 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+16219c )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa80110384e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880059b019c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+16219c
fffff880`059b019c ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`077f3630 fffff880`04ebf72b : fffffa80`110384e0 fffff880`04f0c0cc fffffa80`110384e0 fffff880`04e8d843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`077f3b50 fffff880`04ec03f0 : fffff8a0`12e62bb0 fffff8a0`12e62bb0 00000000`00000080 fffffa80`110384e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`077f3ba0 fffff880`04e946b3 : 00000000`00000001 fffffa80`0fbda000 00000000`00000000 fffff880`000000d2 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`077f3bd0 fffff880`04ec0f43 : fffffa80`0fb97a58 ffffffff`fffe7960 fffffa80`110384e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`077f3c80 fffff880`04f9103d : fffffa80`0b2eb830 00000000`00000080 00000000`00000000 fffffa80`0fb97410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`077f3d00 fffff800`03b15456 : 00000000`04cf45f9 fffffa80`0fb74b50 fffffa80`0a043b10 fffffa80`0fb74b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`077f3d40 fffff800`0386d2c6 : fffff800`039fae80 fffffa80`0fb74b50 fffff800`03a08cc0 00000060`ce854000 : nt!PspSystemThreadStartup+0x5a
fffff880`077f3d80 00000000`00000000 : fffff880`077f4000 fffff880`077ee000 fffff880`077f3110 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+16219c
fffff880`059b019c ??              ???

SYMBOL_NAME:  nvlddmkm+16219c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5581075a

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x117_image_nvlddmkm.sys

FAILURE_ID_HASH:  {c306f7be-ced2-9b11-9b10-d0239a4fd800}

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

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0584e000 fffff880`06317000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jun 17 11:06:26 2015 (5581075A)
    CheckSum:         00A850BE
    ImageSize:        00AC9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Mini Kernel Dump does not contain unloaded driver list

There is no new crash dump in either of your later posts.

But, if you have issues with multiple versions of the display driver, it is not a driver issue. Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

I was able to do a stress test with Fumark but everytime it came out of fullscreen it would go out on me. I didnt have time to screenshot the fumark test results. During test, GPU temp reached about 75C temperature. it was a 60 sec FHD test with Post FX ticked on the options.

in a repeated attempt to FUmark, i noticed that i had another video shutdown when temperature reached 75¤C

eventually it generated a new BSOD which popped up to me as an unexpected shutdown upon restart.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1046

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800DB364E0
BCP2: FFFFF8800608C128
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071015-32651-01.dmp
C:\Users\4-PATA-2P\AppData\Local\Temp\WER-69810-0.sysdata.xml

rediew said:

I was able to do a stress test with Fumark but everytime it came out of fullscreen it would go out on me. I didnt have time to screenshot the fumark test results. During test, GPU temp reached about 75C temperature. it was a 60 sec FHD test with Post FX ticked on the options.

in a repeated attempt to FUmark, i noticed that i had another video shutdown when temperature reached 75¤C

eventually it generated a new BSOD which popped up to me as an unexpected shutdown upon restart.

It seems that the graphics chip is failing. And the graphics chips like your GTX 485M are not very easy to replace. It is attached to the motherboard like this image:

I would suggest you to take the computer to a repair shop. And get the GPU replaced.