startup error in liberated Agilent / Keysight DSO-X 3014A  - Page 1
Forum section: electronics / testgear

author: Blue
author_rank: Regular Contributor
timestamp: November 08, 2021, 12:01:03 pm
content: I get (sometimes) the following error when starting up my scope:Rebooted due to exception 0xC0000005 address 0x4027236c.Firmware version: 02.65.2021030741 (liberated - see other thread).It also contains a Lan card without vga output.Hardware selftest performed without any problem.Anyone any idea? The scope is about 10 years old. I think it contains an internal battery. Never checked if it does nor replaced.

author: msquared
author_rank: Regular Contributor
timestamp: August 26, 2022, 03:37:20 pm
content: I'm having the same issue with my unliberated, never opened MSOX3054A which is also about 10 years old. It only happens if the scope is powered off for a few days so it really does feel like a battery issue.Did you ever happen to find a resolution?Thanks.

author: TheSteve
author_rank: Unknown
timestamp: August 26, 2022, 07:13:59 pm
content: Quote from: msquared on August 26, 2022, 03:37:20 pmWhat firmware version is in your scope? Your problem sounds like NAND corruption which only gets worse in time and will prevent the scope from booting. If you're not running the latest firmware now is the time to upgrade before it fails completely. The newer firmware will remap the bad blocks and likely fix any issues. This is much easier than recovering a non-booting scope.It will not be a battery issue, it only retains the clock data.

author: wraper
author_rank: Unknown
timestamp: August 26, 2022, 07:20:41 pm
content: Quote from: TheSteve on August 26, 2022, 07:13:59 pmYes, these scopes have a NAND corruption issue. You you could get them repaired for free even after warranty expiration, but that free repair program ended already. Since you are using latest firmware, it likely self repairs as mitigation as it was included in latest firmware versions. But I would reflash the firmware anyway.

author: msquared
author_rank: Regular Contributor
timestamp: August 26, 2022, 07:42:58 pm
content: Thanks for the replies.I've owned the scope since 2014 and have always updated the firmware within a few days of new firmware being available. I've read about the NAND corruption issues and was hoping I avoided it by keeping the firmware updated. Currently the scope is running 02.65.2021030741.Also I only see the issue is the scope is powered off (still plugged in) for more than a few days.btw.Has anyone ever replaced the coin cell in the 3000? I looked at Dave's old tear down video and there's a soldered in battery on the board.

author: msquared
author_rank: Regular Contributor
timestamp: October 24, 2022, 05:03:06 pm
content: Just a quick follow up if anyone else runs into this issue.Before opening up the scope I decided to flash the firmware again. (Same version 2.65)Well it's been a few months and the the scope no longer suffers from the error. It's been powered off for up to a month and it comes back on with no errors and no issues. Thinking back the issue started right after flashing it to 2.65 the first time I'd just been ignoring since I wasn't seeing the error unless the scope was powered off for bit. Looks like it may have been a bad flash to begin with.Hope this helps someone in the future.