Toshiba Satellite P70-A-11V MB:DA0BDBMB8F0 REV:F schematics

[Tiagocamara]

Hey guys

I have this dead P70.. No image in both internal and external monitor, did reset the bios, removed all peripherals, checked voltages around the board and all seem ok, except what I think is CPU vcore, 1.8v there (big cap on the other side of the board below CPU).

Gave some heat to GPU, no luck.

Fan spins, stops and spins then constantly.
looks great, no liquid damage, all clean, no dust.
do you guys have some ideas?

Also if someone has schematics i appreciate

thanks in advance.

[piernov]

Re: Toshiba Satellite P70-A-11V MB: DA0BDBMB8F0 REV:F

I've got Quanta BDBD and BDBE but not BDB, I don't know if they are almost the same.
1.7-1.8V for VCore on a Haswell CPU should be fine.

I guess the board is not POSTing at all (this is not just a "no display" situation).
Did you try to flash the BIOS?
CPU_RST#_R present?
+1.35V_CPU present?
Any activity on BIOS CS# pin?

[Tiagocamara]

Re: Toshiba Satellite P70-A-11V MB: DA0BDBMB8F0 REV:F

Didn't flash bios as i don't have a programmer.. Did see activity in bios pin 1 as I turn on, then stays at 3.3V

"CPU_RST#_R present?
+1.35V_CPU present?"

Dont know where to check that

[Tiagocamara]

Re: Toshiba Satellite P70-A-11V MB: DA0BDBMB8F0 REV:F

Got 1.29v and 1.7v around CPU caps, the first is +1.35V_CPU ??

[piernov]

Re: Toshiba Satellite P70-A-11V MB: DA0BDBMB8F0 REV:F

Probably. If you have activity on the BIOS CS# pin then the CPU reset signal must be present. And it means the BIOS is starting, but the POST fails. Which could be many things, but most of the times it is either:
— BIOS corruption, that's why flashing the BIOS in this situation could help
— Dead PCH
— Dead CPU
— Issue with RAM, but often the board will have a specific pattern in this case, either a beep sound or a LED flash. Try to remove the RAM to see if it does any of this.
It could also be any other chip: GPU, audio IC, Ethernet IC… or components. Check if the audio IC or Ethernet IC gets hot, check for burnt mark around the board too.
Without any clue it's really hard to diagnose this kind of issues.
If you have a POST diagnostic card, you can see on which code it stops, sometimes it helps, most of the times it doesn't.