Ventuz 6 crash after render to full screen

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
kysour
Posts: 3
Joined: 04 Feb 2019, 14:02

Ventuz 6 crash after render to full screen

Post by kysour » 04 Feb 2019, 18:18

Hello,

We are currently having a big issue with Ventuz 6
Problem occurs when trying to set render to full screen {alt+enter].
Ventuz crashes right after switching to full screen.

Sys info:

OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name XLAB28
System Manufacturer Micro-Star International Co., Ltd.
System Model MS-7B92
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor AMD Ryzen Threadripper 1920X 12-Core Processor, 3500 Mhz, 12 Core(s), 24 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1.10, 09/08/2018
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Micro-Star International Co., Ltd.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume4
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.17134.471"
Time Zone Central Europe Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 28.2 GB
Total Virtual Memory 36.6 GB
Available Virtual Memory 31.0 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes


Following event in Windows LOG:
////////////////////////////////////////////////////////////////////////////////
Faulting application name: Ventuz.exe, version: 6.3.0.24, time stamp: 0x5c470bf0
Faulting module name: Ventuz.Pure.dll, version: 0.0.0.0, time stamp: 0x5c470bc4
Exception code: 0xc0000005
Fault offset: 0x00000000001ce985
Faulting process ID: 0x1d88
Faulting application start time: 0x01d4bcaacc432805
Faulting application path: C:\Program Files\Ventuz Technology Group\Ventuz 6\Ventuz.exe
Faulting module path: C:\Program Files\Ventuz Technology Group\Ventuz 6\Ventuz.Pure.dll
Report ID: e4ce30ae-b0bf-4db7-8c9d-8558f40087d5
Faulting package full name:
Faulting package-relative application ID:
////////////////////////////////////////////////////////////////////////////////

and another log:

////////////////////////////////////////////////////////////////////////////////
Application: Ventuz.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Ventuz.Kernel.Particles.ParticleApi.DisablePartStream(IntPtr, Int32)
at Ventuz.Kernel.Particles.PgParticleStreamInline.Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.CModel.BGroup ByRef)
at Ventuz.Kernel.CModel.PropertyGroup.ValidateInternal(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice)
at Ventuz.Kernel.CModel.VGroupProperty`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice)
at Ventuz.Kernel.CModel.VComponent.ValidatePropertyGroups(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice)
at Ventuz.Kernel.CModel.VComponent.ValidateComponent(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.CModel.BGroup, Int32)
at Ventuz.Kernel.Sys.VModule.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.ProgressItem)
at Ventuz.Kernel.Sys.VScene.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.ProgressItem)
at Ventuz.Kernel.Sys.VModule.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice)
at Ventuz.Kernel.Sys.ScenePortBase.ValidateComponent2(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.CModel.BGroup)
at Ventuz.Kernel.Sys.ScenePort.ValidateComponent2(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.CModel.BGroup)
at Ventuz.Kernel.CModel.VComponent.ValidateComponent(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.CModel.BGroup, Int32)
at Ventuz.Kernel.Sys.VModule.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.ProgressItem)
at Ventuz.Kernel.Sys.VScene.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice, Ventuz.Kernel.ProgressItem)
at Ventuz.Kernel.Sys.VModule.Phase_Validate(Ventuz.Kernel.Gfx.VRenderer, Ventuz.Kernel.Gfx.VDevice)
at Ventuz.Kernel.Gfx.VRenderer.Render(Boolean, Ventuz.Kernel.Gfx.IRenderItem[])
at Ventuz.Kernel.Gfx.VRenderer.Render()
at Ventuz.Designer.Shared.LongJobProgress.WatchProgress[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`1<Boolean>, System.String)
at Ventuz.Designer.Mainform.Render()
at Ventuz.Designer.Mainform.Launch(System.String[], System.IDisposable)
at Ventuz.Designer.Launch.MainLaunch(System.String[], System.IDisposable)
at Launcher.MainProgram.Main(System.String[])

////////////////////////////////////////////////////////////////////

Did somebody experienced similar issue?

User avatar
Dennis
Posts: 284
Joined: 08 Jun 2015, 11:29

Re: Ventuz 6 crash after render to full screen

Post by Dennis » 05 Feb 2019, 10:08

Hey and welcome to the forums

It would be great if you could use the support(at)ventuz.com to get in touch with us and send us some details.

Does this crash happen if you just start ventuz and open a new scene (blanc or with rotating ventuz cube) and switch to fullscreen? Or does it happen with a particular scene only?

If it happens with a specific scene, please make this scene available to us as well.

Is this a Virtual Machine? What kind of Graphics board is installed?
Multiscreen setup? How many Devices are attached? Using a mosaic or eyefinity group?

Thanks and have a nice Day
Dee

:ugeek:

User avatar
Dierk Ohlerich
Posts: 71
Joined: 10 Jul 2012, 09:01
Location: Hamburg, Germany

Re: Ventuz 6 crash after render to full screen

Post by Dierk Ohlerich » 05 Feb 2019, 10:48

Hi,

It would be interesting to know if the mode-switch goes from one GPU to a different GPU, like from an on-board Intel Graphics to an discrete AMD/NVIDIA GPU, or the other way around.

-- Dierk
-- Dierk Ohlerich

kysour
Posts: 3
Joined: 04 Feb 2019, 14:02

Re: Ventuz 6 crash after render to full screen

Post by kysour » 05 Feb 2019, 17:40

Hi guys,

Thank you for your time.

@Dennis It happens in specific scene[s] but as you presume not in rotating cube or blank screen scene :] Unfortunately Iam not able to upload any
current project due to NDA.
Its physical system with Radeon Pro WX2100 card which is used for displaying primary working monitor and Radeon Pro WX9100 with six
active output ports for displaying main out.
As we are using AMD hardware the multiscreen setup is managed by Eyefinity. [6 active output signals on WX9100]
@Dierk Yes it does. From WX2100 to WX9100. I already tried multiple drivers with same result.

As far as I can tell from previous logs it looks like it started failing on Validation process and afterwards Renderer crashes as well.
BUT it doesnt happens when WX2100 GPU is used for rendering fullscreen [Disconecting all other outputs]....so I think same as Dierk that its related to~
switching between GPUs for processing....

Michal

kysour
Posts: 3
Joined: 04 Feb 2019, 14:02

Re: Ventuz 6 crash after render to full screen

Post by kysour » 06 Feb 2019, 15:51

Hello All,

I have additional information to this case.
There is a small workaround for this bug.

Start Ventuz designer->open new blank screen->send to fullscreen [it works as I mentioned before]->let render on fullscreen ->open issued scene with render on full screen still on and SOMETIMES it works. But not in every case so its not stable solution.

System works fine when only ONE GPU is used for working monitor and main output. One question: Is multiple GPU using supported by Ventuz? Are there any restrictions to this? On Ventuz 5 system works fine...

I also tried to reinstall Net.framework package {as you can see from log its failing component as well] but after Windows creator update its impossible to downgrade versions down from 4.7 because those geniuses implemented it as system component :shock: :shock: Some men want to watch the world burn :roll:

Thanks for your help and have a nice day

Michal

Post Reply