Nvidia driver crashes X and freezes system

I've installed Arch Linux last night and the nvidia driver I installed crashes X a few seconds after I start it.
At the moment I'm using Nouveau without a problem but I'm not satisfied with the performance so I'd like to use the official nvidia driver. So far I tried the one in the package database (270), the beta one from the AUR (280) and two older ones, (250 & 260). Neither of the latter would install, I'm guessing because of old kernel version?
So basically the problem is that whenever I start X it works for a couple of seconds (less than 10) and then my system freezes to a black screen. When I boot gdm the same thing happens, everything works including input and sound but shortly after seeing the login screen the black screen appears again.
Here's an X error log: http://pastie.org/2248178
So any ideas?

Well the new driver changes the way the GPU throttles. Accoding to Nvidia's update notes, it will throttle up or down allot faster based on load. I have also noticed the DPC latency has significantly dropped on those hardware changes as well and along with the repeated interrupts for state change requests. Did you uninstall the previous drivers first?
Eric
ADK

Similar Messages

Nvidia Driver Crashed and Recovered

I've been getting errors that say my 258 version nVidia Driver crashed and recovered. It's happened probably five times since I got my new replacement machine.
This time, it managed to corrupt a 3DS max file I was working on for school, so I just lost a bunch of work. I'm really close to just throwing my machine away and spending another $2700 on a Dell or something.
Before I do that though, what could cause a driver to crash like that? I've updated to the version on nVidia's site, since Lenovo's driver is over a year old. Do I need to revert?
Every day I'm more disappointed with the build quality and reliability of something I spent so much money for. I do believe this is the last time I will *ever* purchase anything from this company.

xtsubarublazin wrote:
Before I do that though, what could cause a driver to crash like that? I've updated to the version on nVidia's site, since Lenovo's driver is over a year old. Do I need to revert?
It is not recommended that you use drivers from Nvidia's Website for your system(It may have a customized version) .... didn't you get a warning dialog when you tried to download them?
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Nvidia driver crashes when fraps is running and a download of a file is done

When I have fraps running in background (but not recording) and I just finish download a file the nvidia driver crashes and restarts. I got the newest nvidia drivers and I am using Windows Vista 32bit

Try doing the update again, but leave all programs off.
Use this if you need it;
'''[http://www.mozilla.org/en-US/firefox/all/ Download Firefox Full Installer For All languages And Systems]''' {web link}

Satellite A500 - NVIDIA driver stopped responding and has recovered

Hello.
I have a TOSHIBA Satellite A500-1GP. I bought this laptop 1 mounth ago, and from 2 weeks before I start to have problem with it. The screen it goes black, like 2-3 seconds, after is appear this message " Nvidia driver stopped responding and has recovered" Is really start to stressing me. I install the laptop with all his original driver, and his original Windows 7. I didn't make any reinstall, or something else.
The updates ar UP TO DATE, and I have no ideea what he should want from my life. Like this are all the new models ? Start to make problems from the begining ? I'm waiting some answers..
Thanks..

My config:
- Toshiba Satellite A500-1GR
- Process: Intel Core i5
- RAM: 4096 Mo DDR3
- Graphic card: nVidia GeForce GT 330M
I had the same problem the graphic driver installed was the 258.96 Version. I kept it up-to-date using nVidia official web site... Afterwards, I believe I was wrong to do so.
I did as you suggested.
- I went to the [Toshiba Support Center|http://fr.computers.toshiba-europe.com/innovation/generic/SUPPORT_PORTAL/]
- I downloaded and installed the 20/08/10 BIOS Update
- I downloaded and installed the 08/06/10 Display Driver
After that, I checked the version of the GeForce GT 330M driver, it's now 188.75.
I have no problem since I did this in the beginning of this afternoon. What a relief !
Thank for your Support!
If I encounter the issue again, I will notify it in this thread, but I hope this issue is solved and that I won't need to!

Premiere pro cc and nvidia driver crash... why?

Hi guys
Since my new PC configuration, I've been having difficulties making my graphics card (Gygabyte Geforce GTX 650 Ti) enable the mercury playback engine cuda on premiere pro cc. it works for a few moments or it renders 2 3 minutes of my video and vith video hardware acceleration, but after that the video driver crashes and the rendering process and premiere as well. i have the latest driver from nvidia, but also have tried with drivers as old as 310.70 (released december 2012). i use wi 7 sp1, my cpu is intel's [email protected] and intel z77 chipset with 16GB of ram if this is of any relevance. Any ideas on what's the cause of the problem or how i may fix it? (the same thing also happened with premiere pro cs6)
Thanks for your help !

From Tweakers Page - Balanced Systems
What about the amount of VRAM?
As a rough guide, how much VRAM should be installed on the video card, think along these lines:
For SD material, 1 GB is enough
For HD material, go for 1 - 2 GB
For 3K or 4K, go for 2 - 4 GB
For 5K+, go for 4 - 6 GB
Keep in mind that the requirements can vary significantly, depending on the complexity of the timeline. If it happens that the VRAM is depleted (not enough memory), hardware MPE is automatically turned off rather ungracefully and stays off for the rest of the encoding. If you use two video cards in CC, each card uses its own memory and cannot use the memory on the second card. The encoding process works like this: Frame 1 rendered on card 1, frame 2 rendered on card 2, frame 3 rendered on card 1, etc. If either card runs out of memory, again hardware MPE is turned off. Simply put, two video cards with 1 GB each can not be treated as a single card with 2 GB, so the risk of turning off hardware MPE automatically is bigger with these two cards than with a single card.

New 27 iMAC keeps crashing iMovie and freezing videos on YouTube & Quicktime

We just got a new Sept 2013 iMac three days ago, purchased refurbished from the Apple Store online. The whole point of the purchase was to be able to use iMovie to thoroughly edit videos for our YouTube channel, use garage band, lots of internet surfing and video watching etc. We spent the extra dollars to get what we thought was the most improved version of the iMac with all the souped up specs in order to avoid any hassle and headaches from a lack of performance. Here's what we have:
3.4GHz quad-core Intel Core i7
27-inch (diagonal) LED-backlit display with IPS technology; 2560-by-1440 resolution
8GB (two 4GB) of 1600MHz DDR3 SDRAM
1TB hard drive (We have only used 80 GBs of it so far, so plenty of space left)
NVIDIA GeForce GTX 775M graphics processor with 2GB of GDDR5 memory
720p Camera & Mic
OS X 10.9
We're feeling a bit duped now as this seems to have turned out to just be a big expensive piece of junk. Here are our problems:
- Firstly, thank goodness that we had our own Logitech HD camera/mic left over from our PC because the "HD camera" built in to the iMac is worse in quality than my old blackberry curve. Grainy, lack luster, mic has sharp and distant sound, really really bad and false advertisement.
- In the middle of using iMovie (iMac came preinstalled with the newest one, i think its 10?), it will stop responding properly or will crash and close, we wont even have any other programs running.
- When opening Quicktime to record a new video, in the middle of a recording or while the recording window is idle, it will start glitching - flashing between live footage and a freeze frame repeatedly. The only way to stop it is to quit out Quicktime and open again and try to record quickly, or in some cases we have to completely restart the iMac, which then still randomly in the middle of a recording or idle window it will continue to flash and glitch. (You can view an example here in the last minute of one of our videos, we tried to make it work and kept the take since we were doing our outro music dance, but it totally ***** when this happens randomly during our content portion and we have to redo recording. http://youtu.be/MAJzaEShJGw?t=4m34s )
- When watching YouTube videos, the computer takes a while to respond to a command, like if we click on a certain part of the video, it will not load it until we press the pause/play button a few times and wait. Also at the beginning of a video it will start glitching and freezing again, similar to how we explained above in the quicktime, but faster.
If you are familiar with what could be the problem or have any advice, PLEASE HELP, we are concerned that after dropping so much money within just 3 days of use, this iMac is not performing flawlessly in the areas that we most needed and want to know if these issues are common and fixable or if its a defect that would require we send this thing back immediately. We did not get apple care and would hate to have wasted money that we really dont have on a glitchy crashing huge piece of junk.
Want to mention a few other pros and cons unrelated to our issues, for those who may be considering buying one too:
PROS:
- The Magic mouse is really great, particularly because of the scrolling and zooming gestures. (Though sometimes i accidentaly swipe in a browser and go back to a previous page losing any information that was input on the page i was originally on, for example, i had to retype this whole apple imac inquiry because i swiped backwards by mistake and the whole form cleared! annoying, wish the horizontal swipe navigated between tabs instead of going through the page view history.)
- When the imovie is not crashing, after watching some tutorials and making a few vids, its a really greatly improved program from the '09 version we used to use. I import and edit videos much faster now, and footage does not freeze or take time to load while im dragging and dropping, it is immediately responsive.
- Love using the Talk to text function (like Siri) by pressing "fn" twice. Use this to write long emails and papers with ease. Would like to see a "Speak" read back option that allows for text to be selected and read back (like Siri on iPad)
CONS:
- The text is SO small everywhere and there is no option to exactly set text size across the whole system, only option given is to set a different resolution which lessens the quality of the screen with pixelation, and some programs give you the option to set custom sized text in their individual preferences.
- Sometimes in both iMovie & Garageband, simple automated functionality will stop working, for example in iMove, when certain screens or images are dragged and dropped to the work area by the activity bar (i dont know what else to call it, the line that rolls across during playback or stays put when pressing spacebar) usually, that screen or image will click into place to align with the activity bar and will highlight the bar yellow to further communicate that alignment before you drop it, but after extended use in a session, that snapping into alignment when adding items stops working. Or sometimes you can drag and drop the ends of a title screen to adjust/trim the clip, but after extended time that too stops responding and does not let the cursor turn into that arrow that allows you to trim or extend, until after many frustrated clicks or a quit and restart.
- When sharing/exporting a video from iMovie, i would recommend unchecking the add to theatre option because it significantly extends the amount of time needed to complete the action and i found out the theatre is just like a video stream of your movies to be shared on icloud for easy access from your other devices (similar to the icloud photostream connected to iPhoto). It takes the time to make the video readily availabe in various sizes on the Mac server for easy access, which means it takes forever for your video to be exported to where you actually want it. This is not something we need and is not worth the wait time. (For example, last ime we left the theatre box checked, the progress status of the video was estimated to be completed in 351 minutes, and then 20 minutes later that somehow inclreased to 385 minutes, then duddenly it was done, so i think this add to theatre option also cause the progress status updates to go berzerk.)

Given the maximum RAM that model can use is 32GB, and the earlier release of that 27" mid-2013 iMac is nearly the same in most regards, you may note the listing of this slightly older iMac 27" is here in an Apple support document...
•iMac: How to remove or install memory:
http://support.apple.com/kb/HT1423
http://support.apple.com/kb/HT1423#1
The images of where the RAM chips are located, behind a metal plate, should be similar in your iMac and the mid-2013 iMac 27" shown in images on that page. Note there are several models discussed.
You could take the computer to a certified Apple service facility (retail store, or specialist reseller) and pay them to do this, and buy the RAM from them, and you will pay for this at a retail level. If they do it, you'd want to be assured the computer did all the things you sought to cure by upgrading RAM, correctly without fault. Like run tests and stuff.... Or there's no reason to not go ahead (after confirming from Apple) that you could buy quality RAM and do this job yourself, citing the Apple page link I'd posted above.
Contact Apple Support:
http://www.apple.com/support/contact/
You'd have to obtain the correct RAM (as indicated in my earlier post, citing MacTracker) of suitable quality for use in a Macintosh computer, and the recommendation for a DIY is to get the kit from 'Other World Computing' OWC online at their site. You can talk to knowledgable sales staff at OWC about what you have and what you need, and to help they may ask for the product serial number.
This is OWC and they have the spec RAM required for your iMac 27" model; double-check info:
http://eshop.macsales.com/shop/memory/iMac/2012_27/DDR3L
Since yours is an Apple Refurbished model it will have a different number series. Unlike those in a retail store, because Apple does that to tell what ones they refurbished; refurbs I bought online were like that.
With questions during the first three months, you can get 'support' under the initial 90-day span of ownership of the new (and certified) Apple refurbs bought online; the other part of that is 'service' for 1 year. Call a nearest retail Apple Store, to set a genius appointment; or go online, and start the process of reporting your issue, while you still have some kind of warranty on the device. They can diagnose the issues you cite and tell you if you can upgrade the RAM (as you likely can) then you can buy and install the RAM yourself and probably pay less than 1/2 the retail rate, if you get some from OWC. A diagnosis is free if the Genius looks into it, but you'd need to set an appointment & lug the iMac to their store; protected from weather/shock.
If you want to extend the complementary service to three years (less the included 90-days) and add two years of AppleCare service, that is an affordable option of about $170. For a total of three years coverage.
{If you had a 21.5-inch iMac the RAM would require a service department visit where they use a different method to install the RAM upgrade. Those are built differently than the 27-inch iMac.}
There is a bit of detailed important information in the Apple link on how to upgrade the iMac RAM. There is a certain amount of RAM installed already and these chips would likely be removed if you get matching sets of new RAM to upgrade the capacity. And no matter what some say, there is a reason why they can be upgraded with more. Even with Mavericks OS X 10.9.x and its 'memory compression' etc, it would gladly accept all the RAM upgrade chips it could swallow. (Behind metal screen, mid-bottom iMac 27")
You may need to consider questions about applications that use system resources separate from those about whatever issues your iMac seems to exhibit. There may be some other cause of the video and iMovie symptoms, but more RAM won't hurt given the beast you bought can use 32GB and it has 8.
And if it seems too much to handle, you have 14 days from date of
purchase to take it back. Contact them ahead of then, if you do.
Hopefully this helps.
Good luck & happy computing!

Lenovo IdeaPad Y500, Linux 3.10, NVidia driver crashes

After today's update of the Linux kernel to 3.10, I can not start X using the proprietary nvidia driver on my IdeaPad Y500 laptop (MBG2BMH with GeForce GT650M GPU).
When I try to do this, it takes a second or two in the "loading GLX" state, after which the screen goes black. My fan goes to max and after a few seconds, the system dies.
X logs don't show much:
[ 49.888] (**) NVIDIA(0): Enabling 2D acceleration
[ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 56.164] (EE) NVIDIA(0): check your system's kernel log for additional error
[ 56.164] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
[ 56.164] (EE) NVIDIA(0): README for additional information.
[ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[ 56.164] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 56.164] (II) UnloadModule: "nvidia"
[ 56.164] (II) UnloadSubModule: "shadow"
[ 56.164] (II) UnloadSubModule: "wfb"
[ 56.164] (II) UnloadSubModule: "fb"
[ 56.164] (EE) Screen(s) found, but none have a usable configuration.
I will add a kernel log after rebooting, because I seem to have lost it.
I think the relevant message read "GPU fell off the bus", which I think indicates a crash of the GPU driver.
After rolling back to 3.9.9, the issue is gone.
My xorg.conf (and xorg.conf.d) does not contain anything special (only a DPI fix). I tried removing it, but the issue is still there.
EDIT: I seem to be unable to get a kernel log for these sessions.
Journalctl simply does not show the failing session.
I don't know why I did get a log before. It happened on a linux-ck build with a couple of modifications, a while back (and the logs seem to be gone).
I'll try again later, making sure I sync.
Last edited by TBoshoven (2013-07-25 13:57:22)

The problem persist for me with:
local/linux 3.10.5-1 (base)
The Linux kernel and modules
local/bumblebee 3.2.1-3
NVIDIA Optimus support for Linux through VirtualGL
local/nvidia 325.15-1
NVIDIA drivers for linux
local/nvidia-utils 325.15-1
NVIDIA drivers utilities
Xorg.8.log
[ 414.008]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 414.008] X Protocol Version 11, Revision 0
[ 414.008] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 414.008] Current Operating System: Linux drog-laptop 3.10.5-1-ARCH #1 SMP PREEMPT Mon Aug 5 08:04:22 CEST 2013 x86_64
[ 414.008] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=2d778b92-8e56-41d2-a238-cb1ea674849b ro quiet
[ 414.008] Build Date: 01 July 2013 10:48:42AM
[ 414.008]
[ 414.008] Current version of pixman: 0.30.0
[ 414.008] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 414.008] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 414.008] (==) Log file: "/var/log/Xorg.8.log", Time: Tue Aug 6 14:58:48 2013
[ 414.022] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
[ 414.022] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 414.033] (==) ServerLayout "Layout0"
[ 414.033] (==) No screen section available. Using defaults.
[ 414.033] (**) |-->Screen "Default Screen Section" (0)
[ 414.033] (**) | |-->Monitor "<default monitor>"
[ 414.033] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 414.033] (**) | |-->Device "DiscreteNvidia"
[ 414.033] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 414.033] (**) Option "AutoAddDevices" "false"
[ 414.033] (**) Option "AutoAddGPU" "false"
[ 414.033] (**) Not automatically adding devices
[ 414.033] (==) Automatically enabling devices
[ 414.033] (**) Not automatically adding GPU devices
[ 414.034] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 414.034] Entry deleted from font path.
[ 414.034] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 414.034] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 414.034] Entry deleted from font path.
[ 414.034] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 414.034] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 414.034] (++) ModulePath set to "/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules"
[ 414.034] (==) |-->Input Device "<default pointer>"
[ 414.034] (==) |-->Input Device "<default keyboard>"
[ 414.034] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 414.034] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 414.034] (II) Loader magic: 0x7fdc20
[ 414.034] (II) Module ABI versions:
[ 414.034] X.Org ANSI C Emulation: 0.4
[ 414.034] X.Org Video Driver: 14.1
[ 414.034] X.Org XInput driver : 19.1
[ 414.034] X.Org Server Extension : 7.0
[ 414.034] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 414.034] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 414.034] setversion 1.4 failed
[ 414.035] (--) PCI:*(0:1:0:0) 10de:0fd1:144d:c650 rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00003000/128
[ 414.036] Initializing built-in extension Generic Event Extension
[ 414.036] Initializing built-in extension SHAPE
[ 414.036] Initializing built-in extension MIT-SHM
[ 414.036] Initializing built-in extension XInputExtension
[ 414.036] Initializing built-in extension XTEST
[ 414.036] Initializing built-in extension BIG-REQUESTS
[ 414.036] Initializing built-in extension SYNC
[ 414.036] Initializing built-in extension XKEYBOARD
[ 414.036] Initializing built-in extension XC-MISC
[ 414.036] Initializing built-in extension SECURITY
[ 414.036] Initializing built-in extension XINERAMA
[ 414.036] Initializing built-in extension XFIXES
[ 414.036] Initializing built-in extension RENDER
[ 414.036] Initializing built-in extension RANDR
[ 414.036] Initializing built-in extension COMPOSITE
[ 414.036] Initializing built-in extension DAMAGE
[ 414.036] Initializing built-in extension MIT-SCREEN-SAVER
[ 414.036] Initializing built-in extension DOUBLE-BUFFER
[ 414.036] Initializing built-in extension RECORD
[ 414.036] Initializing built-in extension DPMS
[ 414.036] Initializing built-in extension X-Resource
[ 414.036] Initializing built-in extension XVideo
[ 414.036] Initializing built-in extension XVideo-MotionCompensation
[ 414.036] Initializing built-in extension XFree86-VidModeExtension
[ 414.036] Initializing built-in extension XFree86-DGA
[ 414.036] Initializing built-in extension XFree86-DRI
[ 414.036] Initializing built-in extension DRI2
[ 414.036] (II) LoadModule: "glx"
[ 414.064] (II) Loading /usr/lib/nvidia/xorg/modules/extensions/libglx.so
[ 415.388] (II) Module glx: vendor="NVIDIA Corporation"
[ 415.388] compiled for 4.0.2, module version = 1.0.0
[ 415.388] Module class: X.Org Server Extension
[ 415.388] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
[ 415.424] Loading extension GLX
[ 415.424] (II) LoadModule: "nvidia"
[ 415.424] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 415.575] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 415.575] compiled for 4.0.2, module version = 1.0.0
[ 415.575] Module class: X.Org Video Driver
[ 415.586] (II) LoadModule: "mouse"
[ 415.586] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[ 415.598] (II) Module mouse: vendor="X.Org Foundation"
[ 415.598] compiled for 1.14.0, module version = 1.9.0
[ 415.598] Module class: X.Org XInput Driver
[ 415.598] ABI class: X.Org XInput driver, version 19.1
[ 415.598] (II) LoadModule: "kbd"
[ 415.599] (WW) Warning, couldn't open module kbd
[ 415.599] (II) UnloadModule: "kbd"
[ 415.599] (II) Unloading kbd
[ 415.599] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 415.599] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
[ 415.599] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 415.599] (--) using VT number 7
[ 415.614] (II) Loading sub module "fb"
[ 415.614] (II) LoadModule: "fb"
[ 415.614] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 415.631] (II) Module fb: vendor="X.Org Foundation"
[ 415.631] compiled for 1.14.2, module version = 1.0.0
[ 415.631] ABI class: X.Org ANSI C Emulation, version 0.4
[ 415.631] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 415.631] (II) Loading sub module "wfb"
[ 415.631] (II) LoadModule: "wfb"
[ 415.631] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 415.647] (II) Module wfb: vendor="X.Org Foundation"
[ 415.647] compiled for 1.14.2, module version = 1.0.0
[ 415.647] ABI class: X.Org ANSI C Emulation, version 0.4
[ 415.647] (II) Loading sub module "shadow"
[ 415.647] (II) LoadModule: "shadow"
[ 415.647] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 415.648] (II) Module shadow: vendor="X.Org Foundation"
[ 415.648] compiled for 1.14.2, module version = 1.1.0
[ 415.648] ABI class: X.Org ANSI C Emulation, version 0.4
[ 415.648] (II) Loading sub module "ramdac"
[ 415.648] (II) LoadModule: "ramdac"
[ 415.648] (II) Module "ramdac" already built-in
[ 415.668] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 415.668] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 415.668] (==) NVIDIA(0): RGB weight 888
[ 415.668] (==) NVIDIA(0): Default visual is TrueColor
[ 415.668] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 415.669] (**) NVIDIA(0): Option "NoLogo" "true"
[ 415.669] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
[ 415.669] (**) NVIDIA(0): Option "UseEDID" "false"
[ 415.669] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
[ 415.669] (**) NVIDIA(0): Enabling 2D acceleration
[ 415.669] (**) NVIDIA(0): Ignoring EDIDs
[ 415.669] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
[ 415.669] (**) NVIDIA(0): mode
[ 421.681] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 421.681] (EE) NVIDIA(0): check your system's kernel log for additional error
[ 421.681] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
[ 421.681] (EE) NVIDIA(0): README for additional information.
[ 421.681] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[ 421.681] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 421.681] (II) UnloadModule: "nvidia"
[ 421.681] (II) UnloadSubModule: "shadow"
[ 421.681] (II) UnloadSubModule: "wfb"
[ 421.681] (II) UnloadSubModule: "fb"
[ 421.681] (EE) Screen(s) found, but none have a usable configuration.
[ 421.681] (EE)
Fatal server error:
[ 421.681] (EE) no screens found(EE)
[ 421.681] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 421.681] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
[ 421.681] (EE)
[ 421.681] (EE) Server terminated with error (1). Closing log file.
dmesg
[ 26.065828] bbswitch: version 0.7
[ 26.065841] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 26.065850] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[ 26.066059] bbswitch: detected an Optimus _DSM function
[ 26.066076] pci 0000:01:00.0: enabling device (0006 -> 0007)
[ 26.066122] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[ 26.068197] bbswitch: disabling discrete graphics
[ 26.119240] pci 0000:01:00.0: power state changed by ACPI to D3cold
[ 26.258241] systemd-logind[1007]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
[ 26.325508] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 33.492411] r8169 0000:03:00.0 enp3s0: link down
[ 33.492451] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 37.846847] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 38.221072] r8169 0000:03:00.0 enp3s0: link down
[ 38.221110] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 45.372589] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 48.517700] wlp2s0: authenticate with 00:25:c4:5a:3b:e1
[ 48.537543] wlp2s0: send auth to 00:25:c4:5a:3b:e1 (try 1/3)
[ 48.539639] wlp2s0: authenticated
[ 48.539671] ath9k 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use
[ 48.540740] wlp2s0: associate with 00:25:c4:5a:3b:e1 (try 1/3)
[ 48.544916] wlp2s0: RX AssocResp from 00:25:c4:5a:3b:e1 (capab=0x431 status=0 aid=2)
[ 48.545097] wlp2s0: associated
[ 48.545113] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 51.051628] EXT4-fs (sda7): re-mounted. Opts: data=ordered,commit=0
[ 51.539082] EXT4-fs (sda8): re-mounted. Opts: data=ordered,commit=0
[ 95.719761] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[ 396.531583] usb 1-4: USB disconnect, device number 2
[ 397.445922] usb 1-4: new low-speed USB device number 3 using xhci_hcd
[ 397.463231] usb 1-4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 397.465641] input: USB Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/input/input14
[ 397.466186] hid-generic 0003:15D9:0A33.0002: input,hidraw0: USB HID v1.10 Mouse [USB Mouse] on usb-0000:00:14.0-4/input0
[ 408.307902] bbswitch: enabling discrete graphics
[ 408.447228] pci 0000:01:00.0: power state changed by ACPI to D0
[ 414.455675] nvidia: module license 'NVIDIA' taints kernel.
[ 414.455679] Disabling lock debugging due to kernel taint
[ 414.460793] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 414.461133] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
[ 414.461140] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 325.15 Wed Jul 31 18:50:56 PDT 2013
[ 416.186061] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
[ 422.155242] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[ 422.175315] NVRM: RmInitAdapter failed! (0x25:0x28:1157)
[ 422.175324] NVRM: rm_init_adapter(0) failed
[ 457.892854] bbswitch: enabling discrete graphics
[ 467.532288] bbswitch: enabling discrete graphics
[ 467.532300] nvidia 0000:01:00.0: power state changed by ACPI to D0
[ 467.542607] nvidia 0000:01:00.0: Refused to change power state, currently in D3
[ 562.917909] bbswitch: enabling discrete graphics
[ 562.917923] nvidia 0000:01:00.0: power state changed by ACPI to D0

USB thumb drive crashes MBP and PowerBook G4

Hi!
I have a USB thumb drive. It mounts on the Desktop (as two drives, which is not strange because it has both an internal 6 MB of memory and a 2GB SD card) and I can open them. But if I attempt to copy a file either to or from the drive, the Finder hangs forever.
This problem exists both on a shiny new MacBook Pro with 10.4.7, and a PowerBook G4 with 10.3---in either case, I must hard-reboot the machine.
DiskUtility says that the drive checks out OK.
Any thoughts? I tried reformatting the thumb drive, which worked temporarily; but when I added a file to the drive on another machine and tried to transfer it to the Mac, the thing hangs Finder again.
I don't have any problems with the drive on PCs, and I don't have the problem with other USB drives on the Mac.
Xcott

It sounds like the file system is corrupt. I am assuming it's FAT32. I would reformat the drive partitions on a Windows machine and see if that helps.
Also, because it's a dual, you might want to make certain that you do not plug it into a hub or a keyboard but directly into your Mac's USB host port. It may need additional power...
Good Luck!

Just upgraded my OS from the app store, so I don't have the actual disk. What do I do if my hard drive crashes (again) and I have to reinstall the OS?

The hard drive on my computer crashed a couple of weeks ago, so I had to re-install the old OS from the CD that came with my computer almost four years ago. After dealing with all that, I decided to upgrade to OS 10.8.4 and purchased the upgrade from the app store. And then about 20 minutes later I made the realization that hey, if this happens again, I don't have an actual disc to reinstall from should my hard drive crash again. I'm planning on getting a new computer once I get my financial aid in September, but it would be just my luck that my hard drive crashes two weeks before I get that, so what should I do to make sure I don't have to re-purchase the upgraded OS?

Bootable Drive - Install
Bootable Drive - Install (2)
Bootable Drive DVD or USB Flash Drive – Lion Diskmaker

Nvidia driver with KMS and fbset?

I read several wiki articles and wanted to try KMS with my nvidia driver so I renamed /etc/X11/xorg.conf to something else and rebooted. My terminal seems to be running in a rather low resolution. When I query with fbset, I get:
$ fbset
open /dev/fb0: No such file or directory
Are KMS and nvidia incompatible at this point in time or is there something I'm not setting up properly?

jskier wrote:
karol wrote:What do you want, graysky? High resolution - use 'vga=' on the kernel line.
This is not advisable for KMS (which the NVIDIA driver does not support anyway).
Per the wiki, if using KMS and you are having resolution problems, use "fbset" which is found in the extra repo.
I'm using nvidia-173xx and fbset returns "open /dev/fb0: No such file or directory".
Does it work for you?

Premiere Pro CC 2014 Crashing with rendering, freezing system, and more

Hello,
I'm having some serious issues with Premiere pro on my late 2013 iMac.
OSX 10.9.5
3.2GHz Intel Core i5
16GB 1600 MHz DDR3
NVIDIA FeForce GT 755M 1024MB
I'm working in 1920x1080 23.976fps. Media files are from sony FS700 .MTS and Cannon 5DmkIII .mov
Multiple times per day, PP crashes on me. It all started when I was getting really choppy playback which would be accompanied by this error message:
A Low Level Exception has occurred in ImporterMPEG (Importer)
This would soon after lead to the program freezing and me having to force quit the program. After contacting Adobe the first time about this persistent issue, the tech explained to me that it was a "Memory Leak" issue and that there was nothing that could be done. After the support team member ended our chat online before helping me solve my issue, I called support. I provided my case number and this person picked up where the helplessly left me and did the typical Adobe one fix all: He went into the hidden library and cleared all of my preferences, removed any third party plugins, and cleared the files in the root applications Adobe folder, renamed a folder "Adobe.Old" etc.
As I explained to the support team member on the phone, this is not a solution but rather a bandaid until it happens again.
Low and behold it has happened again. This time the support team member had me create a new System Administrator account on my computer thinking that there was a permissions problem with my other account which was conflicting with PPCC2014. While this was a major pain to switch between the new account and any other program that I had set up for day to day work, it allowed me to continue editing and at least (at a less efficient rate) get things done.
Now, while using my new System Administrator account, I am getting terrible crashes that not only stall the program, but force me to hard re-boot my computer. These crashes are accompanied by a terrifying looking screen that I was only able to capture once.
They've only become more intimidating as now I cant even see the program when this happens, but this is the only screen capture that did not turn out completely black.
I'm looking to see if anyone has had any extreme issues like this and if so how they were able to fix it. I've now spent 6+ hours with support and after the last one was told I would receive a personal email follow up by the end of the day (never happened) to take further actions based on the performance after the new account creation.
I need help. Now.
-John

