WEI Fails PD7 Windows 7 Ultimate on Lion

Discussion in 'Windows Virtual Machine' started by James Minnihan, Sep 1, 2011.

  1. James Minnihan

    James Minnihan Member

    Messages:
    24
    WEI fails during running the assessment in a newly upgraded PD7 VM (Windows 7 Ultimate). The following error occurs: "The windows experience index for your system could not be computed". Looking at the winsat.log, the following errors appear:

    133031 (3536) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured


    134312 (3536) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device
    134312 (3536) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created
    134328 (3536) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance


    134562 (3536) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock
    134937 (3536) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.


    135359 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    135625 (3536) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.
    136062 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    136312 (3536) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.
    136703 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
    137062 (3536) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.
    137937 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3
    138218 (3536) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    138671 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    138671 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
    138671 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3
    138671 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1
    138671 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138671 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1
    138687 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.
    138687 (3536) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6
    138687 (3536) - d3d\graphicsop.cpp:0209: Driver is not WDDM 1.1; aborting DX10 assessment.


    144421 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_MPEG2_HD_15mbps.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
    144421 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144421 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
    144421 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144421 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480i_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
    144421 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144421 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480p_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
    144421 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144437 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
    144437 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144437 (3536) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
    144437 (3536) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment.
    144453 (3536) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0
    144453 (3536) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability
    144453 (3536) - winsat\processresults.cpp:1405: No DX9 capability - limiting D3D Score to 1.0
    144453 (3536) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0

    144640 (3536) - winsat\main.cpp:4736: ERROR: Unable to save validated results.

    There's a few errors here that never occurred under PD6 with the same VM.

    Parallels: Please look into this as soon as possible.

    Thanks.

    James Minnihan
     
  2. KrisM

    KrisM Bit poster

    Messages:
    2
    What Mac are you running? I completed the W7 WEI tests on my Mac Pro:

    CPU: 7.3
    RAM: 5.5
    Aero: 6.0
    3D Gaming: 6.0
    HD: 6.9

    I'm mostly curious if you're running something with an integrated video card, as my MacBook has only ever run XP under Parallels. I'm also using Parallels 6 under 10.7
     
  3. serv

    serv Forum Maven

    Messages:
    817
    James,

    Looks like Parallels graphics driver did not install for some reason. Can you open DxDiag Display tab to see the driver and its version? (Click Windows Start button and type in 'dxdiag' without quotes in search field).
    I would also double check that you have 3D acceleration enabled in VM configuration.
     
  4. James Minnihan

    James Minnihan Member

    Messages:
    24
    Yes, I was thinking the same thing, there's seems to be something up with the display driver. Note this was a PD6 created Windows 7 Ultimate x64 VM, and all I did was have PD7 do its VM upgrade and then uninstalled and reinstalled Parallel Tools.

    Here's the dxdiag information regarding the display:

    System Information
    ------------------
    Time of this report: 9/2/2011, 14:14:03
    Machine name: JIMSWIN7VM
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
    Language: English (Regional Setting: English)
    System Manufacturer: Parallels Software International Inc.
    System Model: Parallels Virtual Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz (2 CPUs), ~2.7GHz
    Memory: 2048MB RAM
    Available OS Memory: 2048MB RAM
    Page File: 1180MB used, 2914MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode

    ------------
    DxDiag Notes
    ------------
    Display Tab 1: No problems found.
    Sound Tab 1: No problems found.
    Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D: 0/4 (retail)
    DirectDraw: 0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay: 0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow: 0/6 (retail)

    ---------------
    Display Devices
    ---------------
    Card name: Parallels Display Adapter (WDDM)
    Manufacturer: Parallels
    Chip type: Virtual Adapter
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_1AB8&DEV_4005&SUBSYS_04001AB8&REV_00
    Display Memory: 512 MB
    Dedicated Memory: 256 MB
    Shared Memory: 256 MB
    Current Mode: 1680 x 1050 (32 bit) (60Hz)
    Monitor Name: Generic Non-PnP Monitor
    Monitor Model: Parallels Vu
    Monitor Id: PRL5000
    Native Mode: unknown
    Output Type: HD15
    Driver Name: prl_umdd.dll
    Driver File Version: 7.14.0010.14920 (English)
    Driver Version: 7.0.14920.0
    DDI Version: unknown
    Driver Model: WDDM 1.0
    Driver Attributes: Beta Debug
    Driver Date/Size: 8/30/2011 01:36:14, 135680 bytes
    WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
    Device Identifier: {D7B71458-0345-11CF-4043-0A24A1C2CA35}
    Vendor ID: 0x1AB8
    Device ID: 0x4005
    SubSys ID: 0x04001AB8
    Revision ID: 0x0000
    Driver Strong Name: oem5.inf:Models.NTamd64.6:DDInstall64_6:7.0.14920.0:pci\ven_1ab8&dev_4005&subsys_04001ab8
    Rank Of Driver: 00F60001
    Video Accel:
    Deinterlace Caps: n/a
    D3D9 Overlay: n/a
    DXVA-HD: n/a
    DDraw Status: Not Available
    D3D Status: Not Available
    AGP Status: Not Available

    Also the 3D Acceleration has been turned on from the start with the VM's configuration.

    Here's the Video section of the VM's config.pvs file:


    <Video dyn_lists="">
    <Enabled>1</Enabled>
    <VideoMemorySize>256</VideoMemorySize>
    <EnableDirectXShaders>1</EnableDirectXShaders>
    <ScreenResolutions dyn_lists="ScreenResolution 0">
    <Enabled>0</Enabled>
    </ScreenResolutions>
    <Enable3DAcceleration>1</Enable3DAcceleration>
    <EnableVSync>1</EnableVSync>
    <MaxDisplays>0</MaxDisplays>
    </Video>

    I'll try updating the video memory to a higher memory setting, and get back to you.
     
  5. James Minnihan

    James Minnihan Member

    Messages:
    24
    Here's the dxdiag 64 bit version of the display information:

    ------------------
    System Information
    ------------------
    Time of this report: 9/2/2011, 14:22:09
    Machine name: JIMSWIN7VM
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
    Language: English (Regional Setting: English)
    System Manufacturer: Parallels Software International Inc.
    System Model: Parallels Virtual Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz (2 CPUs), ~2.7GHz
    Memory: 2048MB RAM
    Available OS Memory: 2048MB RAM
    Page File: 1098MB used, 2996MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 64bit Unicode

    ------------
    DxDiag Notes
    ------------
    Display Tab 1: The file prl_umdd.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
    Sound Tab 1: The file prl_sound.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
    Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D: 0/4 (retail)
    DirectDraw: 0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay: 0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow: 0/6 (retail)

    ---------------
    Display Devices
    ---------------
    Card name: Parallels Display Adapter (WDDM)
    Manufacturer: Parallels
    Chip type: Virtual Adapter
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_1AB8&DEV_4005&SUBSYS_04001AB8&REV_00
    Display Memory: 512 MB
    Dedicated Memory: 256 MB
    Shared Memory: 256 MB
    Current Mode: 1680 x 1050 (32 bit) (60Hz)
    Monitor Name: Generic Non-PnP Monitor
    Monitor Model: Parallels Vu
    Monitor Id: PRL5000
    Native Mode: unknown
    Output Type: HD15
    Driver Name: prl_umdd.dll
    Driver File Version: 7.14.0010.14920 (English)
    Driver Version: 7.0.14920.0
    DDI Version: unknown
    Driver Model: WDDM 1.0
    Driver Attributes: Beta Debug
    Driver Date/Size: 8/30/2011 01:36:14, 135680 bytes
    WHQL Logo'd: No
    WHQL Date Stamp: None
    Device Identifier: {D7B71458-0345-11CF-4043-0A24A1C2CA35}
    Vendor ID: 0x1AB8
    Device ID: 0x4005
    SubSys ID: 0x04001AB8
    Revision ID: 0x0000
    Driver Strong Name: oem5.inf:Models.NTamd64.6:DDInstall64_6:7.0.14920.0:pci\ven_1ab8&dev_4005&subsys_04001ab8
    Rank Of Driver: 00F60001
    Video Accel:
    Deinterlace Caps: n/a
    D3D9 Overlay: n/a
    DXVA-HD: n/a
    DDraw Status: Not Available
    D3D Status: Not Available
    AGP Status: Not Available
     
  6. James Minnihan

    James Minnihan Member

    Messages:
    24
    I upped the video memory from 256MB to 512MB and now the WEI index will calculate. Looks like with PD7, Windows 7 x64 requires a little more video memory. Thanks for increasing it from its max of 256MB in PD6 to 1GB in PD7!

    BTW, does the video memory take away from system memory in the PD7 VM? I.e. if I have allocated 2GB of system memory for Windows and 512MB for video, is the system memory now decreased by 512MB?

    Let us know, thanks!
     
  7. James Minnihan

    James Minnihan Member

    Messages:
    24
    I am running Parallels 7 now on a 2010 MacBook Pro 17" 2.66GHz Core i7 with 8GB of memory, with PD7 installed on a OWC Mercury Extreme 3G Pro SSD, and the VM installed on a Seagate 750GB 7200 rpm drive. Graphics is the nVidia GT 330M 512MB.

    For my Windows 7 Ultimate x64, I have 3GB system memory allocated, with an additional 1GB for the Graphics memory, with 3D Acceleration turned on.

    My current WEI stats are:

    CPU: 6.5
    RAM: 5.9
    Aero: 5.0
    3D Gaming: 5.0
    HD: 5.9

    Jim
     
  8. serv

    serv Forum Maven

    Messages:
    817
    James,

    I'm a bit puzzled why increasing the amount of video memory enabled 3D acceleration in your VM. It should have worked regardless of video memory size. I've sent you a private message asking for more detail.

    Regarding your question. No, video memory does not subtract from system memory allocated to VM. But both add up to Parallels memory consumption in OS X. Basically you don't have to give VM lots of video memory unless you run modern games or some demanding applications.
     
  9. adanguspf

    adanguspf Member

    Messages:
    40
    Similar experience with 10.6.8

    I was running Win7 under PD6 and took the upgrade to PD7. First, let me say that this was the simplest and easiest upgrade of a Parallels machine in I can't remember how long. Well done! No hours of machine conversion. No crashes or confusing options along the way. Just opened and ran. Well, almost. Win7 came up and claimed not to be genuine after install; but I clicked the get genuine and it activated instantly.

    Also, Win7 insisted on installing drivers while Parallels tools installed, and I didn't seem to be able to find a way to stop it from doing that. Also oddly, while doing the install, the screen was in Aero mode, as it had been in PD6, but Aero stopped when the tools were installed and the machine rebooted. I reran WEI and got a 2.0 score for graphics. Then I looked here and saw a couple of suggestions about bad driver installs and upping graphics memory. So, I reinstalled Parallels tools and ran WEI again, with no change; still 2.0 for graphics. I then upped graphics memory from 256k to 512k, enabled 2 CPUs, and turned on the hypervisor. (Brave me.) I should mention I'm running under 10.6.8 on a 2.66 GHz Intel Core 2 Duo iMac8,1 with 4GB of 800MHz DDR2 SDRAM. Then WEI gave me 4.7 for graphics and upped the CPU score from 4.7 to 6.1, while the lowest score was 4.5 for memory. My guess is that that score will improve when I up the memory allocation to 2GBs.

    In any case, bravo. This is the version of Parallels that I've been waiting for for years, it seems. So far, it's installed simply and run flawlessly. Speed is better than with PD6, but more importantly, the obvious performance improvement hooks work like they ought to. So far. I still have my PD6 install DMG and a full copy of my v6 machine files, just in case. No point being too much of a mindless fan boy.
     
  10. PatrickJ

    PatrickJ Member

    Messages:
    94
    I'm having the same issue. In the process of creating a new VM so I'll check it again shortly, but the first W7 (x64) I created WEI-crashed almost immediately after it started. However, Aero was work (shadows, transparency, etc).
     
  11. PatrickJ

    PatrickJ Member

    Messages:
    94
    Not sure what changed this go round, but working fine now.
     

    Attached Files:

Share This Page