locked
HP laptop, OEM Win7, Error 0xC004F057 RRS feed

  • Question

  • We have an HP laptop (ProBook 450 G0), with Windows 8 Pro downgraded to 7 Pro. The downgraded OS was as supplied by HP around 2 years ago.

    It has recently started displaying MGA errors at login, with error code 0xC0004F057.

    The full output from MGADiag is:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-788W3-H689G-6P6GT
    Windows Product Key Hash: yr8OHoeXhbT4dc6MxGYjdAStSPY=
    Windows Product ID: 00371-OEM-8992671-00008
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {D34C1655-222B-4799-9697-510B753CC93C}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.150316-1654
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{D34C1655-222B-4799-9697-510B753CC93C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-6P6GT</PKey><PID>00371-OEM-8992671-00008</PID><PIDType>2</PIDType><SID>S-1-5-21-3898112498-2031704006-1823019056</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP ProBook 450 G0</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68IRF Ver. F.04</Version><SMBIOSVersion major="2" minor="7"/><Date>20130624000000.000000+000</Date></BIOS><HWID>08373107018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00178-926-700008-02-1033-7601.0000-1982013
    Installation ID: 019993795013326203419056405783550370237286919754725035
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 6P6GT
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 0
    Trusted time: 15/05/2015 11:18:54
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 3:23:2015 09:47
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: NgAAAAEABAABAAEAAAABAAAABAABAAEA6GFGCuD6mm+ub45aGqM2KFpvDkPh0JRxBswo15Zj
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name	OEMID Value	OEMTableID Value
      APIC			HPQOEM		1949    
      FACP			HPQOEM		1949    
      HPET			HPQOEM		1949    
      MCFG			HPQOEM		1949    
      ASF!			HPQOEM		1949    
      SSDT			HPQOEM		SataPri
      SSDT			HPQOEM		SataPri
      SSDT			HPQOEM		SataPri
      MSDM			HPQOEM		SLIC-MPC
      FPDT			HPQOEM		1949    
      BGRT			HPQOEM		1949    
      SSDT			HPQOEM		SataPri
      SSDT			HPQOEM		SataPri
    
    

    HP have punted me quite firmly in the direction of Microsoft.

    Can anyone with better knowledge in this area than me point me to the problem?

    Friday, May 15, 2015 10:34 AM

Answers

  • OEM Activation 2.0 Data-->
    BIOS valid
    forOA 2.0:yes,but noSLIC table

    The problem is that the SLIC table that should be present in the BIOS appears to be missing - this is definitely HP's problem, and not MS's.

    Have you done any form of BIOS update?

    Call HP back and tell them what I said above - and ask what they are going to do about it ;)

    The only other thing you can try (and it may not work) is a recovery to Factory settings.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 15, 2015 1:46 PM
    Moderator

All replies

  • OEM Activation 2.0 Data-->
    BIOS valid
    forOA 2.0:yes,but noSLIC table

    The problem is that the SLIC table that should be present in the BIOS appears to be missing - this is definitely HP's problem, and not MS's.

    Have you done any form of BIOS update?

    Call HP back and tell them what I said above - and ask what they are going to do about it ;)

    The only other thing you can try (and it may not work) is a recovery to Factory settings.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 15, 2015 1:46 PM
    Moderator
  • OEM Activation 2.0 Data-->
    BIOS valid
    forOA 2.0:yes,but noSLIC table

    The problem is that the SLIC table that should be present in the BIOS appears to be missing - this is definitely HP's problem, and not MS's.

    Have you done any form of BIOS update?

    Call HP back and tell them what I said above - and ask what they are going to do about it ;)

    The only other thing you can try (and it may not work) is a recovery to Factory settings.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Thanks for that. I have called them back, and after being told a BIOS update would "surely" fix the problem, then that a system restore would "definitely" sort it out, they've accepted that maybe the motherboard might be at fault.

    Unfortunately it's 6 months out of warranty; fortunately I'm well practiced at arguing in such cases :)

    Monday, May 18, 2015 1:10 PM
  • The SLIC table isn't usually part of any BIOS update - which is why it didn't work. (if it was part of an update which you'd previously installed, it could even explain why it failed, since it would by default not be present).

    Good luck with them!


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Monday, May 18, 2015 2:04 PM
    Moderator