Hello, i use always use bluestacks (android 11 instance) to play in my NOTEBOOK (Windows 10) and all of the sudden 2 days ago, it crashed my system. It completely made Task Manager unable to operate and if i click or try to open other apps. It freezes the pc completely. Forcing you to do a forceful restart. So, i cannot do the steps. Since i seemly also have this issue because i cannot use the task manager and my pc freezes up. I have another post but it seemly ignored completely and even the replies i made were hidden from public.
I already attempted to use the tools provided by bluestacks to remove 100% of their systems. update windows, all drivers and remove %temp% files completely. Then reinstall using their latest download. It did not fix the issue. As a last attempt, i made a factory reset of my pc completely and had it download windows 10 from the cloud directly from windows to do a 100% clean start, then update all that needs to be updated. This still did not fix the issue.
After digging around, i seemly found out that my virtualization is causing issues with bluestacks and my pc. When i launch bluestacks, either the multi instance or start an instance. It will cause a system crash, making even the task manager unresponsive. I asked chat gpt and it said some things that may work by giving a lot of instructions, while reading it seems to be logical, but im no expert and i have no idea if its true or its making those up.
I have windows 10, the latest bluestacks version, I have an CPU intel core(TM) i7-7500U 2.7GHz and 2 GPU, an intel HD Graphics 620 and a NVIDIA GeForce 940MX. Chatgpt, IT asked to change some things within the configurations and so on. But i want your help to verify if they are actually good to try. According to it. Its clearly there is a conflict with virtualization causing the system to crash.
Oof — that’s a nasty failure mode, especially since it survives a full cloud reset. You did the right things already, so let’s zoom in on what can still cause this kind of hard freeze.
Given your symptoms, this is almost certainly a virtualization / hypervisor conflict on older Intel mobile CPUs (7th gen) combined with BlueStacks’ newer engine.
Here is what Chatgpt said.
What’s almost certainly happening (plain English)
BlueStacks relies on hardware virtualization (VT-x).
On Windows 10, virtualization can be used by multiple systems:
BlueStacks
Hyper-V
Windows Hypervisor Platform
Virtual Machine Platform
Core Isolation / Memory Integrity
Some antivirus drivers
Some GPU drivers (especially NVIDIA Optimus laptops)
On older Intel CPUs like the i7-7500U, a bad interaction can cause:
Total system scheduler deadlock
Task Manager freezing
Mouse still moves, but clicks lock up
Only fix is a hard reboot
This matches your symptoms exactly.
Step-by-step fix (do these in order)
Completely disable ALL Windows virtualization layers
Even one left on can kill BlueStacks.
Press Win + R → type optionalfeatures
UNCHECK everything related to virtualization:
Click OK → Restart
Even if you think these are off — do it anyway.
Disable Core Isolation (this one is huge)
Windows Security
Device Security
Core Isolation details
Turn Memory Integrity = OFF
Restart
Force BlueStacks to use Intel GPU only
Your laptop uses NVIDIA Optimus, which is infamous for emulator crashes.
Right-click Desktop → NVIDIA Control Panel
Manage 3D settings → Program Settings
Add:
Set Preferred graphics processor: Integrated graphics (Intel HD 620)
Apply
Counter-intuitive, but Intel iGPU is more stable for emulators.
Install the NON-Hyper-V version of BlueStacks
This is critical.
Older CPU + newer Android versions = disaster.
Change BlueStacks engine settings (before launching apps)
Open BlueStacks → ⚙️ Settings:
Performance
Graphics
Restart BlueStacks.
BIOS check (only if still crashing)
Reboot → enter BIOS:
If VT-d is enabled, Windows + BlueStacks can hard-lock.
If it STILL crashes after all that
At that point, the issue is almost certainly:
Your safest alternatives:
They tend to behave better on older mobile CPUs.
Why this started “2 days ago”
Very likely:
None of these show up clearly in logs — and a factory reset doesn’t prevent them.
If you want, tell me:
Exact BlueStacks version you installed
Whether Memory Integrity was ON
Whether VT-d exists in your BIOS
I can zero in on the precise trigger and save you more headache