|
Korg Forums A forum for Korg product users and musicians around the world. Moderated Independently. Owned by Irish Acts Recording Studio & hosted by KORG USA
|
View previous topic :: View next topic |
Author |
Message |
Mezzopiano Junior Member
Joined: 10 Nov 2015 Posts: 57
|
Posted: Sat Feb 17, 2024 5:37 pm Post subject: About that dread message "A problem has been detected&q |
|
|
I know this has been discussed before, even on this same page is a thread that talks about this issue, i just have a different approach to the question
Im about to sell a Kronos X 88 that i got "kinda cheap" and ive been repairing and buying parts for it, now it looks better and feels better (purchased some Keys from Syntaur, etc)
Now, the buyer is a friend of mine, so it MUST work and lately it has been giving the dreaded message "A problem has been detected, turn KRONOS off 10 seconds.."
This message is differente from the one that says something about power cycling error, that one usually resolves itself when you upgrade the firmware...
It is already on the latest subsystem firmware and OS, i have reseated the RAMS several times (altough i tend to notice the error more frequently when KRONOS is moved around) and it keeps happening from time to time.
Yesterday i had enough and changed the SSD, cloned the original with Clonezilla. Now KRONOS boots up and has been running all night with no errors
The question is. Of all the times it has shows the message (that yo uare aware of), how many are due to loose RAMS? and how many due to corrupted SSDs? and more important, how many (%) are about faulty PSUs? This last one is my nightmare, because i dont have anywhere to get a Kronos PSU, or a compatible one for that matter.
I hope changing the SSD resolved the issue, i dont want to sell the KRONOS and some days later it starts going faulty again. |
|
Back to top |
|
|
KK Platinum Member
Joined: 13 Oct 2016 Posts: 1430
|
Posted: Sat Feb 17, 2024 8:38 pm Post subject: |
|
|
With the years here, I've read quite a few different diagnostics and conclusions about what could have fixed those problems. In short, I think it's very difficult to be 100 % sure even when such problems stop after changing something.
Common causes I would personally look for would be loose connections, too full or corrupt SSD, electric noise, voltage measurements on the PSU and important check points according to the repair manual, etc. The Kronos is a quite complex machine to program and master and also to repair. |
|
Back to top |
|
|
Gargamel314 Platinum Member
Joined: 25 Dec 2007 Posts: 1156 Location: Carneys Point, NJ
|
Posted: Fri Apr 05, 2024 5:17 pm Post subject: |
|
|
Shame on Korg for the extremely vague error messages.
Mine apparently needs a new motherboard. This was decided after the system continued to fail following changing the SSD, RAM, and that it crashed in the middle of the OS install. It's truly heartbreaking that such an awesome workstation is plagued by the unreliabilty that we've been experiencing. _________________ Korg Kronos-61, 01/Wfd, SONAR Pro |
|
Back to top |
|
|
SeedyLee Platinum Member
Joined: 13 Sep 2006 Posts: 1379 Location: Perth, Australia
|
Posted: Sat Apr 06, 2024 12:18 am Post subject: |
|
|
The reason for the vague error messages is that, due to the way the Kronos is architected, it would be hard to give more specific error messages without additional diagnostic hardware built in to the machine.
The message simply means that the ARM subsystem, which is responsible for panel operations and controlling what is displayed on the LCD during boot, is unable to communicate with the Intel subsystem, which is responsible for sound generation, user interface etc.
Because the ARM subsystem can't communicate with the Intel subsystem, there is no way for the ARM subsystem to inform the issue what the issue is, other than it couldn't communicate.
It could the SSD, preventing the Intel system from booting, power supply, preventing the motherboard from receiving adequate power, RAM, preventing the system booting, bad motherboard, bad CPU, or any number of other things. _________________ Current Equipment:
Korg Kronos 2 88, Reface CS, Roland JV-1080, TE OP1, Moog Subsequent 37, Korg ARP Odyssey, Allen & Heath Zed 18, Adam F5, MOTU MIDI Express XT, Lexicon MX200 & MPX1, Yamaha QY700, Yamaha AW16G, Tascam DP008ex, Zoom H6, Organelle, Roland J6 & JU06A
Previous: Triton LE 61/Sampling/64MB/4GB SCSI, MS2000BR, Kronos 1 61, Monotribe, NanoKontrol, NanoKeys, Kaossilator II, Casio HT3000, Roland VP-03, Reface DX, Novation Mininova, MPC One |
|
Back to top |
|
|
Gargamel314 Platinum Member
Joined: 25 Dec 2007 Posts: 1156 Location: Carneys Point, NJ
|
Posted: Mon May 06, 2024 3:53 am Post subject: |
|
|
In my case, it was a bad motherboard. I just had it replaced, and it's back to running fine, with my regular SSD installed. I really hope others find simpler solutions! This repair was both expensive, and time consuming (took 3 months!).
Thanks for your insight, SeedyLee _________________ Korg Kronos-61, 01/Wfd, SONAR Pro |
|
Back to top |
|
|
Xenophile Senior Member
Joined: 14 Nov 2017 Posts: 359
|
Posted: Mon May 06, 2024 9:57 pm Post subject: |
|
|
Gargamel314 wrote: | In my case, it was a bad motherboard. |
Could be. But it also could be coincidence. Maybe in the process of replacing the motherboard they jiggled or re-seated a nearby ribbon cable connection that was the actual cause of the problem, while the decision to replace the motherboard was just a generic, sledgehammer approach after they weren't able to identify the real problem.
There are too many variables, and not enough data to be absolutely sure of anything with these machines. |
|
Back to top |
|
|
Gargamel314 Platinum Member
Joined: 25 Dec 2007 Posts: 1156 Location: Carneys Point, NJ
|
Posted: Mon May 06, 2024 11:04 pm Post subject: |
|
|
Xenophile wrote: | Gargamel314 wrote: | In my case, it was a bad motherboard. |
Could be. But it also could be coincidence. Maybe in the process of replacing the motherboard they jiggled or re-seated a nearby ribbon cable connection that was the actual cause of the problem, while the decision to replace the motherboard was just a generic, sledgehammer approach after they weren't able to identify the real problem.
There are too many variables, and not enough data to be absolutely sure of anything with these machines. |
I pulled all the cables out of the mobo and put them back in, except for the ones that were hot-glued in, but I gave them a good little jiggle for good measure. I tried everything. _________________ Korg Kronos-61, 01/Wfd, SONAR Pro |
|
Back to top |
|
|
Mezzopiano Junior Member
Joined: 10 Nov 2015 Posts: 57
|
Posted: Tue May 07, 2024 5:38 pm Post subject: |
|
|
Well, hi again
I already sold the Kronos, looks like the issue was faulty RAMS (not just loose ones) so i got a brand new (and old) cheap 4 gb dimm that replaced both 2 gb ones in the Kronos
Havent had a problem since and my friend is happily using it on live shows |
|
Back to top |
|
|
Xenophile Senior Member
Joined: 14 Nov 2017 Posts: 359
|
Posted: Tue May 07, 2024 6:15 pm Post subject: |
|
|
I tried a little bit of Deoxit contact cleaner on my SO-DIMM contacts, and it _seems_ to have helped. I also bought a spare memory stick that I'll try if and when I start seeing our not-so-favorite error message again.
I am pretty sure that noisy AC power is a major contributing factor. One outlet in my home seems to be particularly troublesome. Also, in one rehearsal room that my band uses frequently there is one AC outlet that always makes my Kronos act up. But our other keyboard player uses that outlet for his Nord with no issues at all.
But it is really hard to make any conclusions when the failures are so random.
Very frustrating! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|