Buffer Overrun Detected

[Baxtor]

Been running fine for a week or so now, up intil last night, now whenever I try to load my 5 accounts keyclone locks up after the 3rd one every time.
I get the error message:

Buffer overrun detected

A buffer overrun has been detected which has corrupted the program's
internal state.
The program cannot safely continue and must now be
terminated.

I have no idea how to proceed with this, any ideas anyone?

[Stabface]

Hmm, can you post what your system spec is ? CPU/memory/etc.
Do you have any problems with other apps or is it only keyclone ? Can you run the 5 accounts (I will assume WoW) separate without using keyclone? And is it keyclone that is crashing or is it the WoW clients that crash?
Virus scanner up to date and ran a system scan lately ? how about a disk check ?

[Baxtor]

QX6700 Quad Core
8800GTX x2
8GB 8000CL5 Geil Ram
Vista 64

No problem with anything else at all, been running keyclone fine up until tonight.
Can run 3 instances of WoW fine with KC nps, but once the 4th loads thats it KC crashes
Will run a Disk Check now, while I go to bed :)
I may go for a reinstall of vista as for some reason it has bloated itself out to 50gb and I can't see where all that has come from.

If I re-install will I still be able to use KC on fresh install or will I need new key?

[Stabface]

You'll need to get your license transferred if you reinstall, just PM keyclone with your old and new system ID

[Baxtor]

Hey Stabface thx for the help m8, I managed to fix it though after much anoyance.
I still don't know what the underlying problem was, but once I redid the maximizer screen and re added the windows it worked again.
Such a simple solution, that took me hours to arrive at :)

[keyclone]

ok.. i'm confused. keyclone crashed when you run your 4th client? but you say you changed your maximizer setup and it worked fine? is that keyclone maximizer or the stand alone wow-maximizer?

[Ripper]

I had this error a long time ago. It turned out that I didn't add .kcl to the end of my setup files when I saved them.

[Baxtor]

ok.. i'm confused. keyclone crashed when you run your 4th client? but you say you changed your maximizer setup and it worked fine? is that keyclone maximizer or the stand alone wow-maximizer?The KC maximizer, i run on 2 monitors , 1 for the main and the second split into 4 quarters, I deleted the 4 regions on the second monitor and remade them, and all was fine again.

[keyclone]

so it could have been either an unknown region being requested by a command or a region already in use being requested twice?

i'll see if i can reproduce... it's on the bug list

[Drakkun]

After using Keyclone for 3-4 months I just received this error. It definitely has something to do with the maximizer portion. I know this because last night was the first time I tried out the maximizer options. I was previously running on 2 different systems. I added a third account last night and tried to set it up to run 2 wow's on one system.

It worked great for about 3 hours and then my system froze up. After restarting, I now receive this error when I try to use the command to launch the wow instances. I rebooted, deleted the keyclone ini file, deleted all keyclone files and downloaded a new set. None of these fixed the problem.

I am currently at work, will post more info from home tonight.

[entoptic]

just had this occur to me.

Everything checks out ok. I was fine last night until i started the computer up this morning. Any help would be great.

Thanks

[zanthor]

I had this happen and had to rebuild my maximizer regions as well. I found that sometimes the keyclone.ini file would get screwed up for some reason and changes wouldn't save, so I was in the habit of duplicating issues by creating a fresh keyclone.ini so the good news was I had a backup... the bad news was, I don't have any of the corrupted files... and never windiffed them or I'd send them on to KeyClone...