Repeated iRay Stop-Starts Lead to a Windows 10 Inverted Smiley Face Screen of Death

acanthisacanthis Posts: 604
edited January 2016 in Daz Studio Discussion

.

Post edited by acanthis on

Comments

  • Are yopu closing the stopped renders?

  • acanthisacanthis Posts: 604
    edited January 2016

    Are yopu closing the stopped renders?

    .

    Post edited by acanthis on
  • I haven't seen this, but recently I've mainly been doing trial renders with new content rather than full scenes - still, quite a bit of cancelling and then swapping materials and doing another render though. It's certainbly worth a bug report - if possible with a scene you know will trigger the issue attached.

  • acanthisacanthis Posts: 604
    edited January 2016

    .

    Post edited by acanthis on
  • acanthis said:

    I don't have enough information gathered yet to report this as a reproducable bug, and was wondering if anyone else has experienced this issue.

    Basically, work on a scene, change some materials, any materials, change anything you like, start iRay rendering, see what it looks like, not quite right, stop iRay, make some more changes, repeat multiple times until happy, leave to render.

    Between 60 to 180 minutes later see Windows 10 report "Oh, dear, something has happened to your PC that requires it to be restarted. Please wait while we gather lots of personal information and send it direct to Bill Gates" (OK, those are not the exact words, but that's the flavour). Reboot. Work lost.

    After reboot load up the scene (because you remembered to save it after each change) and let it render. Finishes OK.

    I am wondering about a possible memory leak either in the iRay Renderer, DAZ Studio, or the NVidia driver. It's definitely related to repeated stop/starts - which seems to imply that it should affect the iRay draw style viewport (which I don't use). Anyone else seen this issue? - with the same precursors, it also manifests itself when you set up an overnight render, come back the next morning and find that your machine was rebooted - but (astonishingly) not because Microsoft decided to install an update.

    I kind of get a similar thing happening, after tinkering with a scene for a while my screen takes longer and longer to refresh properly and my pc will eventually crash when I click the render button.

     

  • Might be worth to have a look at NVIDIA's site, I would think they have a forum there, just in case it's a problem with IRAY and not DS.

  • I stop and start mulitple times on Win 10 and never had this happen (Yet!).

    dbb

  • I could confirm this. I just upgrade to windows 10 recently and have this problem. This never happen before while using windows 7. Memory usage bloating every time I render and finished rendering. Start from 800mb to 1gb to 1.3gb to 1.8gb and so on. Until it crashed windows. I've tried using purge memory and clear undo stack, but to no avail.
  • acanthisacanthis Posts: 604
    edited January 2016

    .

    Post edited by acanthis on
  • JPayneJPayne Posts: 79

    I haven't had the issue where Windows would reboot, but I have had similar crashes in Win 7- 8.1 and 10. I run GPU-Z.0.8.5 to keep an eye on things with regard to the card temps and other things like memory etc. Sometimes GPU-Z.0.8.5 will show that the card isn't rendering the scene. It's all on the CPU. At that point, a crash usually follows, especially when you close an older render you had started and stopped but left up in case I wanted to finish the render. 

  • Digital TouchDigital Touch Posts: 187
    edited October 2015

    I hope they found the problem soon, I can't work with my project without restarting DAZ Studio every 3-4 iray render, it's so annoying.

    I don't think this is HW related problem for sure. I could run any game, other 3D software, you named it, without any problem, except DAZ Studio with iray, go wonder.

    Post edited by Digital Touch on
Sign In or Register to comment.