SOLVED - Qosmio Black Screen (Nvidia Driver Problem)
I have a Qosmio X505-860 with the NVidia 360M display adapter. I experienced the occasional "Display Adapter has stopped responding and recovered" screen flicker as well as the adapter turning off upon log off, switch user, close lid (even with sleep disabled) etc.
I installed the ancient drivers provided by Toshiba and lo and behold, no problems -- except games look like crap.
Through trial and error I discovered that straight NVidia drivers work up to Verde 260.99, the last of that generation of drivers. As soon as the driver is updated to the next gen, starting with 266.58, the problems reoccur.
Through a long process of plodding through log files, tracing processes and scanning dlls with disassembly software, which I will not discuss here for copyright reasons, I linked the crashing to the NVidia Control Panel App rather than the actual driver. I am not entirely sure on this as I was hurrying through things and employing a lot of guess-and-check. I know for the 266.58 driver, renaming System32/nvapi64.dll solves the problem, though doing so will also make your system wonky...
Anyway, what eventually solved it for me, I believe, was uninstalling the (266.58) driver via the Control Panel. The computer went into No-Driver-640x480 mode, rebooted, and came back up. I could only see about an eighth of my desktop, but that didn't last long as Windows prompted me to reboot again for "changes to take place." After the second reboot, the NVidia Control Panel worked and showed version 301.42 (latest at the time of writing), even though the driver was absent from the list of Programs and Features. So far I have been able to Switch User and Log Off and back on without any trouble. I haven't tested it much, but this problem was 100% reproducible before.
I hope this helps somebody. If it doesn't work, let me know, I will try harder to figure out what exactly in my afternoon of registry editing and file scrambling did the trick.
That's great troubleshooting! Thanks for sharing your findings.
- Peter
Similar Messages
-
[Solved] Startx black screen on nvidia macbook
startx goes to a black screen, Xorg.0.log doesn't report anything unusual (that I noticed). I've been using arch for a few years, but this is my first install on a mac, and my knowledge is rather thin in places, so I apologize if I'm missing something obvious. any help would be appreciated. here's my log. I have nvidia graphics
btw this is the first time I've ever posted, (although these forums have helped me tremendously over the years)
[ 608.040]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[ 608.043] X Protocol Version 11, Revision 0
[ 608.043] Build Operating System: Linux 3.11.6-1-ARCH x86_64
[ 608.044] Current Operating System: Linux Quixote 3.12.1-1-ARCH #1 SMP PREEMPT Thu Nov 21 08:18:42 CET 2013 x86_64
[ 608.044] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=78c7995e-65e8-48b9-aa92-cd0a6a7ad1d1 rw quiet rootflags=data=writeback
[ 608.046] Build Date: 01 November 2013 05:10:48PM
[ 608.047]
[ 608.048] Current version of pixman: 0.32.4
[ 608.050] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 608.050] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 608.054] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 26 15:32:02 2013
[ 608.090] (==) Using config file: "/etc/X11/xorg.conf"
[ 608.091] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 608.120] (==) ServerLayout "Layout0"
[ 608.120] (**) |-->Screen "Screen0" (0)
[ 608.120] (**) | |-->Monitor "Monitor0"
[ 608.120] (**) | |-->Device "Device0"
[ 608.120] (**) |-->Input Device "Keyboard0"
[ 608.120] (**) |-->Input Device "Mouse0"
[ 608.120] (**) Option "DontZap" "False"
[ 608.120] (==) Automatically adding devices
[ 608.120] (==) Automatically enabling devices
[ 608.120] (==) Automatically adding GPU devices
[ 608.161] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 608.161] Entry deleted from font path.
[ 608.161] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 608.161] Entry deleted from font path.
[ 608.161] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 608.161] Entry deleted from font path.
[ 608.161] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 608.161] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 608.161] Entry deleted from font path.
[ 608.161] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 608.161] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 608.161] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 608.161] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 608.161] (WW) Disabling Keyboard0
[ 608.161] (WW) Disabling Mouse0
[ 608.161] (II) Loader magic: 0x7fdc20
[ 608.161] (II) Module ABI versions:
[ 608.161] X.Org ANSI C Emulation: 0.4
[ 608.161] X.Org Video Driver: 14.1
[ 608.161] X.Org XInput driver : 19.1
[ 608.161] X.Org Server Extension : 7.0
[ 608.161] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 608.164] (--) PCI:*(0:4:0:0) 10de:08a0:106b:00c2 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00001000/128, BIOS @ 0x????????/131072
[ 608.165] Initializing built-in extension Generic Event Extension
[ 608.166] Initializing built-in extension SHAPE
[ 608.167] Initializing built-in extension MIT-SHM
[ 608.168] Initializing built-in extension XInputExtension
[ 608.169] Initializing built-in extension XTEST
[ 608.170] Initializing built-in extension BIG-REQUESTS
[ 608.171] Initializing built-in extension SYNC
[ 608.172] Initializing built-in extension XKEYBOARD
[ 608.173] Initializing built-in extension XC-MISC
[ 608.175] Initializing built-in extension SECURITY
[ 608.176] Initializing built-in extension XINERAMA
[ 608.177] Initializing built-in extension XFIXES
[ 608.178] Initializing built-in extension RENDER
[ 608.179] Initializing built-in extension RANDR
[ 608.180] Initializing built-in extension COMPOSITE
[ 608.181] Initializing built-in extension DAMAGE
[ 608.182] Initializing built-in extension MIT-SCREEN-SAVER
[ 608.183] Initializing built-in extension DOUBLE-BUFFER
[ 608.184] Initializing built-in extension RECORD
[ 608.185] Initializing built-in extension DPMS
[ 608.186] Initializing built-in extension X-Resource
[ 608.187] Initializing built-in extension XVideo
[ 608.188] Initializing built-in extension XVideo-MotionCompensation
[ 608.189] Initializing built-in extension XFree86-VidModeExtension
[ 608.190] Initializing built-in extension XFree86-DGA
[ 608.191] Initializing built-in extension XFree86-DRI
[ 608.192] Initializing built-in extension DRI2
[ 608.192] (II) LoadModule: "glx"
[ 608.219] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 609.006] (II) Module glx: vendor="NVIDIA Corporation"
[ 609.006] compiled for 4.0.2, module version = 1.0.0
[ 609.006] Module class: X.Org Server Extension
[ 609.006] (II) NVIDIA GLX Module 331.20 Wed Oct 30 17:36:48 PDT 2013
[ 609.022] Loading extension GLX
[ 609.022] (II) LoadModule: "nvidia"
[ 609.062] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 609.149] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 609.149] compiled for 4.0.2, module version = 1.0.0
[ 609.149] Module class: X.Org Video Driver
[ 609.158] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013
[ 609.158] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 609.159] (++) using VT number 1
[ 609.171] (II) Loading sub module "fb"
[ 609.171] (II) LoadModule: "fb"
[ 609.171] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 609.190] (II) Module fb: vendor="X.Org Foundation"
[ 609.191] compiled for 1.14.4, module version = 1.0.0
[ 609.191] ABI class: X.Org ANSI C Emulation, version 0.4
[ 609.191] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 609.191] (II) Loading sub module "wfb"
[ 609.191] (II) LoadModule: "wfb"
[ 609.191] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 609.193] (II) Module wfb: vendor="X.Org Foundation"
[ 609.193] compiled for 1.14.4, module version = 1.0.0
[ 609.193] ABI class: X.Org ANSI C Emulation, version 0.4
[ 609.193] (II) Loading sub module "ramdac"
[ 609.193] (II) LoadModule: "ramdac"
[ 609.193] (II) Module "ramdac" already built-in
[ 609.214] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 609.214] (==) NVIDIA(0): RGB weight 888
[ 609.214] (==) NVIDIA(0): Default visual is TrueColor
[ 609.214] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 609.215] (**) NVIDIA(0): Enabling 2D acceleration
*Edit* Never mind, just switched to nouveau drivers, everything's fine now. marking as solved!
Last edited by Lawless Flogic (2013-11-27 00:31:28)startx goes to a black screen, Xorg.0.log doesn't report anything unusual (that I noticed). I've been using arch for a few years, but this is my first install on a mac, and my knowledge is rather thin in places, so I apologize if I'm missing something obvious. any help would be appreciated. here's my log. I have nvidia graphics
btw this is the first time I've ever posted, (although these forums have helped me tremendously over the years)
[ 608.040]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[ 608.043] X Protocol Version 11, Revision 0
[ 608.043] Build Operating System: Linux 3.11.6-1-ARCH x86_64
[ 608.044] Current Operating System: Linux Quixote 3.12.1-1-ARCH #1 SMP PREEMPT Thu Nov 21 08:18:42 CET 2013 x86_64
[ 608.044] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=78c7995e-65e8-48b9-aa92-cd0a6a7ad1d1 rw quiet rootflags=data=writeback
[ 608.046] Build Date: 01 November 2013 05:10:48PM
[ 608.047]
[ 608.048] Current version of pixman: 0.32.4
[ 608.050] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 608.050] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 608.054] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 26 15:32:02 2013
[ 608.090] (==) Using config file: "/etc/X11/xorg.conf"
[ 608.091] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 608.120] (==) ServerLayout "Layout0"
[ 608.120] (**) |-->Screen "Screen0" (0)
[ 608.120] (**) | |-->Monitor "Monitor0"
[ 608.120] (**) | |-->Device "Device0"
[ 608.120] (**) |-->Input Device "Keyboard0"
[ 608.120] (**) |-->Input Device "Mouse0"
[ 608.120] (**) Option "DontZap" "False"
[ 608.120] (==) Automatically adding devices
[ 608.120] (==) Automatically enabling devices
[ 608.120] (==) Automatically adding GPU devices
[ 608.161] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 608.161] Entry deleted from font path.
[ 608.161] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 608.161] Entry deleted from font path.
[ 608.161] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 608.161] Entry deleted from font path.
[ 608.161] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 608.161] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 608.161] Entry deleted from font path.
[ 608.161] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 608.161] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 608.161] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 608.161] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 608.161] (WW) Disabling Keyboard0
[ 608.161] (WW) Disabling Mouse0
[ 608.161] (II) Loader magic: 0x7fdc20
[ 608.161] (II) Module ABI versions:
[ 608.161] X.Org ANSI C Emulation: 0.4
[ 608.161] X.Org Video Driver: 14.1
[ 608.161] X.Org XInput driver : 19.1
[ 608.161] X.Org Server Extension : 7.0
[ 608.161] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 608.164] (--) PCI:*(0:4:0:0) 10de:08a0:106b:00c2 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00001000/128, BIOS @ 0x????????/131072
[ 608.165] Initializing built-in extension Generic Event Extension
[ 608.166] Initializing built-in extension SHAPE
[ 608.167] Initializing built-in extension MIT-SHM
[ 608.168] Initializing built-in extension XInputExtension
[ 608.169] Initializing built-in extension XTEST
[ 608.170] Initializing built-in extension BIG-REQUESTS
[ 608.171] Initializing built-in extension SYNC
[ 608.172] Initializing built-in extension XKEYBOARD
[ 608.173] Initializing built-in extension XC-MISC
[ 608.175] Initializing built-in extension SECURITY
[ 608.176] Initializing built-in extension XINERAMA
[ 608.177] Initializing built-in extension XFIXES
[ 608.178] Initializing built-in extension RENDER
[ 608.179] Initializing built-in extension RANDR
[ 608.180] Initializing built-in extension COMPOSITE
[ 608.181] Initializing built-in extension DAMAGE
[ 608.182] Initializing built-in extension MIT-SCREEN-SAVER
[ 608.183] Initializing built-in extension DOUBLE-BUFFER
[ 608.184] Initializing built-in extension RECORD
[ 608.185] Initializing built-in extension DPMS
[ 608.186] Initializing built-in extension X-Resource
[ 608.187] Initializing built-in extension XVideo
[ 608.188] Initializing built-in extension XVideo-MotionCompensation
[ 608.189] Initializing built-in extension XFree86-VidModeExtension
[ 608.190] Initializing built-in extension XFree86-DGA
[ 608.191] Initializing built-in extension XFree86-DRI
[ 608.192] Initializing built-in extension DRI2
[ 608.192] (II) LoadModule: "glx"
[ 608.219] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 609.006] (II) Module glx: vendor="NVIDIA Corporation"
[ 609.006] compiled for 4.0.2, module version = 1.0.0
[ 609.006] Module class: X.Org Server Extension
[ 609.006] (II) NVIDIA GLX Module 331.20 Wed Oct 30 17:36:48 PDT 2013
[ 609.022] Loading extension GLX
[ 609.022] (II) LoadModule: "nvidia"
[ 609.062] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 609.149] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 609.149] compiled for 4.0.2, module version = 1.0.0
[ 609.149] Module class: X.Org Video Driver
[ 609.158] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013
[ 609.158] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 609.159] (++) using VT number 1
[ 609.171] (II) Loading sub module "fb"
[ 609.171] (II) LoadModule: "fb"
[ 609.171] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 609.190] (II) Module fb: vendor="X.Org Foundation"
[ 609.191] compiled for 1.14.4, module version = 1.0.0
[ 609.191] ABI class: X.Org ANSI C Emulation, version 0.4
[ 609.191] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 609.191] (II) Loading sub module "wfb"
[ 609.191] (II) LoadModule: "wfb"
[ 609.191] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 609.193] (II) Module wfb: vendor="X.Org Foundation"
[ 609.193] compiled for 1.14.4, module version = 1.0.0
[ 609.193] ABI class: X.Org ANSI C Emulation, version 0.4
[ 609.193] (II) Loading sub module "ramdac"
[ 609.193] (II) LoadModule: "ramdac"
[ 609.193] (II) Module "ramdac" already built-in
[ 609.214] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 609.214] (==) NVIDIA(0): RGB weight 888
[ 609.214] (==) NVIDIA(0): Default visual is TrueColor
[ 609.214] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 609.215] (**) NVIDIA(0): Enabling 2D acceleration
*Edit* Never mind, just switched to nouveau drivers, everything's fine now. marking as solved!
Last edited by Lawless Flogic (2013-11-27 00:31:28) -
[Solved] Can't install Nvidia driver: Mesa-libgl conflict
I just finished installing my first GUI, KDE to be exact, on Arch Linux. Right now, I'm using the nouveau driver but I want to unlock the full power of my GTX 780 with proprietary nvidia drivers. On my last attempt at installing KDE, I went directly to installing the nvidia driver 304.24. After rebooting and seeing some text flash on screen, however, I was meant with only a black screen. I could still type, login and reboot but not much more since I couldn't see. I tried booting into the Arch Linux fallback GRUB provided for me with no prevail so I decided to just reinstall the OS. For that reason, I want to install this nvidia driver in hopes of being able to avoid another blank screen. So far, I have this:
[root@arch /]# pacman -S nvidia
resolving dependencies...
looking for inter-conflicts...
:: nvidia-libgl and mesa-libgl are in conflict (libgl). Remove mesa-libgl? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: nouveau-dri: requires mesa-libgl
I've tried looking across the forums for similar problems and even tried to uninstall mesa-libgl and all its dependencies but it just yields this:
[root@arch /]# pacman -Rns mesa-libgl
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: cairo: requires libgl
:: glu: requires libgl
:: libva: requires libgl
:: mplayer: requires libgl
:: nouveau-dri: requires mesa-libgl
:: qt4: requires libgl
:: qt5-base: requires libgl
I feel like I might need to uninstall the nouveau driver so as to be able to uninstall mesa-libgl. If I installed the nvidia driver at that point, I fear I might see the blank screen again. Thanks for your help in advance.
Last edited by Firephyz (2014-07-19 20:04:11)Firephyz wrote:
I just finished installing my first GUI, KDE to be exact, on Arch Linux. Right now, I'm using the nouveau driver but I want to unlock the full power of my GTX 780 with proprietary nvidia drivers. On my last attempt at installing KDE, I went directly to installing the nvidia driver 304.24. After rebooting and seeing some text flash on screen, however, I was meant with only a black screen. I could still type, login and reboot but not much more since I couldn't see. I tried booting into the Arch Linux fallback GRUB provided for me with no prevail so I decided to just reinstall the OS. For that reason, I want to install this nvidia driver in hopes of being able to avoid another blank screen. So far, I have this:
[root@arch /]# pacman -S nvidia
resolving dependencies...
looking for inter-conflicts...
:: nvidia-libgl and mesa-libgl are in conflict (libgl). Remove mesa-libgl? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: nouveau-dri: requires mesa-libgl
I've tried looking across the forums for similar problems and even tried to uninstall mesa-libgl and all its dependencies but it just yields this:
[root@arch /]# pacman -Rns mesa-libgl
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: cairo: requires libgl
:: glu: requires libgl
:: libva: requires libgl
:: mplayer: requires libgl
:: nouveau-dri: requires mesa-libgl
:: qt4: requires libgl
:: qt5-base: requires libgl
I feel like I might need to uninstall the nouveau driver so as to be able to uninstall mesa-libgl. If I installed the nvidia driver at that point, I fear I might see the blank screen again. Thanks for your help in advance.
You do it wrong.
sudo pacman -Rdd mesa-libgl && sudo pacman -S nvidia
After it, you can decide if you want to reinstall mesa-libgl and remove nvidia-libgl or leave nvidia-libgl and do not install mesa-libgl. I do it all the time during update.
Last edited by firekage (2014-07-19 19:48:30) -
Computer, black Screen and reboot problem
I have problems with my computer black screening and rebooting randomly recently. Tried a few things like downgrading the nvidia drivers and only using one monitorscreen.
I was using version 347.52 but downgraded to 344.11 but still got the problem
The times this happens can be anytime but happens most often while i'm playing games and at the moment i'm only playing on normal graphics while my graphics card should be well good enough to handle ultra graphics.
I used this program "WhoCrashed" and got this crash report:
On Sat 2015-02-21 18:29:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022115-10420-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x91951C)
Bugcheck code: 0x116 (0xFFFFFA8010DD3010, 0xFFFFF8800FE0151C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 344.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 344.11
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR
SPECS
Board: MSI Z97 Gaming 5
Bios: Version 1.0
VGA: MSI GeForce GTX 970 GAMING 4G
PSU: Chieftec "CFT-650-14CS" (18a 12v rail)
Intel Core i5-4690k Haswell 3.5GHz LGA 1150 88W
MEM: Crucial Ballistix Sport 2x8GB 1600MHz!
HDD: Samsung 256gb SSD
COOLER: NH-U12P SE2 CPU Cooler
OC: No overclock
OS: Windows 7 64bit ProfessionalI'm getting the same issue. Only in games.
On Sun 2/22/2015 1:32:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022115-7160-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x7A3F38)
Bugcheck code: 0x116 (0xFFFFFA800DBEE010, 0xFFFFF880053E2F38, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 344.16
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 344.16
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.16 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR
Board: MSI Z97 Gaming 7 LGA 1150
Bios: Version 1.8
VGA: MSI 970GTX TWIN FROZRV
PSU: Seasonic ATX12V/EPS12V 750 Power Supply (SSR-750RT)
Intel Core i5-4690K Processor 3.5 GHz LGA 1150
MEM: G.SKILL Ripsjaws X Series 8GB (2x4GB)
HDD: Samsung 250G Evo Series SATA III Internal SSD
COOLER: Corsair H100I Liquid Cooler
OS: Windows 7 64bit Home Premium -
Help solving the Black Screen of Death
Hello There!
I have an HP Touchsmart 610-1100z 3 days ago I put it to sleep and when I tried to wake it up nothing happened. I restarted it and it was just a black screen, no HP logo ect, but I could hear all the fans and drives working. I checked the light issue with a desk lamp and revealed that is not the problem. I then tied the BIOS F10 to F5 work around with no luck. I have gotten it to boot up twice since then by repeatedly turning it off and on until by sheer luck it just boots up. When it boots up there is absolutely no issue but clearly something is eskew that I would like to fix so that I don't live in fear of turning off my computer. Does anyone have any ideas?Hello Vman009,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that you are getting a blank screen when you boot your HP Touchsmart 610-1100x All-In-One Desktop PC. I am providing you with a link to an HP Support document: HP and Compaq All-in-One and TouchSmart Desktop PCs - Screen is Blank after Starting the Computer, which addresses what appears to be the issue you are describing. I would recommend that you review the document and make the adjustments recommended.
Please re-post if you require additional support. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter -
Has anyone got the B500 to work with Ubuntu? (nvidia driver problems)
In two weeks, I have been completely unable to get the nvidia driver working with the B500 on Linux. No matter what I try to do, the X server doesn't start, and my /var/log/Xorg.0.log file ends with "fatal server error: no screens found." I have tried feeding a custom modeline to xorg.conf, explicitly calling an EDID file which I extracted from the Windows installation, using the upstream nvidia driver installer, using the official repository driver, and probably a bunch of other stuff that I'm not recalling right now.
Versions I've tried this on:
Kubuntu 10.04, 32- and 64-bit
Ubuntu 10.04, 32-bit
Kubuntu 9.10, 32-and 64-bit
I am stumped. Has anyone successfully gotten this to work?
best,
-p.
Solved!
Go to Solution.Solved with the kind assistance of paulricardomc on the Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=1477507
Short version of the fix:
1. Extract the edid from the Windows partition using softMCCS, saving as edid.bin
2. Save the edid.bin file in /etc/X11 (or wherever you like)
3. Include the following in the device section of your xorg.conf:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etc/X11/edid.bin"
Fire up X and you're good to go. -
Ultra 40 fx3500 nvidia driver problem with XP
Hello,
I have a Sun Ultra 40 Workstation with an fx3500 graphic-card. With Solaris, Mandriva and 64Bit-Windows
the card works without problems. But with XP 32-Bit only the old 9x drivers from Nvidia work. If I try to
install a driver-release above 100 (today I tried 191.00, but I also have tried many other releases) the driver
installs fine. But after rebooting the workstation powercycles short before the Windows-Login-Screen
appears and Windows boots in "Safe-Mode". Then I can install the old 9x drivers and XP works again.
I tried a tool which wipes out the old Nvidia-driver first, bevor installing the new one, but no success.
Why is it not possible to install new Nvidia-drivers?
After the second boot when the driver has failed to load, the following messages appears on the screen
after the Bios has finished:
"Nvidia Rom Bios" "Detecting Arrays"
I could not read the whole text, because the message appears only a very short time, so I could not
read the message exactly. But the message only appears after the problem with the graphics card driver.
I have not configured disk-arrays. I'm not shure, but is it possible that there is something wrong with
the Nvidia-fx3500, the Nvidia-mainboard-Chipset and the Nvidia-graphics-driver above the 100. release.
Can you please help me?
Best Regards
RalfFirst of all, thank you guys for your replies, and sorry if I answer you late; but I was tring to apply some of your suggestions.
pharao:
My old card was "the stupid" (Hercules 3D Prophet 4000XT with Kyro 4000XT chipset)
Hotoro:
What do you mean by reload Windows XP? Un/Re-Install it?! It is not a good solution for me, at least, right now. I have huge data, my settings and a lot of application installed that needs days to restore or reconfigure, and I do not think that I have that much time.
daveg4otu (Dave):
Thank you for your help. I already removed old card drivers and registry entries, and now I also removed the new ones using "Driver Cleaner" as you suggest, but the same was the result
Raven236:
No, my old card was not ATI. OK, I will try this new driver (56.72), but I can not keep downloading all drivers without result, can I?
coollg:
I do not think so, because the card is working fine on the same PC on Windows 98SE. So, it is not Mainboard, AGP or compatibility problem, as I think. In other hand, you are right, I am not expecting to get the maximum performance from that card, I am, now, looking for the minimum.
Did I have to do someting else?!!!
Thanks again. -
270X Gaming - Black screen after driver install
I just recently purchased an MSI R9 270X Twin Frozr Gaming.
I physically installed the board and booted my PC. Windows started fine, albeit in VGA mode. I then proceeded to install the latest AMD drivers for the card (13.11 Beta). I made it through installation and then rebooted. When I rebooted, I got a blank, black screen after the "Starting Windows" screen. I was unable to boot windows, so I restored to last known configuration and tried again with different drivers (13.9) with the same result.
Does anyone know why windows hangs when it loads the display driver? Any help would be much appreciated.
Thanks
Windows 7 x64 SP1 (fresh install)
ASRock Z77 Extreme4
Core-i5 3570K (no overclock)
4x4GB Corsair Vengeance (stock profile)
Rosewill CAPSTONE 550W ([email protected])
MSI R9 270X Twin Frozr Gaming (S/N 602-V303-03SB1309077057)Hi everyone. I just wanted to give you an update. It seems I have resolved the problem.
After attempting other fixes (fresh Windows install, MB BIOS update, etc), flashing the BIOS of the video card fixed the problem. I used the BIOS version
015.040.000.000.002887. I believe the BIOS the card shipped with is 015.039.000.000.002887. Anyway, there are no problems now. I was able to install Catalyst 13.11 Beta 9.5 with no problems and no black screens.
I got the BIOS and ATIWinflash from TechPowerUp. I'd post links, but I am too new to the board.
Thanks guys. -
WINDOWS 8 BLACK SCREEN AFTER LOGIN PROBLEM
Please help me i have a problem with my computer it goes black screen after i login
my desktop is hp pavilion a5055d my os is windows 8 i dont know what the problem
i have a ati radeon xpress 1100 for videocard ..
I tried to restart many times.Hi,
Did this issue occur before?
Try to logon with Safe Mode to see if the same issue occurs.
Furthermore, you can try to update BIOS for your machine?
You can refer these article to update BIOS if your machine cannot boot:
http://www.ehow.com/how_7356859_update-bios-windows-won_t-boot.html
http://www.wikihow.com/Fix-a-PC-Which-Won't-Boot
Hope that helps.
Leo Huang
TechNet Community Support -
Win7 black-screen-hanging-cursor problem on brand new rMBP
I am sorry but a face a problem similar to (surprisingly) many in this thread.
I have a brand new rMBP 15'' with bootcamp Win7 installed (90GB partition). Installation went painless ONLY with a fresh Yosemite 10.10.3 installation, otherwise I fell into said black screen-hanging cursor trap already during installation. After installation I could enter Windows and install some software there. Upon re-boot, black-screen-hanging cursor in top left problem.
Here is what sudo gpt -vv -r show /dev/disk0 says:
gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 1954210119
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 1772843400 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
1773253040 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1774522576 1840
1774524416 179685376 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1954209792 295
1954210087 32 Sec GPT table
1954210119 1 Sec GPT header
And here for sudo fdisk /dev/disk0:
Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AC 1023 254 63 - 1023 254 63 [ 409640 - 1772843400] <Unknown ID>
3: AB 1023 254 63 - 1023 254 63 [1773253040 - 1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [1774524416 - 179685376] HPFS/QNX/AUX
Any help greatly appreciatedIf you built a USB using BCA and Windows ISO/DVD, it will show Windows and EFI boot both as options, when Alt Key is held.
W7 USB has the following structure .
W8+ USB has the following structure.
Does the behavior change if you
a. Resetting the System Management Controller (SMC) on your Mac - Apple Support
b. How to Reset NVRAM on your Mac - Apple Support -
Both nouveau and nVidia driver problems with Stellarium
Stellarium v0.12.4 with either xf86-video-nouveau 1.0.9-1 or nvidia (latest driver) and an nVidia MCP78S (GeForce 8200) chip usually results in either distorted graphics and sometimes complete system lock-up.
The nVidia driver is worse, nouveau sometimes works but its a crap shoot. This has been going on for about 2 months now, and I have tested both drivers.
With nouveau it dumps these boot errors, but works on other software just fine:
Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x10022c
Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x100230
Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x1002e4
I cannot use the nvidia driver in general because it sometimes causes graphics faults when using Chromium.
I don't get any other graphics issues other than with Stellarium (and obviously I cannot run google-earth with nouveau either).
Any ideas on where to start with this problem would be appreciated.Thanks for answering!
Following your advice, I downloaded and installed the latest driver from Nvidia (http://www.nvidia.fr/object/notebook-win7-winvista-64bit-260.99-whql-driver-fr.html). I'm not sure this is the one I updated on the first place since I don't remember when I did it (it was a few months ago, and as I had internet without using wi-fi, I didn't see that much the BSOD, but now that I'm back to wi-fi, the problem occurs often). Until now, no BSOD, but the first problem "Display Driver Stopped Responding and Has Recovered" is still here, and a little bit more annoying since it can occurs while watching some video files (it didn't happen before).
For the BIOS problem, it was the one described on the link you gave, but no the problem is over. I was just thinking it could be relevant to understand the others problems.
I'll let you know if the BSOD is (or seems) definitively gone. In the meantime, if someone knows how to fix the problem of the display driver that stopped responding and was recovered, it would be greatly appreciated! -
When I enter the command startx I get a black screen and then it crashes and returns to the command line. This has been happening ever since my compter turned itself off (I might have knocked it but I'm not sure), it was the first time it had been turned off since two updates. I have reinstalled the NVIDIA propriatery drivers and Xorg, tried a new xorg.conf, downgraded to nvidia 331.20.1 and installed nvidia-beta all to no avail(I don't wan't to use Nouveau because some Steam games don't work with it and it).
Xorg.0.log
xorg.conf
Linux 3.12.6-1-ARCH
NVIDIA 331.20.3
Xorg 1.14.5
Last edited by XxArcaneXx (2014-01-02 06:24:49)ewaller wrote:
Okay, You backgrounded the OpenBox session, then the rest of the script continues to run. Everything else, with the exception of xset, were backgrounded as well. When xset exits, the script ends and the X session closes.
Move the exec openbox-session & line to the last line of the script, and get rid of the '&' so that it does not background. When the OpenBox session eventualy ends, the script will complete and X will close
Thanks, it works now. I can't believe that I've had it like this for so long and it's worked unitl now. -
[SOLVED] KDE black screen on resume after suspend
Yesterday I wasted the day investigating this and at the end the problem was not suspending the computer but the KDE lock screen as explained here. I thought to open a new thread so other people would not wasted their time looking into the wrong issue as I did.
Anyway, this is what happens, when KDE resumes, it only displays a black screen and the mouse pointer. The problem appears only when the system suspends through KDE (through the menu, the global shortcut or closing the laptop lid), suspending the system directly through systemd (systemctl suspend) or dbus (qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend true) works fine.
The way to recover is to kill kdm (ctrl+atl+backspace) or to restart kdm (switch to a terminal and execute systemctl restart kdm) .
As explained in the post #12 of this thread, if you use a transparent widget style (I use Oxygen Transparent) you have to add the lock screen to the background opacity exception list, for that go to:
System Settings -> Application Appearance -> Style -> Applications -> Configure … (to the right of 'Widget style') -> General -> Exceptions...
And select both "kscreenlocker" and "kscreenlocker_greet", if they do not exist add them through the 'Add' button.
Last edited by thepadawan42 (2013-07-20 08:43:33)Hi,
I am also having this issue. After resuming from suspend-mode, I get a black screen with a mouse-cursor. I can follow you instructions up until "-> General". I don't see an "Exceptions"-button/area where I can select the kscreenlocker exceptions. Can you help? -
Black screen and applications problem on iPhone 4S after upgrading to iOS6
I've upgraded my iphone 4s to the iOS6, all the applications suddenly stops while I am working on it, then the phone shows a black screen and after some seconds shows the main menu screen. When I open the application again after that, things I was doing were lost. Even if I am making a call, the black screen appears, the call is muted to me for a while until when the phone shows me the main screen again and I have to tap to the call. If I am playing music, suddenly the phone shows the black screen and stops the playback, after of it, I try to recover my playback but there is no playback. And happens with everything: facebook, mails, sms, maps, among others. When I was using the iOS 5.1.1. phone was working well.
i looked on the right there is no solution to my problem.i charge my phone to 100% after 2 hours with no usage at all of the phone with 3G off with wifi off with all applications shut down all notifications and locations off battery goes down to 50% when it was running on the older ios never had this problem in my iphone.when will this problem solved
-
[HELP] MSI Radeon R9 270X BLACK SCREEN during driver installation
Hello,
I own the R9 270X, which is on my PCI-E x16 slot, motherboard: Gigabyte ga-b85m-d3h.
When I try to install drivers for my card (those that come from AMD site, those from MSI site or those on the CD attached with card) my screen turns black in the middle of installation.
The monitor works, but there is just black screen displayed. When I restart it stays black after the Windows logo or it crashes during the usage. When it crashes it displays a solid color screen with some vertical stripes. Usually somewhere after 15 minutes from start.
My motherboard BIOS is up to date.
Card has worked great for 2 hours after fresh installation of Windows but then the problems i mentioned came back. I was even able to play games on high settings, but then the solid-color-crash occured again.
Is my card faulty and should I return it?
Specs:
Intel Core i5-4440
Gigabyte GA-B85M-D3H Intel B85 LGA 1150 mATX
Power: Corsair VS 450W ATX 120mm
Windows 8.1 64, but tested also on Windows 7 64 installed on my computer.I'm back on my computer (where I can't install propper drivers), haven't checked with afterburner.
Two scenarios:
1. The screen started to flick/jump when we wanted to run testing game (Call Of Duty 4) on his computer, we didn't even get pass the starting window, then when we returned to Windows the flickering and jumping didn't stop. Then it was steady for a 5 second, and again flickering and jumping.
2. When I first received my newly assembled computer after fresh Windows installation I was able to play Assassins’ Creed Black Flag for about 15 minutes, then the flickering/jumping occur. Then after many trials (including removing and trying different drivers, setting up fresh windows and so on -remember, I wasn't able to even install the drivers after that) I was able to again install drivers and play for like 2 hours. Then - same as earlier problem occur.
So in conclusion, I've manage to install my drivers two times. But then the "solid color and stripes" or "jumping and flickering" problem occurred after few minutes of computer usage.
One more thing. On my computer even at low resolution the screen had some glitches (stripes here, dots there), on my friend's computer, there were no glitches at first. The flickering-and-jumping or solid-color-and-stripes problem occurs only on resolution HIGHER than 800x600.
Maybe you are looking for
-
IPhone 4 stuck in recovery mode - Hardware or software problem?
Hi So I just fixed my iPhone 4 screen, and it worked fine, except my vibrator didn't work. Then I opened my iPhone up again and took the vibrator out, and put it in again. Then everything worked fine... Until I updated to IOS 7 (I restored it to fact
-
EBS 12.1.3 Database 11.1.0.7 OS RHEL 5.7 64-bit Hi All, We are receiving following error while logging in to our EBS dev instance from front end: Error Page Exception Details. oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27
-
Problems with set up disc after upgrading hard drive
I am having problems starting up my Macbook after upgrading the hard drive from 80GB to 160GB. The new hd is SATA, a WDScorpio. The pins on the end look the same, and I've had no problem with the physical install. When I go to start up the Macbook
-
Hi, I have to change the column values in a table. The values in the column are to be updated. For e.g. If the old value is "xxxxxxxxxx", I need to take that and update into "xxxyyyxxxx". The column values is so long as its a description field, so it
-
Integration model activation issue - After Prod to Quality refresh of R/3
Hi Guys, Our R/3 quality system refreshed from production. Hence all the integration models Logical system pointing APO production system. Mistakenly I deactivated all the integration model in R/3 Q system which having APO Production logical system.