Fault Code 61

Posted by: Mike-B on 31 May 2017

Anyone any experience of code 61 ??

This morning I found my NDX screen showing Fault 61 - BridgeCo init fail.  It was locked up or at least stuck on the fault screen.   It was not playing as such,  just ethernet connected to broadband & doing whatever that does.    

I fixed by power cycling,  the faults not returned so I assume a temporary glitch,  but its worrying not knowing the cause & what potentially might be required to actually fix it.       I've done a forum search & found some stuff,  also looked in 'Knowledge Base',  but nothing much that shows anything conclusive.    Any ideas ??

Posted on: 31 May 2017 by Huge

No experience of Fault 61, but plenty of experience of random 1 off fault occurrences with computer systems; they occur for many reasons, but the most random of which is an alpha particle strike on a memory cell or a processor register!

Posted on: 31 May 2017 by Mike-B

  Does that mean I need to house it 500m underground in a lead mine ???

Posted on: 31 May 2017 by Huge

Mike, that's definitely not what you need...

Lead is a decay product of Uranium 238 which is an α emitter (along with at least 10 other α emitters in the decay chain).

However none of those α particles will get through the plastic encapsulating the chip...  No, the reason for not living in a lead mine is the toxicity!  

Posted on: 31 May 2017 by Mike-B

Phew thats a relief, I was looking to see if I had any lead bearing strata under the garden.

Seriously though, I was aware of alpha strikes as we had a few experiences with marine data logging via satellite comms in my previous life. I understood the event risk could be reduced by better engineering/design & that was introduced about the time I retired so I did not see how effective the changes were.     That said it did not occur to me that this might be a cause of code 61.   Reading forum threads on this I previously said there was not much info, but there is mention of software corruption. Given that an alpha strike can cause minor disruption, data & software corruption some of which can be permanent defects, I'm still left concerned.

Anyone from Naim have any comments ???

Posted on: 31 May 2017 by Kevin Richardson

I kept getting Fault 35 at seemingly random times. After too much work/thinking/yelling/praying, I discovered that Netflix was messing with both my NDX and ND5.

 

 

Posted on: 01 June 2017 by DrPo

i had Fault 36 for a couple of years until Phil Harris recommended I send the unit back for a check. Turned out to be H/W problem. Now fixed.

Posted on: 01 June 2017 by Huge

I had fault DYLX, so I went to see a psychologist: She said I had dyslexia!

Still not fixed!