If this is the case, what you want to do is go ahead and raise the number of cores incrementally one at a time to see if the change resolves the issue. We wouldn’t recommend toying with the “CPU cores” setting unless the error persists. Move the slider up to the “Recommended memory” value just above if it isn’t already set by default. In a similar vein, under the “Engine” settings, check to see what the RAM allocation is set to in the “CPU and RAM allocation” section. Bluestacks will boot up and should load up without any issues.Click on the blue “Restart Now” button that appears below.A “Checking DirectX compatibility” message will show up briefly, followed by a message saying “Restart Bluestacks to boot in DirectX.”.

Under “Choose graphics mode” tick the “DirectX” option on the right rather than “OpenGL.”.

In the Settings window, click on “Engine” from the options running vertically down the left-hand of the screen.

Select “Settings” from the drop-down menu that appears.

Click on the cogwheel icon located in the top right corner next to the minimize and close buttons.

Ignore the “engine won’t start” error message. Here, we’re shifting from OpenGL to DirectX.

As a gaming emulator, Bluestacks is wholly reliant on the graphical output to do its thing, so when it isn’t behaving well, switching up the graphics mode can do wonders to inject new life. Here’s a quick and easy fix that works for most users.

Bluestacks 4 hyper v problem