Emulator: Process finished with exit code -1073741819 (0xC0000005)


I'm using android studio 3.0.1, when I start my emulator I get many error messages, I've tried to solve each problem separately, I also searched a lot but nothing works for me.

12:24 م Emulator: init: Could not find wglGetExtensionsStringARB!

12:24 م Emulator: OpenGL backend 'angle' without OpenGL ES 1.x library 
detected. Using GLESv2 only.

12:24 م Emulator: Failed to eglInitialize

12:24 م Emulator: Could not initialize emulated framebuffer

12:24 م Emulator: Warning: requested RAM 1024M too high for your system. 
Reducing to maximum supported size 512M

12:25 م Emulator: emulator: ERROR: Could not initialize OpenglES emulation, 
use '-gpu off' to disable it.

12:25 م Emulator: Process finished with exit code -1073741819 (0xC0000005)

I also tried this

asked on Stack Overflow Dec 4, 2017 by Sufian Awad • edited Dec 4, 2017 by BDL

4 Answers


Make sure your graphics driver is updated

  1. Go to tools
  2. Go to Android
  3. Select AVD Manager.

enter image description here

  1. click on the pencil icon in under Action
  2. Click Advanced Settings button.
  3. In Emulated Performance row change Graphics to Software GLES 2.0
  4. In Memory, row change RAM field to 512(minimum).

enter image description here

answered on Stack Overflow Dec 4, 2017 by Arslan Ahmad • edited Mar 16, 2018 by Asif Raza

I modified the avd config file and solved a similar problem.

  1. find your avd folder.(If your using Windows OS, the default path is C:\Users\USER_NAME\ .android\avd\YOUR_VIRTUAL_DEVICE_NAME.avd)
  2. open the file config.ini
  3. find hw.gpu.mode and set it to off (hw.gpu.mode=off)
  4. launch the AVD manager
  5. launch your virtual device.
answered on Stack Overflow Aug 8, 2018 by David • edited Aug 8, 2018 by Lescurel

check in your emulator setting Use Host GPU enabled shown in below image

enter image description here

this will you get Android Studio -> Tools -> Android -> AVD Manager here

answered on Stack Overflow Dec 4, 2017 by OmiK

I faced the same problem. In my case, running Android Studio as an administrator solved the problem.

answered on Stack Overflow Sep 14, 2018 by Dmitro25

User contributions licensed under CC BY-SA 3.0