Bottom Left, you should see that image on top of the chip:

No, that's it. Since the realtek audio chips are very small, the best way to try this is by having the motherboard plugged-in but outside the case; maybe on top of a non-conductive card-box (motherboard's box for example) or something. This way you will have more space for your hands. Also, something very thin (and conductive of course) must be used to bridge/short the pins properly.

Zitat von getyasome im Beitrag #713

---

ok I found the chip but it is hard as hell to see the pins , I've tried a couple of times with no luck. Is there anything else that can be done?

---

Zitat von geneo im Beitrag #717

---

Just got back from the holiday. I reinstalled the 10.0.30.1054 driver to see what driver it was using and it was the TeeDriver, which was what I thought I remembered. But now the reboot cycle is back to 17s. Go figure.

---

Updated since 24/11/2014:

* Added at ME System Tools v10.0: Debug Configuration Tool(DOS): 1.0.0.1405
* Added at ME System Tools v10.0: ME 10 SW 1.5MB and 5MB SKUs HotFix Notes WW12 2014 documentation
* Updated at ME System Tools v9.0: Flash Programming Tool(DOS) from v9.0.21.1452 --> v9.0.22.1467
* Updated at ME System Tools v9.0: Flash Programming Tool(Windows) from v9.0.21.1452 --> v9.0.22.1467
* Updated at ME System Tools v9.0: Flash Programming Tool(Windows64) from v9.0.21.1452 --> v9.0.22.1467
* Fixed ME7 MEManuf link title from v7.1.20.1119 to v7.1.30.1139
* A lot of text changes, removals, additions, moving etc to make the thread more informative & easier to read

General Notes:

--> Regarding Intel ME: Are you still wondering what the hell it does exactly? THIS should help you understand. Also added to the ME Thread on the top.

--> Regarding ME System Tools v9.1: As you can see this is the only incomplete package and that's because it's hard to track tools for it. The recently added HotFix Notes WW12 documentation that was added at ME System Tools v10.0 confirms my suspicions that the ME System Tools v9.1 are included with certain v10.0 packages + drivers that Intel releases at their VIP site. So, to find v9.1 tools we need to find a v10 package that is intended for 9-series systems. This makes sense since there were never v9.1 drivers but v9.0, v9.5, v9.6 and then v10.0. Almost always, same version firmware comes with same version drivers (v9.5 firmware + v9.5 drivers etc).

--> Regarding MEManuf Tool: MEManuf is clearly the most important tool when it comes to ME validation so make sure you use it. Keep in mind that the correct command to run is actually MEManuf -EOL which verifies that the ME is ready for consumers. However, this command will show errors if your descriptor is unlocked since it's a security risk and thus not recommended by Intel. For example, my Gigabyte Z77 system came with an unlocked descriptor so the -EOL command will report 3 errors related to Mfg Mode, Mfg Done Bit & Flash Region Access Permissions.

Dammit Intel, I just uploaded that 100MB file. Also, the correct version is 1000 not 1001 that can be found at Station drivers. Thank you Stasio for the Intel links! I added the pages from Intel, not just the links.

* Updated Intel MEI Drivers & Software from v10.0.30.1072 --> v10.0.31.1000 for 1.5MB systems
* Updated Intel MEI Drivers & Software from v10.0.30.1072 --> v10.0.31.1000 for 5MB systems

Yes, these tools are already available. Still, thank you for the reply.

Zitat von plutomaniac im Beitrag #722

---

I added the pages from Intel, not just the links.
* Updated Intel MEI Drivers & Software from v10.0.30.1072 --> v10.0.31.1000 for 1.5MB systems
* Updated Intel MEI Drivers & Software from v10.0.30.1072 --> v10.0.31.1000 for 5MB systems

---

Yes, if the drivers were updated I would have mentioned it. These are just software. Btw, a quick way to check what MEI & SOL driver versions are included within the SetupME.exe packages is to open the included .xml file.