Intel HAXM 1.0.6 crashing Windows 8.1

Intel Hardware Accelerated Execution Manager (HAXM) 1.0.6 is the last version that is delivered by Android SDK (check android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager\Release Notes.txt) but this one is causing BSODs with Windows 8.1. Intel has fixed the issue since, but you will have to install the old version and then download the new 1.0.7 version from Intel's website yourself.

Intel® Hardware Accelerated Execution Manager
http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager/

?

1 2 3 4 5 6 7 8 9

Intel(R) Hardware Accelerated Execution Manager (HAXM) with Intel(R) Virtualization Technology (VT) for faster Android* Emulation   Version 1.0.7 ---------------------------- Changelog ---------------------------- Hot fix for OS X Mavericks (10.9) and Windows 8.1

?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88

windbg> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************   CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code  or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel  debugger that was not attached when the system was booted. Normal breakpoints,  "bp", can only be set if the debugger is attached at boot time. Hardware  breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a01f58992ad4f7, Reserved Arg2: b3b72bdeebaad53e, Reserved Arg3: fffff800820b3000, Failure type dependent information Arg4: 0000000000000003, Type of corrupted region, can be  0 : A generic data region  1 : Modification of a function or .pdata  2 : A processor IDT  3 : A processor GDT  4 : Type 1 process list corruption  5 : Type 2 process list corruption  6 : Debug routine modification  7 : Critical MSR modification   Debugging Details: ------------------     DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump   CUSTOMER_CRASH_COUNT:  1   DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT   BUGCHECK_STR:  0x109   PROCESS_NAME:  System   CURRENT_IRQL:  2   ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre   LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8008055eca0   STACK_TEXT:  ffffd000`235d31c8 00000000`00000000 : 00000000`00000109 a3a01f58`992ad4f7 b3b72bde`ebaad53e fffff800`820b3000 : nt!KeBugCheckEx     STACK_COMMAND:  kb   FOLLOWUP_IP: nt+14dca0 fffff800`8055eca0 48894c2408      mov     qword ptr [rsp+8],rcx   SYMBOL_STACK_INDEX:  0   SYMBOL_NAME:  nt+14dca0   FOLLOWUP_NAME:  MachineOwner   MODULE_NAME: nt   IMAGE_NAME:  ntkrnlmp.exe   DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c   IMAGE_VERSION:  6.3.9600.16452   FAILURE_BUCKET_ID:  0x109_nt+14dca0   BUCKET_ID:  0x109_nt+14dca0   ANALYSIS_SOURCE:  KM   FAILURE_ID_HASH_STRING:  km:0x109_nt+14dca0   FAILURE_ID_HASH:  {8339dd0b-1f09-c6df-317e-b65c941183a4}   Followup: MachineOwner ---------