Latest post Mon, Apr 7 2014 2:37 AM by Pilgrim. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • Sat, Apr 5 2014 7:12 PM

    • Pilgrim
    • Not Ranked
    • Joined on Mon, Dec 19 2011
    • Posts 6
    • Points 70

    Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    I know I'm posting this right as NAB starts up, so here goes nothing.

     

    Just upgraded all the Avids in our office to MC7. Three z400 stations and a z420 all running Windows 7 64-bit SP1. Everything went smoothly until we came to the last workstation, mine. Installed all new software without a hitch. Last thing I went to do was install the nVidia driver in the folder path

    C:\Program Files\Avid\Utilities\nVidia\nVidiaDriverInstaller_331.65

    The installer usually goes through the process and then prompts for a reboot to continue installation. That didn't happen this last time, so I clicked finish. Opened up Avid and did NOT get the "GPU display driver mismatch" error meaning that Avid saw the 331.65 driver was installed. Great! Went to reboot and after the "Starting Windows" splash I get a Blue Screen of Death (BSoD) stating "Attempt to reset the display driver and recover from timeout failed." 

    I booted into SafeMode and tried installing the driver from there, but with the same results. Long story short from that point, I tried to revert to an earlier restore point but they were all corrupted, could no longer boot into SafeMode anymore, and had to do a complete reinstall of the OS, programs, ISIS client, everything.

    From that point I had everything up and running, except for that driver. Created a new restore point. This time I tried the driver in the "previous" folder, 320.78 (noting in the ReadMe that it was for Windows 7 and the newer 331.65 driver was for Windows 8 only, even though it successfully installed on the other avids). The installer ran, but it never prompted for a reboot. So I rebooted manually, and after the "Starting Windows" page I got another BSoD stating the same thing. Was able to successfully restore back to me restore point before the driver install.

    Contacted nVidia support. Guy in the online chat said "The Settings on the computer are not getting saved." They scheduled a call and over the phone walked me through installing a newer driver 332.76 successfully. Rebooted and everything was working... except MC7, because the 332.76 driver wasn't certified. We then tried to install the other two drivers (331.65 and 320.78, respectively) with installers downloaded directly from the nVidida website, thinking that the installer that unpacked with MC7 might've gotten corrupted. Same story, though. Installer never prompted for a reboot, and after a manual reboot I get a BSoD. 

    So the nVidia guy said to try and use the 332.76 driver, since MC7 will still start up and let me edit. About an hour after I get off the phone with him, displays go dark for a second and come back up with MC7 gone and an error stating: "the nVidia OpenGL driver detected a problem with the display driver and is unable to continue". In the taskbar I get a notification stating that "nvidia driver has stopped working and recovered successfully".

    What possible issues could there be? Do I need to update something in the OS? I have 105 important updates qeued, but only because I just did a clean install.

    What would you try?

    EDIT: Forgot system specs and a quick note. Half of the PCs are custom built to mirror the z400 specs, and the other half are HP Avid-certified z400s. Two Quad-core Xeon E5620 @2.40 GHz, 16GB RAM. Has been running MC5 through MC6.5 smoothly. All PCs are connected to an ISIS 5000.

  • Sat, Apr 5 2014 7:18 PM In reply to

    • mjolnarn
    • Top 10 Contributor
    • Joined on Wed, Feb 8 2006
    • Sweden
    • Posts 13,346
    • Points 159,335

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    Pilgrim:

     I have 105 important updates qeued, but only because I just did a clean install.

    On a clean OS install, I always, and that means always, does all the WU before installing Avid.

    And, of course, also a Quicktime install before installing Avid.

     

    Mac: 17" Macbook Pro i7 2,66 ghz with 8Gb Ram, 500gb 7200rpm drive___ PC_NEW Win10 Pro Mbo Asus Rampage IV Black CPU Ivy Bridge-E 4960X ( = 12 x 4... [view my complete system specs]

    Tomas 

     

  • Sat, Apr 5 2014 7:21 PM In reply to

    • Pilgrim
    • Not Ranked
    • Joined on Mon, Dec 19 2011
    • Posts 6
    • Points 70

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    I've heard conflicting advice as to whether Avid recommends installing any updates past SP1 for Windows 7.

  • Sat, Apr 5 2014 7:26 PM In reply to

    • mjolnarn
    • Top 10 Contributor
    • Joined on Wed, Feb 8 2006
    • Sweden
    • Posts 13,346
    • Points 159,335

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    Before installing a new version of Avid I always make sure that my system is fully updated assuming that the techs that have created that version did the same.

    Have worked well so far.

    Running a WU afterwards, when already having installed Avid, is something that I seldom do, if it is more than 100 updates needed I guess I would uninstall Avid before doing that update.

    Has never happened though

    Mac: 17" Macbook Pro i7 2,66 ghz with 8Gb Ram, 500gb 7200rpm drive___ PC_NEW Win10 Pro Mbo Asus Rampage IV Black CPU Ivy Bridge-E 4960X ( = 12 x 4... [view my complete system specs]

    Tomas 

     

  • Sat, Apr 5 2014 8:24 PM In reply to

    • BarkinMadd
    • Top 25 Contributor
    • Joined on Fri, Nov 4 2005
    • Ontario, Canada
    • Posts 4,589
    • Points 59,945

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    Maybe you should uninstall your nVidia drivers, reboot, install the correct drivers 320.78 and then reboot again. Finally setup the nVidia properties per the instructions in the read me file. See if that helps. Not sure about windows updates. I typically ghost my machine before doing significant changes just in case I need to roll them back. 

    Camera(s) PXW-X70, HDR-FX1, Hero 6 Black | MC 18.7 | QT 7.7.9 | BCC 11 | Sapphire 11 | Mocha Pro 5.6 | Titler Pro 6 | Windows 10 Pro x64 | System: P6X58D... [view my complete system specs]

    Steve

    ______________________

    www.nelliedogstudios.com

  • Sat, Apr 5 2014 8:27 PM In reply to

    • TVJohn
    • Top 25 Contributor
    • Joined on Fri, Nov 4 2005
    • Bayonne NJ
    • Posts 4,317
    • Points 53,375

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    Years ago, I had a similiar problem. Had to install a different (ATI) graphics card, completely unstall the quirky NVidia driver. Reinstall the NVidia card and driver.

    A workaround would  be to remove the card in device manager, the driver, then to let the computer reboot, directing it to the proper driver. Ofttimes a fragment of a generic Windows Driver install remains and currupts an install.

     

    Dell Display U2713HM(2560x1440), AMD FX8350 8core, AMD 990FX mobo, 32gig-DDR3-1600, Quadro K620/GTX260/core 216, Audigy2zs, 1TB SSD system drive, 2TB SATA... [view my complete system specs]

    Using MC 8.4. Avid FX6.4, Vegas Pro 15/ DVD Architect 6pro, DVDit6.4proHD, CCE Basic, TmpGe Express4, TmpGe Authoring Works 4, DVDLab-Studio. Sony EX-1R, Canon XH-A1, GL2, GL1, Canon EOS 60D

  • Mon, Apr 7 2014 2:37 AM In reply to

    • Pilgrim
    • Not Ranked
    • Joined on Mon, Dec 19 2011
    • Posts 6
    • Points 70

    Re: Upgraded to MC7; new nVidia drivers cause BLUE SCREEN

    Okay, I kinda figured out what's causing the issue, but it's raised another question.

    After uninstalling all nVidia drivers (going back to the generic PnP driver), I physically took the card out of the machine and put it back in. Booted, installed the 320.78 driver.

    It asked to reboot!!!!

    I rebooted and everything came up! Well, on my one monitor at least. Forgot to plug the second one in. I restarted just to make sure, and BSoD again. This piqued my interest, so I unplugged the second monitor from the back of the monitor itself (still leaving the cable plugged into the card), and BSoD still! Unplugged cable from card, and it works!

    Imagine that. Something physically inserted into the card is causing the BSoD, even when it's not transmitting any data!

    *walks away grumbling... comes back*

    Okay, just checked the cables. My first monitor is using a DVI-D (single link) cable, and my second monitor (the one with issues) is using a DVI-D (dual link) cable going into a small display port adapter.

    *Goes to find a single link cable*

    HO-LY CRAP. This entire issue was caused by my DVI-I (dual link) to Display Port adapter. I grabbed an adapter off another system, which was a DVI-D to DisplayPort, tried both single and dual link DVI-D cables, and only the single link cable worked. So something about DVI-I, or DVI-D with a dual link cable doesn't play well with this new driver. Fascinating.

    Thanks for all your help, peoples. It was quite a ride!

    EDIT: I got my DVIs mixed up. Everything above is correct now.

Page 1 of 1 (7 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller