News:

PSR Tutorial Forum is Now Back to Life!

Main Menu

Unaxpected error

Started by amadeusorrento, Feb 07, 2025, 06:03 AM

Previous topic - Next topic

amadeusorrento

Good morning
I purchased a PSR SX920 about twenty days ago (I had all the previous versions).
Yesterday while I was playing the keyboard it stopped giving me a screen with "unexpected error" and I only solved it when I turned the instrument off and on again.
Has this problem happened to anyone? I updated to version V1.11

Thank's
Antony
  •  

Amwilburn

I acutally have, but not since updating it to 1.11

Previously it was almost always after loading a custom style or registration (that I didn't create myself) but I've had no such BSOD since; perhaps double check your firmware?

Mark
https://www.youtube.com/user/MarkWilburnTLM/videos

Guets are not allowed to view links. In order to access the links, please Register or Login
Mark Wilburn

https://psrtutorial.com/perf/markWilburn.html
  •  

DaPaleRider

Quote from: amadeusorrento on Feb 07, 2025, 06:03 AMGood morning
I purchased a PSR SX920 about twenty days ago (I had all the previous versions).
Yesterday while I was playing the keyboard it stopped giving me a screen with "unexpected error" and I only solved it when I turned the instrument off and on again.
Has this problem happened to anyone? I updated to version V1.11

Thank's
Antony

Have you installed expansion packs, custom styles?
Yamaha CK61, Yamaha PSR-SX920, Yamaha SEQTRAK, Korg Pa5X, Roland Boutique D-05/TR-08, Roland Go:KEYS 5, Roland AIRA S-1/T-8/J-6, Logic Pro,
  •  

amadeusorrento

I haven't installed any expansions, but I often modify or create my own styles from the USB. I like to use the STYLE CREATOR ASSEMBLY or create new Styles. When it failed I was playing one of these styles
  •  

Leading Edge

I had exactly the same problem.  It was caused by a 3rd party style.  When I removed the offending the style the problem was resolved.  I called Yamaha for help on this problem and they immediately asked if I had loaded and new 3rd party styles as this could have caused the problem.  Luckily, I remembered the last style I had added so it was easy to remove the offending style.
  •