Sketchup 2017 - dpc watchdog violation
-
This is kind of a hail mary hoping that someone out there has had this issue and has found a fix.
I am guessing it is not related to sketchup 2017 or I would have seen other posts relating to it, but I have to at least take a shot.My set up:
i7 5820k, 3.3 ghz
gtx 1080 gpu
crucial bx100 ssd
32gb ram
sketchup 2017 latest release.
windows 10on large models, heavily laden with 3d trees and bushes I am getting the following system crash when I initiate heavy duty tasks such as turning shadows on or rotating the model with all the layers on and shadows on.
These are operations that I carried out routinely, if slowly, in sketchup 2016.It does not happen all the time, but if I am not careful to unburden the system by turning 3d tree and bush layers off, as well as turning shadows off before initiating an orbit or changing time of day I will crash it more often than not.
I am using the same 3d components and styles and modeling technigues that I have always used with 2016. I opened several models in 2016 that are crashing in 2017 and have not had the crash happen in 2016.
Here is the blue screen.
I have updated all drivers and firmware updates, read most of the fixes on google, but no joy yet.
My machine is currently at the computer shop where it was built, but they have not had any luck yet either.Like I said, I am guessing it is not a 2017 sketchup issue, but I thought I would ask if anybody else has experienced this since changing to 2017.
Thanks
-
I haven't seen it, knock on wood, but I did some looking. Probably saw the same thing you did. One common thread is that it has to do with out of date SSD firmware. Have you recently installed a solid state drive? Any other hardware changes?
-
I do have an SSD drive but it's the same one that I have had since it was built. Firmware and drivers are up-to-date.
The only thing that I know that has changed is going from 2016 SketchUp to 2017 SketchUp.
I sure hope that my computer guys can figure it out soon because I really like the way 2017 performs in comparison to 2016 on these large complicated models right up until it crashes. -
I wish I had more to offer but I wish you good luck. I hope your computer guy can find something, too.
-
disable the nVidia High Definition sound support from the Windows Device Manager and unistall from the Windows Software control panel, restart Windows after doing this.
btw, checking the Windows Event Viewer might ched some more light on issues happened.
-
Thank you for that idea. I just swung by the computer shop to steal some files that I need off of my computer and ask them specifically if they have uninstalled and reinstalled the audio drivers. They have uninstall and reinstall every single driver that there is and still experiencing the problem. Currently backing up all of my files in preparation for a full reinstallation of Windows 10.
-
@pmolson said:
...and reinstalled the audio drivers.
don't install but disable and uninstall instead for resolving the likely cause of the issue.
-
I have my computer guys trying that now. I'll let you know how that works.
-
Thanks again for the Ideas.
Turned out to be the graphic cards driver. It was up to date, but the current driver somehow created a problem with su2017.
The previous driver also had the same problem, so we had to roll the driver back two releases.
Probably not coincidentally, two drivers ago was when I installed "the gforce experience" application that is designed to prompt you when new drivers are available so you can stay current with the actual manufactures latest and greatest. I actually thought it would be better to let the manufacture prompt me rather than let windows update handle when and what gets updated. I have had two instances with this gtx1080 gpu in the recent past where windows has changed the driver for me and it has caused problems so I was trying to be smart by going to the gforce experience. I guess i will just let windows do its thing and put the fires out after.
p
Advertisement