Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 0x00000116, no screen when reboot, Please power down and connect.

16 Oct 2014   #1
wuTz

Win 7 Pro 64
 
 
BSOD 0x00000116, no screen when reboot, Please power down and connect.

Hi there,

I thought that I had solved this problem half a year ago, when I often got a BSOD and the message

"Please power down and connect the PCIe power cable(s) for this graphics card"

when turning on my PC.

Now it's back and I need some more help on the issue.

I already tried reinstalling my GPU drivers.

First BSOD accured one week ago when setting a youtube vid to fullscreen.

Second one I think was while playing Middle Earth Shadow of Mordor.

When starting my PC today, my GPU went off right from the start.

After disabling and enabling the device again and a restart the GPU worked until I opened chrome...BSOD!

So seems like it's accurring more often and also not only when GPU is much in use (regular chrome browser, not even a vid playing...).

Before writing this I took out my GPU and blew the dust away (which I did half a year ago when I remember correctly) and plugged it in again (also checked the connections to the PSU).

Thanks for your help in advance!

wuTz

Edit1: Maybe worth mentioning is that I have to set Vysnc in the NVIdia Control Panels' Global Settings on "ON" because some games tend to make my GPU "cry(high pitched noise)" and too high temps, too high fps(?). Well I think it's bad programming..
It's with those and some other games
Magic the gathering 2013 and 2014's menu
GTA 4
Age of Wonders III

Edit 2: "GPU Shark" says Limiting policies (Nvidia): - volt limit (more often) or power limit reached, when playing 3d intensive games. But as mentioned above, BSOD also accures when just going into fullscreen watching a yt-vid...


My System SpecsSystem Spec
.
18 Oct 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

All the BSODs are with 344.11 WHQL driver installed which itself is not very stable.

Uninstall the display driver using Display Driver Uninstaller and then install 340.52 WHQL.

Let us know the changed situation.
________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800688f4e0, fffff8800f92851c, ffffffffc000009a, 4}

*** 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+91951c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800688f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f92851c, 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+91951c
fffff880`0f92851c 48ff255dc9ecff  jmp     qword ptr [nvlddmkm+0x7e5e80 (fffff880`0f7f4e80)]

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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03db9a48 fffff880`0fd40134 : 00000000`00000116 fffffa80`0688f4e0 fffff880`0f92851c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03db9a50 fffff880`0fd13867 : fffff880`0f92851c fffffa80`08b02000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03db9a90 fffff880`0fd3ff43 : 00000000`ffffd846 fffff800`03801080 fffffa80`0688f4e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03db9b40 fffff880`03e3803d : fffffa80`0846b4e0 00000000`00000080 00000000`00000000 fffffa80`07e0b410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03db9bc0 fffff800`0336e73a : 00000000`031b87b2 fffffa80`085dba00 fffffa80`06676b30 fffffa80`085dba00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03db9c00 fffff800`030c38e6 : fffff800`0324de80 fffffa80`085dba00 fffff800`0325bcc0 fffff880`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`03db9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+91951c
fffff880`0f92851c 48ff255dc9ecff  jmp     qword ptr [nvlddmkm+0x7e5e80 (fffff880`0f7f4e80)]

SYMBOL_NAME:  nvlddmkm+91951c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5414a236

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f00f000 fffff880`0fce3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Sep 14 01:29:50 2014 (5414A236)
    CheckSum:         00C8E3A6
    ImageSize:        00CD4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
13 Dec 2014   #3
wuTz

Win 7 Pro 64
 
 

It worked. Thanks.

So since then I manually update my graphics card drivers. How do I know when to get a newer stable version? Still have the one installed you mentioned above..
My System SpecsSystem Spec
.

21 Feb 2015   #4
wuTz

Win 7 Pro 64
 
 

I still have v340.52 installed. Should I install a newer one?
My System SpecsSystem Spec
21 Feb 2015   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

You may try 347.52 WHQL. I am using it for a good time without any hint of an issue.

But, as there is no BSOD report over a long time, you may mark this thread as solved.
My System SpecsSystem Spec
Reply

 BSOD 0x00000116, no screen when reboot, Please power down and connect.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Is it possible to connect a particular screen saver to a power plan?
Probably not but it would be cool and convenient.
General Discussion
Wierd lines and colors on my screen and BSOD : 0x00000116
My computer was working normaly 2 days ago, i was just playing some counterstrike and teamfortress, and suddenly i got a blue screen. So i tried to plug out all the cables of the gpu and unplug it from the mobo. Did that like 3 times but it didnt help. Another day passed, and now i got all these...
BSOD Help and Support
BSOD playing full screen games, error 0x00000116
Random computer lockup to BSOD at random times while playing games in fullscreen mode. I've updated my video drivers with a full uninstall with driver sweeper but the crashes continue. I've also run a memory test and believe that my memory is fine. Any further assistance with solving this problem...
BSOD Help and Support
BSOD on reboot at login screen
My laptop crashed last night after AVG caught and removed a threat. Unfortunately I did not see what the threat was or which file was removed. Now whenever I reboot the laptop it freezes at the user login screen and gives me the BSOD and reboots. I can thankfully load in safe mode so I have been...
BSOD Help and Support
BSOD/Black Screen Reboot
Windows 7 Starter 32-bit OEM - netbook. Netbook about 1-2 years old but I have a bad memory. Never re-installed. Made a thread about this in Hardware and devices, I also thought it might be my USB mouse causing problems because recently I have been getting the USB device is...
BSOD Help and Support
[REBOOT] Sudden Random Reboot and black screen at start up!
- x64; - the original installed OS on the system: Windows 7 fresh install; - full retail version; - What is the age of system (hardware): less than one year; - What is the age of OS installation: less than three months. Hello, this morning my elitebook 8540w suddenly rebooted and during...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 13:46.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App