Hello there,
I installed Blood Omen 2 today but during really short play I have encountered 3 freezes/crashes that made me to restart my laptop. I tried various compability settings, fixes shown in this forum, etc. but nothing seemed to have helped me so far :/ I had similiar problems with Soul Reaver 2 but the issue was not so severe. Surprisingly Soul Reaver 1, the oldest installment I have, worked perfectly on the same exact machine.

My specs are as follows:

Windows 10
Intel Core i5-8300H (4 cores, 2.3 GHz-4.0 GHz, 8MB cache)
RAM 8 GB (SO-DIMM DDR4, 2666MHz)
NVIDIA GeForce GTX 1050Ti
+ Intel UHD Graphics 630
SSD drive 480 GB

Please help :(

Does that include setting affinity to 1 core? Because it's the most likely cause of the problem.

How to do that correctly in PowerShell?

Why PowerShell?
The most convenient solution is a batch file. Admittedly, I did not have a chance to test it on Windows 10 yet, but the Windows 7 way is making a bo2.bat file in the game directory and putting the following line in:
start /affinity 1 /high bo2.exe

You can also change affinity in the task manager, but you would have to do it every time you start the game, and from my experience it does not always work if the game is not actually starting with one core.

I created that file but it didn't help much :/ The game froze again today in a cutscene :/

Just to make sure - you are running the game by executing that batch file, right?
You can Alt - Tab and check if the affinity is in fact changed.

Yep, I did run the game using the created file. Another freeze after 5-10 minutes, crap :/ At this rate this PC will need formatting after all these "brute" restarts :/
Perhaps I made this file wrong? Or running this file requires something more?

Here is the line I have written in the file:

start /affinity 1 /high bo2.exe

EDIT

Even setting processor affinity in the task manager did not help :/

No, that should be enough, but if after running the game with that file task manager still shows all cores ticked, then it means that it is not doing what it should (which would mean that MS has messed something up with Win 10 again).

I'll try to do some testing - but unfortunately this will have to wait until Friday.

So, I've run some tests on my Windows 10 machine.
I've actually run into menu slow-motion issue, so I may have to use dgVoodoo for further testing.
But, concerning the core affinity - the batch file works for me - it actually does set the cores properly, so I don't know why it doesn't work for you. Could you please confirm that the affinity is still set to all cores after running with that batch file (check in task manager)? If it actually is set to 1 core then your problem has a different cause and unfortunately I can't help you in this case.

If it is still running on all cores, then there may still be a solution, although a rather crude one. You can set your whole system to only use one core. Obviously, this will impact your PC's performance and should be reverted every time you are not playing the game.
To do this:
1) Go to search bar and type msconfig or system configuration - run it.
2) Go to boot menu and select advanced options.
3) Set number of processors to 1.
4) Restart.

Hello,
Late reply because I have not had much time recently due to my work.
The screenshot presents the core affinity after running the game using the batch file. As you can see, all cores are still set :| What the hell is wrong with my machine? :/

EDIT
OK, after some another settings it seems that the game is willing to cooperate, at least today. I have played for 1-2 hours i nothing wrong happened.
Sometimes I don't get this machine.
Thank you for all your help.

I have no idea why this does not work (as I noted, it does work for me). Good news is that the cause of the freezes is most likely the affinity. In the Windows XP days I used a little program called setaffinity. I'll see if it is still around and if it still works, but I'll be away from my PC until Saturday so I ask for a little patience.

A bit late, but a small update. StartAffinity is still up and working, at least for me. So it may be an alternative worth looking into.