GPU Crashes while rendering.
dakkuuan
Posts: 305
I'm sorry if there was a post about this already, but I couldn't find it. So I figured I'd make one and see if anyone had an answer. My GPU keeps crashing during 3Delight renders. The render I did before that was Iray and it didn't crash then, but I've had a windows update or two since then so I can't guarantee that 3Delight is part of the problem. It used to do this when I first installed Windows 10 and my way around it was to shut the view port while rendering. Now it happens no matter what, but as long as the render doesn't take too too long, it will finish. On the final version of a comic panel I was making last night it crashed numerous times and eventually caused the computer to reboot. I wasn't happy. Any ideas what might be causing this?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Does it overheat or anything, you can download GPU-Z from techpowerup and check what its doing.
Any error messages or info in the log file?
Nah that's not the case. I keep a close eye on my GPU because it's old. It's not getting far past idling. The CPU is getting rathe warm, but that would cause a display driver crash. And oddly I tried the same render again today and it didn't happen...maybe it's because I had the temp app on the top, obscuring daz? I don't know...but I do need to find a way to cool that CPU... it's all i've got a for a while.
Can't find anything of suspect in the log file either. And now it's running fine... I really can't figure out what causes this and what stops it.
Time to check your video drivers...if you have an Nvidia card, update them from Nvidia.
I have the latest drivers. I've had this issue with the last few too. I just had a render crash on me. It would complete when I had no lighting, but I put in one of the Yosemite HDR backgrounds/lighting, puit on Average Quality with AMR's render presets, it crashed literally as soon as it started. Nvida Open GL error 6 it says. And this is literally the last thing the daz log file has "WARNING: libpng warning: iCCP: known incorrect sRGB profile".
EDIT: Just crashed on me again. That warning wasn't even listed this time. Have no idea what to think.
Those two errors tell me that there is something deeper than a problem with Studio and rendering...
What video card do you have?
What about other hardware...was this a custom built machine?
Yes it was custom built and it never had this problem under anything but windows 10. Before Windows 10 it rendered fine. Unfortunately it runs better with Windows 10 than it did with Windows 7 with this one exception. nvidia Geforce 275 GTX. I hope this isn't telling me the MB is simply too old for Win10 (the machine is 6+ years old). I really would prefer not to go back. And it hasn't always done this with Windows 10, it tends to be an on again, off again problem, but that could also relate to me not rendering as much. I've always assumed it was something to do with updates it was installing but now I'm not so sure.
Not sure about the motherboard...but...there seems to be a bit of a conflict/not quite reading something right.
The OpenGL error, from what I could find seems to indicate that the OpenGL version the card drivers says it supports isn't what the hardware is actually capable of supporting. If the OpenGL version is too low, then Studio will just throw an error and not open (that could be because of bad/no drivers and not just too low of an OpenGL version). But this error basically means that something is either wrong with the card (like it should be able to support the minimum required version) and there is a fault in the hardware, itself, that is preventing it from using all the features, or that the driver is just lieing about what it supports.
The second error is not a major problem, but more of an indicator that something went wrong. Do you have an HP monitor or printer/scanner attached?
The problem appears to be an HP color profile is both 'embedded', probably system wide and is wrong...at least for Windows 10.
Both of those, together, say to me, that there is an underlying driver problem/OS problem with your Win10 install...
Was it an update install? And did you update any drivers through Windows Update (or however they are doing it now)?
You may want to try downloading a fresh copy of the driver from Nvidia, uninstalling the current driver and reinstalling it 'clean'...
The same if you have an HP printer/scanner/etc...a clean reinstall of the drivers from HP.
It's a fresh install. No I don't have an HP monitor or printer. I'll try downloading the drivers for my moniter. As for drivers beyond my video card I'm using whatever MS installed on the thing. This install of the graphics driver was somewhat clean, because my HDD failed and I have install Windows 10 all over again. The only settings that are on here were ones that might have been left from the driver MS installed at first. Might try the clean install just in case.
"I keep a close eye on my GPU because it's old."
Any chance that the fan is failing? It would be a common problem for an older video card, and it may not be obvious. I keep a small makeup mirror that I got from my daughter in my PC toolkit that I use for such purposes, as it allows me to see beneath the video card and confirm that the fan is spinning. GPUs of that vintage and later run notoriously hot and cooling is crtical since GPUs lack the thermal protection of CPUs. Just take care if you do this not to touch anything with the mirror, as there is a significant risk of shorts or ESD when mucking about inside a running computer. (the little mirror that I have is not only quite small, but has a plastic frame so it is safer to use). Lastly, have you cleaned the heatsink\fan on the video card recently. Blowing the dustbunnies out of your case may not be enough since cowling has become the defacto standard for video card cooling these days. The latter has the disadvantage of trapping dust in the heatsink fins and other underlying components. Just a couple of things worth checking.
Keep an eye on it means I watch it's temps. They don't really move during rendering. It was cleaned not very long ago actually. It's not an overheating issue, I'm certain of that.
/sigh thought it was Error Code 6, now it's 3. Maybe it's both. This is after a clean install of the GPU driver.This was rather instant. I managed to do a rather long render without it happening. This is getting old... I think it has something to do with Daz optimizing the textures, because it didn't do it with this render. I don't think I see error code 6 unless daz doesn't optimize ALL of the textures before the render.
It's the card...unfortunately.
The 275 isn't going to be able to handle the update. It really doesn't have the features needed for the version of OpenGL that is now being used. If there were a newer driver, than the 340.xxx series, then maybe. But that driver series just isn't going to cut it...and that is the latest driver for that card.
Crap... /sigh. So in the end it's really a driver issue. What I'm running now is the 341.92.
So is this really a Windows 10 problem... a driver problem or both. I was under the assumption Opengl came with the driver.
It's sort of both...
The card is old enough that it can't fully handle everything Win10 could potentially throw at it...so there aren't any newer drivers for it that could possibly extend it's abilities/'keep it alive'. That's close to being a 7 yr old card...that means it's like a Ford Model-T, these days.
Oddly finding a card more powerful than it is still out of bargain range. Although I did knock down some of DS's interface settings in referece to the 3D stuff and it seems to be helping. Won't know for sure for a while though.
Oh I probably should have mentioned that the GPU stopped crashing after the driver reinstall. Completely forgot about it lol
If you are keeping Win10, you need a minimum card capable of handling DirectX 11/12...or at least 600/700 series card.
And to make a difference for Iray rendering, it should have a minimum of 4 GB of RAM.
And that's the root of the problem the 275 is only a DirectX 10 card (and the OpenGL level at that time). It may be better under Win7, but there's still a chance that things like Studio could still cause problems.
I don't know if you are in the US or not, but there are a bunch of 1 GB GT710 cards on Newegg.com in the $35 to $45 range. No they won't do much for Iray or anything, but they are usable in Win10.
I'm considering this one to replace the 440 in my HTPC, the fan on the 440 is rather noisy and it makes watching anything a little less fun...
http://www.newegg.com/Product/Product.aspx?Item=N82E16814500392
Windows 7 was the last OS it was running. Daz Studio ran fine under it. Also, I thought I wasn't having this problem anymore because I was mostly doing iray renders, which it wasn't doing this with. I can't GPU render with this thing I know. As for those 1TB cards, they would likely still be a downgrade. I've done comparisons with bargain cards and they always end up slower. If I just did renders that would be one thing, but I'm a gamer too lol. But I think I have the problem under control now (I hope). I checked out GPU Boss with that card versus mine: http://gpuboss.com/gpus/GeForce-GTX-275-vs-GeForce-GT-710
Well...then the 'best' replacement is starting with the GT740.
The 275 just doesn't have what it takes to handle Win10. In Win7 it could very well be rock stable. And for the most part, in Windows it's the cards DirectX capabilities that matter most.
I've found the real culprit. When I first re-installed Win 10, it ran fine. This render is proof, http://dakkuuan.deviantart.com/art/Autumn-at-School-587937721 , I let it render for around 8 hours. I found the real problem was PrecisionX, which I installed AFTER that render. Unfortunately, the video card gets a bit too hot without it, even at idle, a sure sign it needs replace. So I'm going to look into a way registry way to control the GPU fan, And it's likely ANY SOFTWARE (MSI Afterburner, etc.) you use to control the fan speed of your GPU can cause this problem, I just figured I would post this incase someone needs this information.