Brand New Machine from OEM, Install of Virtual PC and XP Mode Causes BSOD on Launch


  • Machine:

    Dell Inspiron 5558

    Intel Core i3-4005U 1.70 GHZ

    RAM: 4.0 GB

    OS: Win 7 SP 1 with updates.

    Problem: A fresh install of Virtual PC and XP Mode crash the system with a BSOD.

    I have run sfc /scannow, and the windows installer repair tool after uninstalling the software. I reinstalled and same result.


    WinDBG Result:

    Question: What can I do to fix this? Can vpcvmm.sys be fixed without a wipe? Is it potentially driver issues?

    Sunday, January 31, 2016 9:18 PM


  • Hi,

    We have analyze your dump file. The driver called "vpcvmm.sys" is a file for Windows Virtual.

    Loading Dump File [C:\Users\v-tiancl\Desktop\013116-30903-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\mysymbol*
    Symbol search path is: SRV*c:\mysymbol*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
    Machine Name:
    Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`0325e730
    Debug session time: Mon Feb  1 04:31:03.228 2016 (UTC + 8:00)
    System Uptime: 0 days 0:24:38.750
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {0, 2, 8, 0}
    Probably caused by : vpcvmm.sys ( vpcvmm!VmmExecuteVp+432 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c8100
    GetUlongFromAddress: unable to read from fffff800032c81c0
     0000000000000000 Nonpaged pool
    00000000`00000000 ??              ???
    PROCESS_NAME:  vpc.exe
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    TRAP_FRAME:  fffff8800b575640 -- (.trap 0xfffff8800b575640)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88004583000 rbx=0000000000000000 rcx=fffff8800ca00000
    rdx=fffff8800c510000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=fffff8800b5757d8 rbp=fffff8800b575b00
     r8=0000000012233204  r9=ffffffffffffffff r10=0000000000000001
    r11=0000000000100080 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    00000000`00000000 ??              ???
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8000308ae69 to fffff8000308b8c0
    00000000`00000000 ??              ???
    fffff880`0b5757d8 fffff880`0458e40a : fffffa80`047928b0 fffff880`00000000 ffffffff`ffffffff fffff880`0c510000 : 0x0
    fffff880`0b5757e0 fffff880`04591ebd : fffff880`04af5000 00000000`00000000 00000000`00000000 fffff880`0ca00000 : vpcvmm!VmmExecuteVp+0x432
    fffff880`0b575870 fffff880`04583dae : 00000000`00001f80 fffffa80`03ca0510 00000000`03eaf4b0 fffff880`0b575b60 : vpcvmm!DispatchFastControlVirtualProcessor+0x41
    fffff880`0b5758a0 fffff800`033a6bb3 : fffffa80`03ca0500 fffffa80`00000000 fffffa80`036e7de0 fffffa80`0d161801 : vpcvmm!VmmFastDeviceControl+0x12
    fffff880`0b5758d0 fffff800`033a76a6 : fffff680`007fe3e8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
    fffff880`0b575a00 fffff800`0308ab53 : fffffa80`0cd82060 0000007f`ffffffff fffff880`0b575a88 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
    fffff880`0b575a70 00000000`77a5dc2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03eaf458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a5dc2a
    STACK_COMMAND:  .trap 0xfffff8800b575640 ; kb
    fffff880`0458e40a 488b0dc7690300  mov     rcx,qword ptr [vpcvmm!WPP_GLOBAL_Control (fffff880`045c4dd8)]
    SYMBOL_NAME:  vpcvmm!VmmExecuteVp+432
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: vpcvmm
    IMAGE_NAME:  vpcvmm.sys
    IMAGE_VERSION:  6.1.7601.17514
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
    BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_code_av_null_ip_vpcvmm!vmmexecutevp+432
    FAILURE_ID_HASH:  {0e280cfd-4579-b158-a595-ebe6bde196a1}
    Followup: MachineOwner
    0: kd> !analyze -v

    Here we have found a hotfix for your issue, and you could give it a try. Before you apply it, please check for updates first.

    If it doesn't work, we would like to suggest you remove the Windows virtual pc and reinstall it again for test. Please download Virtual PC and XP mode from Microsoft official website.

    Hope it will be helpful to you.

    Best Regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact

    Tuesday, February 2, 2016 2:41 AM