none
'WindowsToGo Device Boot Test' failing with 'Error Code: 0x0' and 'Error Text: 0x00000000' RRS feed

  • Question

  • Greetings,

    Subjecting a 'Mass Storage Device' for 'WindowsToGo Device Boot Test' is failing (please see log listed below).  Please let me know how to get this test to pass.

    Host used as WHCK client : Intel DH87MC with latest bios

    Running WHCK version 8.100.26652 on Windows 2008 R2 SP1

    Tried install.wim file from both 'Windows 8.1 Enterprise 64bit eval' and 'Windows 8.1 Enterprise with update 64bit' with same result as shown below:

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


    Start Test

    4/10/2014 12:28:23.957 PM BootTest::CBootTests::HostPostProcessResults
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    MetadataRef 4/10/2014 12:28:23.957 PM _
    Message 4/10/2014 12:28:22.551 PM Before debugging any issues ensure that the system you're running this test on has the most recent firmware See the system vendor's website for firmware updates
    Message 4/10/2014 12:28:23.551 PM WTG device booted succesfully.
    Message 4/10/2014 12:28:23.551 PM WTG device ran at the correct operating speed when booted
    Error 4/10/2014 12:28:23.551 PM Something prevented the system from entering sleep (S3) or Connected Standby. When booted from the WTG drive open a command prompt and run "powercfg -a" and note what component is listed as blocking S3 or Connected Standby. This is usually the result of missing graphics drivers. Add any missing drivers for your machine to the wim file you're using for this test.
    File: Line: -1
    Error Type:
    Error Code: 0x0
    Error Text: Error 0x00000000
    Message 4/10/2014 12:28:23.551 PM Succesfully entered and resumed from Hibernate (S4) while booted from Wtg Device
    Message 4/10/2014 12:28:23.551 PM Rebooted from Wtg drive to host OS without manual intervention
    Message 4/10/2014 12:28:23.551 PM No surprise removal events were encountered while running the test
    End Test 4/10/2014 12:28:24.957 PM BootTest::CBootTests::HostPostProcessResults
    Result: Fail
    Pass/Fail Result Rollup Counts 4/10/2014 12:28:23.410 PM _
    Total: 1
    Passed: 0
    Failed: 1
    Blocked: 0
    Warned: 0
    Skipped: 0

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

    Thursday, April 10, 2014 8:44 PM

Answers

  • Got it working after injecting 'Graphics' driver into install.wim.

    Added driver to the WIM file using DISM with the /image & /add-driver switches.


    • Marked as answer by karthi1 Monday, April 14, 2014 7:48 PM
    Monday, April 14, 2014 7:48 PM

All replies

  • Got it working after injecting 'Graphics' driver into install.wim.

    Added driver to the WIM file using DISM with the /image & /add-driver switches.


    • Marked as answer by karthi1 Monday, April 14, 2014 7:48 PM
    Monday, April 14, 2014 7:48 PM
  • Hi, i have some problem with this test.


    Message 3/20/2015 12:45:39.784 AM Before debugging any issues ensure that the device you're running this test with has the most recent firmware See the device vendor's website for firmware updates  
    Error 3/20/2015 12:45:40.784 AM Failed to boot to Wtg device Validate that your system is able to boot to USB when resuming from hibernate (S4) Validate that the windows image you used does not include any 3rd party USB drivers Validate that your system enumerates USB devices when a USB Class Entry is part of the boot order Validate that your system gives USB devices enough time to enumerate before moving to the next entry in the boot order Take a USB trace to determine what caused the system to abort its attempt to boot the UFD If you've taken these debugging steps and believe your system is behaving correctly run the test again with a certified system and compare the results.
    File:    Line: -1
    Error Type:    
    Error Code:   0x0
    Error Text:   Error 0x00000000

    Can you help me?

    Friday, March 20, 2015 11:12 AM