Hi John,
First of all, try this: Re: A low level exception occured in: Importer MPEG (Importer)
Next, make sure that if you updated OS X to 10.9.x, or later, you must check the following each time you update: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Other things to try:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Delete media cache
Remove plug-ins
Repair permissions
Disconnect any third party hardware
Remove QT components from Mac HD > Library > QuickTime
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin

Macbook problems, hard drive crash, random shutdown, freezes

I bought my macbook used a few months ago, and it worked flawlessly until about 3 weeks ago. The system started freezing and not booting (getting folder icon instead of apple at startup). I ran drive setup and tried to repair the drive, but this did not fix the problem. DiskWarrior also could not fix it. I pulled the drive and installed a new hard drive, as I wanted a larger capacity anyways. All my problems appeared fixed for about two weeks, then similar problems began occurring. I backed up all the files I needed to an external firewire drive and attempted to reformat the new internal drive. Drive Setup says it can not reformat the drive - can't mount it and if it does, the drive disappears while in the process of formatting. I pulled the new drive and am having it replaced under warranty. I am using the firewire drive to run my computer, and this seemed to work fine for a day or two until the computer just started shutting down with no warning. Everything goes black, including the little light on the front of the computer. I have to hold down the power button for 10 seconds before it lets me start the computer back up. I had read this may be a memory issue, so I ran memtest and it says the memory is fine (I need to do it in single user mode still, however). I also tried pulling both sticks of ram. They are both 1GB crucial memory. I put each stick in by itself and tried it in both slots and was able to reproduce the shutdown issue with any ram configuration of either stick.
After all this, I realized the firewire drive was only running 10.5, so I updated all the software through software update, and it is now running 10.5.2. It seems to be working better as I have not experienced a random shutdown yet, but I'm anticipating it may start back up soon. Today, however I experienced a different problem - the screen froze on me and the only way to get anything to happen was to force a shutdown with them power button. It's restarted and seems to be working fine again for now.
I've run some logs and here's some things I've found:
When the latest freeze happened, I got this repeated over 100 times:
Apr 29 11:04:31 jon-turners-macbook quicklookd[536]: CGContextClosePath: no current point.
I've also seen this:
Apr 29 11:18:19 jon-turners-macbook kernel[0]: Previous Shutdown Cause: 3
Apr 29 11:18:19 jon-turners-macbook kernel[0]: GFX0: family specific matching fails
Apr 25 19:19:50 localhost kernel[0]: hi mem tramps at 0xffe00000
Should there be anything else I can check? I would run Apple Hardware Utilities, but I don't have the original disks, just the Leopard installer. I have Disk Warrior, but it seems strange this would happen with multiple systems and drives. I'd like to get Techtool Pro, but haven't had the money/time to order it yet.

