PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

Hello everyone, I recently discovered this forum through the YouTube video of "RipFelix" about the history of the YLOD of the PS3, researching on how I could repair my PS3 retrocompatible version cecha01", since it has YLOD, however, it is something strange, since the PS3 turns on and starts normally in general, however it is a constant that about 5 minutes after being turned on it turns off followed by a beep and the blinking of the red light.
I have personally tried to diagnose the problem but to be honest I haven't come to anything conclusive yet. I have managed to extract the errors from the syscon chip using the method of "db260179" in his GitHub repository and using "PS3 ADVANCE TOOLS".

This is the DUMP that I got using "PS3 ADVANCE TOOLS".
Firmware Version: 4.89 (build 50740)
Platform ID: Cok14
Product Code: 00 84
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFFFFFFFFFFFF
Syscon Fimware Version: 0B8E.00010000000000000006 (EEPROM: 00010000000000000006)
Bringup Count: 432, Shutdown Count: 384
Runtime: 11 Days, 5 Hours, 21 Minutes, 56 Seconds
Error Log
01: A0801301 Sat Dec 31 05:14:25 2005
02: A0801301 Sat Dec 31 00:03:06 2005
03: A0801301 Sun Jan 1 21:14:12 2006
04: A0801301 Sun Jan 1 13:38:41 2006
05: A0801301 Sun Jan 1 12:21:14:14 2006
06: A0801301 Sun Jan 1 11:56:11 2006
07: A0902120 Sun Jan 1 11:49:32 2006
08: A0403034 Sun Jan 1 11:49:32 2006
09: A0902203 Sun Jan 1 11:46:51 2006
10: A0801301 Sun Jan 1 11:46:51 2006
11: A0801301 Sun Jan 1 11:46:39 2006
12: A0801301 Sun Jan 1 10:58:26 2006
13: A0801301 Sun Jan 1 10:25:49 2006
14: A0801301 Sun Jan 1 10:24:45 2006
15: A0801301 Sun Jan 1 10:08:52 2006
16: A0801301 Sun Jan 1 08:30:28 2006
17: A0801301 Sun Jan 1 08:09:22 2006
18: A0323033 Sun Jan 1 08:06:16 2006
19: A0801301 Sun Jan 1 08:06:07 2006
20: A0801301 Sun Jan 1 08:00:03 2006
21: A0801301 Sun Jan 1 01:07:06 2006
22: A0801301 Sat Dec 31 21:30:48 2005
23: A0801301 Sat Dec 31 13:42:56 2005
24: A0801301 Sat Dec 31 13:42:17 2005
25: A0801301 Sat Dec 31 10:11:35 2005
26: A0801301 Sat Dec 31 07:32:25 2005
27: A0801301 Sat Dec 31 07:00:29 2005
28: A0801301 Sat Dec 31 01:15:56 2005
29: A0801301 Sat Dec 31 01:14:28 2005
30: A0801301 Sat Dec 31 00:02:56 2005
31: A0801301 Sat Dec 9 19:02:02 2006

This is the DUMP I got using the GitHub tools from "db260179".
ERR 00: 00000000 A0801301 0B48873A
ERR 01: 00000000 A0801301 0B4B02A4
ERR 02: 00000000 A0801301 0B4A97E1
ERR 03: 00000000 A0801301 0B4A85BA
ERR 04: 00000000 A0801301 0B4A7FDB
ERR 05: 00000000 A0902120 0B4A7E4C
ERR 06: 00000000 A0403034 0B4A7E4C
ERR 07: 00000000 A0902203 0B4A7DAB
ERR 08: 00000000 A0801301 0B4A7DAB
ERR 09: 00000000 A0801301 0B4A7D9F
ERR 10: 00000000 A0323033 0B4A49F8
ERR 11: 00000000 A0801301 0B4A49EF
ERR 12: 00000000 A0801301 0B4A4883
ERR 13: 00000000 A0801301 0B49E7BA
ERR 14: 00000000 A0801301 0B49B508
ERR 15: 00000000 A0801301 0B494760
ERR 16: 00000000 A0801301 0B49473939
ERR 17: 00000000 A0801301 0B4915D7
ERR 18: 00000000 A0801301 0B48F089
ERR 19: 00000000 A0801301 0B48E90D

As you can see, the list of errors is practically identical one to the other, recapping a little, my PS3 has never been serviced until now, it was the first time it was disassembled and cleaned since I have it. It has never been reballed or delid

Any suggestions on what the next steps would be to try to repair it ?
 
Argum99 said:
Firmware Version: 4.89 (build 50740)
Platform ID: Cok14
Product Code: 00 84
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFFFFFFFFFFFF
Syscon Fimware Version: 0B8E.00010000000000000006 (EEPROM: 00010000000000000006)
Bringup Count: 432, Shutdown Count: 384
Runtime: 11 Days, 5 Hours, 21 Minutes, 56 Seconds
Error Log
01: A0801301 Sat Dec 31 05:14:25 2005
02: A0801301 Sat Dec 31 00:03:06 2005
03: A0801301 Sun Jan 1 21:14:12 2006
04: A0801301 Sun Jan 1 13:38:41 2006
05: A0801301 Sun Jan 1 12:21:14:14 2006
06: A0801301 Sun Jan 1 11:56:11 2006
07: A0902120 Sun Jan 1 11:49:32 2006
08: A0403034 Sun Jan 1 11:49:32 2006
09: A0902203 Sun Jan 1 11:46:51 2006
10: A0801301 Sun Jan 1 11:46:51 2006
11: A0801301 Sun Jan 1 11:46:39 2006
12: A0801301 Sun Jan 1 10:58:26 2006
13: A0801301 Sun Jan 1 10:25:49 2006
14: A0801301 Sun Jan 1 10:24:45 2006
15: A0801301 Sun Jan 1 10:08:52 2006
16: A0801301 Sun Jan 1 08:30:28 2006
17: A0801301 Sun Jan 1 08:09:22 2006
18: A0323033 Sun Jan 1 08:06:16 2006
19: A0801301 Sun Jan 1 08:06:07 2006
20: A0801301 Sun Jan 1 08:00:03 2006
21: A0801301 Sun Jan 1 01:07:06 2006
22: A0801301 Sat Dec 31 21:30:48 2005
23: A0801301 Sat Dec 31 13:42:56 2005
24: A0801301 Sat Dec 31 13:42:17 2005
25: A0801301 Sat Dec 31 10:11:35 2005
26: A0801301 Sat Dec 31 07:32:25 2005
27: A0801301 Sat Dec 31 07:00:29 2005
28: A0801301 Sat Dec 31 01:15:56 2005
29: A0801301 Sat Dec 31 01:14:28 2005
30: A0801301 Sat Dec 31 00:02:56 2005
31: A0801301 Sat Dec 9 19:02:02 2006
Click to expand...

I highlighted the most telling codes IMO. The 3034 is the most concerning (GPU issue requiring a reball/replacment). 2203 and 2120 are often seen with it. It doesn't just go away. And my guess is the PLL unlock (1301) is related.

What gets me is the low use. Only 11 days makes me think it had a poor reflow at the factory. We know SONY's LF profile wasn't always dialed in. Probably toward the begining of production, but that's not confirmed. What is the manufacture date on your console? Check the back sticker for the date it was made. If it's the BGA a simple reball may be all it needs.

One thing you can do to confirm this is the pressure test. Place a 2mm thermal pad (like the one on the blue ray drive or Southbridge) behind the RSX, between motherboard and RF shield. This will apply pressure to the RSX and if it makes the console stable, then it's definately a GPU issue (likely a BGA defect).

Of course the console shouldn't be left this way. You'll need to replace or reball the RSX.
 
