Kernel update 4.12.14-lp150.12.45.1-x86_64 stops machine booting

After installing update patch openSUSE-2019-65 via Software Updates Applet on KDE my machine no longer boots. After starting the machine the initial loading screen is displayed on boot which says:

Booting ‘openSUSE Leap 15.0’

Loading Linux 4.12.14-lp150.12.45-default …
Loading initial ramdisk …

and then the screen goes blank with a cursor in the top left hand corner.

I have traced the issue down to the kernel-default package version 4.12.14-lp150.12.45.1-x86_64 from openSUSE-Leap-15.0-Update repository.
The previous available version works correctly i.e. 4.12.14-lp150.12.28.1-x86_64.

I have also tried installing Linux Mint on the machine and applied all updates to it and the machine continues to boot correctly. This results in the kernel being version 4.15.0-43-generic.

I am hoping this suggests that eventually the openSUSE kernel will get upgraded to a point where the fault goes away again but in the meantime is there a way to stop the kernel-defaults package from getting upgraded any further by the Software Updates Applet? I would like it to stop reminding me about update patch openSUSE-2019-65 and any other subsequent updates that involve upgrading the kernel-defaults package.

The machine is a desktop with no Wireless or Bluetooth cards. Other information (on the working version of the kernel):
Processor: AMD Ryzen 5 1600
Graphics: AMD Radeon RX560
KDE Plasma Version: 5.12.6
Kernel Version: 4.12.14-lp150.12.28-default

You can lock the kernel from being updated. However, to be honest, I’m not sure if that works for kernel updates.

Use Yast Software Manager. Search for “kernel-default” (or whatever). Right click on that line. Select “Protected - do not modify”.

I suggest that you file a bug report

openSUSE:Submitting bug reports

The kernel team won’t know about your problem unless you report it.

One other suggestion. As root, edit “/etc/zypp/zypp.conf”. Look for the “multiversion.kernels” line and add “oldest” to the list of what to keep. That’s to make sure that you keep a working kernel around that you can boot to.

Thanks for the suggestions which I have made.
I have also filed a bug report: