TSH943a + 5.2xtrm works perfect for 5 minutes then wont eject.

[sparc]

I've read thousands of posts here over the years and this fault seems very similar to gigabites dead MT chip, supposing it does eject functions and not just dram.  This unit is an MS28a hw005 May06
It was originally flashed with 4.2a with no problems for a few months, it then started to throw e64 followed by e65 thereafter.
The guaranteed way of reproducing the fault is by turning it on, waiting 5 minutes for the components to heat and pressing eject.  The centre light would flash once for every eject press.  If I turn the unit off, then on again, the centre light will constantly flash, no eject and e64.  Sort of like modeb.
If I let the unit cool down for 10 minutes I can boot a game copy and originals no worries, after 5 minutes, the game will freeze, dashboard software gets real sluggish and no eject.  Turn off, then on..E64-65.
I've re-flowed just about every chip in the unit, tested every supply point and re-tapped the legs of the MT.  Re-flashed the original firmware and different xtreme firmwares.  The fault remains.
I've tested the 360 with an ms25 xtrm 5.2 with no problems, works a treat, so I know its the ms28a board.
Is there any other methods I have missed which cover this issue other than replacing the MT, and if I have to replace it, are we 100% sure its responsible for eject functions?

I should add that it was flashed via vcc method, well earthed (to pc).  When the drive stops ejecting, it is also un-detectable by pc.  Removing the hard drive makes no difference, continuity on cables and sata check out (even replaced them completely)

[glaze83]

e64 usually means a cable isn't plugged in, and e65 means the vcc point isn't reconnected.

Your eject motor could also be dead.

[sparc]

I mentioned in the post that the drive functions as normal for 5 minutes, first glance it looks as if its going into mode b by itself because the drive stops reading the disc also.  It will only show e64-65 after I turn it off.   Once its cooled down I can do the process again, same timing, same fault.
the vcc points are fine.  My status may be newbie but I'm waaaaaay beyond that, hense the minimal posts, I usually dont need help.  This one is interesting and not like any problem I've encountered.
I've replaced gpu and cpu chips in the past on multiple consoles and built a multitude of home made controllers,we have a large lab here with plenty of tools.
If you have an idea what it might be, let me know.
*this is not a repair* its research, sometimes replacing large components just isnt cost effective.

error e64 - code 1000
error e65 - code 1001

Something is slowly dieing, this is clear.  Just need to catch it, isolate and document.

[sparc]

Another little update..  When I insert a burnt/orig game when its working, its reads fine.  Once a few minutes have passed the drive spindle motor cuts out.  There is laser activity and power to the worm gear.  At this stage the eject button now doesnt work, this is starting to sound like a dud power reg or something up with the controller.  Most of the traces on the spindle line head out to the BD7909F Driver, could this be acting up, it heats up a helluva lot then goes cold (sounds solved huh)  Might try keeping it cool during operation to see the effects.  The DRAM also stays cool.

Question, the regulator that powers VCC, it runs quite hot, should it

[gigabite]

Nothing in the DVD drive should feel "hot" or at a blistering temp "as in when u touch it you get a blister) the big  chip in the middle (which l00ks like the MN103 in the Hitachi) should get warm but not blistering hot.  Have you checked the DVD drives power cable ? Also can you get individual Elite MT chips..if you can I am very interested please PM me

gigabite

[sparc]

There are variants you can use, the EliteMT has been around for donkeys, its just basic EDO dram that can be pulled from scanners, ram cards and other dvdroms.  I've seen memory expansion cards for old mainframe servers PACKED with dozens of MIIB (MT).
I'm now in search of voltage tests on a good ms28 for comparisons.  I'm pretty sure the Driver IC is to blame for the spindle cut out and theres something happening with the power reg, too hot.

The DriverIC is responsible for Tray, Spindle, Pickup and wormgear, when it gets too hot, it goes into thermal protection...  I will find whats cooking it!

[Arakon]

the driver IC usually has a heatspreader pad on top that is supposed to lead the heat to the drive casing. did you possibly lose that?

[sparc]

no, that is present, I'm replacing it with a higher thermal conducter block as the original only removes a small percentage of heat.  Board is currently outside the unit, all hooked up with a dirty big ram heatsinc on it..  the unit will run longer without the lockup.  Testing voltages as we speak.

[sparc]

ok, voltages on the vcc regulator is good, input loads are within limits, I'm still searching for the datasheet for the bd7909sf, There are variants, but I need to be 100%  This driver is the fault, and not due to vcc modding technique.  Currently conducting tests with heat sincs to cool this IC.  If all goes well, I will source a better grade controller and continue tests.  This unit was destined to die and report e64-65 code 1000-1001 SATA SMART thermal ID.  Even without modding.  I bet there is more out there, seems ms28a specific.
Running firmware with drive speed low, takes a little longer to go thermal, hense less power usage.  This ic just isnt up to the task, hmmm what to do.

[sparc]

The drive finally stopped working today, e64 is permanent and the pc bios cannot see the drive so I cant flash it without removing the pic.
Surely you can flash it if the firmware is up the $#!t, keeps detecting as an sst25vf040 which aint much help.

[sparc]

Whenever I have the ms28 board connected, PC HDD light stays on, the 360 eject light constantly flashes and mtkflash incorrectly id's the pic (defaults?).  Has it died completely or needs special loving.  I've tried hotswapping the unit in windows, VCC and 10sec, the drive stays online but wont communicate although the pc sata hdd is still operating.  Could the controller be naff (MT) or is the Elite chip cactus (gigabite?)  Its about to get stored in a box, any suggestions?

This is 1 ms28 in many 360's done at this workshop, a mystery and time waster at that.  I'd still like to know why it went south..