I got this machine a few weeks ago. It most likely had been stored in a damp place and it showed. Initially it seemed to be working well but the characters in the screen looked a bit off , like they had some 'ghosting' effect. Also some garbage showed up on screen randomly. The power connector also seemed to be not ok and if I touched the machine would glitch and power off and on again, it was wobbly. After I gave I gave it a clean it powered on normally just once more and as I touched the wobbly power plug it powered off and when I powered on again it shows just a garbled screen with some patterns. The patterns seem to change at every power on. Sometimes the border is a different color. Any idea? See pics
(https://i.ibb.co/gZDgkcmv/20250616-134933.jpg)
(https://i.ibb.co/zHjR3zWh/20250617-110149.jpg)
(https://i.ibb.co/DgSZJDzV/20250630-070831.jpg)
(https://i.ibb.co/h1Fbwpr4/20250630-070837.jpg)
(https://i.ibb.co/zHJRF8rG/20250630-070846.jpg)
(https://i.ibb.co/0R2F6Kq1/20250630-070856.jpg)
(https://i.ibb.co/pjVyWk3w/20250630-072607.jpg)
Hi,
the ghosting and dots are due to the video converter you are using, not a CPC issue. The power socket is obviously very dirty and/or has bad solder joints. Fix the power socket first and then see if you still have problems. If the patterns in the last pics still come after fixing the socket, then one or more RAM IC's failed while you were testing it.
Bryce.
Quote from: Bryce on 19:40, 30 June 25Hi,
the ghosting and dots are due to the video converter you are using, not a CPC issue. The power socket is obviously very dirty and/or has bad solder joints. Fix the power socket first and then see if you still have problems. If the patterns in the last pics still come after fixing the socket, then one or more RAM IC's failed while you were testing it.
Bryce.
Hi,
Thanks for replying. I did manage to desolder and replace the power connector with a new one. The original one was rusted and very dirty. However the situation did not change, I still see the patterns on screen. Would a diagnostic rom help pinpointing the failed chips? I am waiting for one such cartridge to be delivered in the next week.
Does this help Garbled Screen Amstrad CPC 464 video failure. (https://youtu.be/BLzHPf1IY8c?si=0ibcirI1sqrBIjPk)?
40007 you can't use without radiator/cooler
Quote from: Rabs on 20:58, 30 June 25Does this help Garbled Screen Amstrad CPC 464 video failure. (https://youtu.be/BLzHPf1IY8c?si=0ibcirI1sqrBIjPk)?
Thanks for the interesting clip. I am planning to study it very closely
Quote from: McArti0 on 21:18, 30 June 2540007 you can't use without radiator/cooler
I am not. What you see is just the stripped down board after I tried to remove and then re-insert the GA in case there was anything amiss. I noticed this chip gets quite hot and I am not planning to use it long term without its insanely thermal paste smeared heat sink
Would this kind of chip be ok as a replacement? I am trying to order some beforehand
(https://i.ibb.co/ztJtw0M/s-l1600.jpg)
You could have already broken 40007 without a cooler.
Quote from: McArti0 on 16:48, 01 July 25You could have already broken 40007 without a cooler.
I never had an issue with running a 40007 without cooler even for a little bit longer. I wouldn't run it for hours without the cooler but I didn't recognize a heat issue when I do a few tests without the cooler applied.
Quote from: salvogendut on 05:59, 01 July 25Would this kind of chip be ok as a replacement? I
yes
Quote from: McArti0 on 16:48, 01 July 25You could have already broken 40007 without a cooler.
Technically correct, but you'd have to run the CPC for quite a while. If the CPC isn't working, I doubt he was running it for more than a few minutes each time.
Bryce.
question for the wise ones: how can I debug ram chips without an oscilloscope? If I used an external rom box that is able to boot to a diagnostic program , would that tell me exactly which chips are failed? I have an ULIfAC , can I use that to boot a diagnostic rom? Would that work? I have seen Noel's Retro Lab videos where he is using a Dandanator with a diagnostic program that somehow shows red or green lines on screen corresponding to ram chips
After Swith On CPC. ROMDIS line to Vcc
O screen You should see narrow stripes.
Quote from: McArti0 on 19:52, 06 July 25After Swith On CPC. ROMDIS line to Vcc
O screen You should see narrow stripes.
Hey thanks for replying! I am not really familiar with the platform so if you could elaborate a bit what ROMDIS is and what should I do with it, that'd be super helpful!!
ROMDIS. Pin22 ROM ic103 cross to +5v like pin28
https://www.cpcwiki.eu/index.php/File:464Schematic_new.png
Quote from: salvogendut on 19:42, 06 July 25If I used an external rom box that is able to boot to a diagnostic program , would that tell me exactly which chips are failed? I have an ULIfAC , can I use that to boot a diagnostic rom? Would that work? I have seen Noel's Retro Lab videos where he is using a Dandanator with a diagnostic program that somehow shows red or green lines on screen corresponding to ram chips
First of all the good news: Your CPC is almost working. There's just a dead RAM IC (or a few) - and at least it does not have a full short but just does not work.
As RAM is not working properly your CPC fails during firmware initialisation as soon as it needs RAM. This will prevent you also from running any tools from a normal ROM board as it fails before further ROMs can be initialised. Therefore you need a ROM BOX that can replace the internal firmware. I'm not sure if the ULIFAC can do that - and if it can do that, if it can do it without a working CPC first. Some boards definitely can do that. E.g. Dandanator can do that, M4 also can do that. (Another option could be to replace the internal firmware PROM with an Eprom that contains Amstrad diagnostics - but that requires desoldering the PROM.)
If you have such a board or if you replace the firmware PROM you can use the "lower ROM" version of Amstrad Diagnostics. Amsdiag then runs instead of the firmware and can test your RAM. It also clearly shows which IC is malfunctioning. Check out the documentation on Github for more information.
Without such a board you might end up with A LOT of manual testing and you might have the chance of causing even more trouble. An accidental short at the wrong pin and another IC could be dead. If you have a desoldering gun and are familiar with replacing ICs the easier solution could be to just remove all RAM ICs put sockets in and replace the RAMs with known working ones.
Quote from: eto on 08:24, 07 July 25Quote from: salvogendut on 19:42, 06 July 25If I used an external rom box that is able to boot to a diagnostic program , would that tell me exactly which chips are failed? I have an ULIfAC , can I use that to boot a diagnostic rom? Would that work? I have seen Noel's Retro Lab videos where he is using a Dandanator with a diagnostic program that somehow shows red or green lines on screen corresponding to ram chips
First of all the good news: Your CPC is almost working. There's just a dead RAM IC (or a few) - and at least it does not have a full short but just does not work.
As RAM is not working properly your CPC fails during firmware initialisation as soon as it needs RAM. This will prevent you also from running any tools from a normal ROM board as it fails before further ROMs can be initialised. Therefore you need a ROM BOX that can replace the internal firmware. I'm not sure if the ULIFAC can do that - and if it can do that, if it can do it without a working CPC first. Some boards definitely can do that. E.g. Dandanator can do that, M4 also can do that. (Another option could be to replace the internal firmware PROM with an Eprom that contains Amstrad diagnostics - but that requires desoldering the PROM.)
If you have such a board or if you replace the firmware PROM you can use the "lower ROM" version of Amstrad Diagnostics. Amsdiag then runs instead of the firmware and can test your RAM. It also clearly shows which IC is malfunctioning. Check out the documentation on Github for more information.
Without such a board you might end up with A LOT of manual testing and you might have the chance of causing even more trouble. An accidental short at the wrong pin and another IC could be dead. If you have a desoldering gun and are familiar with replacing ICs the easier solution could be to just remove all RAM ICs put sockets in and replace the RAMs with known working ones.
Thank you
@eto , this info is very helpful. I am waiting on a dedicated diagnostic rom cartridge to arrive and then we'll see! Grazie!
Ok here we go. These are the pics from the diagnostic cartridge. Can you guys help me locate the offending RAM chips?
(https://i.ibb.co/rGwXVhS6/20250708-131134.jpg)
(https://i.ibb.co/Ng6PP1H3/20250708-131052.jpg)
(https://i.ibb.co/fG4JC4bn/20250708-131517.jpg)
from: https://github.com/llopis/amstrad-diagnostics/wiki
Quote from: eto on 15:07, 08 July 25from: https://github.com/llopis/amstrad-diagnostics/wiki
Thank you!!! As soon as I get replacement chips I'll try swapping them.
@salvogendut Please Fit sockets before the Ram Chips
Thanks
Keep Safe
Ray
Quote from: Audronic on 06:17, 09 July 25@salvogendut
Please Fit sockets before the Ram Chips
Thanks
Keep Safe
Ray
Will do! Thanks
And finally success. I was able to desolder the older chips and replace them with sockets and fresh ram chips. I gotta thank each and every one of you who encouranged and helped me with this. I have learned so much! Thank you!!
(https://i.ibb.co/bMHfM7kM/20250711-152044.jpg)
(https://i.ibb.co/RGBn0hPB/20250711-152318.jpg)
and now the real fun begins! Any other fans of Spindizzy?
(https://i.ibb.co/BH3rNGLy/20250711-210956.jpg)