RIP-Felix said:
I highlighted the most telling codes IMO. The 3034 is the most concerning (GPU issue requiring a reball/replacment). 2203 and 2120 are often seen with it. It doesn't just go away. And my guess is the PLL unlock (1301) is related.

What gets me is the low use. Only 11 days makes me think it had a poor reflow at the factory. We know SONY's LF profile wasn't always dialed in. Probably toward the begining of production, but that's not confirmed. What is the manufacture date on your console? Check the back sticker for the date it was made. If it's the BGA a simple reball may be all it needs.

One thing you can do to confirm this is the pressure test. Place a 2mm thermal pad (like the one on the blue ray drive or Southbridge) behind the RSX, between motherboard and RF shield. This will apply pressure to the RSX and if it makes the console stable, then it's definately a GPU issue (likely a BGA defect).

Of course the console shouldn't be left this way. You'll need to replace or reball the RSX.
Click to expand...
It was made on December 2006
 
That's pretty early. It launched in November, so that could fit with the LF reflow profile not being dialed in theory.
 
RIP-Felix said:
I highlighted the most telling codes IMO. The 3034 is the most concerning (GPU issue requiring a reball/replacment). 2203 and 2120 are often seen with it. It doesn't just go away. And my guess is the PLL unlock (1301) is related.

What gets me is the low use. Only 11 days makes me think it had a poor reflow at the factory. We know SONY's LF profile wasn't always dialed in. Probably toward the begining of production, but that's not confirmed. What is the manufacture date on your console? Check the back sticker for the date it was made. If it's the BGA a simple reball may be all it needs.

One thing you can do to confirm this is the pressure test. Place a 2mm thermal pad (like the one on the blue ray drive or Southbridge) behind the RSX, between motherboard and RF shield. This will apply pressure to the RSX and if it makes the console stable, then it's definately a GPU issue (likely a BGA defect).

Of course the console shouldn't be left this way. You'll need to replace or reball the RSX.
Click to expand...
I just tried putting a thermal pad underneath the RSX, and unfortunately it did not solve the problem, the PS3 turns on for about 5 min and then abruptly turns off followed by a beep and the red light blinking
 
Pressure test often doesn't work. It doesn't rule out a BGA defect, but if it did change things then and only then would I say a reball is viable. At this point I would instead reccomend a replacment GPU (frankie). May as well get tokins done at the same time.
 
hi i am new here i need your help
i have ps3 slim with board jsd-001
its turn on green light then immediately turn off with no light its not yellow light
i connect uart and reed the error

C:\Users\GAMER\Desktop\Syscon Connection Drivers and Diagrams ByNSC>python "C:\Users\GAMER\Desktop\Syscon Connection Drivers and Diagrams ByNSC\1.py" COM6 SW
> AUTH
Auth successful
> errlog
00000000
# CODE CLOCK
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0093003 FFFFFFFF
# A0902024 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF

> bringup
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [SSM] Bringup Start.
# [PowSeq] Error:A102
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.



can you help me to fix the ps3 thanks a lot .
 
Hi all,
I got PS3 2500A JSD-001 SW2-303 with GLOD with a strange error in the errlog. The behavior when pressing the power button is very typical - pressing the power button, 1 second and fatal shutdown.
Code: 
>$ ERRLOG
# CODE CLOCK
# A0111B01 FFFFFFFF
…
When launched, the following is displayed in the terminal, I don't know how useful this information is:
Code: 
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOFF State)
# [SSM] Bringup Start.
# [PowSeq] Error:A115
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOFF State)
Having studied the error definition page, I did not find error 1B01 there, the maximum that is there is 1902 rtc error. There is no doubt that this is 1b01, this is not 1801 or 1601. I would like to know if anyone has thoughts about this error.
On the board, measurements did not reveal anomalies at obvious control points, all resistances are within normal limits, the main voltages are available at that second of switching on, the fuses are all in good condition. I thought the errlog would give the cause of the problem, but created only additional questions.
Additionally, I wanted to know if the additional power supply on the jsd-001 board for the bluetooth module should be 2.4v or 1.8v? On an earlier version of the slim it was 1.8v, I did not find any information here.
I apologize in advance for possible errors in the construction of the text, this is a machine translation into English.
 
