Announcement

**dans** · 09-11-2017, 05:43 PM

Not sure if this slows you down too much, but maybe excluding your local machine from DR ("Use local host" option in DR settings) is a short term option to avoid the blue screens?

Blue screens are driver issues or hardware issues. So some software may trigger it, but the actual problem is in some system driver or device driver or a hardware issue. A buggy application can not cause a bluescreen directly. The word "uncorrectable" part is nothing specific to worry about - it is not worse than any other blue screen error.

If you have time for troubleshooting:
- don't overclock CPU or GPU
- rollback any recent driver updates
- reduce system power consumption (saw some reports that under-voltage can trigger this error)

Wishing you good luck with the deadline,
Daniel

**Morbid Angel** · 09-11-2017, 06:06 PM

its quite hard to say what it can be. If you think its hardware, perhaps excluding your machine as dans says can help. I would try to render on half the threads and see if this works better? Does it happen without ornatrix at all? Usually bsod is hardware related though. Also you might try using max 2017 as an alternative to isolate software issue.

**Morbid Angel** · 09-11-2017, 06:09 PM

there is also a free proggie called blue screen view, it can tell you what driver caused the crash and it might help isolate the problem.
I have a farm and I can help you render your stuff out if need be (though I don't have max 201

**jstrob** · 09-11-2017, 07:08 PM

Ok thanks guys,

It seems that rendering witrhout DR doesn't cause blue screen but since it doesn't happen every time I will have to test this a bit more.

also one of my slaves with completely different hardware (a dual xeon) (except the GPU) was also restarted. Underpower is not a cause (my ws has 1500W psu and only one gpu and 1 cpu) my dual xeon has 4 gpu but 2 power supply, a 1600W and 1200W.

I have no overclock.

So maybe it's the nvidia driver (388.13). I will try another one. Though I don't use GPU rendering right now, just v-ray adv...

I will look for that blue screen view. and thanks for your offer morbid angel, very nice.

**Morbid Angel** · 09-11-2017, 07:18 PM

what did bluescreen view say?

**glorybound** · 09-11-2017, 07:54 PM

I started getting blue screens the day I got the Windows Fall Creator update. Each time it was a different error code, but they were all Nvidis errors and I have since gotten three updates from Nvidia and this last one, which was yesterday, looks to have corrected things,

**jstrob** · 09-11-2017, 09:47 PM

@morbid angel: it just said the error was maybe caused by hal.dll and ntoskrnl.exe so nothing very specific...

@bobby: thanks for your input I will try to install the latest one.

I tried to render my scene on a different computer (the dual xeon I talked earlier) and used DR without my main new workstation. And i could render 2 times the same frame without crash and the third time it just restarted without blue screen and blue screen view doesn't see anything.

So the only common hardware is the video card and they both have the same driver version. So that's my main suspect now.

**jstrob** · 09-11-2017, 09:50 PM

Oups the latest Nvidia driver is

Version:	388.13 ^WHQL
Release Date:	2017.10.30
Operating System:	Windows 10 64-bit
Language:	English (US)
File Size:	439.1 MB

That's the one I already have installed.

Is this the one that you have Bobby?

I will try to roll back to the previous one.

**jstrob** · 09-11-2017, 11:49 PM

I did some hardware check with my Alienware hardware checker and it found nothing. Also did a memory scan with memtest 85+, all is good.

I will try using meshFromstrands instead of VrayOrnatrixMod and also try to render with Corona just to see.

**jstrob** · 10-11-2017, 12:51 AM

I am trying Corona right now since an hour and not a single blue screen so far... The hair shader is amazing in corona BTW!

**jstrob** · 10-11-2017, 03:50 AM

I spent all night rendering with Corona with DR, GI, displacement, fur and I didn't get any blue screen. So It really seems the blue screens are due to V-Ray in some way.

**Ihno** · 10-11-2017, 06:23 AM

Hm.. did you try to turn embree off?

**jstrob** · 10-11-2017, 06:33 AM

No. i could try but now it 's going well with Corona so I think I will finish this project with it cause I 'mm running out of time to debug V-Ray.

**Svetlozar Draganov** · 10-11-2017, 06:51 AM

Since we don't have Deadline with support for 3dsMax 2018 yet I would like to ask if the same issue occurs if Deadline is excluded from the equation?
Instead of using it, can you perform a regular V-Ray DR(no Deadline, Backburner and other render managers) rendering and see if there is any difference?

Since according to lots of users 3dsMax 2018 is extremely unstable can we also perform a few tests with the same scene but rendered with 3dsMax 2017 and with V-Ray Standalone also?

V-Ray cannot be the root of the Blue Screen crashes, those are usually hardware/driver related crashes which might appear during the rendering with V-Ray but not necessary caused by V-Ray.

Let's try to render the scene with V-Ray Standalone, with 3dsMax 2017, without Deadline and etc to get more results which will help us to dig into the right direction.
I'll also try to render the scene here and will post if I found anything suspicious or if I have any questions about it.

Announcement

critical urgency deadline warning blue screen WHEA UNCORRECTABLE ERROR help please!

critical urgency deadline warning blue screen WHEA UNCORRECTABLE ERROR help please!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment