does "Timed out after 300seconds" issue relate to this driver?

Hi there,

I tried many virtual device settings but all comes to the same ending: device wont start.

From task manager, I can see ``qemu-system-i386.exe`` runs with ``T:\Tools\Android\sdk\emulator\qemu\windows-x86_64\qemu-system-i386.exe -netdelay none -netspeed full -no-snapstorage -avd 00_durmaz_profili_API_23``

qemu uses about 25% CPU during all that time but but there is nothing coming up. Then it simply says it fails to start after 300s.

I tried Android M and R images with both x86 and x64 and with/out Google APIs, and different device profiles . All resulted same. I tried to use an ARM image. It gave me at least the starting android logo but then just stuck to continue.

So, is this a virtualization problem caused by this driver? or else where do you think should I go then?

below are my system values.
- CPU: AMD Phenom II X4 940 3GHz
- GPU: AMD Radeon R9 280 3GB
- RAM: 8GB

``emulator-check.exe`` gives following results. It also says "Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release." but I take it using Cold Boot should work.
- accel: GVM (version 1.6) is installed and usable.
- cpu-info: AMD CPU|Virtualization is supported|64-bit CPU|
- window-mgr: Windows
- desktop-env: Windows
- hyper-v: Hyper-V is not installed