The Error entries in the log is the most important ones, yes. They are the most helpful when troubleshooting.

The other CTD you mentioned, the one where shot, happens to alot of people. I can't remember it happening to me, so it might be driver related or some graphic setting you're playing with. Start by turning on or off the blood setting in the options. If that doesn't help, try different settings with the graphic options, you might get lucky.

Or turn it off all graphic options :P

I don't care about good graphics, I'm playing old games of spectrum like Dungeon Master, UFO Enemy Unknow, monkey islad etc.

Txk again for all, now I´m go to sleep, It´s late here, and tomorrow I have to get up earlier to go study, tomorrow I paste all of my "error" CTD log.

Here it is more of them

00:00.023 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.025 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.024 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
02:04.448 ERROR [0] .\Monster\m_general.cpp (5557) !HealingObject
48:33.032 ERROR [0] .\World\Squad.cpp (230) Target deleted. POPing task.
54:27.690 ERROR [0] .\Quests\E1p\e1pext.cpp (284) Interlocutor not found by GUMID: -1
56:03.370 ERROR [1] .\Quests\E1p\e1pext.cpp (284) Interlocutor not found by GUMID: -1
00:00.024 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.024 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.026 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.019 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.018 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.018 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.018 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.018 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
00:00.024 ERROR [0] .\Parser\TextParser.cpp (683) Error parsing : '' found, int expected
03:18.859 ERROR [1] .\Parser\TextParser.cpp (683) Error parsing : 'WillBeHit' found, int expected

These are very common in the game and doesn't cause any serious problems, and the WillBeHit error only occurs once when the game is newly installed. The other one is a misplaced " that I've tried to find but it still eludes me. But it's not a big issue so i've learned to live with ti.

This happens when the engine can't find the INI file for an NPC or the NPC's INI file has been altered in some way. But since you're playing vanilla it's weird for that to happen. I know that this causes a CTD, often when you try to leave the sector where the NPC is located.

These two are new to me, from what I can tell they're prolly a result of the memory leak, but I'm not sure.

Is the game more stable since you started playing in shorter sessions? Or do you still get CTD's as often as before?

Yes, for the moment, the game only kick me out when someone shoot me.

I put all the graphics options ON, I want to see If putting it OFF, the game run better or not, So I'm gonna try diferent options to see what happend

I'll keep posting log's here, you are very kind for healping me, Thank's again.

I just remembered that a long time ago there was talk about the stability and the anti-aliasing. The tip was to set it to 2x or lower and that should increase the game stability. Since I've never had any problems with stability I've never known for sure if it works, but it could be worth checking out in your situation.

I can say for sure that under Windows 7 64-bit, stability has massively decreased, compared to XP 32.. Even when running XP32 SP3 compatibility, I randomly crash trying to open the map screen, open the radio, after saving (but fortunately not corrupting it)... I think I've pressed F5 more than I've fired bullets.