550D - Err 70 when saving image

[djig]

Hello

I am a new user and recently got hit by the apparently famous ERR 70 problem. I looked up at some of the numerous posts on the subject but I could not solve my issue so far and would appreciate any help in solving the problem.

I am using the 550D with 1.0.9 firmware and the lastest nightly build of ML. In my case I can access all menus and operate anything on the camera; but anytime I try to take a picture, I got the Err 70 message coming up on the screen, at the time the camera should try and save the picture. (which it does not)
I tried to reinstall the firmware, reinstall ML, switch SD cards, lens, clear all settings, format SD card to normal and low level but all this seems to have no effect.

I have no CRASH*.LOG file generated, but I got the normal log file in which I found the ERR 70 occurence but cannot make sense of anything above it, here is the extract :

  1625:  4441.062 [EM] emLockControl (TYPE_JOBSTATE = 0x0)
  1626:  4441.271 [RSC] SRMExMem1_1State Event 6 Result State 6->6
  1627:  4441.295 [RSC] hExMem1_2StateObject Through Event 6 State 0
  1628:  4441.968 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1629:  4442.161 [MC] JobState 0
  1630:  4442.415 [BIND] PROP_LAST_JOB_STATE (SW = 1, GUI = 0)
  1631:  4442.995 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1632:  4443.439 [EM] emAutoPowerOff : PERMIT (1)
  1633:  4443.627 [BIND] bindReceiveNewTFTOLC
  1634:  4443.668 [GUI_E] GUI_Control:86 0xae2a90
  1635:  4444.155 [GUI_M] copyOlcDataToStorage Length(7)group1(0x10)group2(0x00)
  1636:  4444.532 [GUI] MainEventHandler handleLastJobState(0x0)
  1637:  4444.894 [JOB] Trash (ID = 6201, dwHandle = 0x91918230, mode = 0x1)
  1638:  4445.293 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1639:  4445.401 [JOB] jobExecTrash (Keep = 0x4)
  1640:  4446.182 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1641:  4447.026 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1642:  4447.871 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1643:  4448.077 [JOB] Free = 0x4, Image = 0x0, Header = 0x0)
  1644:  4448.229 [FCACHE] fcacheReplaceFileCacheItem (ID = 0x91918230, 0, 0)
  1645:  4448.269 [FCACHE] ReplaceCacheItem : Removed (ID = 0x91918237)
  1646:  4448.927 [RSC] RealClearBusy(0x10000) 0x0->0x0,0x0(0x0)
  1647:  4448.962 [RSC] RealClearBusy(0x200000) 0x0->0x0,0x0(0x0)
  1648:  4449.146 [FCACHE] ReplaceCacheItem : Removed (ID = 0x91918238)
  1649:  4449.811 [RSC] RealClearBusy(0x10000) 0x0->0x0,0x0(0x0)
  1650:  4449.853 [RSC] RealClearBusy(0x200000) 0x0->0x0,0x0(0x0)
  1651:  4449.980 [FCACHE] ReplaceCacheItem : Removed (ID = 0x91918239)
  1652:  4450.619 [RSC] RealClearBusy(0x10000) 0x0->0x0,0x0(0x0)
  1653:  4450.659 [RSC] RealClearBusy(0x200000) 0x0->0x0,0x0(0x0)
  1654:  4451.624 [RSC] RealClearBusy(0x2100) 0x0->0x0,0x0(0x0)
  1655:  4452.365 [RSC] RealClearBusy(0x10000) 0x0->0x0,0x0(0x0)
  1656:  4452.402 [RSC] RealClearBusy(0x200000) 0x0->0x0,0x0(0x0)
  1657:  4452.587 [PTP] Dispatch : Cur = 0, Event = 8, Param = 0x0
  1658:  4452.617 [PTP] PROP_LAST_JOB_STATE = 0
  1659:  4473.343 [MC] DisplaySensor : 1(1)
  1660:  4473.813 [MC] Current DisplaySensor : 1
  1661:  4473.841 [GUI] MainEventHandler PROP_DISPSENSOR_CTRL(1)
  1662:  4473.865 [MC] Current DisplaySensor : 1
  1663:  4473.922 [GUI] StartShootOlcInfoApp
  1664:  4474.251 [GUI] DlgShootOlcInfo.c GOT_TOP_OF_CONTROL
  1665:  4616.830 < GUI Lock > GUILock_TurnOnDisplay (PUB)
  1666:  4616.935 < GUI Lock > GUILockTask 1
  1667:  4616.969 [DISP] TurnOnDisplay call
  1668:  4617.074 [DISP] TurnOnDisplay action Type=0
  1669:  4636.286 [DISP] VdInterruptHandler bmp=ff05ca90 img=0
  1670:  4720.793 [DISP] TurnOnDisplay finish Type=0
  1671:  4949.425 [MC] PROP_LV_LOCK : LVLOCK_PERMIT
  1672:  4949.579 [LVCFG] PROP_LV_LOCK PERIMIT
  1673:  4949.647 [LV] JudgeStartLV 0x1 0x1 0xFFFF 0 Rs:0 St:1 RecSt:0 l:8054
  1674:  4949.669 < GUI Lock > GUILock_PermitPowerLockOnlyImagePlay (PUB)
  1675:  4949.724 [IMPD]  (PUB) UnlockImagePlayDiriver
  1676:  4949.740 [IMPD]  SetLockState 350
  1677:  4949.762 < GUI Lock > GUILock_PermitPowerLock (PUB)
  1678:  4949.997 < GUI Lock > GUILockTask 1
  1679:  4950.036 [DISP] TurnOnDisplay call
  1680:  7070.622 [MC] Disp Error : 70

Please tell me if you can help or if I missed a similar case on the forum.

Thanks in advance

Matthieu

[a1ex]

Any lines saying ASSERT somewhere in the log?

[djig]

Thanks for the lightning fast reply.

I cannot find any ASSERT in the log file unfortunately

[a1ex]

If you update to latest nightly and take a full-res silent picture, what's the result?

[djig]

Sorry but is that feature available on 550D ? I do not see it under the SHOOT menu (and I have the 29MAR2015 build)

[djig]

FYI : I also just noticed that going into LIVE VIEW automatically lead to ERR70 directly after the shutter noise.

[a1ex]

In this case, we have to use a custom build.

autoexec.bin

In M mode, "don't click me", then upload dm.log.

[djig]

OK, I clicked where I should not have but was told to 

I got the following crash.log :

ASSERT: Iso != 0
at Param\HivshdParam.c:59, task ShootCapture
lv:0 mode:3

Magic Lantern version : Nightly.2015Mar29.550D109
Mercurial changeset   : 72720e9dbb41 (dm-spy-experiments)
Built on 2015-03-29 18:21:55 UTC by alex@thinkpad.
Free Memory  : 231K + 1025K

Please also find the link to the DM log :
http://www.fast-files.com/getfile.aspx?file=88804

[a1ex]

ASSERT: Iso != 0

Set ISO to a nonzero value

[djig]

Sorry !  I don't know how I had ISO at 0...seemed on AUTO mode after I reseted everything. I now put a 400 ISO and got this new DM.log file when slicking on "don't click on me"

http://www.fast-files.com/getfile.aspx?file=88806

[a1ex]

ShootCaptu:ff19fca4:91:06: Image Power Failure

Looks pretty nasty. What did you do right before getting the error?

I could ask you to send me your ROM files, and flash them on my 550D, just to rule out some unlikely ROM corruption. Not sure what else I can do to troubleshoot it...

[djig]

Well, nothing specific as in most ERR 70 it seems... I had it a few times on a holiday trip but back then I managed to get the camera back by just restarting it (battery off) as advised by Canon. It is recently back with no mercy, but I see no obvious trigger unfortunately. The first time I had it was on a rainy day (I saw similar post mentioning rain or splash on camera), but camera got barely wet so I doubt this is the reason of my problems.

Here are the ROM files :
http://www.fast-files.com/getfile.aspx?file=88809
http://www.fast-files.com/getfile.aspx?file=88810

[godovic]

I have also problem with this build.. Got a bluescreen error after taking a picture. Tried in M and Auto mode

[Walter Schulz]

Try recording some video ...