GMAL error 04

Discussion in 'FirstDefense-ISR Forum' started by Egelie, Aug 1, 2011.

Thread Status:
Not open for further replies.
  1. Egelie

    Egelie Registered Member

    There is already a thread about Gmal. but it is very old.
    To day a met this error the first time.
    I don't know what is caused. But yesterday , deleted several snapshots and copied one snapshot and jumped to that snapshot goes well.
    Then i installed Perfectdisk 10 on it and defragmented it.
    to day i would jump to another snapshot, but the famous error comes up.
    so i have done nearly all what is mentioned in the Gmal rro -04 thread before.
    But nothing helps.
    it looks the only way is to remove the other snapshots, and then completely erase the snapshots.
    After this , do i stay in the last snapshot ?

    also, is there a doscommand to go to other snapshots ?
    Or knows somebody a other solutution ?

    Frits Egelie

    Extra: i used the dos option ISR control.
    a list gives all the snapshots but booting to it gives the same gmal 04 error
    Strange thing is: i can copy a snapshot but booting to it , i can't
    Last edited: Aug 1, 2011
  2. Egelie

    Egelie Registered Member

    I tried some other things . like renew the MBR. but nothing helps.
    I am now so far that i do format the whole drive C:

    But i like to know how to solve such a problem for the future.

  3. Longboard

    Longboard Registered Member

    "lo Egelie
    Sounds like you are experienced user :)

    THis hasn't popped up for a while.

    IIRC all the issues re "GMAL errors" usually resolved to a problem with the file system.

    This thread here:

    Although never expanded ( heh: Pandlouk never explained what he did to recover...suggests a reformat ??)

    Whatever happened screwed the FAT ??
    SO you could boot your "primary" ie the snapshot you were in ??
    Any other new installs ..of anything...there have been issues with other softs...likely to be more.. :doubt:
    Sounds like you might have been going through some housekeeping after new installs o_O

    FWIW, the last time I had a complete failure of copying/updating was when my HD was about to fail : many bad sectors...:p
    Required rebuild.

    I have also had intermittent issues with various tools usually AV apps with HIPS type options.

    You're not alone. :)

    FDISR is "Retire-ware" as we know.
    Got to treat it carefully...we lonely few. :D
    Likely to be some other conflicts..... consider other strategies in case of FDISR-fail.

    Reminder to have a good imager as well.

    I know notmuch help, just some observations...PM Panagiotis..ask what he figured out.

    WRT defraggers...I know PD10 is supposed to be compatible with FDISR, but ...I have had no issues with Power defrag and contig
  4. Egelie

    Egelie Registered Member

    thanks for the reply. Thinking about the gmal -04 error. it must be somewhere in the MBR/bootsector.
    When i am finishing installing all on My windows 7 64 bit, i go looking in the MBR to look where it is.
    Perhaps copying the MBR on regular basis looks to me necessarily.
    Strange that all look to work. I could even copy snapshots
    But i could not delete snapshot. This i have done with ISR tool.
    Even delteing all and excecute MBR does not help.
    I don't know any more what precisely changed with MBR execute.
    Not the partition tabel.
    But that is all for later.
    On this moment i have formatted my C: drive. Took a very long time.
    Installed Windows 7 and the Sp1. After that some basic prgr like Ashampoo uninstaller 4 and Windows 7 manager.
    I think i place also PD 10 on it. Nothing more.
    This all is my basic 64. I do copy it several times with ISR, and leave the basic64 on its own.
    Mainly, i use these snapshots for testing prgrs as beta -tester.
    You told you have lots of bad sectors ? Use Spinrite 6.0 for a while.
    Taht prgr knows how to handle wiht it.
    I know ISR is retirted. Some people of Raxco said it can't be used with Windows 7.
    But it can ! used it for a year or so.
    Regards .
  5. starfish_001

    starfish_001 Registered Member

    I had this same problem ... not sure of the root cause but I did the following

    • Defrag
    • disk check

    this did not fix I then uninstalled and reinstalled FDISR .... on boot this seemed to fix things.
  6. Egelie

    Egelie Registered Member

    i did the same, bit it idn't help.
    So doing all possibilities i know, there is one option left:
    Total format and install every thing new.
    Because of this reason i like to know a other good working solution.
    It may also be in hex mode to manupilate the MBR or other sector.

    Who knows the right solution ??

  7. Leapfrog Software

    Leapfrog Software Leapfrog Management

    Greetings All,

    The error GMAL-04 if for NR Buffer Overflow. NR(Non-Resident) records optimize the storage requirements and reduce the I/O overhead in NTFS. In this case, the number of non-resident MFT attributes has exceeded what can be stored in the buffer. It is likely that the internal MFT attribute buffer overflows first. Windows should be migrating these NR records out of the MFT, but rarely something in Windows causes the system to get to alarming levels before responding.

    Sadly, the legacy FD-ISR is unable to handle this situation. I wish I had better news.
  8. pratzert

    pratzert Registered Member

    Hi Todd.

    Thanks for that info.

    Nice to see you posting.

    How are things going for you ?
  9. Egelie

    Egelie Registered Member


    thanks for that information.
    perhaps Perfect disk 10 is debet on this situation, then i did delete some snapshots, three of them and after this using PD 10 to defragment.
    No trouble so far, but next day i would jump to another snapshot... rest you know.
    PD 10 handles the MFT. Can i take precautions for such a Gmal error 4 ??

    Frits Egelie
  10. Leapfrog Software

    Leapfrog Software Leapfrog Management

    Doing well. Busy.

    NR Buffer Overflow is something that should not happen often. It is controlled by Windows. Windows should not allow this condition to happen, and for the most part is doesn't. Nothing, that we know of, to trigger Windows to adjust NR migration.
  11. Longboard

    Longboard Registered Member

    Echo that :)

    Anything for us ?? :D

    Still one of the greatest tools... for this much thanks.
  12. Egelie

    Egelie Registered Member

    Still one of the greatest tools... ,

    indeed !
    And some do not know it works also with Windows 7 64 bit and 32 bit.
    Stronger !
    The company i bought FDISR told me it couln't.

    p.s .why is n't sold anymore !
Thread Status:
Not open for further replies.