I am getting A0213013 on DIA-001. There were more errors originally. What are the necessary prerequisites for the CELL BE to respond on the SPI bus to the SysCon? On DIA-001, 1.2V_MC2_VDDIO and 1.2V_BE_VCS are both available and the syscon does send /CS, clk and data to the BE, but there is no return data from the BE - BE_SPI_DI keeps high. BE_RESET goes correctly high too. Are any clocks or other supply voltages necessary for the BE to reply on the SPI bus?

Initial errors list (now, it is full of only A0213013):
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0213013 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0902203 FFFFFFFF
ERR 11: 00000000 A0902203 FFFFFFFF
ERR 12: 00000000 A0801200 FFFFFFFF
ERR 13: 00000000 A0801200 FFFFFFFF
ERR 14: 00000000 A0801200 FFFFFFFF
ERR 15: 00000000 A0902203 FFFFFFFF
ERR 16: 00000000 A0801200 FFFFFFFF
ERR 17: 00000000 A0801200 FFFFFFFF
ERR 18: 00000000 A0801200 FFFFFFFF
ERR 19: 00000000 A0801200 FFFFFFFF
 
Hi there,
I got a COK-002 PS3 which doesn't boot anymore. It starts with green light, then green + red light and 3 beeps and it shuts down.
I changed NEC caps few years ago and it run normal. After lying around a year it now doesn't boot anymore.

Syscon:
===================================
ERR 00: 00000000 A0801701 FFFFFFFF
ERR 01: 00000000 A0801701 FFFFFFFF
ERR 02: 00000000 A0801701 FFFFFFFF
ERR 03: 00000000 A0801701 FFFFFFFF
ERR 04: 00000000 A0801701 FFFFFFFF
ERR 05: 00000000 A0801701 FFFFFFFF
ERR 06: 00000000 A0801701 FFFFFFFF
ERR 07: 00000000 A0801701 FFFFFFFF
ERR 08: 00000000 A0801701 FFFFFFFF
ERR 09: 00000000 A0801701 FFFFFFFF
ERR 10: 00000000 A0801701 FFFFFFFF
ERR 11: 00000000 A0801701 FFFFFFFF
ERR 12: 00000000 A0801701 FFFFFFFF
ERR 13: 00000000 A0801701 FFFFFFFF
ERR 14: 00000000 A0801701 FFFFFFFF
ERR 15: 00000000 A0801701 FFFFFFFF
ERR 16: 00000000 A0801701 FFFFFFFF
ERR 17: 00000000 A0801701 FFFFFFFF
ERR 18: 00000000 A0801701 FFFFFFFF
ERR 19: 00000000 A0801701 FFFFFFFF
===================================

I tried a diffrent harddrive, but as I get the same error without any harddrive, that might not be the problem.

Any ideas what's wrong? Might be a problem with the Cell according to syscon guide.
 
Well if that's a concern I do not know about fats but from cech 2500x to cech 4300x have Sherwood 2 or 3 syscon and use same tmp411 a and b. But question is if I swap a tmp411 a from a cech 3000x kte-001 motherboard with my pqx-001 tmp411a. Would it be successful transplant or not . I am questioning compadibility.what do you say @sandungas @RIP-Felix .
 
