- User Since
- Dec 25 2018, 9:57 AM (38 w, 22 h)
Jan 6 2019
I have taked in windows events viewer some info.
Module with error: ntdll.dll, version: 6.1.7601.18247
Exception code: 0xc0000374 (i readed it mean heap corruption)
Offset error: 0x000c3873
Path to module with error: C:\Windows\SYSTEM32\ntdll.dll
You have right. The only things which i dont understood is that happen only with blender 2.8. I have other graphics packages (like blender 2.79, gimp etc) and no problem with them :(
Jan 5 2019
UPDATE: Dont works anymore (neither hash: 46795cee4938 or last beta version) :((((
No update in my system, i dont understood what happening
Jan 1 2019
UPDATE: Tried last beta version (hash: 4d795cee4938) and blender starts without problems :D
Dec 30 2018
Dont exists some blender version pre-builded for debug? I cannot build blender because something dont allow me to install VS 2017
I forgotten to share system-info.txt. This is the content:
============================================ = Blender 2.80 (sub 39) System Information = ============================================
Note that Error in console happen on closing the window
Runned as blender.exe --debug-all > debug.txt
With last beta release (hash 7c438e5366b2, date 29 december) its worse.
Crash without cmd params and with --debug-gpu/--debug-gpu-workarounds.
Run with --debug/--debug-all BUT starting time its VERY slow
Dec 29 2018
Yes, and this time nothing is printed on console :(
Futhermore it RUN with --debug or --debug-all
It crash with --debug-gpu like said. The only message printed on console is
Dec 28 2018
The output of blender with which params?
Dec 27 2018
No luck... Tried last version for Windows 32Bit (hash 2c0c1f494dcf) and same happen :(
No, it crash if started with --debug-gpu or --debug-gpu-force-workarounds
I will try most updated version and i will inform if any difference