CPU Address error HELP !

Did anyone has experienced this message on startup? Message says : CPU Address error(read). and after error there is commands and addresses. MPC 1000 is frozen at this point. However tried to put the OS 2.12 and JJ os 3.08, both installed successfully, but error at startup remains.
Could somebody suggest a cure? Please help.

contact vstservice.com there is a problem with your core processor

Opened machine, checked for loose contacts. Somehow got it booted up. That means processor board is ok. But it seems the problem is in pads triggering itself. It works for some time and then crashes. When sequencer window is opened it is visible that f....n pads are trigerring itself. And some weird combination af sounds is heard. And than comes that CPU address error and machine hangs up.
Could that be pad problem???

Anything is possible, but I'd think it unlikely that it's a pad problem causing this issue.

Might be worth disconnecting the pad ribbon cable and booting up and see what happens though. Never done this personally so I can't say if you will or will not get any problems from them not being connected. You won't be able to do much, but see if you can use the arrows and such to move around.

Disconnected ribbon cable for pads. The problem still exists Pads are not the cause
Does somebody knows some diagnostic software for MPC? Would be much appreciated.

SpaceRider wrote:Disconnected ribbon cable for pads. The problem still exists Pads are not the cause
Does somebody knows some diagnostic software for MPC? Would be much appreciated.

Run the memory test (forget how to start it) and make sure the memory is in tight?

Refer to my original post. If your looking for an easy fix you will not find it. There is a problem with your CPu and unless you are an akai tech you will not be able to fix it. Contact vst. The only debugging software is in akais possesion.

Memory test- OK. Press PLAY while powering up.

Hallelujah...

The cause was cheap connectors Akai used to connect between boards. All overhauled and contacts cleaned. Noo moore errorrs

"The cause was cheap connectors Akai used to connect between boards. All overhauled and contacts cleaned"

I have the same problem, what do you mean by all "overhauled and contacts cleaned" how do do that on my mpc 1000.

@SpaceRider Where did you go to get the problem fixed?

I'm experiencing kind of the same problem.
I bought my MPC1000 2 months ago, brand new.
Problems started 1 week ago.
I happens randomly... I start working and sometimes it just crashes... It suddenly starts triggering random pads fast and then crashes.
First time it said:
CPU address error (write)
and last two times it's saying:
Illegal general instruction exeption

I'm worried. I use it everyday.
I have to say, this last 2 weeks weather has been a bit too hot, could that be the cause?
I re-sitted the 128 ram and re-installed the OS already (JJOS2xl latest version) hoping that would help but it happened again today.
By the way, it's the last MPC1000 version, the one with the good pads.

Any help would be really appreciated guys.

SOLVED

This is not a bad CPU.

You may see this along with other errors, and the most likely cause is your CF card, or hard drive / zip drive..
if the disk is bad, it can't write on it. get a new one, then format it with the mpc before doing anything.
NEVER repair an MPC disk in OSX or windows.

Chkdsk and disk utility will also cause this. If you are not sure - back it up, format it on another mpc, or just format it fat 16 for now, then if you can boot then go to load > format immediately.

Hello everyone, I'm new to the forum. AKAI MPC 1000 expanded w/ 128MB here. I had a similar problem [SOLVED].

CPU address error (read)
PC(8844cfe4) SR(40001060) TEA(7f027b13)

After cleaning and restoring the sampler, as I do every year, I started encountering this error at some point. The sampler would crash when I installed the 128MB RAM, but worked fine without it. So, I decided to replace the RAM with a new one.
The problem was solved, but be careful with the length of sample names (max 16 characters). In some cases, it can cause a CPU error.
It's a good idea to leave some extra space—at least 2 or 3 characters—when naming samples that you plan to trim.
Maybe I just wanted to test it in the most extreme way possible, but after all, it should be built to handle the maximum allowed sampling time without crashing, so I kept going to understand the problem.
I ran into an issue where the sampler would save a new chop using the same number on its name as an existing sample, without asking if I wanted to replace the existing one. After a while, it would crash.
I was losing my mind over it haha but the solution was the simplest one I could imagine. Maybe it was just a distraction on my part, and it's a basic testimonial for beginners, but it might help someone.
Good work to you all!