Article ID: 117858, created on Oct 10, 2013, last review on Apr 26, 2014

  • Applies to:
  • Virtuozzo containers for Windows

Symptoms

On a fresh install of Parallels Virtuozzo Containers for Windows on a Windows 2008 x86 host I get a Blue Screen of Death after the reboot, and system can only boot into Safe Mode now.

Memory dump analysis is similar to:

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: b1b45319, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b382090e, address which referenced memory

Debugging Details:

------------------

READ_ADDRESS:  b1b45319

CURRENT_IRQL:  1b

FAULTING_IP:
vzsched+190e
b382090e 8a0401          mov     al,byte ptr [ecx+eax]

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  a899f9f4 -- (.trap 0xffffffffa899f9f4)
ErrCode = 00000000
eax=b1b45309 ebx=a169d5a0 ecx=00000010 edx=00000000 esi=a16a1800 edi=b1b45309
eip=b382090e esp=a899fa68 ebp=a899fa68 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
vzsched+0x190e:
b382090e 8a0401          mov     al,byte ptr [ecx+eax]      ds:0023:b1b45319=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from b382090e to 81869fb9

STACK_TEXT:  
a899f9f4 b382090e badb0d00 00000000 00000000 nt!KiTrap0E+0x2e1
WARNING: Stack unwind information not available. Following frames may be wrong.
a899fa68 b3828439 b1b45309 a1654d68 a169d5a0 vzsched+0x190e
a899fa84 b3827b00 a169d5a0 a899fab4 b38285d7 vzsched+0x9439
a899fa90 b38285d7 a169d5ac b382e034 a1654d68 vzsched+0x8b00
a899fab4 b3828e32 a899fac8 00000000 00000000 vzsched+0x95d7
a899faec b38340ba a1654d68 a165c000 0070006e vzsched+0x9e32
a899fb18 81987a68 a1654d68 a165c000 00000000 vzsched+0x150ba
a899fcfc 81988029 00000001 00000000 a899fd24 nt!IopLoadDriver+0x805
a899fd44 818c1e22 ab789d00 00000000 9f58ead0 nt!IopLoadUnloadDriver+0x70
a899fd7c 819f1c42 ab789d00 0cb6835d 00000000 nt!ExpWorkerThread+0xfd
a899fdc0 8185aefe 818c1d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

Cause

This issue takes place when the host have maximum allowed logical CPUs (for x86 systems that is 32 cores). Thus, right now it's impossible to run PVCfW 4.6 on x86 system's with 32 logical CPU's.

This behavior is recognized as a bug, it's internal ID is PCWIN-20240.

Resolution

Bug will be permanently fixed in one of the future updates, meanwhile please use one of the workarounds:

  1. (It is recommended to use this workaround if possible) Use x64 system instead of x86 - there won't be such problem.
  2. Limit amount of CPUs to 31 using following command:

    bcdedit /set numproc 30
    

Search Words

bsod

vzsched

installation

965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF