Jump to content
Sign in to follow this  
Followers 0
ADHDMedia

nVidia Gfx Kexts = Random KP after updating to Yosemite 10.10 (MAS) from GM

1 post in this topic

Recommended Posts

So I spent a couple hours last night upgrading from Yosemite 10.10 GM3 to the official MAS release, and everything went fairly smoothly.  After updating, I installed the new nVidia Web Driver, which actually broke my UEFI Clover boot for some reason (would cause an OSXAptioFixDrv error at startup), so I got in via legacy boot and uninstalled the driver, and all was fine.  Got some work done last night and went to bed like usual.  

 

Well, I woke up this morning to my machine having been restarted for some reason.  The logs show this: 

Wed Oct 22 01:30:57 2014

*** Panic Report ***
panic(cpu 0 caller 0xffffff800041e80a): Kernel trap at 0xffffff7f811a053b, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000008e2d000, CR4: 0x00000000000626e0
RAX: 0xffffff801de54800, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000001
RSP: 0xffffff817ee1b450, RBP: 0xffffff817ee1b470, RSI: 0xffffff8020e5b008, RDI: 0x0000000000000000
R8:  0xffffff8020f5b000, R9:  0x0000000000000000, R10: 0xffffff813d0781e8, R11: 0x0000054cebb716f3
R12: 0xffffff813cd84008, R13: 0xffffff8020e7a008, R14: 0x0000000000000000, R15: 0xffffff8020f5b000
RFL: 0x0000000000010202, RIP: 0xffffff7f811a053b, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff817ee1b100 : 0xffffff800033a811 
0xffffff817ee1b180 : 0xffffff800041e80a 
0xffffff817ee1b340 : 0xffffff800043a443 
0xffffff817ee1b360 : 0xffffff7f811a053b 
0xffffff817ee1b470 : 0xffffff7f812d1f4c 
0xffffff817ee1b4b0 : 0xffffff7f812d18df 
0xffffff817ee1b4e0 : 0xffffff7f8147af36 
0xffffff817ee1b520 : 0xffffff7f81470bc0 
0xffffff817ee1b580 : 0xffffff7f812b1993 
0xffffff817ee1b5f0 : 0xffffff7f814c6fb3 
0xffffff817ee1b630 : 0xffffff7f814c6e74 
0xffffff817ee1b650 : 0xffffff7f811ec2fa 
0xffffff817ee1b6d0 : 0xffffff7f811ef5c5 
0xffffff817ee1b8d0 : 0xffffff7f811f0d64 
0xffffff817ee1b9b0 : 0xffffff7f81391c08 
0xffffff817ee1ba60 : 0xffffff7f81385e63 
0xffffff817ee1bc30 : 0xffffff7f8119c78b 
0xffffff817ee1bcc0 : 0xffffff7f81185fc4 
0xffffff817ee1bd40 : 0xffffff7f81188c8f 
0xffffff817ee1bdb0 : 0xffffff7f811889aa 
0xffffff817ee1be20 : 0xffffff7f8114d71a 
0xffffff817ee1be60 : 0xffffff7f8114cb50 
0xffffff817ee1be90 : 0xffffff7f81148d33 
0xffffff817ee1bef0 : 0xffffff80008d7162 
0xffffff817ee1bf40 : 0xffffff80008d507d 
0xffffff817ee1bf80 : 0xffffff80008d5146 
0xffffff817ee1bfb0 : 0xffffff80004192c7 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0xffffff7f8113d000->0xffffff7f81183fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff7f80b24000
         com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xffffff7f81184000->0xffffff7f81193fff
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0xffffff7f8113d000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff7f80b24000
         com.apple.nvidia.driver.NVDAResman(10.0)[53CC0E05-7382-336C-8239-AE884D6CA71A]@0xffffff7f8119a000->0xffffff7f8141afff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff7f80b24000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xffffff7f81184000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0xffffff7f8113d000
            dependency: com.apple.AppleGraphicsDeviceControl(3.7.21)[4700601D-3FEB-3B86-B2BA-8D71AF84D1C4]@0xffffff7f81194000
         com.apple.nvidia.driver.NVDAGK100Hal(10.0)[DC43029D-568A-3B7C-976B-E922C17F5143]@0xffffff7f8141b000->0xffffff7f815dcfff
            dependency: com.apple.nvidia.driver.NVDAResman(10.0.0)[53CC0E05-7382-336C-8239-AE884D6CA71A]@0xffffff7f8119a000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff7f80b24000

…which looks like a kernel panic related to the default OSX nVidia graphics drivers.  I was obviously in bed when this happened, so I don't really know the circumstances relating to the panic, but it's obviously cause for concern.  

 

I will update this post if it happens again, I'm just curious if anyone else has had any nVidia-related issues since updating to the MAS official release of Yosemite…?  Thanks.  

 

***EDIT***

 

…not sure if this is related or not, but I've never seen anything like this in the console before: 

10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w4
10/22/14 2:18:46.000 PM kernel[0]: XXX i=2
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w5
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w5
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w5
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w5
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:46.000 PM kernel[0]: XXX w1
10/22/14 2:18:46.000 PM kernel[0]: XXX w5
10/22/14 2:18:46.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w4
10/22/14 2:18:58.000 PM kernel[0]: XXX i=2
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w5
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w5
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w5
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w5
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:18:58.000 PM kernel[0]: XXX w1
10/22/14 2:18:58.000 PM kernel[0]: XXX w5
10/22/14 2:18:58.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w4
10/22/14 2:19:12.000 PM kernel[0]: XXX i=2
10/22/14 2:19:12.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w5
10/22/14 2:19:12.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w5
10/22/14 2:19:12.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w5
10/22/14 2:19:12.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w5
10/22/14 2:19:12.000 PM kernel[0]: XXX w8
10/22/14 2:19:12.000 PM kernel[0]: XXX w1
10/22/14 2:19:12.000 PM kernel[0]: XXX w5
10/22/14 2:19:12.000 PM kernel[0]: XXX w8

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By renandesouza
      Hi guys, I recently installed OS X 10.10 Yosemite on my PC, everything was fine in the installation, video card already configured and working perfectly, the sound also had no problems, but I just can not connect to the internet, no connection with ethernet etc ... I tested some kex but it did not work.
       
      PC:
      Asus P5GC-MX/1333
      Core 2 Duo E8400 3.0 GHz 
      2GB DDR2 
      ATi HD 5450
      Realtek ALC883 HD Audio
      Atheros L2 Fast Ethernet 
       
      Network Screen Prints:

    • By al3asdfmovie
      Buongiorno a tutti,
      E la prima volta che scrivo su questo forum, spero di non sbagliare nulla!
      Scrivo qua sperando che qualcuno di voi possa darmi una grossa mano, perchè ho letto di tutto, visto qualsiasi video possibile, ma non riesco proprio ad uscirne fuori.
      Ci avevo già provato 3 anni fa, ma ero riuscito solo su un notebook Sony, sul fisso non ero riuscito a fare nulla. Dicevano che c'erano problemi con i driver della serie Skylake, così ho voluto riprovare ora a distanza di anni.
      Premetto che non sono un informatico, non ho conoscenze particolari. Sono semplicemente un ragazzo che si informa, legge tutorial ed esegue, quindi chissà che la soluzione non sia in realtà una banale sciocchezza.
       
      Dunque, il problema consiste nel fatto che, in circa 8 ore di prove, non sia ancora riuscito ad andare oltre il caricamento del logo, dopo aver selezionato la chiavetta da clover.
      Sto cercando di installare High Sierra, ho provato con una chiavetta con un programma che non ho capito bene perchè, ma non posso scriverlo qui, e una con Clover Configurator (che tra l'altro, nella schermata boot mi da un'interfaccia diversa da quella che ho visto nel tutorial, o anche solo 3 anni prima), ma il problema è sempre lo stesso: dopo circa metà caricamento, o mi esce il simbolo di divieto, o si riavvia il computer, riportandomi nel boot di clover.
      Ho provato un po' di flags, come -v, -x, -s, -f, nv_disable=1 (tra l'altro, per evitare problemi al principio, ho impostato la scheda video di intel come primaria), cpus=1, dart=0, Slide=0, insomma, qualsiasi cosa leggessi in giro che avesse portato esiti positivi, la provavo
      Ho provato su porte sub 3.0, 2.0 e le 2.0 dietro al pc.
      Penso sia irrilevante, ma nel caso, sto usando una chiavetta da 32 gb.

      Nella firma dovrebbero esserci tutte le specifiche del mio PC, non so se debba postare altro. Nel caso scusatemi, ditemi pure cosa manca che la aggiorno.
      Spero davvero che qualcuno di voi possa aiutarmi. Ho un MacBook Air (High Sierra l'ho scaricato da qui) e ho scoperto quanto sia più affidabile usare Final Cut rispetto a quel bug chiamato Premiére Pro che ho usato per anni, e vorrei poterlo usare anche sul fisso, senza dover acquistare un iMac. Ho letto in giro che con Mojave non è supportata l'accelerazione grafica, per questo vorrei installare High Sierra.

      Grazie mille a chiunque vorrà aiutarmi!
    • By ShiroOne
      Hi! Newbie here.
       
      Been browsing the forums for a while and trying to setup a Mojave 10.14.3 with the following hardware:
      Motherboard: ga-z370n-wifi - BIOS revision F5 CPU: Intel i7-8700k  RAM: G.Skillz Trident Z 32gb (2x 16gb) DDR4-3000 HDD: Samsung 860 Evo M.2 1 TB  PSU: Corsair RX750  
      USB used is 2.0
       
      I've run into an issue where I'm trying to load the installer, but I am getting a panic error before getting to the Grey install screen.
      Followed this guide:
       
      See attached Screenshot for kernel panic.
       
      If I need to provide more info, let me know and I'll do my best to provide the info
       
       
      Also i'm not sure how to get the panic logs since I don't get shell unless I boot into single-user mode. (That of which I noticed a panic error whenever I try to run diskutil from single user mode)

    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not display you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.
       
      Cheers!
    • By MaLd0n
      Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&t=6771   Install MacOS with Olarila Image, Step by Step, Install and Post Install
       
      https://olarila.com/forum/viewtopic.php?f=50&t=8685
          First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generated in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609  Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder  CLOVER.zip   --Install Sierra/High Sierra and boot into system!   Post Installation   --Install Clover in HDD/SSD and replace with my folder CLOVER.zip   --Reboot and activate video!   -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/   --DSDT My DSDT with Skylake patches DSDT.MaLd0n GA H110M-S2.zip Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI --FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
×