I was trying to draw layout for a circuit when suddenly the whole software crashed with an error window
All the unsaved progress was lost. And this happens every time when I try to add footprint to the PCB. Please let me know a fix.
v5.1 is so ancient that even if the cause could be discovered, it won’t be fixed, as it’s 4 versions behind the current release.
If you are starting off, start with v9.
If you have to use v5.1 the only thing I can suggest is to upgrade to the last 5.1 patchlevel which is 5.1.12, from here: Downloads | KiCad EDA
1 Like
For any found problem first action is to use last version (each version update means tens bugs fixed).
Last V5 version was 5.1.12.
I suppose no one here remembers V5 details.
Since V5 I was using V6, then V7 then V8.
To use most current and less buggy version you should move to 8.0.9.
9.0.0 was released recently, but as first new version release it probably has many bugs.
If you can’t use later versions because of having Win7 PC than a solution can be to use Unix and then V8 or V9. I have never installed any Unix version but I believe if you decide to do it just to use KiCad latest versions and have a problems with it than you probably will get help in it here.
Any problems you will encounter with V9 have a big chance to be solved fast. No one will be searching a bug in V5 now.
KiPro has a support option for legacy versions and I think in some cases they might also provide patches. However this is obviously not for free and not really a reasonable option if it is a hobby project: Subscribe – KiPro
An organisation that can afford KiPro is unlikely to be a first poster.
Yeah true😅. I’m just a freelancer trying out projects.
is there a reason why you use such an ancient KiCad version? You couldn’t pay me enough money to go back to such an old version. Modern KiCad is so much better
Remember that even if you get 5.1.12 to work, you won’t get much help on this forum with questions about using it as many people have forgotten 5.1.
I get that your trying to start doing private work and that’s a commendable effort and I personally wish you the best 
But what is the problem regarding using a more uptodate version ? I mean is it hardware ? I assume it must be 
I think maybe finding a better PC should be a priority as even when (If) your present problem is solved you will have more 
and Kicad was a very different animal back then, in fact it almost functioned as to separate programs and most of us can’t remember or refuse to remember what to do 
Our help will be limited I fear ! but who knows you might find what you need 
I think the most logical reason would be to run on an older computer.
A few years ago I partitioned the HDD on my XP laptop so that I could install Linux Mint and run KiCad (6.X or 7.X?) with Mint in my lab. It did work, but I used it seldom and Linux Mint seemed very foreign to me; never learned it well.
So about 18 months ago my Win10 office laptop started giving me occasional blue screens and I no longer trusted it. I exiled that one up to the lab and now run KiCad 8.X on it in the lab.
I am sympathetic to the desire to use a good old tool when it gets the job done. Of course the OP is complaining about problems, but I think I ran 5.X years ago without serious issues.
1 Like
Screenshot of the GUI window there is clearly Windows 10.
marekr BobZ mousey retiredfeline Mineotopia Guys I wanted to add that the v5.1.9 started showing problem only after I installed v8.0.8 on my laptop. I don’t have any issue on the hardware side as I have a laptop with sufficient specs to run KiCad smoothly, but I guess the issue started after I installed the newer version. A large number of my older projects were on KiCad v5.1.9 that’s why wanted to continue with it.
Yeah sounds like some interference, maybe some newer DLLs installed due to v8. Can you revert to a previous OS snapshot?
You don’t need to create links to the people you are replying to. Just prepend @ in front of the names and they will be notified.
Is there a way to fix the issue without doing that? Maybe manually replacing any conflicting DLLs or adjusting environment variables?"
Sorry, no idea. I’m not a Windows user.
If you can find the DLL in question you can place it in the same folder as the KiCad 5.1.9 EXE, that may help . . . to find the DLL you might use something like Dependency Walker
Thank you @RaptorUK . Will try that method. If it works then fine, else will completely shift to kicad v8. Thank you guys for your time and help.
1 Like