Problem with WoW ui resetting and kernel memory dumps.

[Kaynin]

Computer specs:
Windows Vista (run as administrator)
4gb ram
Q6600 core2quad

Error:

Microsoft Visual C++ Library

Buffer overrun detected!

Program: C:\etcyadayada\keyclone.exe

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

[ OK ]

Happens everytime I want to execute a command (ie. attempting to load up a WoW instance.). Changed nothing to the settings whatsoever prior to getting this error. Although I had an ugly systemcrash that caused me to reset my PC, as soon as I wanted to execute a command after start up since, I'm getting this error. What must I do to continue to satisfy my WoW addiction now! :(

I've never had an error of this kind and have no idea whatsoever on how to counter it. I would prefer not reinstalling my PC or anything drastic if possible, so trying my luck here first. :P

[Kaynin]

Some further specifics I noted so far.

If I try to open my main region, I get the error message. If I try the other ones, nothing seems to happen, however, keyclone trays will spawn like mad in the start icon bar. (bottom right thingy) if I spam trying to open one of those instances. If I mouseover the icons, they poof again. Appearing to have been terminated right after start up but exited incorrectly perhaps.

Also, if I tried to open some of those and attempt to exit keyclone. It won't exit at all and I have to bring up task manager and end the proces for it to exit. Otherwise, it simply won't exit.

*shrug*

So, seems to be related with maximizer, somehow, and it started after a system crash. :P

[Kaynin]

oioioi, sorry for three posts in a row an a row and not using the edit function. But since this happens in intervals it might be easier to understand in seperate posts. :p

I fiddled some more with restarted, changing my maximizer screen etc. Tried to start up my main instance again (the one that previously gave the error message.)

This time it didn't, however, something really very odd happened. (There are GHOSTS IN MAH PEECEE! : ( )

It started wow in 800x600, fullscreen mode. Beginning with the movie, crappy graphics and all the ToS and agreement crap. In other words. My entire WoW seemed to have completely reset. As if starting up the first time. Accountname field was blank, even tho on second checking it should have entered the account I gave the command in keyclone. The resolution was all wrong. Basicly, keyclone somehow failed to open the instance correctly, and on top of that WoW felt like it was the first time restarting.

I quit WoW almost immidiatly to try again. Same thing, starts up with crappy graphics. (Tho this time not the movie and agreement crap) but still in full screen mode. And at this point I got a nice little BOSD with a physical memory dump.

Upon restarting, I got this little thing. (Added approximate translations in brackets)


Probleemhandtekening: (Problem signature)
Gebeurtenisnaam van probleem (Eventname of the problem): BlueScreen
Versie van besturingssysteem (OS version): 6.0.6000.2.0.0.768.3
Landinstelling-id(country code): 1033

Aanvullende informatie over dit probleem(Extra information about the problem):
BCCode: 1a
BCP1: 00041284
BCP2: 08F20001
BCP3: 00000000
BCP4: C0801000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Bestanden die helpen bij het beschrijven van het probleem: (Files that help describe the problem)
C:\Windows\Minidump\Mini052608-01.dmp
C:\Users\Fluffy\AppData\Local\Temp\WER-40560-0.sysdata.xml
C:\Users\Fluffy\AppData\Local\Temp\WERAE29.tmp.ver sion.txt

Lees onze privacyverklaring:(Privacy statement)
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0413

I'm too afraid to fiddle more with it. :P

[Kaynin]

On last little check before I am off to work, it might appear to be a problem caused by WoW and not Keyclone. (Maybe keyclone caused something, but for some odd reason, all my wtf folders resetted and I'm even getting wow errors without keyclone running now.)

Will have to reinstall wow probably. ;_;

[keyclone]

let me know how it works after the re-install.
if you are still having issues, please drop me a PM with your system specs and keyclone system-id

[Kaynin]

Well, 'resetting' my wow seems to have worked. Keyclone has been restored to its old capabilities after I have deleted and completely remade my ui's for the past 4 hours.

Tested by doing a heroic, no more problems, no more memory dumps. Works like a charm again.

I reckon that it was something like this.. I had a crash, WoW somehow got 'screwed up' and resetted its cache and perhaps certain stuff in WTF (Altho they appeared to be 'mostly' intact. But weird, addons acting up etc. Since I got the movie and the ToS and the realm choice and the standard bad graphics though I can only assume that WoW had some kind of safety reset or something.

And I think, that somehow because of that reset, keyclone couldn't quite use the maximizer option for some reason that eludes myself, perhaps you could figure that out. That it crashed or messed up on a 'reset' WoW. (Trying to adjust resolution perhaps but since wow starts in fullscreen mode in 800x600 standard it goes like "NO!")

I reckon it was something silly like that anyhow. So, WoW problem, not keyclone. I mean, I've not changed anything in keyclone, not reinstalled or anything, and it works again now that I apparantly fixed my WoW installations with all the right settings. :P

Also, having asked some people ingame. I've had various sources of people having their UI's completely screw up and 'reset' in the past few weeks. Like, once. So it might be an addon glitch with the 2.4.2 patch or something like that. In any case, I'm upgrading what I can and disabling addons I don't need for now. :P It's the most obvious solution I can think off.

In any case, maybe you can do something with this info, my problem is sorted anyhow, for now. And if it comes back, I have the feeling I should go to the technical support on the official blizzard forums instead. x)

[keyclone]

good to hear you've got it working again. could you change the title to something less alarming? thx