[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
chinobino
Posts: 59 | Last online: 03.27.2017
Date registered
08.09.2013
Sex
not specified
    • chinobino has written a new post "Excuse me, what time you can download the uefi BIOS update? " 02.16.2017

      I have supplied a HTTP link for UBU v1.66 below;

      (If either Fernando or SoniX does not wish for this link to remain active then I will take it down)

      EDIT by Fernando: The link has been removed on demand of American Megatrends Inc. (AMI)

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.28.2016

      Updated ME FW to 11.6.0.1117 on a Gigabyte GA-Z170-HD3 DDR3.

      Looks like we need an updated MEManuf;

      C:\>MEManufWin64

      Intel(R) MEManuf Version: 11.0.0.1205
      Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.

      Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(0)
      Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d)

      Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(1)
      Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d)

      Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(2)
      Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d)

      MEManuf Operation Passed (with warnings)

    • chinobino has written a new post "Make "Auto" values visible?" 09.17.2016

      RTL's are Round Trip Latency.

      They should be left on Auto so that the motherboard can train the memory and POST successfully - they are not really for optimizing performance as Primary, Secondary and Tertiary timings are far more crucial.

      If you are getting very bad bandwidth at high clocks speeds, sometimes it can be due to one memory channel or rank having a much higher RTL than then others, by which case you could attempt to correct it by setting it manually to a lower value that is closer to the others.

      Sometimes a BIOS fix is issued to deal with bad RTL memory training issues for certain IC's.

      One a Z170 motherboard RTL's can be set for each channel (A/B) and each DIMM rank (R0/1), not sure about Z97 though. [Edit] Just noticed your screen shot shows that it can.

      You can download Asus Memtweakit here which *may* be able to read the RTL's in Windows.

      When overclocking RAM the round trip latencies for each DIMM slot will increase (and may differ more) as you increase the clock frequency.

      Generally, the DIMM slots closer to the CPU have shorter trace lengths and therefore lower latency and vice-versa.

      Hope that helps.

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.13.2016

      @ Plutomaniac

      I have narrowed the problem down to my Windows installation, it appears something went awry when I did the Anniversary Update.

      A clean install on another partition showed no ME issues and the PC was able to sleep as per before the update.

      I guess I can look at this positively - the motherboard is fine and I have a nice new & clean Windows installation, the only real downside is have to reinstall all of my programs.

      Thankyou for your time and help!

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.12.2016

      I was editing my post while your posted yours - FPT in DOS worked fine.

      Zitat von plutomaniac im Beitrag #2463
      something is causing issues at the OS level


      This is what I am thinking also.

      Maybe I need to do a clean install to fix it...

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.12.2016

      Well nothing changed after the fptw -greset and when I try the second option I am met with this;

      C:\>fptw64 -rewrite -f me_orig.bin -me

      Intel (R) Flash Programming Tool. Version: 11.0.10.1002
      Copyright (c) 2007 - 2016, Intel Corporation. All rights reserved.

      Error 366: Fail to load driver (PCI access for Windows).
      Tool needs to run with an administrator priviledge account.

      PMxdll.dll DebugMsg: Call to PMXDestroy()


      My account is an admin account, I am running the command prompt elevated and also tried using a batch file but I get the same result.

      I made a new admin account and no dice...

      [Edit] Just grabbed the DOS version FPT and this was the result;

      C:\fpt -rewrite -f me_orig.bin -me

      Intel (R) Flash Programming Tool. Version: 11.0.15.1000
      Copyright (c) 2007 - 2016, Intel Corporation. All rights reserved.

      Reading HSFSTS register... Flash Descriptor: Valid

      ○--- Flash Devices Found ---
      ○MX25L6405DoID:0xC22017○Size: 8192KB (65536Kb)

      PDR Region does not exist.
      Gbe Region does not exist.


      - Erasing Flash Block [0x200000] - 100 percent complete.
      - Programming Flash [0x0200000] 2044KB of 2044KB - 100 percent complete.

      - Verifying Flash [0x0200000] 2044KB of 2044KB - 100 percent complete.
      RESULT: The data is identical.

      FPT Operation Successful.


      Still getting same error messages in MEInfoWin64.

      The new kernel mode driver signing in Win10 AU isn't blocking access is it?

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.12.2016

      @ Plutomaniac - I need your assistance kind sir!

      Not really sure what happened or when but ME appears to be corrupt on my system, I noticed my PC would not wake from sleep after installing Windows 10 AU and ran MEinfoWin64 to discover this;

      C:\>MEInfoWin64

      Intel(R) MEInfo Version: 11.0.15.1003
      Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.

      Intel(R) ME code versions:

      BIOS Version F6a
      MEBx Version 11.0.0.0005
      GbE Region does not exist.
      GbE Version Unknown
      Vendor ID 8086
      PCH Version 31
      FW Version 11.0.0.1168 H
      LMS Version Not Available
      MEI Driver Version 11.0.0.1181
      Wireless Hardware Version Not Available
      Wireless Driver Version Not Available

      FW Capabilities 0x31101940

      Intel(R) Capability Licensing Service - PRESENT/ENABLED
      Protect Audio Video Path - PRESENT/ENABLED
      Intel(R) Dynamic Application Loader - PRESENT/ENABLED
      Intel(R) Platform Trust Technology - PRESENT/DISABLED

      TLS Disabled
      Last ME reset reason Firmware reset
      Local FWUpdate Enabled
      BIOS Config Lock Enabled
      GbE Config Lock Enabled
      Host Read Access to ME Enabled
      Host Write Access to ME Enabled
      Host Read Access to EC Enabled
      Host Write Access to EC Enabled
      SPI Flash ID 1 C22017
      SPI Flash ID 2 Unknown
      BIOS boot State Post Boot
      OEM ID 00000000-0000-0000-0000-000000000000
      Capability Licensing Service Enabled

      Error 86: Communication error between application and Intel(R) ME module (FWU client)
      OEM Tag Unknown

      Error 83: Communication error between application and Intel(R) ME module (HCI client)
      Slot 1 Board Manufacturer Unknown

      Error 83: Communication error between application and Intel(R) ME module (HCI client)
      Slot 2 System Assembler Unknown

      Error 83: Communication error between application and Intel(R) ME module (HCI client)
      Slot 3 Reserved Unknown

      Error 83: Communication error between application and Intel(R) ME module (HCI client)
      M3 Autotest Unknown

      Error 83: Communication error between application and Intel(R) ME module (HCI client)
      C-link Status Unknown
      Independent Firmware Recovery Disabled
      EPID Group ID 0xF84

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      OEM Public Key Hash FPF Not set

      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "OEM Public Key Hash" value

      OEM Public Key Hash ME Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      ACM SVN FPF Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      KM SVN FPF Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      BSMM SVN FPF Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      GuC Encryption Key FPF Not set

      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "GuC Encryption Key" value

      GuC Encryption Key ME Not set

      FPF ME
      --- --

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Force Boot Guard ACM Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Force Boot Guard ACM Enabled" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Protect BIOS Environment Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Protect BIOS Environment Enabled" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      CPU Debugging Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "CPU Debugging" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      BSP Initialization Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "BSP Initialization" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Measured Boot Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Measured Boot Enabled" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Verified Boot Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Verified Boot Enabled" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Key Manifest ID Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Key Manifest ID" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      Enforcement Policy Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Error Enforcement Policy" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      PTT Not set
      Error 83: Communication error between application and Intel(R) ME module (HCI client)

      Error 57: Failed getting variable "Intel(R) PTT Supported" value

      Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      EK Revoke State Not set

      Error 84: Communication error between application and Intel(R) ME module (FPF client)
      PTT RTC Clear Detection FPF Not set


      Tried a CMOS reset, and BIOS flash using a flash programmer but the errors persist (the ME Firmware version was also downgraded with the BIOS flash from 11.0.15.1003 CON-H (1.5MB) to 11.0.0.1168 CON-H).

      C:\>MEManufWin64 -verbose

      Intel(R) MEManuf Version: 11.0.0.1205
      Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.

      FW Status Register1: 0x90000255
      FW Status Register2: 0x06F60506
      FW Status Register3: 0x00000000
      FW Status Register4: 0x00084000
      FW Status Register5: 0x00000000
      FW Status Register6: 0x00000000

      CurrentState: Normal
      ManufacturingMode: Enabled
      FlashPartition: Valid
      OperationalState: CM0 with UMA
      InitComplete: Complete
      BUPLoadState: Success
      ErrorCode: No Error
      ModeOfOperation: Normal
      SPI Flash Log: Not Present
      Phase: ROM/Preboot
      ICC: Valid OEM data, ICC programmed
      ME File System Corrupted: No
      PhaseStatus: AFTER_SRAM_INIT

      FPF and ME Config Status: Not committed

      FW Capabilities value is 0x31101940
      Feature enablement is 0x11101940
      Platform type is 0x71220322
      No Intel vPro Wireless device was found
      Feature enablement is 0x11101940
      ME initialization state valid
      ME operation mode valid
      Current operation state valid
      ME error state valid
      OEM ICC data valid and programmed correctly
      MFS is not corrupted
      PCH SKU Emulation is correct

      Request Intel(R) ME BIST status command...
      Error 120: Communication error between application and Intel(R) ME module (BIST client)
      error


      MEManuf Operation Passed (with warnings)


      Here is the result from a BIOS dump from fptw;

      C:\>fptw64 -d SPI.bin

      Intel (R) Flash Programming Tool. Version: 11.0.10.1002
      Copyright (c) 2007 - 2016, Intel Corporation. All rights reserved.


      Reading HSFSTS register... Flash Descriptor: Valid

      --- Flash Devices Found ---
      MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)


      - Reading Flash [0x0800000] 8192KB of 8192KB - 100 percent complete.
      Writing flash contents to file "SPI.bin"...

      Memory Dump Complete
      FPT Operation Successful.


      GA-Z170-HD3_DDR3_BIOS_F6a_CORRUPT4.zip

      Please advise on how to proceed. Thanks in advance.

    • chinobino has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 09.03.2016

      Although not a clean 1607 install, it is working for me also.

      Although I noticed;

      Intel MEI v11.6.0.1010 Beta = 06/22/2016,11.6.0.1010

      Intel MEI v11.6.0.1018 WHQL = 06/20/2016,11.6.0.1009

    • chinobino has written a new post "Msi GTX 560TI OC BIOS moding uefi" 09.03.2016

      These are the Fermi products that can possibly be modded for GOP/UEFI;

      GF119 (17 Products)

      GeForce GT 710 (Device ID 104D)
      GeForce GT 705 OEM (Device ID 104C)
      GeForce GT 625 OEM (Device ID 104B)
      GeForce GT 620 OEM (Device ID 1049)
      GeForce GT 610 (Device ID 104A)
      GeForce GT 610 OEM (Device ID 104A)
      GeForce GT 610 PCIe x1 (Device ID 104A)
      GeForce GT 610 PCI (Device ID 104A)
      GeForce 605 OEM (Device ID 1048)
      GeForce GT 520 (Device ID 1040)
      GeForce GT 520 OEM (Device ID 1040)
      GeForce GT 520 PCIe x1 (Device ID 1040)
      GeForce GT 520 PCI (Device ID 1040)
      GeForce 510 (Device ID 1042)
      GeForce 510 OEM (Device ID 1042)
      NVS 315 (Device ID 107C)
      NVS 310 (Device ID 107D)

    • chinobino has written a new post "Msi GTX 560TI OC BIOS moding uefi" 09.02.2016

      The BIOS chip on GTX560/570/580 is too small to accommodate a modified BIOS with GOP so even if you mod it it won't physically fit onto the chip.

    • chinobino has written a new post "Clone OS from Raid 0 to M2?" 07.24.2016

      You could give it a shot and see what happens, no big loss except for the time to clone.

      Try it in AHCI mode and if that fails switch it over to RAID.

      I know Fernando said he can swap over without issue on his Z97, when I tried to switch from AHCI to RAID I get BSOD on my Z170 (and yes the 950 Pro has my boot partition on it).

      I guess the result is motherboard/UEFI dependent.

    • chinobino has written a new post "Clone OS from Raid 0 to M2?" 07.23.2016

      I have just come from that exact scenario and ended up deciding to clean install.

      Although it is possible - it is a bad idea, you would have to mess with the registry (swapping from RAID mode to AHCI) and then uninstall the storage controllers in device manager before you cloned the RAID array.

      If you just set the RAID controller back to AHCI without changing the registry setting and attempt to boot form the cloned drive you will get a BSOD with the error ""Inaccessible_Boot_Device" due to the installation being in RAID mode.

      If you attempt to boot with the RAID controller in RAID mode it will likely also BSOD due to not loading the (Windows default) NVMe driver on boot.

      You would be better off clean installing in AHCI mode and using the Samsung NVMe driver.

Recipient
chinobino
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor