Ventuz 6 crash after render to full screen
Posted: 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?
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?