I have a 2014 mxzx 800 etec with a stator eating problem all a sudden this season. Currently sitting at 7200 miles on it with ski-doo putting a new motor (under warranty) in it at 3600 miles due to a coolant ingestion problem.
Stator 1: I put about 400 miles on it this season then all a sudden the stator went but still ran fine at idle and up to about 3500rpm. After getting it apart and everything testing out fine, per ski-doos service manual, i built a "bridge" between where the stator connects to the sleds wiring harness and did my testing. Found the voltages were all over the board above 3500rpm. Took the stator out and it was fried. Checked and replaced thinking it was just another stators time to go. Fly wheel is the newer flywheel and is free of any marks. Roughly 3200 miles on this ski-doo stator.
Stator 2: SPI aftermarket stator. Made it about 300 miles then it throws check engine lights just like before and shuts down only this time not to restart. Took the stator out and sure enough it was fried. SPI claimed it was a faulty stator, sent me a new stator.
Stator 3: SPI aftermarker stator. Made it ~90 miles on it and once again the check engine lights show up but it still runs fine with no check engine lights under 3500rpm. Took it apart and once again we have a fried stator.
Here's some of the troubleshooting I've done. Gone through all the wires that I'm able to see looking for cuts or melted wires. Cleaned up all the grounds. Checked the voltage regulator and capacitor and they are in spec per the service manual.
I know a couple other people running SPI stators without issues so I'm fairly confident it's not just a poor aftermarket stator. My thoughts are I'll pony up the big $$$ to throw a ski-doo stator on it and haul it straight to the dealership to see the BUDS system can find anything as I'm seeing, per the service manua,l they do have some electrical system monitoring built in. To me there's certainly something else causing this but about all I can point back to is the voltage regulator that's built into the ECM...
Has anyone seen an issue like this or able to point me in a direction of things to check? Thanks