Hi,
ich habe leider immer wenn ich unter Windows Virtual PC den XP Mode installieren will einen Bluescreen (sobald ich auf Setup starten klicke). Ich habe die Anleitung hier durchgearbeitet und hier ist das Ergebnis vom Windows Debugger :
Ich probiere bereits seit Tagen herum, aber ich komme einfach nicht drauf. Beim Googeln bin ich auf einige andere Englische Foren gestoßen wo empfohlen wird Windows6.1-KB977632-x64 und Windows6.1-KB2652034-v2-x64 zu installieren. Hat mich aber alles leider nicht weiter gebracht, ich hoffe hier hat noch jemand eine Idee ich brauche leider den XP Mode (auf alten Laptop lief er super, der ist aber leider hinüber).
Vielen Dank schonmal
ich habe leider immer wenn ich unter Windows Virtual PC den XP Mode installieren will einen Bluescreen (sobald ich auf Setup starten klicke). Ich habe die Anleitung hier durchgearbeitet und hier ist das Ergebnis vom Windows Debugger :
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
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.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0365c000 PsLoadedModuleList = 0xfffff800`038a1890
Debug session time: Tue Jul 14 20:55:42.919 2015 (GMT+2)
System Uptime: 0 days 0:02:05.995
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Probably caused by : vpcvmm.sys ( vpcvmm!VmmExecuteVp+432 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
READ_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+0
00000000`00000000 ?? ???
PROCESS_NAME: vpc.exe
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff880083f3780 -- (.trap 0xfffff880083f3780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003f60000 rbx=fffff880083f39a8 rcx=fffff88008400000
rdx=fffff88008738000 rsi=fffff680008002e8 rdi=fffff80003806d1e
rip=0000000000000000 rsp=fffff880083f3918 rbp=fffff880083f3c00
r8=0000000004131982 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 fffff800036cdfe9 to fffff800036cea40
FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000000 ?? ???
STACK_TEXT:
fffff880`083f3918 fffff880`03f6b40a : fffffa80`088b2730 fffff880`00000000 ffffffff`ffffffff fffff880`08738000 : 0x0
fffff880`083f3920 fffff880`03f6eebd : fffff880`00b38000 00000000`00000000 00000000`00000000 fffff880`08400000 : vpcvmm!VmmExecuteVp+0x432
fffff880`083f39b0 fffff880`03f60dae : 00000000`00001f80 fffffa80`0897b950 00000000`03a4f8a0 fffff880`083f3ca0 : vpcvmm!DispatchFastControlVirtualProcessor+0x41
fffff880`083f39e0 fffff800`039ea643 : fffffa80`0897b900 fffffa80`00000000 fffffa80`06d2b360 fffffa80`08762101 : vpcvmm!VmmFastDeviceControl+0x12
fffff880`083f3a10 fffff800`039eb136 : fffff680`008002e8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`083f3b40 fffff800`036cdcd3 : fffffa80`0a823750 0000007f`ffffffff fffffa80`0a8e2240 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`083f3bb0 00000000`76e8dc4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a4f848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e8dc4a
STACK_COMMAND: .trap 0xfffff880083f3780 ; kb
FOLLOWUP_IP:
vpcvmm!VmmExecuteVp+432
fffff880`03f6b40a 488b0dc7690300 mov rcx,qword ptr [vpcvmm!WPP_GLOBAL_Control (fffff880`03fa1dd8)]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: vpcvmm!VmmExecuteVp+432
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vpcvmm
IMAGE_NAME: vpcvmm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7b294
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
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.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0365c000 PsLoadedModuleList = 0xfffff800`038a1890
Debug session time: Tue Jul 14 20:55:42.919 2015 (GMT+2)
System Uptime: 0 days 0:02:05.995
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Probably caused by : vpcvmm.sys ( vpcvmm!VmmExecuteVp+432 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
READ_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+0
00000000`00000000 ?? ???
PROCESS_NAME: vpc.exe
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff880083f3780 -- (.trap 0xfffff880083f3780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003f60000 rbx=fffff880083f39a8 rcx=fffff88008400000
rdx=fffff88008738000 rsi=fffff680008002e8 rdi=fffff80003806d1e
rip=0000000000000000 rsp=fffff880083f3918 rbp=fffff880083f3c00
r8=0000000004131982 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 fffff800036cdfe9 to fffff800036cea40
FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000000 ?? ???
STACK_TEXT:
fffff880`083f3918 fffff880`03f6b40a : fffffa80`088b2730 fffff880`00000000 ffffffff`ffffffff fffff880`08738000 : 0x0
fffff880`083f3920 fffff880`03f6eebd : fffff880`00b38000 00000000`00000000 00000000`00000000 fffff880`08400000 : vpcvmm!VmmExecuteVp+0x432
fffff880`083f39b0 fffff880`03f60dae : 00000000`00001f80 fffffa80`0897b950 00000000`03a4f8a0 fffff880`083f3ca0 : vpcvmm!DispatchFastControlVirtualProcessor+0x41
fffff880`083f39e0 fffff800`039ea643 : fffffa80`0897b900 fffffa80`00000000 fffffa80`06d2b360 fffffa80`08762101 : vpcvmm!VmmFastDeviceControl+0x12
fffff880`083f3a10 fffff800`039eb136 : fffff680`008002e8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`083f3b40 fffff800`036cdcd3 : fffffa80`0a823750 0000007f`ffffffff fffffa80`0a8e2240 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`083f3bb0 00000000`76e8dc4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a4f848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e8dc4a
STACK_COMMAND: .trap 0xfffff880083f3780 ; kb
FOLLOWUP_IP:
vpcvmm!VmmExecuteVp+432
fffff880`03f6b40a 488b0dc7690300 mov rcx,qword ptr [vpcvmm!WPP_GLOBAL_Control (fffff880`03fa1dd8)]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: vpcvmm!VmmExecuteVp+432
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vpcvmm
IMAGE_NAME: vpcvmm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7b294
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_vpcvmm!VmmExecuteVp+432
Followup: MachineOwner
---------
Ich probiere bereits seit Tagen herum, aber ich komme einfach nicht drauf. Beim Googeln bin ich auf einige andere Englische Foren gestoßen wo empfohlen wird Windows6.1-KB977632-x64 und Windows6.1-KB2652034-v2-x64 zu installieren. Hat mich aber alles leider nicht weiter gebracht, ich hoffe hier hat noch jemand eine Idee ich brauche leider den XP Mode (auf alten Laptop lief er super, der ist aber leider hinüber).
Vielen Dank schonmal
Zuletzt bearbeitet von einem Moderator: