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

V-Ray V-Ray for 3ds Max Issues
1

Hi,

I am working on a scene with Ornatrix fur in it and using DR. My deadline is almost dead and I can’t go forward with those bluescreens. Can you help me please?

I sent the scene by email to chaosgroup support.

The message I get from windows 10 in the bluescreen is whea incorrectable error. But I hope the error is correctable cause I may loose a lot of money if I can’t render my job!!!

Displacement and GI are turned off and still getting blue screens.

I noticed at least one of my dr slave also restarted before my workstation while trying to render this.

It is not always crashing. I just render one frame cause I am tweaking my fur right now. And sometimes it renders entirely other time it will do that blue screen and restart the computer.

Max 2018.3

vray_adv_36003_max2018_x64_27812

windows 10 1703

i9-7980XE cpu 2.60 Ghz 64GB of ram

zotac 1080Ti mini

and my vraylog:

[2017/Nov/9|17:16:06] ============================================================
[2017/Nov/9|17:16:06] Console created, V-Ray Adv 3.60.03 for x64 from Nov 3 2017, 05:50:53
[2017/Nov/9|17:16:06] ============================================================
[2017/Nov/9|17:16:06] Compiled with Intel C++ compiler, version 16
[2017/Nov/9|17:16:06] Host is 3ds Max, version 20
[2017/Nov/9|17:16:06] V-Ray DLL version is 3.60.03
[2017/Nov/9|17:16:14] Constructor entered.
[2017/Nov/9|17:16:14] Setting default filter kernel.
[2017/Nov/9|17:16:14] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:16:14] Constructor done.
[2017/Nov/9|17:16:17] Resetting VRender.
[2017/Nov/9|17:16:17] Setting default filter kernel.
[2017/Nov/9|17:16:17] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:16:21] Constructor entered (loading from file).
[2017/Nov/9|17:16:21] Setting default filter kernel.
[2017/Nov/9|17:16:21] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:16:21] Constructor done.
[2017/Nov/9|17:16:21] Loading from file.
[2017/Nov/9|17:16:21] Loading filter parameters.
[2017/Nov/9|17:16:21] Adding host “anpanman”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “hakaba”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “hedoro”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “kaiki”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “kamakiri”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “kurayami”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “macurosuke”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “newegga”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “sasori”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “u1komori”:20204 from scene
[2017/Nov/9|17:16:21] Adding host “ufo”:20204 from scene
[2017/Nov/9|17:16:21] Loading done.
[2017/Nov/9|17:16:21] Constructor entered (loading from file).
[2017/Nov/9|17:16:21] Setting default filter kernel.
[2017/Nov/9|17:16:21] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:16:21] Constructor done.
[2017/Nov/9|17:16:21] Loading from file.
[2017/Nov/9|17:16:21] Loading filter parameters.
[2017/Nov/9|17:16:21] Loading done.
[2017/Nov/9|17:16:21] Constructor entered.
[2017/Nov/9|17:16:21] Setting default filter kernel.
[2017/Nov/9|17:16:21] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:16:21] Constructor done.
[2017/Nov/9|17:16:21] VRenderer destructor entered.
[2017/Nov/9|17:16:21] VRenderer destructor done.
[2017/Nov/9|17:16:24] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:24] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:24] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:24] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:24] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:24] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:16:24] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:16:26] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:16:26] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:16:26] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:16:26] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:16:27] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:16:27] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:16:28] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:28] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:28] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:28] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:28] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:28] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:16:28] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:28] Loading HDRI map “Map #20”
[2017/Nov/9|17:16:28] Loading HDRI map “Map 22”
[2017/Nov/9|17:16:29] Loading HDRI map “Map 22”
[2017/Nov/9|17:16:29] Loading HDRI map “Map 22”
[2017/Nov/9|17:16:29] Loading HDRI map “Map 22”
[2017/Nov/9|17:17:23] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:17:23] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:17:23] Loading HDRI map “topCouetteDistri”
[2017/Nov/9|17:17:23] Loading HDRI map “Map #20”
[2017/Nov/9|17:17:23] Loading HDRI map “Map #20”
[2017/Nov/9|17:17:23] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:17:23] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:17:24] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:17:25] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:17:25] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:17:25] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:17:25] Loading HDRI map “distribution_Bedaine”
[2017/Nov/9|17:17:25] Loading HDRI map “elengthMapBedain”
[2017/Nov/9|17:17:25] Saving to file.
[2017/Nov/9|17:17:25] Saving distributed renderer.
[2017/Nov/9|17:17:25] Saving filter parameters.
[2017/Nov/9|17:17:25] Saving done.
[2017/Nov/9|17:17:25] Saving to file.
[2017/Nov/9|17:17:25] Saving distributed renderer.
[2017/Nov/9|17:17:25] Saving filter parameters.
[2017/Nov/9|17:17:25] Saving done.
[2017/Nov/9|17:21:22] Loading HDRI map “Map 22”
[2017/Nov/9|17:21:22] Loading HDRI map “Map 22”
[2017/Nov/9|17:30:18] Cloning VRender.
[2017/Nov/9|17:30:18] Constructor entered.
[2017/Nov/9|17:30:18] Setting default filter kernel.
[2017/Nov/9|17:30:18] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:30:18] Constructor done.
[2017/Nov/9|17:30:18] Constructor entered.
[2017/Nov/9|17:30:18] Setting default filter kernel.
[2017/Nov/9|17:30:18] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:30:18] Constructor done.
[2017/Nov/9|17:30:18] Cloning VRender.
[2017/Nov/9|17:30:18] Constructor entered.
[2017/Nov/9|17:30:18] Setting default filter kernel.
[2017/Nov/9|17:30:18] “default” preset not loaded: Preset name “default” not found
[2017/Nov/9|17:30:18] Constructor done.
[2017/Nov/9|17:30:18] VRenderer destructor entered.
[2017/Nov/9|17:30:18] VRenderer destructor done.
[2017/Nov/9|17:30:37] VRenderer destructor entered.
[2017/Nov/9|17:30:37] VRenderer destructor done.
[2017/Nov/9|17:30:37] VRenderer destructor entered.
[2017/Nov/9|17:30:37] VRenderer destructor done.

--
Jocelyn ?Strob? Simard www.strobfx.com

2

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

3

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.

4

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 2018)

5

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.

6

what did bluescreen view say?

7

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,

8

@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.

9

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.

10

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.

11

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!

12

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.

13

Hm.. did you try to turn embree off?

14

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.

15

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.

16

Hi Svetlozar,

Sorry I didn’t use deadline yet, I was just saying that I have a deadline for my project :wink: I am just doing regular DR.

Thank you for your help. I will try to render with max 2017 to see… But as I said I rendered all night in Corona and didn’t get any blue screen. But It could be a combination of max and vray and some hardware causing the blue screens.

Also I upgraded to max 2018 cause I was having so many bugs in 2017 with CAT, Ornatrix etc. that I thought I would give it a try…

17

And after a night of testing Corona hair shader, I strongly prefer the results I was getting with the vray hair shader so I hope it will work in max 2017. So far I stopped using DR and it seems that it is not crashing in max 2017 without DR…

18

Funny, that’s my overall opinion of Corona. At first it seems nice, but when you get right down to it, V-Ray does almost everything better. Before it was ‘speed vs quality’ and not is is ‘ease of use vs quality’.

19

While I was going to write that so far max 2017 hasn’t crashed, it just did crash, but not a blue screen this time, my system is still up , just max disappear without any error message while I was trying to stop a render region with DR. but it seems to be more stable than 2018 so far.

20

And yes Bobby, I’m still interested in Corona. Quite fast to learn coming from V-Ray. And well designed. But I can’t replace V-Ray that I used for so many years in a single night! And I like the fact that it’s free to use commercially for 45 days.