Constant crashing? BSODs? Memory_Management issues?

So I've put together a new rig this year that is vastly superior to my old one. And as a prerequisite to all this, I just want to state that I never had iRay issues with my PC crashing on my older rig, and that thing only had 16GB of RAM and (I think) a single GTX 760. My new PC has 32GB Ram and dual GTX 1080s with 8GB VRAM each. Here are all the specs for it: https://pcpartpicker.com/list/hcKLBP

My old PC was really slow on iRay rendering but it never crashed on me. Now my new rig usually crashes at least one per scene. Sometimes mid-scene creation, sometimes after initializing the render. A variety of weird BSODs have popped up but by far the most common one has always been Memory_Management and to be honest, I have no idea why. Keep in mind I'm not bloating my scenes with 4K textures and a bazillion polygons; I actually use the Scene Optimizer these days because my rig crashes even while rendering older scenes that worked perfectly fine on my previous, inferior computer. 

I was hoping other people may have had this issue and found ways to alleviate it.

Some other things worth noting is that SLI is disabled on the two devices, Optix Acceleration is selected as well both of my GPUs. CPU is unchecked because, with it selected, my CPU usage usually skyrockets which typically results in a crash too. I'd like to reiterate that these scene files aren't graphically intensive, sometimes they're as simple as a single human figure (subD set to 1) and a HDRi Environment Map in effect, no physical lights. I have Windows 10. Daz is fully updated. Drivers are all updated. And of course I'd be happy to provide more data and screenshots if necessary.

Here's to hoping someone can relate to this issue and has found ways around it. Thank you very much for your time and consideration.

Comments

  • FishtalesFishtales Posts: 6,228

    It might be a heat problem or else there is something not seated right. Try resetting all the ram modules, graphics cards and anything else that might have worked loose. If that doesn't help then try removing one ram module at a time and restart, it may be a faulty module. Try the same with the graphics cards.

  • Have you tried deselecting Optix Acceleration as I think in the past having Optix ticked has caused problems for some set ups so could be worth trying.

    The only problems I have ever had with crashing were caused by a plugin - Iray Catalizer for LAMH & everyone else had the problem to so if you have this plugin installed make sure it is the most up to date version

     

     

  • srieschsriesch Posts: 4,243

    You could try running a utility such as memtest or similar to see if your new memory has any errors, as that can lead to BSODs.

  • Fishtales said:

    It might be a heat problem or else there is something not seated right. Try resetting all the ram modules, graphics cards and anything else that might have worked loose. If that doesn't help then try removing one ram module at a time and restart, it may be a faulty module. Try the same with the graphics cards.

    I checked and everything is seated nicely. Took your advice even further but no such luck. The intregrity of everything seems to be intact. Thank you for your helpful reply though! 

    Tottallou said:

    Have you tried deselecting Optix Acceleration as I think in the past having Optix ticked has caused problems for some set ups so could be worth trying.

    The only problems I have ever had with crashing were caused by a plugin - Iray Catalizer for LAMH & everyone else had the problem to so if you have this plugin installed make sure it is the most up to date version

     

    I'll try to look up the adverse effects from leaving Optix ticked and see any past issues correlate with my own. And when I get home later I'll definitely give it a shot and post any results. Unfortunately I don't have that plug-in either so it can't be that. :(  

    reelyor said:

    I really don't want to have to reinstall Windows 10 or Daz without exploring other options first, but this definitely looks worth a shot as a last resort sort of thing. I might have to bite the bullet and follow your advice though. Thank you for your insightful reply!

    sriesch said:

    You could try running a utility such as memtest or similar to see if your new memory has any errors, as that can lead to BSODs.

    I've ran memtest before and everything is fine. I probably should have mentioned that in original post. Thank you for your helpful reply though!

  • FishtalesFishtales Posts: 6,228
    edited September 2017
    Post edited by Fishtales on
  • PadonePadone Posts: 4,210

    I see that you said SLI is disabled on both cards. Be sure to really disable SLI completely. Not only at the driver level but at the BIOS level. SLI is a killer for iray. Disable it in BIOS so that the driver can't see it at all.

  • Padone said:

    I see that you said SLI is disabled on both cards. Be sure to really disable SLI completely. Not only at the driver level but at the BIOS level. SLI is a killer for iray. Disable it in BIOS so that the driver can't see it at all.

    Is that really the case? My two GPUs are linked up by an actual SLI bridge. Would simply removing the bridge impact it in a meaningful way?

  • PadonePadone Posts: 4,210

    Absolutely. I heard of users having constant crashes for not having disabled SLI in BIOS. Do get rid of it in any possible way, at the lower level you can.

  • JamesJABJamesJAB Posts: 1,766

    Try running your render on each of the cards individualy.  Could be that one of your cards is overheating or defective.

  • PetercatPetercat Posts: 2,324
    edited October 2017

    Check the airflow to your cards, if the spacing is too tight
    one of them might be blocking the other. There is software
    that will let you monitor the cards' temperatures and memory
    usage, like MSI's.

    It will also let you control the cards' environment, for example,
    if the supplied voltage is wrong that will cause problems.

    Post edited by Petercat on
Sign In or Register to comment.