Last edited:
PahanSkl said:
Hi all,
I got PS3 2500A JSD-001 SW2-303 with GLOD with a strange error in the errlog. The behavior when pressing the power button is very typical - pressing the power button, 1 second and fatal shutdown.
Code: 
>$ ERRLOG
# CODE CLOCK
# A0111B01 FFFFFFFF
…
When launched, the following is displayed in the terminal, I don't know how useful this information is:
Code: 
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOFF State)
# [SSM] Bringup Start.
# [PowSeq] Error:A115
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOFF State)
Having studied the error definition page, I did not find error 1B01 there, the maximum that is there is 1902 rtc error. There is no doubt that this is 1b01, this is not 1801 or 1601. I would like to know if anyone has thoughts about this error.
On the board, measurements did not reveal anomalies at obvious control points, all resistances are within normal limits, the main voltages are available at that second of switching on, the fuses are all in good condition. I thought the errlog would give the cause of the problem, but created only additional questions.
Additionally, I wanted to know if the additional power supply on the jsd-001 board for the bluetooth module should be 2.4v or 1.8v? On an earlier version of the slim it was 1.8v, I did not find any information here.
I apologize in advance for possible errors in the construction of the text, this is a machine translation into English.
Click to expand...
could be translated to 1101 error if we try hex to decimal conversion but that's a wild guess
 
Fallen777 said:
Well if that's a concern I do not know about fats but from cech 2500x to cech 4300x have Sherwood 2 or 3 syscon and use same tmp411 a and b. But question is if I swap a tmp411 a from a cech 3000x kte-001 motherboard with my pqx-001 tmp411a. Would it be successful transplant or not . I am questioning compadibility.what do you say @sandungas @RIP-Felix .
Click to expand...
Yes, it will work but it needs to have the suffix A (with the CELL ID hardcoded inside it)

Fallen777 said:
could be translated to 1101 error if we try hex to decimal conversion but that's a wild guess
Click to expand...
I agree, they asigned this identifyers incrementally and the higher one we know about was 9 (from error 1902) so this seems to be newer

the original error is A0111B01:
A011
1 = category (system error)
B01 (B is newer than 9)

Usually the last digits "01" means that is related either directly or indirectly with CELL, but this doesnt seems to be an strict rule, some of the error codes in the list in wiki doesnt follows this rule
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3003_.28CELL_Core_Power_Failure.29
But in general... yeah if we would be forced to make our bet the chances are high that this is CELL related
 
sandungas said:
Yes, it will work but it needs to have the suffix A (with the CELL ID hardcoded inside it)
Click to expand...
Ok so I can just go ahead and replace the tmp411A from cell side of KTE-001 with the tmp411A from cell side of PQX-001 right.
Btw can you point out what other components are associated with tmp411A circuit and is the cell id general or CPU specific. Also can I use the tantalum caps from KTE-001 motherboard for my fat dia-002 it has 3003,4 errors
 
Fallen777 said:
Ok so I can just go ahead and replace the tmp411A from cell side of KTE-001 with the tmp411A from cell side of PQX-001 right.
Btw can you point out what other components are associated with tmp411A circuit and is the cell id general or CPU specific. Also can I use the tantalum caps from KTE-001 motherboard for my fat dia-002 it has 3003,4 errors
Click to expand...
All the the temperature monitors (chips) of the PS3 motherboard are directly connected to syscon using a shared 2-wires bus named SMBus... that is based on the I2C protocol
https://www.psdevwiki.com/ps3/Thermal
https://en.wikipedia.org/wiki/System_Management_Bus
https://en.wikipedia.org/wiki/I²C

In other words, all the temperature monitors of the PS3 motherboard are connected to the same 2 copper traces, and that 2 copper traces are also connected to 2 syscon pins/pads
Syscon is the "master" (responsible to monitor the 2-wires bus) and every "slave" device connected to the bus needs to have an unique identifyer (usually named "I2C address")

The I2C address of the TMP411A is mentioned in the datasheet, as far i remember (written in wiki) is 0x4C
The syscon firmware have that value hardcoded and everytime a slave device is trying to communicate with syscon using identifyer 0x4C the syscon firmware translates it into "this is the temperature monitor for CELL"
There are a bunch of syscon firmware versions for all the diffeernt PS3 motherboards, i dont know if this identifyers changed along time

