Computer Crashes when Rendering in Iray? Memory_Management BSOD?

Hello! I recently builted up my new eig. Here are all the parts: https://pcpartpicker.com/list/hcKLBP .. GTX 1080 8GB Overclocked x 2 .. 32 GB of RAM .. i7-7700K 4.2 GHz processor.The link speaks for itself.
But in any case, my computer seems to love crashing with the Memory_Management Blue Screen of Death when I render with Iray. I've run a memory diagnostic and there doesn't appear to be anything wrong with the memory cards. My PC recognises my 32 GB. I keep the subD on my models relatively low, but I also rarely have more than two models per scene. What's more is that 99% of my scenes are devoid of any physical props in the background, and I light up my scenes via HDR Environment Maps. I've been forced to utilise scripts to dramatically reduce the resolution of the texture maps.
I have my scene files from my older rig where I only had 16 GB of RAM and a single GTX 760. Surprisingly enough these older scenes appear to cause my new system to crash during rendering too, even though my older rig had no issue rendering them.
I have Daz fully updated. In my render settings, I just have my two GPUs selected for preview and for rendering. OptiX acceleration is enabled. I'm not sure what's making my PC crash so frequently when rendering in Iray but I'm hoping there are other users who have experienced similar issues and can, perhaps, lead me in the right direction in solving it.
Thank you for your time and consideration!
Comments
Have you tried rendering your scene with one render device selected at a time? Try each GPU seperately and once with just the CPU?
Do you have any system monitoring and/or overclocking software installed? (What temperature do your GPUs get up to while rendering)
Are you running GPU drivers directly from Nvidia, or did Windows automaticly install them from Windows Update?
Are you Motherboard drivers updated?
Does your motherboard have overclocking profiles enabled for your RAM and CPU?
is your motherboard running the most recent BOIS?
Do your GPUs have an SLI bridge installed? (if so you might want to try removing it as Iray does not use SLI)
There is a little list to get you started troubleshooting.
So I ran some tests and think I found the source of main issue. I had taken your advice and saw my CPU usage went up to 100% when rendering even while CPU was unchecked in the Render Settings. Then I had noticed my Texture Compression was set to really high values. While I was tinkering with various settings to observe the effect on CPU usage, I discovered that lowering that the Texture Compression reduced it by 70%! Who would have thought T. Comp. would have that sort of adverse effect? This case might be solved for now . . . though my PC still has crashed twice (not a big deal in the slightest, normally it would have crashed like thirty times).
Thank you for your advice!
Going to try this for myself becuase I've been having crashses as well again with the new PC. After taking it to the shop where it was built, all hardware was fin, after a drive and bios reset, everything was good for a couple of weeks. Now, the last 2 weeks, after Daz3d crashes, I even get crashses to startups later when Daz3D is not running. Other programs and games like the Wticher 3 set at Max Settings don't cause a crash, and it "seems" running the computer after a daz3d crash leads to random shutdowns after.
I've swtiched to a slow start up now becuase of some advice that after the crash, the computer may try a reload what it had been doing before... meaning running whatever cause it to crash before (thanks Microsoft, great design) :P I haven't had a crash the last 36 hours, but I haven't run Daz3d. It's funny coming to terms that I may live a life without Daz3d.
This is just my opinion, but I would not run those cards with the overclock for renders unless they were watercooled as that particular card tends to run hot. Having two of them together in close proximity with just the fans to cool them might be a problem.
Windows may restart the programs that were running after a crash. It cannot restart a render or anything like that. You've been given good avenues to investigate what is actually wrong with your computer. I suggest you investigate those rather continuing to macro threads.