Xtrap causing memory dumps? O_o;; I don't feel safe running Fiesta at all anymore @_@

[rafale]

^ as title.

It seems that Xtrap errors are popping up more often than before since the last patch (before this Monday). I've had no less than three sudden client crashes within the past hour. And on the very last time, Fiesta suddenly shuts off and a fiesta.bin error came up.

Now I realize this has to do with the .bin file being either corrupted, modified, or accessed during gameplay. Neither of which applies since I've just had a fresh copy of Fiesta installed and fully patched a week or so ago.

Back to the details: a few seconds after the bin error popup, my computer suddenly reboots. Now, my computer is pretty stable as it goes. I've only had one or two sudden reboots ever since I'd built and purchased it over a year ago. Ever since XTrap came, the reboot rate has gone up. Fine. I can deal with it.

But what, I ask, is THIS?

http://i129.photobucket.com/albums/p215/rafaIe/xtraperrors.jpg

^ This is what greeted me as soon as I relogin Windows =| Memory dumps?? Registry values? System kernels being changed?

I don't feel safe launching Fiesta again until I get an idea of what Xtrap is doing with my registry that requires multiple boots and kernels being bounced around faster than popcorn.

[rafale]

*sigh* ._. nobody knows why xtrap is rewriting registry values and messing around with memory dumps? >_<

[GM_Pilkysico]

http://www.techspot.com/startup/12082/

This doesn't seem to be Fiesta related to me. There's no actions that your OS is receiving that points to Fiesta.

Even your source says it's your startup list (I'm assuming that your name is Paul Collins). You can change your startup programs (each time you boot Windows, theres programs that are run).

Read the link I posted above.

If the BIN file is altered, you cannot load Fiesta period. You will receive Color.shn info Error or connection errors.

[rafale]

Thanks Silkypico for the response.

I have read the link you gave. Unfortunately, it didn't state anything new, or give further descriptions as to the error. @_@

The "source" on the error report window in the screencap means the information source by which the error report comes from. Paul Collins would probably be the guy who contributed to the info database for SpyBot. @_@; My irl name is Rafale, lol.

My bin file isn't altered in anyway. It was updated from a clean install of Fiesta from a week ago and since then haven't been touched by me. Only the patching process had any contact with it. I haven't got a color.shn info nor any connection errors either - I was connected and fully ingame for a hour or so before the bin error happened. So.. I have no clue as to how my bin file might have gone corrupted. ;;



The problem is, this error only occurred after Xtrap closed my Fiesta client with the bin error. It froze screen then immediately rebooted. I've never seen an error such as this ever occur before on my system.

I remember reading reports on these technical support forums something about memory dumps in association with XTrap/Fiesta client before. About a bug where the client continuously uses up memory without discarding any, finally causing an overload which causes a full memory dump and the OS to reboot.

Are there no protection against memory leaks and memory dumping? I am worried because kernels are system internal files, and for them to be suddenly changed in conjunction immediately after this incident tells me that XTrap or the client might be causing harm to my PC by messing with unknown kernels.

This and the circumstantial evidence are what pointed the problem to be XTrap, or some bug in the client itself.



// blah, sorry about the wordiness; I try to be descriptive in order to make the situation clear and to get to the root of the problem.