New windows update breaks Studio

dragotxdragotx Posts: 1,138

My PC just installed the new major update from windows, and now Daz crashes with an Access Violation every time I try and open it.

 

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\WINDOWS\SYSTEM32\nvoglv64.DLL" at 0033:000000006636035D, DrvPresentBuffers()+36365 byte(s)

Post edited by dragotx on

Comments

  • Check to see if there is an update for your nVidia Drivers, as that's an error message for the nVidia OpenGL driver. Mine just updated and I'm not seeing it, but I do have the latest driver installed already.

  • dragotxdragotx Posts: 1,138

    Rolling the update back to the previous build brings Studio back to life, so there's definitely something in the new windows build that doesn't play nicely with Studio 4.9

  • It's a video card driver issue, as the error points to the nVidia OpenGL driver; if you're using a version of the nVidia drivers prior to 281.65, I would suggest updating, as they likely are not compatible with the Windows 10 Creator's Update.

  • dragotxdragotx Posts: 1,138
    edited April 2017

    It's a video card driver issue, as the error points to the nVidia OpenGL driver; if you're using a version of the nVidia drivers prior to 281.65, I would suggest updating, as they likely are not compatible with the Windows 10 Creator's Update.

    I'm on the most current nvidia drivers, 381.65.  I wonder if it could be the old 650 I still have installed, mostly for physix.

    Post edited by dragotx on
  • takezo_3001takezo_3001 Posts: 1,974
    edited April 2017
    dragotx said:

    It's a video card driver issue, as the error points to the nVidia OpenGL driver; if you're using a version of the nVidia drivers prior to 281.65, I would suggest updating, as they likely are not compatible with the Windows 10 Creator's Update.

    I'm on the most current nvidia drivers, 381.65.  I wonder if it could be the old 650 I still have installed, mostly for physix.

    Should roll back the nvidia driver as the CEUpdate has broken more than a few dlls; though admittedly, it still falls upon the 3rd party software devs to update their software as well because we cannot rely on M$ to do it unfortunately...

    However, if you login to an admin account DAZ and other conflicted progs seem to work perfectly, so I'm willing to bet that it's M$'s mandatory default settings that are applied to our systems, which is partially unavoidable, but also M$'s discretion for their own purposes, independent towards the end user's benefit...

     

     

    Post edited by takezo_3001 on
  • dragotxdragotx Posts: 1,138
    dragotx said:

    It's a video card driver issue, as the error points to the nVidia OpenGL driver; if you're using a version of the nVidia drivers prior to 281.65, I would suggest updating, as they likely are not compatible with the Windows 10 Creator's Update.

    I'm on the most current nvidia drivers, 381.65.  I wonder if it could be the old 650 I still have installed, mostly for physix.

    Should roll back the nvidia driver as the CEUpdate has broken more than a few dlls; though admittedly, it still falls upon the 3rd party software devs to update their software as well because we cannot rely on M$ to do it unfortunately...

    However, if you login to an admin account DAZ and other conflicted progs seem to work perfectly, so I'm willing to bet that it's M$'s mandatory default settings that are applied to our systems, which is partially unavoidable, but also M$'s discretion for their own purposes, independent towards the end user's benefit...

     

     

    I've already rolled back the creator's update for windows, I haven't run into any bugs with the Nvidia driver on the previous Windows build at all (but my account is an admin account, so that'll bypass that particular issue).  I'm going to hold off on the new update until it's been in the wild a bit longer and I can find some confirmation that Studio does work on it.  Right now, I'm kinda leaning toward it being something with the older card I've got in, but I plan on getting a 1080ti once the aftermarket cards start hitting the shelves, so that old card will be replaced with my current 1070.  I may try it again once I get the upgrade done.

  • takezo_3001takezo_3001 Posts: 1,974
    edited April 2017

     

     

    dragotx said:
    dragotx said:

    It's a video card driver issue, as the error points to the nVidia OpenGL driver; if you're using a version of the nVidia drivers prior to 281.65, I would suggest updating, as they likely are not compatible with the Windows 10 Creator's Update.

    I'm on the most current nvidia drivers, 381.65.  I wonder if it could be the old 650 I still have installed, mostly for physix.

    Should roll back the nvidia driver as the CEUpdate has broken more than a few dlls; though admittedly, it still falls upon the 3rd party software devs to update their software as well because we cannot rely on M$ to do it unfortunately...

    However, if you login to an admin account DAZ and other conflicted progs seem to work perfectly, so I'm willing to bet that it's M$'s mandatory default settings that are applied to our systems, which is partially unavoidable, but also M$'s discretion for their own purposes, independent towards the end user's benefit...

     

     

    I've already rolled back the creator's update for windows, I haven't run into any bugs with the Nvidia driver on the previous Windows build at all (but my account is an admin account, so that'll bypass that particular issue).  I'm going to hold off on the new update until it's been in the wild a bit longer and I can find some confirmation that Studio does work on it.  Right now, I'm kinda leaning toward it being something with the older card I've got in, but I plan on getting a 1080ti once the aftermarket cards start hitting the shelves, so that old card will be replaced with my current 1070.  I may try it again once I get the upgrade done.

    Yeah, I only use my admin account when installing programs naturally, but I still log into my standard "Online" account as I don't favor the idea of going online while logged into my admin account, though I might have to do my 3D and some gaming via my admin account anyways as this seems the best solution. 

    Either that, or turn my "standard online account" into an admin while making a new online one...Confusing yes, but I don't care for the idea of the huge amount of reconfigs that need to be done with all my programs currently using my standard account!...I'd roll back the CEU, 'cept it both took a long time to install, and I've already did my 450 gb backup/sys restore already!

    Post edited by takezo_3001 on
  • This is one of the strangest I've encountered.  In the past few days, I received an update to my Windows 10 and an update of my Nvidia drivers to 381.65.  I was crashing on startup with an access violation on nvoglv64.dll.  The crash occurs every time UNTIL I open an Administrative Command Prompt.  With the command prompt sitting in the background, DAZ 4.9.3.166 starts as though nothing is wrong.

  • takezo_3001takezo_3001 Posts: 1,974

    This is one of the strangest I've encountered.  In the past few days, I received an update to my Windows 10 and an update of my Nvidia drivers to 381.65.  I was crashing on startup with an access violation on nvoglv64.dll.  The crash occurs every time UNTIL I open an Administrative Command Prompt.  With the command prompt sitting in the background, DAZ 4.9.3.166 starts as though nothing is wrong.

    I just rolled back my NVidia driver and all is well, and I didn't even have to change nor login to my admin account to boot, so it is most definitely an NVidia driver issue as I still have my CEUpdate! And yeah, logging into an admin account or running DAZ elevated is a pain as I have to reconfig and re-Register my plugins...So you may want to give that a go!

  • WandWWandW Posts: 2,819

    This is one of the strangest I've encountered.  In the past few days, I received an update to my Windows 10 and an update of my Nvidia drivers to 381.65.  I was crashing on startup with an access violation on nvoglv64.dll.  The crash occurs every time UNTIL I open an Administrative Command Prompt.  With the command prompt sitting in the background, DAZ 4.9.3.166 starts as though nothing is wrong.

    I had something similar happen on my Mom's computer when I first upgraded it to Windows 10.  The sound didn't work, and so I logged in as Administrator and the sound immediately came on, and worked on her account thereafter.  Aparrently the driver wasn't being either installed or initiallized properly under a user account...

  • This is one of the strangest I've encountered.  In the past few days, I received an update to my Windows 10 and an update of my Nvidia drivers to 381.65.  I was crashing on startup with an access violation on nvoglv64.dll.  The crash occurs every time UNTIL I open an Administrative Command Prompt.  With the command prompt sitting in the background, DAZ 4.9.3.166 starts as though nothing is wrong.

    Sounds right, based on other comments. Is there a way to activate Game Mode for applications that need higher privileges without having to run them as Administrator?

  • nicsttnicstt Posts: 11,715

    This is why i disable updates.

    I see what happens first

  • nicstt said:

    This is why i disable updates.

    I see what happens first

    It's not reallly broken as such; I've posted some feedback on the Feedback Hub to see what I can find out.

  • thekmaxxthekmaxx Posts: 5

    Be aware! Once you update you only have 10 days to roll back then Windows will wipe the old installation files which of course, I had no idea until it was too late. 

Sign In or Register to comment.