Cool,
did you reinstall the runtime to fix it?
Also can you check your antivirus logs, it would be useful to know if it was the culprit - some will quarantine files they think are suspicious.
Would be useful to know, as mighty reoccur or spear for others
Glad you can get back to patching 
I also reinstalled the runtime but that didnt work.
Zonealarm had blocked arm-none-eabi but after fixing this it still wasnt working.
Only a fresh install of the editor helped.
I didnt restart windows the first time I reinstalled.....
Hi and thanks philoop for also stepping in and telling your problems.
I am now home again and simply did try another reinstall again, it does go live now here again.
What I did different: I got 2 partinions on my one laltop harddrive C and D, I do install axoloti on my C program files, but this time i did install the runtime on the D partition and it did work.
Just for further info:
My windows is: Win 7 Professional Service Pack 1
Java and stuff I am right now not sure where to find, but if this is really important to you just say a word and I willl look it up.
Thanks for your kindly support, so now I am trying the midi clock stuff and get back with results.
I've just had the same problem (win 8.1 x64) and resolved it by deleting the build folder in \Documents\axoloti folder.
Had the problem again, dopnt knwo what issue is causing this, BUT you are right, i deleted the installation 3 times, nothing changed i got the error again, but when deleting my documents/runtime..blbalbalbaa folder it does work again now.
Just wanted to say that it seems to be the solution or workaround
i just experienced thesame issue, and i solved it by going to my documents>axoloti>build and delete everything in that folder
is the error still exactly the same as you had originally?
if this happens again, rather than deleting the build directly, can you just try to delete the xpatch.h.gch file
and then try to go live, and see if this fixes it.
also can you confirm it does it with all patches e.g. even the tutorial patches.
the issue is, this is not an axoloti bug as such, its the compiler crashing... so we need to determine what it is thats causing the compiler to crash.
whats obviously odd, is that it appears to be working for you, for months at a time, then suddenly stops...
so something must change... Im guessing its not something as 'obvious' as immediately after you upgrade Axoloti, as you would notice this... so its something outside of axoloti.
are others getting this regularly?
seems odd, johannes doesnt seem to get it... as he uses windows most of the time. (I dont)
I had this a fair amount today while testing out some new objects I have been working on. I'll try and see if there is any pattern when I continue tomorrow.
not really the 3 last times it had short message mingw32 error, sorry i didnt copied it, i will investigate further
its more like this
not soo urgent i guess, next time i will monitor closer what i did.
I haven't experienced this, maybe a the compiler was aborted somehow while generating the xpatch.h.gch file, but leaving a corrupt/incomplete file. Virus scanners are also suspect, quarantining the compiler, do you run any?
yeah, thats what I was wondering.... if deleting the build directory fixes it, then it sounds like a file that used across builds.
but even then, its odd... since the gch wont be changing, unless the firmware is updated... so how does it 'suddenly' become corrupt, if it was working before.
anyway, would be nice to narrow down , which file in the build directory is causing the trouble, then work out why 
btw, if deleting xpatch.h.gch doesn't immediately fix it, i.e. build still crashes, delete one file at a time in the build directory (remembering which you deleted!) and try again... though I think its only the gch file across builds.
(I guess we could have a 'secret key' e.g. pressing ALT whilst going live, which could perform a make clean, then make.)
I just experienced this. I'm running Win 10 and it just published an update and restarted my computer while the program was running. When I tried to load and compile any Axoloti patch, I would get this error. I restarted the computer and the error is gone. If you get this error, I recommend restarting your computer. Luckily it was an easy fix.
Just had this error again (hdan't had it since a long time), I just deleted the 3 files in the documents/axoloti/build folder and it works again, as usual.
Just thought I'd let you know
ok, so just got myself a windows laptop (something I'm surprised about too 
) and been playing with Axoloti on it (quite fun with a touchscreen, doesn't work too bad.)
and just encountered this error.
so, I can now confirm its the precompiled header that is the issue, if you delete xpatch.h.gch then the problem is resolved. it is corrupted.
a quick check shows the corrupted file is the same size as the 'uncorrupted version' but has some bytes differing... now, I know that last time I used Axoloti, it was ok.
BUT the accompanying dependency file has the same timestamp, so it doesn't look like its been altered... quite odd.
Thanks for this. Might make sense to put a sticky on this answer or document it somehow.
Had the same issue and deleting documents/axoloti/build/xpatch.h.gch did the trick.
A bit more info. Windows 10 machine. Installed the software about a month ago, played with somebody else’s Core without getting this problem.
Just received my own Core today. Plugged it in, updated the firmware, encountered the same problem with the first tutorial patch (01_sine_oscillator). Did a web search for MapViewOfFileEx axoloti and got to this thread. Scanned the thread, saw @mtyas mentioning the correct folder, and @thetechnobear confirming which file was affected.
Disconnected everything, deleted the xpatch file, fired up the Axoloti software, plugged the Core, and now everything sounds like it’s working.
Now comes the fun part of learning how to really do stuff with Axoloti.
