NDS - Fault 36 DSP ERR 2 - The 24 MHz

Alan I think that there is a software update fix that you can get from Naim for this.

My NDS is fine unless I turn it off, and then back on again, in less than about 30 minutes.  If I do that, I get that same error.  I need to reach out to Naim support too.

Good luck,

Bart

Hi Bart,

Thank you for your message.

Is firmware version 3.22 from Naim can fixed this problem?

I saw your previous posts and mentioned that the sound quality may decline when updated the firmware, is this true?

Thx.

Alan

The sound quality has been known to change. Improve, decline or no change is in the ear of the beholder. I thought the original firmware at launch, which was quickly superseded sounded best, not that anything subsequently release could be described as bad.

Hi Alan, unfortunately 3.22 doesn't fix this problem 

We're all waiting for Naim to address this problem permanently.

In the meantime, the fix is available from those nice guys at Naim - it's a software fix so can be loaded by you.

Thanks rjstaines.

I have nothing to say now

When I switch off my NDS, I need to wait for 30 min before I can use it

How long I need to wait to resolve this bug  .........

Just out of interest, Alan, you may need to wait more than 30 minutes.  When I first had this problem, 30 minute shutdown fixed it, BUT the last three times 30 minutes has not been enough - I've switched back on after 30 and the error is still there.  I now leave it for 90 minutes !!!  (and that fixes it... so far)

3.22 didn't solve it, but I've heard for many months that there IS a different patch they can apply.  My fault for not reaching out to support for this earlier.

Very disappointed !

Why NDS will have this bug and still can’t resolve it ???

Use the ndx dsp load instead, naim can provide details. That's what we're all doing until there is a new nds version.

I also had the problem. There is a fix which is still unofficial. To get it contact Phil Harris who answers very quickly.

Best,

Michel

In November 2012 in the thread about the 3.17 firmware Phil explained the exact cause of the fault 36 condition. In summary, an over zealous error check on clock timing differences. The bug was fixed for all other network players in this release and we were told a fix would be available for the NDS once it had passed listening tests... Roll forward 15 months and it still seems to be an issue.

So, I can only conclude that the fix must degrade the performance of the NDS in some way and that the occurrence of Fault 36 on the NDS must be relatively rare. Be good to get an official update though.

Luckily, I don't ever get the fault on my NDS... Doh, I've jinxed it now haven't I...

Can't help feeling:

1.  the fix priority is influenced by the perceived number of problem NDS's out there

2.  the perceived number of NDS's with the problem is far too low because many sufferers grin, power  cycle and bear it  !

Am I not right ?   

Hhhmmm, after 6 months of careful pre-positioning with the better half, I now have royal approval to switch from our CDS3/555PS to an NDS/555PSDR.  The main benefit?  Because it de-clutters the living room.  This really matters to the boss.  Much more so than to me.

Now I read about this.  It certainly makes one stop & think.  Perhaps CDs aren't so bad after all...

Yours teetering on the brink, FT

Brought my NDS in July 2012 and never had any problems with mine!!

I suspect some people do just power cycle to clear the problem. Once in a blue moon I have resorted to the same tactic when I can't get nStream to connect to the NDS. I wonder if there is any correlation between power supply type and frequency of fault? I'm using a 555 PS DR which I suppose is the natural partner to the NDS.

Hi Richard,

did you ever update your firmware? That's when the problem started occurring with mine.

Hi Jeremy I have updated all my stremers to 3.21 but not 3.22 and had no problems yet, so I must be lucky.