Embedded Controller issues, living an absolute H*LL with my ASUS Vivobook Pro 16X OLED

[GardevoirForEver]

I've been dealing with so many complications for months, trying to find and then fix the root cause of the issue I really need help and I have to solve this on my own (Going to Asus headquarters isn't an option for me. First, because I'm very stubborn and want to insist that I can fix this sort-of-myself somehow, and second, the location is too far away for me anyway).

Right now I'm desperate trying to put an end to this nightmare, but OK, I'll do my best to be somewhat brief in explaining and relating the entire situation and context.

==
The motherboard of my ASUS Vivobook Pro 16X OLED burned in an electrical accident, only the motherboard was damaged while other components weren't affected. I didn't have the budget to buy a new laptop. But I had money to spend on buying a new spare motherboard.. And I bought it; it was new and fresh, and I undertook the difficult task by myself of removing all the screws, putting everything back in place, replacing the motherboard, applying thermal paste, etc. Not something easy to do on a laptop like this, but I pulled it off. And I then even reinstalled Windows 10.

This is when the eternal nightmare began.

My computer would randomly freeze and the screen would glitch, and this would happen at least once or twice a day, usually forcing Windows to restart and leaving behind a crazy WHEA-log in the event viewer. Even though the laptop worked perfectly for the rest of the day.

After MONTHS of investigation I found the real cause of the problem.

In Powershell the command: C:\Windows\system32> Get-WmiObject -Class Win32_BIOS | Select-Object *
It returns me the following:

===

