Hey everyone, I've got an original Xbox console (version 1.6) that I modded with Modxo/PrometheOS loaded on a Rasberry Pi Pico, and it's giving me a headache. Hoping someone can give me some insight.
Problem:
-Console has a 60% change to freeze during the "flubber" bootup animation. If I change the boot animation to a pre-recorded video instead, works fine every time.
-Console will sporadically freeze while playing StarWars: Knights of the old Republic. Generally happens during dialogue, but will also happen while running around the world. Never in the menus. Happens in other games too, but this is the best example.
-Console will freeze in the PrometheOS menus, specifically and only if I am transferring large amounts of data to/from the HDD.
Repair attempts:
-Replaced every capacitor on the motherboard (other than the few tiny surface mount ones), CPU caps are the recommended low ESR caps. Removed non-low ESR caps installed by mistake to no affect.
-4 Different Hard Drives (2 SATA with an adapter, and 2 original, placing these setups in another xbox worked perfectly fine)
-2 Different IDE Cables (again, both worked in other xbox)
-Re-soldered all solder joints relating to the mod on both the pico and the mother board
-Re-soldered LPC Rebuild multiple times
-Re-soldered IDE and Sata headers on both adapter board and mother board
-2 Different PSUs (Admittedly, I don't have another xbox to test these in, but it seems unlikely that they'd both be broken in the same way.
-Shortened the wires to the mod board (They are about 4 inches long now, did not change anything, and I've also done this the same way on 2 other xbox, so I really don't think this is it.)
-Shoved a piece of foam behind the adapter board to prevent the lid from dislodging the adapter board from the HDD (This did make a pretty big difference in how frequently the game crashes, but not the boot animation, and the problem persists even when the lid is off.)
I have also used Xbdiag to stress-test the GPU, CPU, and RAM, all passed with no issues after 30 minutes each.
I think that this all points to there being some fault in how the motherboard is communicating with the HDD, but I just don't have any more ideas on where that fault could be.
Grateful to anyone who has an idea as to next steps, Thanks!