19 beta 5 gamma bug with advanced panels

Hello,

just installed 19b5 and I found a strange bug: when trying to adjust gamma with the second control ring Resolve immediately quits. First and third control ring (lift and gain) work fine.

If, instad of using the panel, I click and drag left-right the mouse on the numeric value (white box under gamma color wheel) everything works as expected, and so does if I enter directly a numeric value.

Reinstalled beta 3 and the panel works again, so it's not an hardware fault.

Anyone else having the same issue?

Thanks,
Andre

Hello,

I've opened the crash dump file with windbg and the result is:

CONTEXT: (.ecxr)
rax=000001dd4d24e470 rbx=000001dd4d24e470 rcx=00007ff69cb2c365
rdx=0000009ebf8f9da4 rsi=0000009ebf8fa030 rdi=0000009ebf8f9d94
rip=00007ff69b28d778 rsp=0000009ebf8f9ae0 rbp=0000009ebf8f9be0
r8=0000009ebf8f9d94 r9=00007ff696060000 r10=0000009ebf8f9af8
r11=0000009ebf8f9ab0 r12=0000009ebf8f9d78 r13=0000000000000004
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
Resolve!boost::serialization::singleton_module::unlock+0x1be88:
00007ff6`9b28d778 c5e0c2150f17fe030d vcmpgeps xmm2,xmm3,xmmword ptr [Resolve!LibRaw::subtract+0x1641690 (00007ff6`9f26ee90)] ds:00007ff6`9f26ee90=43480000434800004348000043480000
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff69b28d778 (Resolve!boost::serialization::singleton_module::unlock+0x000000000001be88)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME: Resolve.exe

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR: c000001d

STACK_TEXT:
0000009e`bf8f9ae0 00007ff6`9b272196 : 000001dc`fb124a10 0000009e`bf8fa030 000001dc`a634e801 000001dd`22d8dac0 : Resolve!boost::serialization::singleton_module::unlock+0x1be88
0000009e`bf8f9e10 00007ff6`9919c3a4 : 00000000`00000001 00000000`00000030 000001dd`1aff2a50 00007ffd`445496fd : Resolve!boost::serialization::singleton_module::unlock+0x8a6
0000009e`bf8f9ea0 00007ffc`869c1144 : 00000000`00000001 000001dc`a634e801 000001dd`22d8dac0 00000000`00000008 : Resolve!boost::archive::codecvt_null<wchar_t>::do_encoding+0x5fde54
0000009e`bf8fa150 00007ff6`98f83e1f : 000001dd`226a4c00 0000009e`00000008 00000000`00000001 00000000`00000001 : Qt5Core!QObject::qt_static_metacall+0x1464
0000009e`bf8fa2a0 00007ffc`869c1144 : 000001dc`9e370000 00007ff6`0000000e 00000000`00000000 000001dc`c2e9aa58 : Resolve!boost::archive::codecvt_null<wchar_t>::do_encoding+0x3e58cf
0000009e`bf8fa300 00007ff6`99263b5d : 000001dd`217a8420 0000009e`0000000b 00000000`ffffffff 00007ff6`99264601 : Qt5Core!QObject::qt_static_metacall+0x1464
0000009e`bf8fa450 00007ff6`9929ffce : 00000000`00000001 00000000`00000063 00000000`00000000 00007ffc`85d443b7 : Resolve!boost::archive::codecvt_null<wchar_t>::do_encoding+0x6c560d
0000009e`bf8fa4b0 00007ffc`857c81b3 : 000001dd`217a8420 000001dd`217a8420 0000009e`bf8fa550 00007ffc`65edf4d3 : Resolve!boost::archive::codecvt_null<wchar_t>::do_encoding+0x701a7e
0000009e`bf8fa4e0 00007ffc`858720e0 : 000001dd`217a8420 000001dd`217a8420 000001dd`217a8420 0000009e`bf8fa880 : Qt5Widgets!QWidget::event+0x153
0000009e`bf8fa570 00007ffc`857a5433 : 000001dc`a5028eb0 0000009e`bf8fa880 0000009e`bf8fa880 000001dd`217a8420 : Qt5Widgets!QFrame::event+0x30
0000009e`bf8fa5a0 00007ffc`857a3a69 : 000001dd`217a8420 0000009e`bf8fa6d0 000001dc`bd16afb0 00000014`00000000 : Qt5Widgets!QApplicationPrivate::notify_helper+0x123
0000009e`bf8fa5d0 00007ff6`98b7c97a : 00000000`00000000 000001dd`228d0070 ffffffff`ffffffff 000001dd`228d0070 : Qt5Widgets!QApplication::notify+0xe59
0000009e`bf8fab40 00007ffc`869a1dcb : 00000000`00000000 00000000`00000000 0000009e`bf8fb2b0 000001dd`217a8420 : Resolve!boost::serialization::singleton<boost::serialization::extended_type_info_typeid<FaceAnalysisParams> >::singleton<boost::serialization::extended_type_info_typeid<FaceAnalysisParams> >+0x1cc3a
0000009e`bf8fb0f0 00007ffc`857f2455 : 00000000`00000000 0000009e`bf8fbf70 00000000`00000000 0000009e`bf8fbf70 : Qt5Core!QCoreApplication::notifyInternal2+0xbb
0000009e`bf8fb160 00007ffc`857ef6c2 : 000001dc`a5028eb0 0000009e`bf8fbf70 00000583`00000167 00000008`00000044 : Qt5Widgets!QSizePolicy::QSizePolicy+0x39c5
0000009e`bf8fb2a0 00007ffc`857a5433 : 000001dc`a5028eb0 000001dc`a5028eb0 0000009e`bf8fbf70 0000009e`bf8fbf70 : Qt5Widgets!QSizePolicy::QSizePolicy+0xc32
0000009e`bf8fb330 00007ffc`857a4568 : 000001dc`a5028eb0 0000009e`bf8fb460 000001dc`bd16afb0 0000009e`bf8fb458 : Qt5Widgets!QApplicationPrivate::notify_helper+0x123
0000009e`bf8fb360 00007ff6`98b7c97a : 40767000`00000000 000001dc`a634e8f0 00000000`00000000 000001dc`a634e8f0 : Qt5Widgets!QApplication::notify+0x1958
0000009e`bf8fb8d0 00007ffc`869a1dcb : 000001dd`471d1530 00000000`00000038 0000009e`bf8fbf28 000001dd`204baa30 : Resolve!boost::serialization::singleton<boost::serialization::extended_type_info_typeid<FaceAnalysisParams> >::singleton<boost::serialization::extended_type_info_typeid<FaceAnalysisParams> >+0x1cc3a
0000009e`bf8fbe80 00007ffc`85d5a6eb : 000001dd`471d1530 00000000`00000001 000001dd`471d1530 00000000`00030000 : Qt5Core!QCoreApplication::notifyInternal2+0xbb
0000009e`bf8fbef0 00007ffc`85d42562 : 00007ffc`86396228 00000000`00000024 00000000`00000024 000001dd`4450d6d0 : Qt5Gui!QGuiApplicationPrivate::processWheelEvent+0x1ab
0000009e`bf8fc020 00007ffc`869eaf9a : 00000000`00000000 00007ffc`86396228 0000009e`bf8fc150 000001dd`4450d6d0 : Qt5Gui!QWindowSystemInterface::sendWindowSystemEvents+0x92
0000009e`bf8fc050 00007ffc`65f30919 : 000001dc`c5fc06a0 00000000`00000000 000001dd`4450d6d0 00000000`00000000 : Qt5Core!QEventDispatcherWin32::processEvents+0x6a
0000009e`bf8ff170 00007ffc`8699e24f : 00000000`00000000 00007ffc`00000014 00000000`00000990 00000000`00000066 : qwindows!qt_plugin_query_metadata+0x2059
0000009e`bf8ff1a0 00007ffc`869a0d95 : 000001dc`a5f177a8 00000000`00000000 0000009e`bf8ff360 00007ffc`86ac1c70 : Qt5Core!QEventLoop::exec+0x1bf
0000009e`bf8ff200 00007ff6`98b44f95 : 0000009e`bf8ff358 000001dc`fb124a10 0000009e`bf8ff360 00000000`00000001 : Qt5Core!QCoreApplication::exec+0x155
0000009e`bf8ff260 00007ff6`98b42c05 : 0000009e`bf8ff610 00000000`00000001 000001dc`a7630070 00000000`0000000a : Resolve!std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::~unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >+0x17b45
0000009e`bf8ff510 00007ff6`98b21ab5 : 00000000`00003134 00000000`00000064 00000000`00003134 000001dc`a8dc75c0 : Resolve!std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::~unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >+0x157b5
0000009e`bf8ff640 00007ff6`98b1dd50 : 00007ff6`9fc9bb00 00007ff6`98b1ddc9 000001dc`a2c542c0 00000000`00000000 : Resolve!LibRaw_abstract_datastream::lock+0x3605
0000009e`bf8ff760 00007ffd`423c53e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Resolve!LibRaw_buffer_datastream::tell+0x58140
0000009e`bf8ff7a0 00007ffd`4452485b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
0000009e`bf8ff7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b


STACK_COMMAND: ~0s; .ecxr ; kb

FAILED_INSTRUCTION_ADDRESS:
Resolve!boost::serialization::singleton_module::unlock+1be88
00007ff6`9b28d778 c5e0c2150f17fe030d vcmpgeps xmm2,xmm3,xmmword ptr [Resolve!LibRaw::subtract+0x1641690 (00007ff6`9f26ee90)]

SYMBOL_NAME: Resolve+1be88
MODULE_NAME: Resolve
IMAGE_NAME: Resolve.exe
FAILURE_BUCKET_ID: ILLEGAL_INSTRUCTION_c000001d_Resolve.exe!Unknown
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 19.0.0.50
FAILURE_ID_HASH: {6533bd2e-d063-e536-097e-57821d6c0d12}


Hope this can help.

[Peter Chamberlain]

That info is of no value. We would only look at the NFO and the full Resolve generated logs, as per the FAQs.

I am experiencing the same issue with the micro panel but also when using the mouse.

That info is of no value. We would only look at the NFO and the full Resolve generated logs, as per the FAQs.

Crash dumps should have been automatically sent to Blackmagic, if that feature actually works. As for the logs, I'm sorry but since I need to be able to use my 27000$ panel I've already rolled back to a previous version of Resolve with less bugs. I'm sure the issue will be fixed in the final release.

