Nuggetz Posted May 7, 2024 Posted May 7, 2024 (edited) After playing from 10-60 minutes my headset goes blank and DCS crashes. When I look at the latter entries in the Log there is a warning that the track file is too large. This happens in both SP and MP. I have been using the Crystal for 10 months and this problem has only just started in the last 2-3 weeks. I have done a slow repair on DCS but is still happening. I have also raised a ticket with Pimax but would welcome any help or advice to resolve this issue. Thank You. ps I have approx 1.0 TB of spare memory at this time. Edited May 7, 2024 by Nuggetz Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
ED Team BIGNEWY Posted May 7, 2024 ED Team Posted May 7, 2024 Hi Nuggetz please include the dcs log from the session when it crashes, or the zip folder it created after the crash. It should give us some clues. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Nuggetz Posted May 7, 2024 Author Posted May 7, 2024 Thanks Bignewy, PSA, TYdcs.log dcs.log-20240507-100112.zip dcs.log-20240507-061550.zip Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Nuggetz Posted May 8, 2024 Author Posted May 8, 2024 I have been trying to fix this problem and thought I had made progress when flying two long missions in the Kola map this morning. I attach this mornings logs. I note there are a lot of XR runtime errors and that the trackfile was skipped due to the large size. Any help gratefully received. TY dcs.log dcs.log-20240508-073445.zip Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Flappie Posted May 8, 2024 Posted May 8, 2024 It looks like a VR issue, indeed: 2024-05-08 07:34:36.121 ERROR ED_SOUND (13224): IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED) 2024-05-08 07:34:36.225 WARNING LOG (8348): 1 duplicate message(s) skipped. 2024-05-08 07:34:36.225 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2024-05-08 07:34:36.225 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-05-08 07:34:36.226 ERROR VISUALIZER (10952): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2024-05-08 07:34:36.229 ERROR VISUALIZER (10952): xrBeginFrame 5876.183146 failed with error: XR_ERROR_CALL_ORDER_INVALID 2024-05-08 07:34:36.229 INFO ED_SOUND (Main): Opening default audio device. 2024-05-08 07:34:36.232 INFO ED_SOUND (Main): Speaker layout: auto 2024-05-08 07:34:36.232 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2024-05-08 07:34:36.232 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2024-05-08 07:34:36.232 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2024-05-08 07:34:36.242 ERROR VISUALIZER (10952): xrBeginFrame 5876.183146 failed with error: XR_ERROR_CALL_ORDER_INVALID 2024-05-08 07:34:36.249 INFO ED_SOUND (Main): Opening default audio device. 2024-05-08 07:34:36.251 INFO ED_SOUND (Main): Speaker layout: forced_stereo 2024-05-08 07:34:36.252 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2024-05-08 07:34:36.252 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2024-05-08 07:34:36.252 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2024-05-08 07:34:36.255 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2024-05-08 07:34:36.376 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2024-05-08 07:34:36.387 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2024-05-08 07:34:36.388 ERROR VISUALIZER (10952): xrBeginFrame 5876.183146 failed with error: XR_ERROR_CALL_ORDER_INVALID 2024-05-08 07:34:36.464 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2024-05-08 07:34:36.616 WARNING LOG (8348): 1 duplicate message(s) skipped. 2024-05-08 07:34:36.616 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2024-05-08 07:34:36.616 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-05-08 07:34:36.617 INFO APP (Main): Device unplugged: [SWD] Pimax (NVIDIA High Definition Audio) 2024-05-08 07:34:36.619 ERROR VISUALIZER (10952): xrBeginFrame 5876.183146 failed with error: XR_ERROR_CALL_ORDER_INVALID 2024-05-08 07:34:36.693 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2024-05-08 07:34:36.699 WARNING LOG (8348): 1 duplicate message(s) skipped. 2024-05-08 07:34:36.699 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME ... 2024-05-08 07:34:45.033 ERROR VISUALIZER (10952): xrBeginFrame 5876.183146 failed with error: XR_ERROR_CALL_ORDER_INVALID 2024-05-08 07:34:45.056 INFO EDCORE (14372): signal caught: 'Abnormal termination' 2024-05-08 07:34:45.056 INFO EDCORE (14372): try to write dump information 2024-05-08 07:34:45.060 INFO EDCORE (14372): # -------------- 20240508-073445 -------------- 2024-05-08 07:34:45.061 INFO EDCORE (14372): DCS/2.9.4.53990 (x86_64; MT; Windows NT 10.0.22631) 2024-05-08 07:34:45.063 INFO EDCORE (14372): C:\WINDOWS\System32\KERNELBASE.dll 2024-05-08 07:34:45.065 INFO EDCORE (14372): # FFFFFFEA (Unknown exception code) at 00007ffcee3d543c 00:00000000 2024-05-08 07:34:45.066 INFO EDCORE (14372): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'jimco' 2024-05-08 07:34:45.068 INFO EDCORE (14372): OS-Version: 10.0.22631 () 0x300-0x1 2024-05-08 07:34:45.069 INFO EDCORE (14372): 0x000000000006543c (KERNELBASE): RaiseException + 0x6C 2024-05-08 07:34:45.070 INFO EDCORE (14372): 0x0000000000006be9 (edCore): ed::current_exception_stack_trace + 0x279 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x000000000007e695 (ucrtbase): raise + 0x1E5 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x000000000007f6a1 (ucrtbase): abort + 0x31 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x000000000007edd9 (ucrtbase): terminate + 0x29 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x0000000000001ab1 (VCRUNTIME140_1): __NLG_Return2 + 0x961 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x000000000000232f (VCRUNTIME140_1): __NLG_Return2 + 0x11DF 2024-05-08 07:34:45.072 INFO EDCORE (14372): 0x0000000000002389 (VCRUNTIME140_1): __NLG_Return2 + 0x1239 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000004189 (VCRUNTIME140_1): __CxxFrameHandler4 + 0xA9 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x00000000000a49ff (ntdll): __chkstk + 0x12F 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x000000000001e466 (ntdll): RtlFindCharInUnicodeString + 0xA96 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000054465 (ntdll): RtlRaiseException + 0x195 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x000000000006543c (KERNELBASE): RaiseException + 0x6C 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000006ba7 (VCRUNTIME140): _CxxThrowException + 0x97 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000011743 (pimax-openxr): (function-name not available) + 0x0 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000003f12 (pimax-openxr): (function-name not available) + 0x0 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000026656 (pimax-openxr): getRuntimeStatus + 0x113E6 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000027c31 (pimax-openxr): getRuntimeStatus + 0x129C1 2024-05-08 07:34:45.073 INFO EDCORE (14372): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2024-05-08 07:34:45.074 INFO EDCORE (14372): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2024-05-08 07:34:45.386 INFO EDCORE (14372): Minidump created. Is your Pimax headset/software up-to-date? The issue starts with "AUDCLNT_E_DEVICE_INVALIDATED". I take it it's an audio component of your headset. It could be caused by a faulty headset but I'm not sure. ---
Nuggetz Posted May 8, 2024 Author Posted May 8, 2024 Thank you for your help. I did recently download the ECHO19 Core update to my existing ECHO19 sound mod but I did delete the new Core update just in case it was that causing the problem. I need to uninstall the original ECHO19 files as well and then reinstall the base module only. Fingers cross that fixes it. thanks again. 1 Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
II.JG1_Vonrd Posted May 9, 2024 Posted May 9, 2024 Are you using the passthrough option? I get the same delayed crash when using it. When I disable passthrough, no crashing even in 3 hour sessions.
Nuggetz Posted May 9, 2024 Author Posted May 9, 2024 4 hours ago, II.JG1_Vonrd said: Are you using the passthrough option? I get the same delayed crash when using it. When I disable passthrough, no crashing even in 3 hour sessions. Thank you for your suggestion. I don’t use pass through. it is early days but I think the Echo19 Core update may have been the root cause. I have deleted the Core update and at least temporarily deleted the ECHO19 sound module. I ran two long missions last night with no crashes in SP Mode. This morning I plan on doing some MP missions. If that works without crashes I will consider the problem resolved. I shall report back later. Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Nuggetz Posted May 9, 2024 Author Posted May 9, 2024 I have been hopeful that I might have fixed things but the crashes continue. I attach the latest log which shows a number of errors and warnings but I cannot figure out what is going on. Any suggestions please? dcs.log Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
hornblower793 Posted May 9, 2024 Posted May 9, 2024 Do you have hot plugging of devices enabled in DCS? The bottom of the log has lots messages showing disconnect / reconnect of USB devices associated with the headset and Nvidia audio Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
Nuggetz Posted May 9, 2024 Author Posted May 9, 2024 I will check next time I log in. Thank you for the suggestion. Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Solution Nuggetz Posted May 10, 2024 Author Solution Posted May 10, 2024 (edited) After much investigation I have found a work around. if I disable eyetracking and auto IPD the headset no longer goes blank thus crashing DCS 10-60 minutes into a session. Note: eyetracking and and auto IPD work fine right up to the crash so it’s not a calibration failure. Historically I had connected the Pimax Crystal data cable to a USB 2.0 (not USB 3.0) which had worked fine for months but now I use USB 3.0. More testing over the weekend and then an email to Pimax on Monday! UPDATE: Following an exchange of emails with Pimax I have restored eyetracking. The solution was to remove the DP cable from the headset socket and disconnect the short cable from that socket direct into the headset. Then the long DP cable is insert directly into the DP socket under the headset top cover. Thus eliminating the short cable altogether. Edited May 15, 2024 by Nuggetz 1 Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Recommended Posts