KMode Exception Not Handled
Loopysue
ProFantasy 🖼️ 39 images Cartographer
I keep getting the blue screen of death when I open CD3 Bitmap A thatched cottages. The computer crashes entirely and I get the message KMode Exception Not Handled (or words to that effect). I've searched online but it goes on about memory, and by watching the Task Manager I can tell that I'm not working the processors to death, so I don't understand.
I can use the symbols without opening the catalogue by going in search of the folder, but doing it that way I can't use all the usual facilities, like tab to change symbol, aligning against the edge of a road... etc.
Has anyone else had this problem? If so, how did you fix it?
I can use the symbols without opening the catalogue by going in search of the folder, but doing it that way I can't use all the usual facilities, like tab to change symbol, aligning against the edge of a road... etc.
Has anyone else had this problem? If so, how did you fix it?
Comments
Yes - its working pretty hard, but also pretty sure this KMode thing isn't being caused by a memory problem:
It can be triggered by an application if it requests resources that should normally be available and working, but for some reason aren't, but it isn't caused by an error in the actual application.
This is often caused by bad drivers or bad hardware. It might be that sections of your memory are bad, sections that you don't normally use, but which gets used when CC3+ starts consuming additional memory (Perhaps when opening that symbol catalog. As house symbols are more advanced than other symbols, it might cause an extra memory load). It could also be your HDD turning bad. I noticed you don't seem to have a lot of memory in your computer, so it will probably swap memory to disk when using more memory, so if the disk is bad, it could cause issues.
You can check your memory for problems following these instructions.
You can check your disk for errors following these steps. Please have backups of your stuff before doing that though, the command itself isn't destructive, but I've had drives that were on the verge of failing fail completely because of the extra strain of checking it.
Note that there may be other sources for the KMODE error too, like bad drivers, but a problem like this is extremely difficult to diagnose and troubleshoot remotely.
I will take it down to the local wiz kid and get it sorted out down there
I will, of course, back everything up first, but if it all goes wrong...
I may be some considerable time.
Looks like I will have to update the poor thing - its 20 years old, my favourite mouse, and they don't write drivers for it any more
Getting right click to work was incredibly... bad.
@Lorelei - I'm really just a traditional gal, you know?
@Nacon4 - If I have to get a new one, I will shop most carefully... after the funeral service of course. I mean, any time before that would just be... disrespectful!
Thanks for all the help Remy
I think there's still something a bit wrong with the new file I've generated. Its working, but when I paste a cottage on a line it "eats" the line, causing it to break into two parts with a missing section where the cottage is pasted. I get around this by drawing a disposable road and then adding the proper road back in after I've finished, but if I accidentally put a house on the end of the line it causes the programme to freeze up. Then the only way I can get out of it is to shut it down through the Task Manager.
I don't think its normal for the cottages to eat the line in this way, but I think this started happening about a fortnight ago, so I'm reluctant to go all the way back to then just to get rid of the line eating problem. Does anyone recognise this behaviour? If so - is there anything I can do about it?
Does this behavior happen with all city symbols, or just one or two? Might be a symbol with a bad control point.
Looks like the file is still corrupted
It appears to be Thatch 10-16 inclusive. The ones that are functioning all right are shown moved away from the line, although among them they exhibited different behaviours. Some of them automatically jumped away from the line the moment I clicked, and others just sat there and slid backwards and forwards waiting to be positioned.
Note that whenever a symbol is used in a map, the symbol definition is copied into the map. So for any map you have already used this symbol, the map will be using the bugged symbol. To fix this, while also keeping your existing instances of the symbol in the map, go into the symbol manager, and rename the symbol there. Now, you don't have a symbol of that name in your map anymore, so the next time you use it from the symbol catalog, it will take the definition from there.