none
A crash with exception code 0x80000003 occurred in module "vrfcore.dll" RRS feed

  • Question

  • A crash with exception code 0x80000003 occurred in module "vrfcore.dll" in process "te.processhost.exe"

    Message:
     WexTraceInfo ThreadId=5852 ProcessId=4884 TimeStamp=1074741179 LogSessionId=0 
     WexContext TAEF
     AppCrashEvent ReportId=96c941e4-f711-4147-8883-a0b952a5d7ef 

    Error:
    [HRESULT 0x800706BE] A failure occurred while running a test operation: 'CApoDeviceTests::TestCustomFormatSupport'.
    (A crash with exception code 0x80000003 occurred in module "vrfcore.dll" in the process hosting the test code while invoking a test operation.)
    AppCrashEvent ReportId=96c941e4-f711-4147-8883-a0b952a5d7efT

    Try to delect vrfcore.dll on the registry entry for your application and try to run, still fail

    Wednesday, January 30, 2019 6:18 AM

All replies

  • Hello Gui Lin,

    After a research I found someone said the following solution work for them so you can have a try to see if it helps:

    Make sure you are not deleting or changing anything else while doing the following step:- Goto Registry editor-> win+R->regedit->HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->Windows NT->CurrentVersion-> Image File Execution Options -> (Your application name.exe). ->Right Click and export the registry settings for backup. ->Delete the registry entry for your application and try to run.

    If it doesn't work. Can you show detailed information about how to reproduce this issue? (The document you have followed and the test code you used, steps of running the test, etc.)

    Best regards,

    Rita


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, January 31, 2019 3:14 AM
  • Rita,

    This does not work.

    Detail steps as below:

    1. Download and install the latest windows 1809 HLK on the test server (Windows server 2012 R2 Standard with 64 bit OS)

    2. Install the Windows HLK Client software on the test system(Window10 32bit with build17763 and Win10 64 bit with build 17763, and Client and server in the same domain)

    3. Create a machine pool and project, select Bluetooth HS as target to test

    4. Load 1809 playlist and then select Audio APO -  Verify All Formats on Device ae Valid - TestCustomFormatSupport or other APO test case ->Fail, A crash with exception code 0x80000003 occurred in module "vrfcore.dll" in process "te.processhost.exe" from log. (The APO test case should 1809 playlist, not include 1803 or previous playlist, try to see case description, blank page display.)

    Try below way after fail:

    1 - Goto Registry editor-> win+R->regedit->HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->Windows NT->CurrentVersion-> Image File Execution Options -> Delete te.processhost.exe or delete te.ext or both, re-run the test case, still fail.

    2 - Download latest AppVirifier app from official site and install it on server or client, re-run the test case, still fail

    Anyone knows how to solove the issue?


    • Edited by Gui Lin Thursday, January 31, 2019 6:36 AM
    Thursday, January 31, 2019 6:29 AM
  • Hello Gui Lin,

    Thanks for detailed information. Since this issue is related to Windows Hardware test I'll move it to Windows Hardware Testing and Certification forum for more professional support. Thanks for understanding.

    Best regards,

    Rita


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Thursday, January 31, 2019 7:43 AM
  • It works for me! Thanks!!!
    Tuesday, June 11, 2019 1:08 AM
  • Is this issue resolved? OR under debug?
    Tuesday, August 18, 2020 8:30 AM