• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Rendering 4K freezes Windows 10, 100% CPU usage

Offline
#1 chowlong
Rendering in 4KUHD locks up Windows 10 when using "high" quality setting.
Works at lower resolutions, and most videos at 4KUHD "medium" setting.
The CPU usage gradually climbs to 100 after a minute or so of rendering, and freezes the system a few seconds after it hits 100.
Liquid cooling, AMD 1950x 3.75 GHz + 32Gb RAM
Not sure how to retrieve the log file without restarting app and overwriting it.

Thank you.

[2019-12-30 07:08:53] INFO: Log file was created at C:\Users\Cary\Documents\LRTimelapse\LRTimelapse.log
[2019-12-30 07:08:53] DEBUG: Loading properties from C:\Users\Cary\AppData\Roaming\LRTimelapse\user.props
[2019-12-30 07:08:53] INFO: LRTimelapse 5.3.3 (2019-11-28) Build 602
[2019-12-30 07:08:53] INFO: © 2019 Gunther Wegner
[2019-12-30 07:08:53] INFO: https://lrtimelapse.com
[2019-12-30 07:08:53] INFO: Java version: 11.0.3 (64bit) from AdoptOpenJDK
[2019-12-30 07:08:53] INFO: Running on: Windows 10 locale: en_US
[2019-12-30 07:08:53] INFO: Windows architecture: 64 bit
[2019-12-30 07:08:53] INFO: Found 32 processor cores.
[2019-12-30 07:08:53] INFO: Java runtime: 64 bit
[2019-12-30 07:08:53] INFO: ------------------------------------
[2019-12-30 07:08:53] INFO: Licensed to: Cary Hanneman, Clayton - Private License.
[2019-12-30 07:08:54] DEBUG: Registered Tiff-Reader: com.sun.imageio.plugins.tiff.TIFFImageReader@7fe7c640
[2019-12-30 07:08:54] DEBUG: Registered Tiff-Reader: com.twelvemonkeys.imageio.plugins.tiff.TIFFImageReader@765f05af
[2019-12-30 07:08:55] DEBUG: Launched worker with 32 threads.
[2019-12-30 07:08:55] DEBUG: Initializing directory chooser
[2019-12-30 07:08:55] DEBUG: Start path: C:\Time Lapse\2019 Las Vegas\2019-12-26 Red Rock Canyon
[2019-12-30 07:08:56] DEBUG: Launched worker with 32 threads.
[2019-12-30 07:08:56] DEBUG: Launching ExifTool: C:\Program Files\LRTimelapse 5\exiftool.exe
[2019-12-30 07:08:57] INFO: ExifTool: 11.38
[2019-12-30 07:08:57] DEBUG: Exif Tool available.
[2019-12-30 07:08:57] DEBUG: Using 64bit DNG Converter in C:\Program Files\Adobe\Adobe DNG Converter\Adobe DNG Converter.exe
[2019-12-30 07:08:57] DEBUG: DNG Converter available.
[2019-12-30 07:08:57] DEBUG: MPEG Encoder available.
[2019-12-30 07:08:57] INFO: Detected 1 screen:
[2019-12-30 07:08:57] INFO: Screen 1: 3840 2160
[2019-12-30 07:08:57] DEBUG: Using temp-dir: C:\Users\Cary\AppData\Local\Temp\lrt_1241940203052728782
[2019-12-30 07:08:58] INFO: Latest Version of LRTimelapse: 5.3.3 (2019-11-28), installed Version: 5.3.3 (2019-11-28)
[2019-12-30 07:08:58] DEBUG: Using DNG Converter: C:\Program Files\Adobe\Adobe DNG Converter\Adobe DNG Converter.exe
[2019-12-30 07:08:59] INFO: Done (dirchooser)...
[2019-12-30 07:08:59] DEBUG: Latest Version of Adobe DNG Converter: 12.1.0 (12010000) Installed Version: 12.1 (12010000)
Offline
#2 Gunther
Sounds rather like a thermal issue on your system, because this isn't happening for others also not on my Threadripper.
Please send the log file after it happens, you'll find it in Documents\LRTimelapse
Subscribe to: LRTimelapse Newsletter, Youtube Channel, Instagram, Facebook.
Offline
#3 chowlong
Using a different version of the encoder you sent me did not help, but I found a workaround by using Task Manager to go to the javaw.exe process and change the affinity setting so it uses only the first 16 cores.

...also check out: