Intel HAXM causes BSOD in Windows 8.1

[sav_s_]

This is easily repoducible. Pl fix this ASAP. 

http://answers.microsoft.com/en-us/windows/forum/windows8_1_pr-system/criticalstructurecorruption-windows-81/42b145c2-20f2-4a50-b4d2-dea455b390f8

[Vincent_P_1]

For those who don't know this product : http://www.genymotion.com/

is a very good alternative until Intel release a patch for HAXM. Very fast Android emulator

[Alexander_W_Intel]

Great news: The hotfix is available for download! Please go to http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager/ . There is a hotfix for Microsoft Windows* 8.1 and for OS X 10.9. 
Let us know if the hotfix is working for you. 

Thanks all for helping us resolving this issue!
Alex 

[Vincent_P_1]

thank you Alex.

[MySKY_O_]

Thanks Alex... however, after update, the Emulator is unable to start with "use host GPU" checked. The Emulator will just load with black screen...

Just tried to uncheck "use host GPU",  the emulator loaded very fast... However, without using host GPU, inside emulator look very laggy and not smooth at all....  

Hope some updates coming soon.. Thanks.

[Andres_C_]

It does seem to work with host GPU for me tho. Might be specific.

MySKY O. wrote:

Thanks Alex... however, after update, the Emulator is unable to start with "use host GPU" checked. The Emulator will just load with black screen...

Just tried to uncheck "use host GPU",  the emulator loaded very fast... However, without using host GPU, inside emulator look very laggy and not smooth at all....  

Hope some updates coming soon.. Thanks.

[A_Hindam]

The fix is working so far - No crach.  Thanks Alex

[MySKY_O_]

Hi all.. just uninstall and reinstall it.. now its working ..... 

Thanks all for the effort..     :)

Andres C. wrote:

It does seem to work with host GPU for me tho. Might be specific.

Quote:

MySKY O.wrote:

Thanks Alex... however, after update, the Emulator is unable to start with "use host GPU" checked. The Emulator will just load with black screen...

Just tried to uncheck "use host GPU",  the emulator loaded very fast... However, without using host GPU, inside emulator look very laggy and not smooth at all....  

Hope some updates coming soon.. Thanks.

[Matteo_A_]

So far it's working fo me, also with GPU host emulation. I will wait some days to judge if it's completely fixed, but I trust Intel engineneers.

Thank you.

[Andrew_A_2]

I installed the hotfix from  http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager/ . 

Then I tried to uninstall an app from emulator working with Intel Atom(x86) CPU selected, and Win 8.1 x64 crashed with the same error CRITICAL_STRUCTURE_CORRUPTION

[Bernard]

Does the crash occure during the uninstall?

[Kenji_K_]

In my first attempt went wrong but I made a mistake and now it is working fine. What I did wrong was that I thought the fix was a patch for the current driver when in fact the fix is the fixed driver itself. Removed the HAXM and installed only the fix and it worked. No crash so far.

[Stephen_C_]

I had this issue as well, same error message whenever my computer would crash every 15-20 minutes following me installing Windows 8.1. I read a ton of forums and one person said that uninstalling the program MacDrive worked for them. I know not everybody has this program, but I did, and I don't know how it causes the problem...but uninstalling it stopped the crashing. I'm going onto my second hour without any crashing.

Also, as a random additional bit of information...when MacDrive was installed Call of Duty: Ghosts would stutter a lot and be unplayable. I thought it was just a buggy game...but when I uninstalled MacDrive the game runs normally at high settings. I don't know if you all have MacDrive, or how it is causing these problems. But uninstalling it definitely helped. I had spoken with HP Tech Support and they were telling me to restore my computer to factory settings (Windows 8), which would've led to days of me reinstalling all of my software...thank God I didn't have to do that.

Anyway, hope this works for those of you who have MacDrive on your computers. For those of you who don't, good luck.

[Bernard]

What is MacDrive?

[Ben_Y_1]

iliyapolak wrote:

What is MacDrive?

MacDrive is a Windows software application where you can open, save, and transfer files on a Mac disk or drive.

http://www.mediafour.com/products/macdrive

[Bernard]

Thanks @Ben for explaining.

@Stephen C

If you have still BSOD of MacDrive(kernel dump file) would you upload it?I am really interesting in investigation of that crash.

Thanks in advance.

[Laurent_G_]

@Alexander The link to the fix download is dead. Is it possible to fix this or is there another link we should use?

[Bill_T_]

I was seeing this blue screen also and just came across this thread.  I installed the latest patch pointed to above, and within an hour still hit another blue screen.  Analysis from WinDbg below, which quite clearly points to the HAXM driver.  I'm running Windows 8.1 x64 on a MacBook Air.

Please let me know how I can help you get to the bottom of this issue.  This is quite impactful.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
 
