a.maali Posted October 13 Posted October 13 Hello, I have a Unigine project, sometimes due to heavy workloads PC crashes, usually i delete .runtimes and the project start mostly normally. Last time PC crashed, after reloading .runtimes form data folder, project.world does load when i double click on it. nor does it respond to opening it. Is there a solution ? EDIT: After inspecting .world, most of the code has been deleted, a back world code is available. however does contain assets location or material ID information, is there another file that contains assets location etc ? Using foxhole world as a template. Best Regards, Allan
arizmenda Posted October 14 Posted October 14 Hi! Could you please send us the information about the PC configuration? The most convenient way would be to attach a dxdiag txt file in your response. Thanks!
a.maali Posted October 14 Author Posted October 14 Dxdiag contain alot of personal information, is there any specific headers or Items I should share ? Unigine's log 16:24:56 ---- Engine ---- 16:24:56 Version: 2.19.0.2 Development Float ver-2.19.0.0-f5c7b9a Aug 27 2024 (2.19 SDK) 16:24:56 Binary: Windows x86_64 Release WinSDK(10.0.10011.16384) Compiler(MSVC:1940 Toolchain:Unknown Toolset:Unknown VisualStudio:Unknown) 16:24:56 Features: Direct3D11.1 Direct3D12.0 Vulkan OpenAL VR OpenVR Varjo Microprofile FloatCoords HalfTexCoords Development 16:24:56 16:24:56 ---- OS ---- 16:24:56 Windows 10 (build 19045) 16:24:56 16:24:56 ---- CPU ---- 16:24:56 AMD Ryzen 9 3900XT 12-Core Processor 16:24:56 Extensions: MMX+ SSE SSE2 SSE3 SSSE3 SSE41 SSE42 SSE4A AVX AVX2 HTT 16:24:56 Frequency: 3799MHz 16:24:56 Cores: 12 Threads : 24 16:24:56 RAM: 48.0GB MB 16:24:56 16:24:56 ---- GPU ---- 16:24:56 GPU 0 Active : NVIDIA GeForce RTX 3090 Memory:24325MB Type:Discrete Vendor:NVidia CommonHeaps:false Priority:32 LUID:000000000000d8a7 DeviceID:00002204 Driver:560.94 16:24:56 GPU 1 : NVIDIA GeForce GTX 1080 Ti Memory:11106MB Type:Discrete Vendor:NVidia CommonHeaps:false Priority:31 LUID:000000000000e7d3 DeviceID:00001b06 Driver:560.94 16:24:56 GAPI: Vulkan 1.3 Dxdiag Info ------------------ System Information ------------------ Time of this report: 10/14/2024, 17:50:45 Machine name: Is this nessesary ? Machine Id: Is this nessesary ? Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: is this necessary ? System Model: is this necessary ? BIOS: 3.50 (type: UEFI) Processor: AMD Ryzen 9 3900XT 12-Core Processor (24 CPUs), ~3.8GHz Memory: 49152MB RAM Available OS Memory: 49102MB RAM Page File: 41241MB used, 7859MB available Windows Dir: is this necessary ? DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, no HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.0.8 DxDiag Version: 10.00.19041.4957 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Display Tab 3: No problems found. Display Tab 4: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Input Tab: No problems found. DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: NVIDIA GeForce RTX 3090 Manufacturer: NVIDIA Chip type: NVIDIA GeForce RTX 3090 DAC type: Integrated RAMDAC Device Type: Full Device (POST) Device Key:Is this necessary ? Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 48875 MB Dedicated Memory: 24325 MB Shared Memory: 24550 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.342773), Green(0.324219,0.630859), Blue(0.153320,0.051758), White Point(0.312500,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Monitor Model: Monitor Id: Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: Driver File Version: 32.00.0015.6094 (English) Driver Version: 32.0.15.6094 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:True Enabled:False Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 8/14/2024 3:00:00 AM, 799776 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Is this necessary ? Vendor ID: Is this necessary ? Device ID: Is this necessary ? SubSys ID:Is this necessary ? Revision ID: Is this necessary ? Driver Strong Name:Is this necessary ? Rank Of Driver:Is this necessary ? Video Accel: Is this necessary ? D3D9 Overlay: Not Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 4 MPO Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 10.000X - 0.500X MPO Media Hints: resizing, colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 10.000X - 0.500X Card name: NVIDIA GeForce GTX 1080 Ti Manufacturer: NVIDIA Chip type: NVIDIA GeForce GTX 1080 Ti DAC type: Integrated RAMDAC Device Type: Full Device Device Key: Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 35656 MB Dedicated Memory: 11106 MB Shared Memory: 24550 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.640625,0.337891), Green(0.310547,0.619141), Blue(0.159180,0.058594), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Monitor Model: Monitor Id: Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: Is this necessary ? Driver File Version: 32.00.0015.6094 (English) Driver Version: 32.0.15.6094 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:True Enabled:False Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 8/14/2024 3:00:00 AM, 799776 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Is this necessary ? Vendor ID:Is this necessary ? Device ID:Is this necessary ? SubSys ID: Is this necessary ? Revision ID:Is this necessary ? Driver Strong Name: Is this necessary ? Rank Of Driver: Is this necessary ? Video Accel: Is this necessary ?
arizmenda Posted October 15 Posted October 15 Thank you for the info. However, it's still not very clear why the PC might crash. I have some additional questions: What gAPI are you running the project with? Try switch it on different one in SDKBro's Global Options, DX11, for instance (screenshot) and run the project. Did this problem occur on previous versions of SDK? Does the same thing happen when you run an empty project?
a.maali Posted October 15 Author Posted October 15 (edited) The project started in SDK version 2.18, also was crashing and I was facing BSOD (stil do sometimes) , it started out in DX11, then i started running it in DX12. also crashed, after migrating to SDK 2.19 i switched to Vulkan, which seemed stable until recently. empty project is fie, it crashed after hours sometimes weeks of work. one note on configuration of hardware I have an RTX 3090 running two screen and a GTX 1080ti running a third screen. It crashed again today, I usually get differnet BSOD, today it was Hypervision. On this SDK 2.19 whenever it crashed .world file get corrupted currently its filed with repeating zeros 00000, a few days ago it looked only like this -> <?xml version="1.0" encoding="utf-8"?> <> <script_name>guid://ca277e6e5e2647ef42a98d3cf923f9b9f54d198f</script_name> <render_settings_path>guid://3f89374a9b79600d1a0a126ab51cf27df64aa704</render_settings_path> </> Edited October 15 by a.maali
bmyagkov Posted October 22 Posted October 22 Hello! @a.maaliIf you have also experienced BSODs it is very likely that this is not a software or UNIGINE issue but a hardware problem. Files can become corrupted due to unexpected termination, so utilizing a version control system (see documentation) is recommended to safeguard your data from loss, especially in cases where you have issues like those described in this topic. For troubleshooting, we recommend resetting your BIOS settings to their default values and disabling any XMP RAM profiles you might have as this counts as overclocking and might produce the issues you've described. This is really important, especially if you have different memory sticks not from a complete kit. Using an XMP profile can provoke unexpected behavior since the parameters are applied across all memory sticks, while the XMP profile is selected by the manufacturer individually, depending on the silicon lottery and the potential that the chips have. The next step is to determine why you are experiencing BSODs. Unfortunately, there is no tool that can show you why the BSOD appears in the first place. It may be due to faulty software (drivers, third-party software, malware) or hardware. In the case of hardware issues, you would need to swap parts until you identify the defective one and replace it. However, you can easily spot a defective GPU if you see artifacts on the screen while benchmarking, so you don't need to cycle through all the hardware parts and can save some time here. :) Also, you might read the BSOD code and refer to topics like the following: - The Overclocker's BSOD Code List - PSA: BSOD Error Code Diagnosis & Possible Solutions This might give you a hint about what exactly is causing this behavior so you can continue digging in that direction. :) Also, note that WHEA (Windows Hardware Error Architecture) errors are logged by the Windows operating system. They are typically recorded in the Event Viewer under the System logs or Windows Logs, specifically categorized under the WHEA-Logger event. There are situations where you don't always get a BSOD but only a log error. That's why it's important to make sure that when your PC is running normally, there are no errors in the background. We would recommend HWInfo64 which has a monitoring mode showing Windows Hardware Errors (WHEA) counter at the bottom of the "Sensors" tab: Moreover, please note that running two GPUs at the same time might also cause unexpected behavior across the entire system. Therefore, for testing purposes, we would recommend sticking with only one GPU for some period of time since it would help isolate the issue. In addition, such a configuration requires quality PSU components with high power. Therefore, it is especially important to choose a PSU that matches the power requirements of your hardware. You can calculate the approximate power consumption for your PC using the following calculator: Power Supply Calculator Before delving deep into troubleshooting the issue, we would recommend clearing your GPU driver using DDU. This driver removal utility can help you completely uninstall AMD/NVIDIA graphics card drivers and packages from your system without leaving leftovers behind. Then, download the latest GPU driver officially provided by NVIDIA. Now, to localize the problem, you need to create a large synthetic load on the system. This way, you can detect the problem sooner and increase the chances of reproducing it. It makes sense to separately test all key components, such as the CPU, GPU and RAM, but also to load all components simultaneously to recreate a situation close to real-world usage. For stressing the CPU, you can use any applications that utilize AVX instructions, such as OCCT, Cinebench, Linpack or Corona. Personally, I recommend Cinebench R20 or R23 as they are free and easy to find online. There's also the 2024 version available for download here: Cinebench 2024 Downloads. Simply download and unpack the archive, then launch the application and perform a multi-core benchmark. In my experience, this software is excellent at detecting CPU problems because it uses a different set of instructions and engages the RAM. Memory testing can be done with TestMem5 as it is easy to use and known as one of the best dedicated tools for this purpose. There are different configurations that create varying levels of load. I recommend finding the configs from Anta777 and testing your RAM properly because, based on your description, the behavior strongly resembles RAM problems. More information on configurations can be found here: Memory Testing with TestMem5. As for GPU stress testing, the choice of applications is even greater. The most effective for reproducing component issues are those that use the latest rendering technologies. You can consider using 3DMark particularly the Time Spy, Fire Strike and Port Royal tests. Based on my experience, these tests indicate video adapter instability earlier than others. However, here are some popular GPU benchmarking tools you can use to evaluate performance and stability issues: FurMark: Great for uncovering cooling issues since it produces a lot of heat while testing. In-game benchmarks: Shadow of the Tomb Raider (the demo is sufficient for testing purposes and free to download on Steam) and Metro Exodus for real-world performance testing. Professional workloads: Try Blender Benchmark and V-Ray. Stress testing tools: MSI Kombustor and OCCT are excellent for stress testing Additionally, consider running tests simultaneously that push your entire system as this will give you a better sense of how all components behave under heavy load. Thanks! 1
Recommended Posts