Thanks for the replies!
Yeah, I think it's the HDD. I was just worried that the RAM was bad and corrupted the HDD or something, but given the symptoms I think you guys are right. Ordered a 7200RPM 320GB HDD off Amazon Prime...will be here tomorrow
I'll post how it goes after I finish installing it. I'm backing up as I type.
I wonder if I can fix the ir port and the sleep indicator light when I install the hard-drive. The sleep indicator light never turns off. It stays on as long as my computer is on, only turns off when I shut it down.

Acrobat causes Nvidia driver to stop and recover

I accidentally started this in the Photoshop forum in an nvidia thread - I was told to move it, so here I am. Apologies.
I am running an EVGA nVidia GeForce 7200GS 512 MB VGA/DVI/TV-out PCI-Express Video Card (model# 512-P2-N430-LR).
Windows 7 (32bit), 2X2.6ghz, 4gb ram, dual monitors.
I'm running Adobe Acrobat 9.0.0 Pro, as a part of Web Premium CS4.
When I run Adobe Acrobat, I see the driver fail and recover - 11 times in the last 30 days. It's often when I'm using Acrobat in a pretty heavy handed manner, like opening 3 large documents at once (but not always that heavy). I updated my driver on June 6th and it still happens.
Event viewer details are:
Log Name:      System
Source:        Display
Date:          6/23/2010 12:33:49 PM
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
I'm installing roughly 1GB of updates for CS4 right now, so hopefully the issue will stop.
I realize this is a video card issue, since it is stopping, but I also realize this is a video card stopping only with the help of Acrobat. Photoshop, Dreamweaver, Fireworks and Flash all have had no trouble from what I can recall.
I have posted a similar issue at the nvidia website, but they have a horrible website and I can't even tell if they support the 7200.
Thanks so much for any help in finding a solution.
Joby

9.3.3 apparently fixed it. I haven't had it happen since I updated and the usual reproduction doesn't stop the driver.
Thanks for the help!!!

Macbook Pro crashes intermittently and freeze!!!

I bought my macbook pro 07 august
my macbook pro crashes intermittently, sometimes a a couple of minutes or a few hours. when it crashes, everything freeze and have to press the power button in order to turn it off. tried changing RAM, but it will crash.
Already sent to Apple service centre twice!!!! Run EVERY HARDWARE AND SOFTWARE TEST! The technician said my macbook pro is FINE!?
what's going on?
I'M REALLY DISAPPOINTED!!!

Suggest you try the following
1. Insert Leopard Install DVD
2. Shut down
3. Reboot holding down the "C" on your keyboard
4. Click on "English" (assuming that's your language on the computer)
5. Find "Dick Utility" on the drop down menu at the top of the screen
6. Select your drive
7. Run "Repair Disk" (permission repair can be run from your hard drive without booting to the DVD)
8. Chances are you're crashing because of an incorrect file/folder count (miss-matched). Disk Utility (from the DVD) will repair this. Continuous freeze-ups are probably from this incorrect count. Unless it's repaired, you'll keep crashing. This repair will keep you running until you figure out the cause. I have a similar problem with sleep/wake. At least this keeps me running for a fair amount of time. I've been trying to figure out the cause (unsuccessfully, as yet).

Why does Nvidia driver crash fFirefox 37.0.2? (using latest 35.012)

Here is the pertinent crash "notes"
AdapterVendorID: 0x10de, AdapterDeviceID: 0x1187, AdapterSubsysID: 36141458, AdapterDriverVersion: 9.18.13.5012
D3D11-WARP? D3D11-WARP- WebGL? EGL? EGL+ GL Context? GL Context+ WebGL+
The latest crash report is "bp-da947c43-6b41-43e3-a746-af6f32150426"
This is happening on two different computers, both with Nvidia graphics adapters. It started around the time Firefox v. 36.x was released.

Hello,
Try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches.
You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
Then perform these steps:
#Open Firefox ''Options'' window (''Preferences'' on Mac or Linux) as follows:
#* In Firefox 29.0 and above, click the menu button [[Image:New Fx Menu]] and select ''Options'' for Windows or ''Preferences'' on Mac or Linux.
#* In Firefox 28.0 and previous versions, click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
#In the Firefox Options (or Preferences) window, click the ''Advanced'' tab, then select ''General''.
#In the settings list, you should find the ''Use hardware acceleration when available'' checkbox. Uncheck this checkbox.
#Now, restart Firefox and see if the problems persist.
Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
* [[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]
* [[Upgrade your graphics drivers to use hardware acceleration and WebGL]]
Did this fix your problems? Please report back to us!
Thank you.

Nvidia driver crashes X and freezes system

Similar Messages

Maybe you are looking for