FAULTING_IP: 
IntelHaxm+c3df
fffff800`0340c3df f30fc775f8      vmxon   qword ptr [rbp-8]
 
CONTEXT:  ffffd00039e8cc80 -- (.cxr 0xffffd00039e8cc80)
rax=0000000000000000 rbx=0000000000000000 rcx=000000026f527000
rdx=ffffd00039e8d770 rsi=ffffe000004a6010 rdi=ffffe000005f0310
rip=fffff8000340c3df rsp=ffffd00039e8d6b8 rbp=ffffd00039e8d6c0
 r8=ffffd00039e8d778  r9=7fffe000005f3750 r10=ffffe000005f3750
r11=7ffffffffffffffc r12=ffffe000004a6010 r13=ffffd00039e8d770
r14=ffffffffffffffff r15=0000000000000002
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
IntelHaxm+0xc3df:
fffff800`0340c3df f30fc775f8      vmxon   qword ptr [rbp-8] ss:0018:ffffd000`39e8d6b8=000000026f527000
Resetting default scope
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x3B
 
PROCESS_NAME:  emulator-x86.e
 
CURRENT_IRQL:  2
 
LAST_CONTROL_TRANSFER:  from 000000026f527000 to fffff8000340c3df
 
STACK_TEXT:  
ffffd000`39e8d6b8 00000002`6f527000 : 00000000`00000001 fffff800`0340994d 00007ffd`00000002 ffffe000`00000001 : IntelHaxm+0xc3df
ffffd000`39e8d6c0 00000000`00000001 : fffff800`0340994d 00007ffd`00000002 ffffe000`00000001 00000000`00000000 : 0x00000002`6f527000
ffffd000`39e8d6c8 fffff800`0340994d : 00007ffd`00000002 ffffe000`00000001 00000000`00000000 00000000`00000001 : 0x1
ffffd000`39e8d6d0 fffff800`034091ab : ffffe000`004a6010 ffffe000`004a6010 ffffd000`3f63f000 ffffe000`004a6010 : IntelHaxm+0x994d
ffffd000`39e8d720 fffff800`0340444a : fffff800`0340dc01 ffffe000`004a6010 ffffe000`004a6010 7fffe000`005f3750 : IntelHaxm+0x91ab
ffffd000`39e8d770 fffff800`03401607 : 00000000`00000000 ffffe000`0e67e9b0 ffffe000`0e67e9b0 00000000`00000000 : IntelHaxm+0x444a
ffffd000`39e8d7b0 fffff800`03401b4f : ffffe000`0e67e8e0 00000000`40002418 ffffe000`028f97d0 ffffd000`39e8db80 : IntelHaxm+0x1607
ffffd000`39e8d840 fffff800`6b7cf395 : ffffe000`0e67e8e0 ffffd000`39e8db80 ffffe000`028f97d0 fffff800`6b6f6180 : IntelHaxm+0x1b4f
ffffd000`39e8d870 fffff800`6b7cfd2a : 00000000`0028e4bc 00000000`0008fdb0 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x845 
ffffd000`39e8da20 fffff800`6b5608b3 : 00000000`00000001 ffffd000`39e8db80 00000000`00000000 fffff800`6b7b730e : nt!NtDeviceIoControlFile+0x56 
ffffd000`39e8da90 00000000`77ad2772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 
00000000`0008ee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad2772
 
 
FOLLOWUP_IP: 
IntelHaxm+c3df
fffff800`0340c3df f30fc775f8      vmxon   qword ptr [rbp-8]
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  IntelHaxm+c3df
 
MODULE_NAME: IntelHaxm
 
IMAGE_NAME:  IntelHaxm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  52784488
 
STACK_COMMAND:  .cxr 0xffffd00039e8cc80 ; kb
 
FAILURE_BUCKET_ID:  0x3B_IntelHaxm+c3df
 
BUCKET_ID:  0x3B_IntelHaxm+c3df
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x3b_intelhaxm+c3df
 
FAILURE_ID_HASH:  {7ce3553e-56e5-47fb-c62f-3ac19ef94b86}
 

[Bernard]

@Bill

Please provide full kernel dump.

Btw, I cannot see register context in your post.I am interesting in rbp-8 content.

[Bernard]

I can see register rbp-8 content and I suppose that argument probably located at rbp-8 caused access violation error.I think that vmxon is dereferencing a bad pointer to VMCS structure.

[Bernard]

Any response from Intel engineers?

[Joshua_B_Intel]

Bill-

We have an updated version of HAXM coming very soon (this week, hopefully). I'd like to have you try it and see if you're still experiencing this crash. I can provide it to you under an engineering license (where you basically promise not to redistribute it). If you're interested, please send me a Private Message with an email address that can receive attachments (~3mb in size). Thanks!