Bluescreen during boot Windows 7 [VirtualKD], x64

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Bluescreen during boot Windows 7 [VirtualKD], x64

Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • September 23, 2011 at 08:25 #357
    Gelbaerchen
    Participant

    Hello, during booting my virtual W7, x64 machine (using VirtualBox 4.0.12) the boot hangs and VS2010 shows the following output. Booting this virtual machine without VirtualKD works fine and also using the boot option [VirtualDK] on a virtual machine using XP SP3 works fine. My host system is also W7, x64 prof. I checked VBoxDD.dll and VBoxDD0.dll … what else could I do?

    Thanks for any idea
    ______________________________________________________________________

    Evaluation complete in 0 ms

    Loaded PDB symbols for 47 out of 51 modules

    *** Fatal System Error: 0x00000124
    (0x0000000000000000,0x0000000000000000,0x0000000000000000,0x0000000000000000)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows 7 7601 x64 target at (Fri Sep 23 10:09:27.503 2011 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ……………………………………………
    Loading User Symbols

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, 0, 0, 0}

    Probably caused by : hardware

    Followup: MachineOwner

    Evaluation complete in 0 ms

    !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: 0000000000000000, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:

    BUGCHECK_STR: 0x124_GenuineIntel

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff880`009ef408 fffff800`027b5ae2 : 00000000`00000000 fffff880`009eff40 00000000`00000065 fffff800`02706718 : nt!RtlpBreakWithStatusInstruction
    fffff880`009ef410 fffff800`027b68ce : 00000000`00000003 00000000`00000000 fffff800`02706f70 00000000`00000124 : nt!KiBugCheckDebugBreak+0x12
    fffff880`009ef470 fffff800`026cad44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheck2+0x71e
    fffff880`009efb40 fffff800`027db5d0 : 00000000`00000124 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx+0x104
    fffff880`009efb80 fffff800`026117a1 : fffffa80`0135f040 fffff880`009efd10 fffff880`009efc70 fffff800`0262e2b0 : nt!WheaReportHwError+0x320
    fffff880`009efbe0 fffff800`0277d8a1 : fffff880`009efdb0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalHandleNMI+0x149
    fffff880`009efc10 fffff800`026c7f82 : fffff880`009e5180 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiProcessNMI+0x131
    fffff880`009efc70 fffff800`026c7de3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    fffff880`009efdb0 fffff800`026d6c0f : fffff880`009e5180 fffff880`02e5bb80 fffffa80`021b95a0 00000000`00000000 : nt!KiNmiInterruptStart+0x163
    fffff880`02e5bb00 fffff800`026227d2 : fffff800`026d45e4 fffffa80`0135f040 fffffa80`021b95a0 fffff880`009eff40 : nt!KiSecondaryClockInterrupt+0x5f
    fffff880`02e5bc98 fffff800`026d45e4 : fffffa80`0135f040 fffffa80`021b95a0 fffff880`009eff40 00000000`00000002 : hal!HalProcessorIdle+0x2
    fffff880`02e5bca0 fffff800`026c293c : fffff880`009e5180 fffff880`009eff40 00000000`00000000 fffff800`027f0ef0 : nt!PoIdle+0x665
    fffff880`02e5bd80 00000000`00000000 : fffff880`02e5c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c

    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_NOERRREC

    BUCKET_ID: X64_0x124_GenuineIntel_NOERRREC

    Followup: MachineOwner

    March 10, 2013 at 12:12 #1972
    Gelbaerchen
    Participant

    hmm … now I installed the latest VisualDDK 1.5.7, up- and downgraded the virtualbox versions from 4.2.4 to 4.2.8 and to 4.1.22 but I’m still running exactly into this BSOD during booting the VirtualBox W7 x64 machine. Is there nobody else having this problem?

    March 10, 2013 at 12:47 #1973
    Gelbaerchen
    Participant

    Now I’ve done some changes in the system settings of my VirtualBox and the problem seems to be related to the number of CPUs. First I tried 2 CPUs and I had the bluescreen, now I’m using a single CPU and I can boot my VirtualBox W7 64 in Virtual KD debug mode without bluescreen 😉

    June 12, 2013 at 11:17 #1974
    Gelbaerchen
    Participant

    My only solution so far ist to use a single CPU virtual machine.

    October 7, 2013 at 12:18 #1975
    jacob374
    Participant

    the virtualbox versions from 4.2.4 to 4.2.8 and to 4.1.22 but I’m still running exactly into this BSOD during booting the VirtualBox W7 x64 machine.

    _______________________
    http://www.umw.edu/
    http://www.microsoft.com/
    http://www.pass4-sure.us/CCNP-training.html
    https://www.facebook.com/Microsoft
    http://www.youtube.com/user/CompTIATV

  • Author
    Posts
Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.