MPC 2000XL is betraying its master

So lately I've been experiencing some problems with my 2XL. When I shift 3 my programs there's a note that says "ERROR:BF(insert random numbers here)" I fix that problem by on/offing my MPC. It usually takes about 4 to 10 tries, no problem. (Not really, considering that I NEVER had to do this before)

The REAL problem is that when my MPC loads up the programs some of the sounds are hella distorted. I auditioned my sounds and noticed one of my snares ended up sounding like bad diarrhea. (No, like it sounded like it.) I have no idea what the heck happened.

ON TOP OF ALL THAT. My sound banks are bugging out. Sound bank A assigns perfectly but bank B, C, and D have this weird problem. When I assign a sound onto a pad the sounds don't play. Also, on the parameters the lines overlap the box/graph that displays the attack/decay/etc. There are also asterisks and weird symbols on the TUNE and various places on where numbers are supposed to be.

I have no idea whats going on guys. I'm ambivalent weather I should purchase a new 2XL or just try to repair it myself. I'm well aware that 2XL's tend to mess up. What should be my plan of attack?

Is there an MPC repair shop or someone in the Los Angeles area that can help me out with my machine?

HAAAAAAAAAAALP~

sounds like bad ram.

how did I mess up my ram?

if the RAM isn't seated correctly into the slots on the circuitboard, electrical shorts can cause RAM to go bad.

if it fixes or slightly changes the problem, it is the ram.

new ram is cheap if you want to go that route - but yea cleaning the contacts on the old ones is often enough to get it.

you messed up your ram by just using it - most likely moving the machine. gremlins maybe? did you load samples after midnight? entropy is inevitable.

lol you guys are hilarious. I flipped that sucker over and cleaned the contact points of the RAM. But to no avail the dreaded "BF0110111" continued to haunt me. I might just retire this machine because theres just too much to handle for me right now.

it could be bad ram.
or a bad connection somewhere.
or hell even try swapping the ram to different spots, if you are using two sticks.
if you could get new ram for cheap enough (you can), i still think its worth a try.

be worth giving the entire machine a once over and reseating all connections.

tapedeck wrote:it could be bad ram.
or a bad connection somewhere.
or hell even try swapping the ram to different spots, if you are using two sticks.
if you could get new ram for cheap enough (you can), i still think its worth a try.

be worth giving the entire machine a once over and reseating all connections.

I've tried taking the ram out and putting it on the other spot. No luck. That sounds like a very good idea but I run the risk of **** something up permanently because I have no experience with these machines what so ever.

can anyone point me out to the best RAM compatible with my 2XL?

Can you take the RAM out and try running it on the on-board 2MB RAM, to test if it happens without any RAM in the slots?

SimonInAustralia wrote:Can you take the RAM out and try running it on the on-board 2MB RAM, to test if it happens without any RAM in the slots?

yes - also a good way to rule out bad ram or not.
if you still have the problem, its something else.