Hi, i have the same problem with the gamma slider in the color page. All other sliders are working well. This problem the problem has existed since 19 beta4. I am already in contact with the support. Second issue is the graphics performance on my geforce 3060. It is much worse than 19beta3 or beta4.

Kind regards

If you encountered a crash, create a Diagnostics Log by going under the Help menu, choosing Create Diagnostics Log on Desktop, then uploading that file to a download site like Dropbox. Then post that link with your message here on the BMD Forum. Don't post the text of the log -- link to the actual Zip file.

Hi Marc, i posted the link already to the BMD support. A colleague of you from UK is already involved.
Thank´s a lot
Ralf

Hi,
the support couldn´t solve the problem. They say it's my computer's fault.
I've been working with this configuration since Resolve 16 and everything worked perfectly until 19 beta 4. Now I'll continue working with the 19 beta 3. It's running perfectly. and I'm waiting for the bugfix in beta 6.
Ralf

Hi,
the support couldn´t solve the problem. They say it's my computer's fault.
I've been working with this configuration since Resolve 16 and everything worked perfectly until 19 beta 4. Now I'll continue working with the 19 beta 3. It's running perfectly. and I'm waiting for the bugfix in beta 6.
Ralf

Hello,

what CPU (not GPU) are you using?

I am not having this issue with the advanced panel (2) and 19 beta 5. I’m on Linux.

I´m using an X5650 with win 10 pro 22H2. So it must be a bug on windows.

[Peter Chamberlain]

Hi guys, we can't repo this so we need resolve generated diagnostic logs and for windows users the NFO as per the FAQs above.

I´m using an X5650 with win 10 pro 22H2. So it must be a bug on windows.

No, the issue is that apparently Resolve is calling vcmpgeps (compare greater equal packed single), which is an AVX/AVX2 instruction, on non-AVX cpus. Hence the crash for illegal instruction calling.

FAILED_INSTRUCTION_ADDRESS:
Resolve!boost::serialization::singleton_module::unlock+1be88
00007ff6`9b28d778 c5e0c2150f17fe030d vcmpgeps xmm2,xmm3,xmmword ptr [Resolve!LibRaw::subtract+0x1641690 (00007ff6`9f26ee90)]

And why this happens only with the gamma slider? Al other sliders (gain, lift and offset) are working.
The numeric input fields of the gamma section are working well, too. I Think, the query of the mouse pointer position for the gamma slider is incorrect and runs into a crash.
I sent my reports already to
Ro Stubbs
Post Production Support Specialist
Blackmagic Design EMEA
in his opinion my Resolve installation is incorrect. I´m working with this installation since REV 16 without any problems. The last running REV 19 on my system is beta 3, and I switched back to it and I´m waiting now for the beta 6.


kind regards
Ralf

And why this happens only with the gamma slider? Al other sliders (gain, lift and offset) are working. The numeric input fields of the gamma section are working well, too. I Think, the query of the mouse pointer position for the gamma slider is incorrect and runs into a crash.

Just checked in 19b5 on our main system -- 2019 Mac Pro running Sonoma 14.5, Advanced Panel 2 -- and no problems with any ring. Checked Log, LGG, HDR, Offset, everything.

I was momentarily taken aback because Offset defaulted to Curves, but I was able to get back to Global Offset and all was fine. "So far."

[Peter Chamberlain]

I believe we have narrowed this down to older CPUs that don’t support the AVX/AVX2 instruction set. These may only be pentium and celeron CPU’s.

If you have a CPU that’s less than 7 years old showing this please post details.

I believe we have narrowed this down to older CPUs that don’t support the AVX/AVX2 instruction set. These may only be pentium and celeron CPU’s.

Xeon 56xx (Westmere-EP), used in dual cpu workstations, don't support AVX.

Adobe ran into the same issue with Photoshop and they fixed it first in the beta version, then in the current stable one.

I think this is my issue: I have dual Xeons.

@Dave Edwards
Do you have the same issue on your Xeons that the final DaVinci Resolve 19 has a decreased frame rate in the EDIT page. My footage is playing with 50 fps in the CUT page and in the COLOR page, but in the EDIT page only with 30 fps and very jerky.
Kind regards
Ralf

Hi: apologies for the delay,- I've only just seen your post. I'm afraid I'm unable to replicate your issue on my system.

Hi,

I have the same problem. Using the Gamma wheel seems to make Resolve crash, regardless of the footage used. I tried dng sequences, jpg, cr2, regardless, it crashes always. Gain, Lift etc work fine.


I'm using an older CPU Intel i7 -see attachment, 36G RAM, NVIDIA Geforce 3060 12G VRAM Windows 10 22H2 Build 19045.4780

I believe we have narrowed this down to older CPUs that don’t support the AVX/AVX2 instruction set. These may only be pentium and celeron CPU’s.

If you have a CPU that’s less than 7 years old showing this please post details.

After reading this I suspect it might be the same problem.

I'm a DaVinci Resolve Studio user. I have upgraded to version 19.0.1 but the bug is still there.

Any progress on that bug?

Your software developers could check if the processor supports that set of instructions at runtime
or make it a global setting somewhere in the settings so we can choose "old processor" or "not AVX/AVX2 compatible" and still be able to use the software.

Thank you in advance. Please let me know if I can help you further with more informations.

Does Blackmagic plan to continue supporting CPUs without AVX/AVX2 like Xeon 5650 or older I7 CPUs or do we have to purchase new hardware for Resolve 19. Everything was fine until 19 beta 3.

new Studio user here

upgraded from 18 free to Studio 19 and Resolve crashes as soon as i touch the gamma wheel

everything was so much faster and smoother (compared to free version) until then but this gamma wheel issue is a bit of a show stopper

do i go back to 18 or is there a fix?

CPU is i7990x so likely issue is lack of AVX/AVX2

RTX 4070

Hi,
same problem here: Resolve (Studio 19.0.3 Build 5) constantly crashes when using the gamma-slider.
All other sliders work fine, and click and drag in the number-field for gamma works too.
My machine has two Xeon 5675,
Windows 10,
Quadro RTX 4000

Kind regards,
Greg

[VivekVedagiri]

Hi,

Could you please try Resolve 19.1 (released today) and see if it helps address the crashing?

Regards,
Vivek

Hi,

it's works fine now with 19.1 using micro color panel.

Intel Core I7 960 without AVX/AVX2.

Reagrds,
Laurent

Great: now working with Mini Panel on Dual Xeon, thank you.

Thanks a lot, it works

new Studio user here

upgraded from 18 free to Studio 19 and Resolve crashes as soon as i touch the gamma wheel

everything was so much faster and smoother (compared to free version) until then but this gamma wheel issue is a bit of a show stopper

do i go back to 18 or is there a fix?

CPU is i7990x so likely issue is lack of AVX/AVX2

RTX 4070

working for me now - thank you

The gamma wheel on color page of Resolve 19.1 is working now correctly on my Xeon 5650
Thank you
Ralf