Windows 98 SE Protection Error Suddenly

[Giapo]

Hi everyone, I need help.
I write this new post after another one, in which I had initially problems with all the Windows-like VMs since the last Windows 10 20H2 Update, and then I found out that for some unreasonable reason there was the Hyper-V activated (also if it was even checked into the Windows Functionalities)... By the way, this didn't resolve everything, and this new post is for one of the VMs which is still having problems.
I have a VM with Windows 98 SE, and it always worked fine.
Now, if I try to open it, it can't start Normally, it manages to only in the Safe modes. If I try to start Windows 98 Normally, it shows the message "Windows Protection Error. You need to restart the Computer."
I tried also to patch Windows 98 with the Windows 95 Fast Processors Hotfix, that someone linked me in the first post about all the Windows-like VMs; but, assuming that I was skeptical about it because it always worked until the last Windows 10 update, I couldn't install it because is not compatible with Windows 98.
I attach a Vbox.log file to help everyone to understand where's the problem and how can I resolve it.
Someone can help me, please?
I thank for every answer, hoping to get some as soon as possible.
Bye ^_^

[mpack]

I'm afraid that I see no VM error recorded in the log, so it would seem that the problem is in the guest OS, not in VirtualBox.

My own Win98SE VM continues to work normally in VirtualBox 6.1.16, so this is not a universal problem.

Since the VM starts in safe mode I believe that indicates that the problem is in a device driver, and since there are no GAs it can't be a VirtualBox supplied driver. My guess would be audio or graphics. For graphics I've always used the BearWindows Universal VESA driver. Speaking of graphics, I see that you have graphics RAM set to 128MB, which seems excessive for a Win98 era PC - the PC itself usually had less RAM than that, and it's not like you have 3D acceleration available and eating RAM. My own VM is only using 20MB.

ISTR that Win98 safe mode allowed you to single step through the driver loads to find the one that crashed. That would be a handy feature about now.

[Giapo]

I'm afraid that I see no VM error recorded in the log, so it would seem that the problem is in the guest OS, not in VirtualBox.

My own Win98SE VM continues to work normally in VirtualBox 6.1.16, so this is not a universal problem.

Since the VM starts in safe mode I believe that indicates that the problem is in a device driver, and since there are no GAs it can't be a VirtualBox supplied driver. My guess would be audio or graphics. For graphics I've always used the BearWindows Universal VESA driver. Speaking of graphics, I see that you have graphics RAM set to 128MB, which seems excessive for a Win98 era PC - the PC itself usually had less RAM than that, and it's not like you have 3D acceleration available and eating RAM. My own VM is only using 20MB.

ISTR that Win98 safe mode allowed you to single step through the driver loads to find the one that crashed. That would be a handy feature about now.

I have the SciTech Doctor Video Driver as Graphic Driver in Windows 98SE and it always had 128MB of Graphic RAM, but it always worked. Anyway, I tried the single step boot and after loading the drivers it goes on Protection Error, the last driver it loads is the mouse driver (which it always worked too); and also denying this last one loading still goes on Protection Error.
Finally, I also gave to Graphic RAM only 64MB, but nothing changed.
It seems a very strange problem...