Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

ADHDMedia

Members
  • Content count

    611
  • Joined

  • Last visited

  • Days Won

    1

ADHDMedia last won the day on January 30 2014

ADHDMedia had the most liked content!

About ADHDMedia

  • Rank
    InsanelyMac Legend

Contact Methods

  • Website URL
    http://www.youtube.com/user/dmeister08

Profile Information

  • Gender
    Male
  • Location
    Modesto, CA, USA
  1. Yea no kidding lol I'm happy with the fact that it runs perfectly once I get to the desktop… I can wait a few mins, life ain't that short hahaha Gotta go big when you're tryna be successful… (delete this if inappropriate please) what you guys think about this song I produced…? It's relevant cuz I did it on a hackintosh hahaha http://soundclick.com/share.cfm?id=13257574
  2. Hey, thanks for the info either way. I'm gonna give it a shot. I know it sounds nuts but I really need my screens… but I might be able to get away with three if I set them up differently. How you like this for a setup [emoji12]
  3. Hey guys. I've got an issue that may or not be related to this one, but I do know for sure that I don't have a second stage boot logo or loading bar, so hopefully fixing that will help fix my issue. After booting through the first stage (takes a matter of seconds off my SSD in UEFI boot mode), I'm greeted with black screens on all four of my monitors (GTX660 driving three, GT430 driving the other one) and it just hangs there for a good couple of minutes. Once that passes and my screens come back, I'm at the desktop and everything is business as usual. Think this might be fixable by correcting boot logo? I'm not all that interested in the boot logo, really, I'm just tired of twiddling my thumbs while I wait for my more-than-capable machine to reach the desktop [emoji23][emoji23][emoji23]
  4. OS X El Capitan Test Thread

    My GUI is a lot smoother on a GTX 650.
  5. OS X El Capitan DP's builds!

    Only issue I'm having so far guys is that every login I get stuck at a black screen with the spinning beachball for about 30 seconds to a minute before it continues to desktop. The Finder also crashes when I go to restart or shutdown. Also having USB issues but I believe that's just related to it being a DP and needing to have the bugs worked out. Anyone else?
  6. What dongle did you buy that works with the patches?
  7. Nope. Matter of fact, it killed my Bluetooth altogether. Where'd you see that someone got it working? I haven't seen that at all. Only working fix I've found is buying all new hardware.
  8. I'd like to know as well. My sleep is functioning properly right now… should I mess with it?
  9. Final Cut Pro X Problems

    Awesome! Glad you got it sorted. I'd be lost without my FCPX (and unemployed too)!!! LMAO
  10. KP report at login, everytime

    I am also experiencing this same issue. Also, when I install the nVidia Web Driver, I can't boot at all with Clover UEFI. I have to use Legacy to even get into my system. Not sure what's going on… Note: I've been using Clover through the entire Yosemite beta process, and everything was fine until I updated to the official version via the MAS.
  11. Clover General discussion

    Hey guys. So after posting this: http://www.insanelymac.com/forum/index.php?/topic/301833-nVidia-Gfx-Kexts-%3D-Random-KP-after-updating-to-Yosemite-10%2E10-%28MAS%29-from-GM ...I realized that I also updated to the latest Clover during the upgrading process, and I was wondering if these new issues are being caused by Clover? Or are they indeed caused by the MAS version of Yosemite? Thanks for any input. Appreciate it as always.
  12. 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
  13. Final Cut Pro X Problems

    Hmm… I dunno. Never had that issue before, been using FCP since 7 on Snow Leopard. I'll try to look into it a bit tho.
  14. Final Cut Pro X Problems

    Okay so same problem with brand new projects and events? You try deleting all of them and starting from scratch? Or at least moving them out of the library?
  15. Final Cut Pro X Problems

    Damn… how about projects/events? Do you have any?
×