PSComputerName : DESKTOP-A26LRUO
Status : OK
Name : X7600PCB.300
Caption : X7600PCB.300
SMBIOSPresent : True
__GENUS : 2
__CLASS : Win32_BIOS
__SUPERCLASS : CIM_BIOSElement
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_BIOS.Name="X7600PCB.300",SoftwareElementID="X7600PCB.300",SoftwareElementState=3
,TargetOperatingSystem=0,Version="_ASUS_ - 1072009"
__PROPERTY_COUNT : 31
__DERIVATION : {CIM_BIOSElement, CIM_SoftwareElement, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : DESKTOP-A26LRUO
__NAMESPACE : root\cimv2
__PATH : \\DESKTOP-A26LRUO\root\cimv2:Win32_BIOS.Name="X7600PCB.300",SoftwareElementID="X7600PC
B.300",SoftwareElementState=3,TargetOperatingSystem=0,Version="_ASUS_ - 1072009"
BiosCharacteristics : {7, 11, 12, 15...}
BIOSVersion : {_ASUS_ - 1072009, X7600PCB.300, American Megatrends - 50013}
BuildNumber :
CodeSet :
CurrentLanguage : en|US|iso8859-1
Description : X7600PCB.300
EmbeddedControllerMajorVersion : 255
EmbeddedControllerMinorVersion : 255
IdentificationCode :
InstallableLanguages : 1
InstallDate :
LanguageEdition :
ListOfLanguages : {en|US|iso8859-1}
Manufacturer : American Megatrends International, LLC.
OtherTargetOS :
PrimaryBIOS : True
ReleaseDate : 20220225000000.000000+000
SerialNumber : N4N0CX06X655158
SMBIOSBIOSVersion : X7600PCB.300
SMBIOSMajorVersion : 3
SMBIOSMinorVersion : 3
SoftwareElementID : X7600PCB.300
SoftwareElementState : 3
SystemBiosMajorVersion : 5
SystemBiosMinorVersion : 19
TargetOperatingSystem : 0
Version : _ASUS_ - 1072009
Scope : System.Management.ManagementScope
Path : \\DESKTOP-A26LRUO\root\cimv2:Win32_BIOS.Name="X7600PCB.300",SoftwareElementID="X7600PC
B.300",SoftwareElementState=3,TargetOperatingSystem=0,Version="_ASUS_ - 1072009"
Options : System.Management.ObjectGetOptions
ClassPath : \\DESKTOP-A26LRUO\root\cimv2:Win32_BIOS
Properties : {BiosCharacteristics, BIOSVersion, BuildNumber, Caption...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers : {dynamic, Locale, provider, UUID}
Site :
Container :

===

EmbeddedControllerMajorVersion : 255
EmbeddedControllerMinorVersion : 255

That's when I understood that the EC was the cause of all the Laptop's malfunctions, because it simply isn't supposed to have these values.
I tried all sorts of things to overwrite the EC, assuming it was a problem with the BIOS being flashed incorrectly or part of it being corrupted.

Nothing worked. I tried flashing the BIOS directly with the official file that Asus offers on their website, right in the BIOS with EZ Flash, try forcing a downgrade to an older BIOS version and then updating to the latest version thinking that maybe this would reset the EC and its state. None of this solved the problem with the EC not responding.

Okay, so no official Asus channel was going to help me.

That's when I downloaded CSME System Tools v15.0 r15, And I found the following:
==

PS C:\Windows\system32> cd "C:\Users\FreezeMan\Desktop\CSME System Tools v15.0 r15\Flash Programming Tool\WIN64"
PS C:\Users\FreezeMan\Desktop\CSME System Tools v15.0 r15\Flash Programming Tool\WIN64> .\fptw64.exe -i
>>
Intel (R) Flash Programming Tool Version: 15.0.35.1951
Copyright (C) 2005 - 2021, Intel Corporation. All rights reserved.

Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
ID:0xC22018 Size: 16384KB (131072Kb)

--- Flash Image Information --
Signature: VALID
Number of Flash Components: 1
Component 1 - 16384KB (131072Kb)
Regions:
DESC - Base: 0x00000000, Limit: 0x00000FFF
BIOS - Base: 0x00600000, Limit: 0x00FFFFFF
CSME - Base: 0x00001000, Limit: 0x005FFFFF
GbE - NOT PRESENT
PDR - NOT PRESENT
EC - NOT PRESENT
Master Region Access:
BIOS - ID: Read: 0x000F, Write: 0x000A
CSME - ID: Read: 0x000D, Write: 0x0004
GbE - ID: Read: 0x0009, Write: 0x0008
EC - ID: Read: 0x0101, Write: 0x0100

Total Accessible SPI Memory: 16384KB, Total Installed SPI Memory: 16384KB

FPT Operation Successful.

PS C:\Users\FreezeMan\Desktop\CSME System Tools v15.0 r15\Flash Programming Tool\WIN64>

==

This means that the EC region isn't declared as an accessible section in the Intel descriptor. Although the access IDs are defined, the EC region itself is neither present nor enabled in the descriptor. The literally entire PC lacked access to the EC despite it being physical on the motherboard.

And I was all, how the HELL do you fix that?????

After talking to ChatGPT, I learned what a CH431a is, and I bought one, received it, and started working.
ChatGPT convinced me that I could find the solution by modifying the firmware of the EC itself to remove the factory protection it probably had and how this would open the EC for writing.
However, after successfully learning how to use a CH431A, set it up properly, and identifying the specific chip on my Motherboard that seems to contain the EC firmware...

Simply messing around with AsProgrammer/NeoProgrammer didn't get me anywhere and ChatGPT just made me go around in circles.

One thing I did in AsP is that, by going to EDIT SREG and then pressing READ, this loaded for me:

So I unchecked all the boxes and pressed Write, and then when I pressed Read again, it loaded, so at least it seemed I was able to edit SREG1 even though SREG3 remained the same???:

Whether this did or changed anything, or helped me in any way toward my goal of making this Laptop work, I have no idea.

But basically now I'm stuck here, not knowing where the hell to go from here, or what I'm even supposed to do or where to ask.

I understand that now that I have the CH341a I can fix all this, but I don't know how...I am just so lost.

The reason I'm not posting this in the BIOS request forum or anything like that is because I'm looking for guidance, since I'm not even sure if I'm addressing the problem right . Do I need to edit and change something in the EC's Firmware? Is the problem with the motherboard's core BIOS...? (Which I haven't even identified the chip which contains it on the motherboard yet, by the way.)...? And if so, why if I correctly flashed the main BIOS with the official file am I having all these EC problems to begin with...What hypothetical help would editing that BIOS with the CH341a would give me..?

Because Yes, I saw that a BIOS dump for the X7600PCB was posted in a thread here, but I don't know to what extent the EC problems fit into all of this… ( https://www.badcaps.net/forum/troubl...88#post3707588 )

Below I will list all my computer specifications, BIOS dumps, and even a scan of the motherboard model (using the burned motherboard in the scan, because it looks identical to the new one except for looking burned from behind, only the one in the image doesn't work as I said).

=====
Specs:
CsManufacturer: ASUSTeK COMPUTER INC.
CsModel: Vivobook_ASUSLaptop X7600PCB_N7600PC
CsOEMStringArray: {kPJ-+7X7+EfTa, jTyRUBSNi7Ydf, fCrOzJ6x1i-eh, ...}
11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz -NumberOfCores (4)-NumberOfLogicalProcessors (8)

Name AdapterRAM DriverVersion
Intel(R) Iris(R) Xe Graphics 2147479552 32.0.101.7040
NVIDIA GeForce RTX 3050 Laptop GPU 4293918720 32.0.15.6607

Manufacturer Capacity Speed PartNumber
------------ -------- ----- ----------
Samsung 17179869184 3200 M471A2G44AM0-CWE
Samsung 17179869184 3200 M471A2G44AM0-CWE
(Two RAM memories, total 16 Gigas)

SerialNumber (PC): N4N0CX06X655158

C:\Windows\system32>wmic baseboard get product, version, serialnumber Product SerialNumber Version X7600PCB N310NBCX009L96MB 1.0

(N310NBCX009L96MB is the serial number of the Motherboard)

Dumps:
Download BIOSASUS.bin | LimeWire

EC1.bin is a dump of the firmware exactly as it was originally from the chip that I was intervening with.
EC2.bin is a dump of the same chip, But after I supposedly edited it with AsProgramador? I'm not sure if anything changed.
BIOSASUS.bin is a dump of my BIOS, BUT I made this one using .\fptw64.exe , because I'm still not sure which chip on my motherboard contains the main BIOS, and I haven't plugged the clips in there yet.

EC1 and EC2 are both dumps of a Winbond 25Q80DVNIG 2140



MotherBoard (Just same model, remember that this scan is of the one that got burned):
Here is the scan of the motherboard model mentioned; the chip circled in red is the one I was trying to edit with the tweezers connected to CH431a. And it is the one that I think corresponds to the EC Chip and its Firmware. From this Chip is the first two dumps I posted.

As I said, I don't know which Chip corresponds to the main normal BIOS, so I would appreciate it if you guys could point that out to me, or if the Chip I enclosed in the red circle corresponds to actually something else and I'm not doing anything right.

[SMDFlea]

BIOSASUS.bin is the bios region, it isn`t a full backup. EC1 (25Q80DVNIG) is thunderbolt firmware.

Leave the status registers alone, don`t mess with anything there is no need to. The chip that you made the BIOSASUS.bin from ,make a backup with the programmer ,start a new thread in the bios requests forum with the thread title "Asus X7600PCB Bios" Post your dump , laptop serial number, and if you can find a QR code on the motherboard such as this one https://www.badcaps.net/filedata/fetch?id=3708312 scan it and post what it says or take a picture of it. Someone will help to make a new bios.

[m1ch43lzm]

My computer would randomly freeze and the screen would glitch, and this would happen at least once or twice a day, usually forcing Windows to restart and leaving behind a crazy WHEA-log in the event viewer. Even though the laptop worked perfectly for the rest of the day.

That looks like faulty RAM, or as RAM is soldered to the motherboard, bad soldering/cracked solder balls, try Memtest86 or Windows Memory Diagnostics, unfortunately looks like you received a defective motherboard

This means that the EC region isn't declared as an accessible section in the Intel descriptor. Although the access IDs are defined, the EC region itself is neither present nor enabled in the descriptor. The literally entire PC lacked access to the EC despite it being physical on the motherboard.

That doesn't matter, the "EC Region" on Intel BIOSes isn't used on 99% of laptops, most have 1. Descriptor 2. ME region 3. BIOS region in that order
The EC firmware is embedded into the EC chip itself (ITE, ENE, Nuvoton), don't think it's the issue as laptop powers on
There's a copy of the EC firmware on the main BIOS

ChatGPT convinced me that I could find the solution by modifying the firmware of the EC itself to remove the factory protection it probably had and how this would open the EC for writing.

ChatGPT is a good liar... I don't trust it (or any other LLM) for technical matters

[GardevoirForEver]

Thank you both very much for your responses.

That looks like faulty RAM, or as RAM is soldered to the motherboard, bad soldering/cracked solder balls, try Memtest86 or Windows Memory Diagnostics, unfortunately looks like you received a defective motherboard

Is there a method I can use to absolutely confirm that this is the cause of the problem and rule out everything else, thus confirming the motherboard is faulty and thus not waste more time on it? I just runned Windows Memory Diagnostics And I give me the result "No Memory Errors were detected". I'm going to try with Memtest86 I'll do it later when I can, but I wanted to post this to see if the result of Windows Memory Diagnostics ruled out the problem with the RAM memory, or that's not enough.

BIOSASUS.bin is the bios region, it isn`t a full backup. EC1 (25Q80DVNIG) is thunderbolt firmware.

Leave the status registers alone, don`t mess with anything there is no need to. The chip that you made the BIOSASUS.bin from ,make a backup with the programmer ,start a new thread in the bios requests forum with the thread title "Asus X7600PCB Bios" Post your dump , laptop serial number, and if you can find a QR code on the motherboard such as this one https://www.badcaps.net/filedata/fetch?id=3708312 scan it and post what it says or take a picture of it. Someone will help to make a new bios.

Okay, thanks the replies of you two and what I've been reading. It seems that EC has nothing to do with my problem, and ChatGPT convinced me of things that aren't true.

I have a few things to comment on.

BIOSASUS.bin is a dump file I generated using fptw64.exe, not using the CH314a + NeoProgrammer as if I did with the other dumps. This is because I haven't even been able to locate which chip the BIOS is on yet. I'm new to this forum, so I guess I should ask for help getting the Schematic and then get help to locate the bios CHIP there? The "it isn`t a full backup" Means it's an incomplete dump, and that must be because I didn't back it up using CH341a, right?

Secondly, and just out of curiosity, what is Thunderbolt firmware and what does it do?

[m1ch43lzm]

Windows Memory diagnostics only runs 2 passes, it will detect immediate faults; but if the fault occurs after several hours, then try Memtest86 https://www.memtest86.com/ for a longer period

Try also running GPU stress tests like Unigine Superposition, and CPU stress test with Cinebench R23

As I explained before, a BIOS for Intel is composed of 3 parts
1. Descriptor
2. ME region
3. BIOS region

What you backed up with FPT is the BIOS region, not the full BIOS image
BIOS chip looks like it's this one:

U2801 on the boardview
Boardview: https://www.badcaps.net/forum/troubl...tics-boardview
Open with FlexBV Free https://pldaniels.com/flexbv5/free.php

Intel Thunderbolt https://www.intel.com/content/www/us.../overview.html

[reformatt]

Intermittent freezes are usually bad balls under the CPU or RAM, or bad RAM itself. Asus Vivobook boards are pretty flimsy, and so are the chassis they put them in so it's usually CPU related. Asus make great products, like routers etc, but their laptops are not one of them.