I mentioned that is important to dont swap them because if you replace a TMP411A by a TMP411B there is going to be a conflict because both are telling "im the temperature monitor for RSX" and syscon is going to ignore them :)

The temperature monitors have some registers in a embedded memory inside them, used to configure them, but we dont know if the I2C address can be changed, probably not posible

The old temperature monitors of the PS3 fats are a bit different because the I2C address is given by "bridging" the pins, the same component could have different I2C address depending of how/where you solder it
Is explained in the wiki page, there are up to 8 posible values

Im not sure about the idea of using the tantalum caps from a KTE-001 motherboard in a DIA-002, im sure that are good quality, but im not so sure if they could handle the workload
It could happen that works fine for a short time of days/weeks but eventually could fail because was working under high stress
 
Last edited:
sandungas said:
All the the temperature monitors (chips) of the PS3 motherboard are directly connected to syscon using a shared 2-wires bus named SMBus... that is based on the I2C protocol
https://www.psdevwiki.com/ps3/Thermal
https://en.wikipedia.org/wiki/System_Management_Bus
https://en.wikipedia.org/wiki/I²C

In other words, all the temperature monitors of the PS3 motherboard are connected to the same 2 copper traces, and that 2 copper traces are also connected to 2 syscon pins/pads
Syscon is the "master" (responsible to monitor the 2-wires bus) and every "slave" device connected to the bus needs to have an unique identifyer (usually named "I2C address")

The I2C address of the TMP411A is mentioned in the datasheet, as far i remember (written in wiki) is 0x4C
The syscon firmware have that value hardcoded and everytime a slave device is trying to communicate with syscon using identifyer 0x4C the syscon firmware translates it into "this is the temperature monitor for CELL"
There are a bunch of syscon firmware versions for all the diffeernt PS3 motherboards, i dont know if this identifyers changed along time

I mentioned that is important to dont swap them because if you replace a TMP411A by a TMP411B there is going to be a conflict because both are telling "im the temperature monitor for RSX" and syscon is going to ignore them :)

The temperature monitors have some registers in a embedded memory inside them, used to configure them, but we dont know if the I2C address can be changed, probably not posible

The old temperature monitors of the PS3 fats are a bit different because the I2C address is given by "bridging" the pins, the same component could have different I2C address depending of how/where you solder it
Is explained in the wiki page, there are up to 8 posible values

Im not sure about the idea of using the tantalum caps from a KTE-001 motherboard in a DIA-002, im sure that are good quality, but im not so sure if they could handle the workload
It could happen that works fine for a short time of days/weeks but eventually could fail because was working under high stress
Click to expand...
Alright then its a straight-up transplant.
what else should I test/replace along with tmp411A.
 
Fallen777 said:
Alright then its a straight-up transplant.
what else should I test/replace along with tmp411A.
Click to expand...
Thats all, because there is no other components in between the temperature monitors and syscon
In between the temperature monitor and CELL there are 2 traces with a tiny SMD resistor in each trace (and a tiny SMD capacitor connecting them), but as far i know this 3 components doesnt uses to fail
 
sandungas said:
Thats all, because there is no other components in between the temperature monitors and syscon
In between the temperature monitor and CELL there are 2 traces with a tiny SMD resistor in each trace (and a tiny SMD capacitor connecting them), but as far i know this 3 components doesnt uses to fail
Click to expand...
alright then now I just wait till the scrap kte-001 arrives rest will follow after transplant.
bts the way can you pinpoint the traces and components connected with tmp411a I can't open the console before the donor board arrives and want to be ready knowing what to replace with what and measurements also.
@RIP-Felix @vyktormvmpay25 can you guys point out component and confirm this fix.error 1200 pqx-001
Thanks in advance
 
Last edited:
Don't have YLOD yet but was curious of syscon codes from previous owners. Any idea what this code is it repeats 32 times.
A0802022 from years 2006/2007
 
You must log in or register to reply here.

Similar threads

Back
Top