First true Kronos CRASH (EVER) since updating to 2.1!

[NuSkoolTone]

Ok Just ordered one. CyberPower Ecologic EC850LCD 850 VA 510 Watts. Cheap and only like 10lbs. I can deal with that as "Extra" weight.

[LZ]

I use one of those "power strip" style UPS's and run my Kronos, a controller, and my rack gear off of it and have had it keep my stuff on for a good solid 10 min or so when stage power went dead. Just don't run any amps/monitors off of it (although I once ran the Kronos and a K10 off of it for a song at a wedding rehearsal at a park where they didn't turn on the power in the pavilion for the rehearsal).

My old band (pre-Kronos) was pulling around $250k a year and I had a complete duplicate backup rig just in case. I didn't bring it along as almost all gigs were local. s**t happens, and even in a pro gig like that, they have to understand that it can happen. The important thing is that it's a rare occurance and that you handle it professionally. Once during a set, my main keyboard died. We did a quick rearrange of songs that I was able to cover with my 2nd keyboard. Meanwhile, a quick call to a buddy who had a key to my house. By the end of the first set, he came walking in with my backup. Went on break, swapped out keyboards, and was good to go the rest of the night.

Even if you don't have a complete duplicate rig, part of being pro is having a contingency plan. If you're running drum loops, etc... record them so that in a pinch, you can switch to tracks and play your parts on a backup board.

[SwissArmyKnife]

I've owned the Kronos basically ever since it came out. Once in a blue moon it would get a little quirky if left on for days (or weeks) at a time but after a reboot it was always back to normal.

Last night I had rehearsal and a TOTALLY different thing happened. In the middle of playing it just flat out CRASHED AND SHUT DOWN.

It went to a black screen with small white writing that said something similar to: "Kronos has shut down because of an error. This can happen from power recycling too quickly. Shut down the Kronos, wait 10 seconds, and reboot."

I was simply playing a Piano in combi mode with the drum track going (Drummer not on this rehearsal, we're just learning new tunes). It just crashed out of NOWHERE and the keyboard went silent and everyone (including me) were like WTF? My band leader looked at me IMMEDIATELY and said "That BETTER not happen on a wedding! What would have you had done if this was at a gig?" So let's just say I was slightly embarrassed and not good for me as a player as my band leader is somewhat of a technophobe to begin with.

So here was my setup: The keyboard may have been setup and powered on for a DAY. I was in a basic combi that had Piano local, a violin played from a controller, a percussion patch hooked up to nanopad2 and the drum track going. That's it! There were no obvious fluctuations in power at the house, and now I'm wondering if I should roll back my OS and firmware?

The new organ is great, but this is NOT COOL. I can only attribute this to the new update because this is the FIRST time I've seen this message or had this happen in TWO YEARS and I gig with this board a LOT. Should I take it apart and make sure the RAM is still firmly seated? That's the only NON-OS thing I can think of since this board travels a lot. But again, FIRST TIME in two years and now all the sudden after the update. Just oddly coincidental!

PLEASE look into this!

I honestly don't have an answer for you, but I can at least share your pain. Haven't owned mine nearly as long as you have, but the moment I installed OS 2.1, mine went black. Everybody told me the same thing ... power supply issue, hardware issue, etc. It makes sense, except that I had operated mine on OS 2.0.6 without a glitch.

After two weeks of fiddling with it -- still unable to keep it running for more than an hour -- I back-installed OS 2.0.6. Guess what? It has run all weekend without a problem.

Don't know why OS 2.1 would be buggy for some keyboards and not others, but I'm beginning to think that's the case. I could be wrong. But I just wanted you to know ... you're not crazy.

[TheWolf]

Many years ago I had a similar problem when installing a new Linux kernel on my PC. The problem was caused by faulty RAM in the location where the Linux kernel itself was loaded to. With the old kernel, the fault happened to be located within a kernel function that was never (or rarely) called, so everything seemed fine. The new kernel put something fairly important there -- and crashed as soon as the corresponding kernel function was called. Replacing the faulty RAM solved that particular problem.

So yes, a software update can indeed trigger problems that have been dormant so far. And then it looks as if it were the fault of the new software while the true cause of the problem is something else.

If it was my Kronos that crashed regularly, I would contact service.

[SwissArmyKnife]

Many years ago I had a similar problem when installing a new Linux kernel on my PC. The problem was caused by faulty RAM in the location where the Linux kernel itself was loaded to. With the old kernel, the fault happened to be located within a kernel function that was never (or rarely) called, so everything seemed fine. The new kernel put something fairly important there -- and crashed as soon as the corresponding kernel function was called. Replacing the faulty RAM solved that particular problem.

So yes, a software update can indeed trigger problems that have been dormant so far. And then it looks as if it were the fault of the new software while the true cause of the problem is something else.

If it was my Kronos that crashed regularly, I would contact service.

Really interesting. Thanks for sharing that.

It will give me something to add when I talk to service.

[TheWolf]

Well, just thinking loudly...

If this were indeed a pure software problem, then more (or even all) folks would be suffering from it (see the MIDI bug mentioned in other threads). If it were a pure hardware problem, then you would see it under all software versions and downgrading would not help.

That's why I am speculating about the possibility of a hardware problem that triggers under the new software only. This does not necessarily mean that it must be bad memory. Could also be a thermal problem, a power problem, a timing problem and many other funny things....

[BillW]

It went to a black screen with small white writing that said something similar to: "Kronos has shut down because of an error. This can happen from power recycling too quickly. Shut down the Kronos, wait 10 seconds, and reboot."

Had this happen to me at a rehearsal last night. I cycled the power and it worked ok for the rest of rehearsal.

Has this recurred for you NuSkoolTone? How did the CyberPower UPS work out?

[NuSkoolTone]

It went to a black screen with small white writing that said something similar to: "Kronos has shut down because of an error. This can happen from power recycling too quickly. Shut down the Kronos, wait 10 seconds, and reboot."

Had this happen to me at a rehearsal last night. I cycled the power and it worked ok for the rest of rehearsal.

Has this recurred for you NuSkoolTone? How did the CyberPower UPS work out?

I haven't had any power outages, but testing by pulling the plug the UPS has been rock solid for gigs thus far. It stays in my bag for gigs only, so can't comment for rehearsal. However I haven't had the issue since.

[BillW]

It went to a black screen with small white writing that said something similar to: "Kronos has shut down because of an error. This can happen from power recycling too quickly. Shut down the Kronos, wait 10 seconds, and reboot."

Had this happen to me at a rehearsal last night. I cycled the power and it worked ok for the rest of rehearsal.

Has this recurred for you NuSkoolTone? How did the CyberPower UPS work out?

I haven't had any power outages, but testing by pulling the plug the UPS has been rock solid for gigs thus far. It stays in my bag for gigs only, so can't comment for rehearsal. However I haven't had the issue since.

I was really asking whether it has ever crashed again on you.

Mine crashed Wednesday night in rehearsal. I had it hooked up to a power strip that I always use there. This time, I had a powered speaker plugged into the same power strip (which might have had some effect on the power). I used the Kronos last night for 6 hours and it was fine.

[jameslol]

All you need is bringing your keyboard to Dealer. They will properly find-out soon.

[kbrkr]

I don't recommend leaving the keyboard powered on for such lengthy amounts of time. Forget the power stability issues, heat is your enemy. The fan inside the Kronos is not that big and does not move around a lot of air.

Electronic components can shut down if they get too hot. This probably won't happen on a gig since your are transporting the equipment and everything is powered down and outside in the cool weather. The gig is only 4 hours so it doesn't have that long a time to heat up to those high temperatures. You may want to be careful in the summer months playing in the direct sun. I have done that, but the Kronos was fine.