VBOX 4.3.4 and 4.3.6 crashes

[Zygmunc]

Hello. I have upgraded VBOX from 4.1.6 first to 4.3.4, and due to crashes to 4.3.6 (newest).
My base machine is desktop on intel B75 chipset with i3 and Win XP 32 installed.
I disabled HT in bios so my i3 cpu is seen as 2 cores cpu (not as virtual 4 cores cpu).
Has disabled VT due to i3 cpu version i3-2125 which doesn't support virtualization tech.

My virtual os is Win XP 32 installed. On 4.1.6 I had extension and guest addition installed (fitted to proper version).
On 4.3.4 I upgraded extension and uninstalled guest additions from virtual os (it crashes with 4.1.6 guest addition, so
I updated it to 4.3.4 but because it still crashes I uninstalled it completly - with no success).
On 4.3.6 extension is upgraded and guest additions are uninstalled.

The virtualbox constantly crashes after some of virtual XP worktime. It is not virtual os crash but "Oracle VM VirtualBox Manager". Crash info:
AppName: virtualbox.exe
AppVer: 4.3.6.0
ModName: vboxrem64.dll
ModVer: 0.0.0.0
Offset: 0000a469.

The moment of crash differs. The offset is always the same (0000a469).
I don't understand why it points to vboxrem64.dll. Isn't this module for x64 os versions?
I will return for now to 4.1.6 and check if crashes will still go on.

EDIT: I tried to make a clean install of VBOX, removed program, removed directories, fresh VBOX install (4.3.6), new profile, default VBOX settings. The same crash. Mostly it crashes when I try to fetch windows updates by IE8. It counted 79 updates to fetch. The moment it crashes is random, but I never get to state when updates are installing. There are always few updates to get.

EDIT2: On 4.2.6 (to which I revert) still crashes. I have found, that in "system" branch, there is Acceleration tab, which is greyed out and inaccesible on 4.3.6. On 4.2.6 I can enter to this tab, so I disabled all options.
I reduced graph memory to 32, system memory to 512 (4GB on board of host), have IO Apic enabled, disabled host i/o cache of ICH6 controller. Crashes are still there, but this time there are different modules, mostly vboxrem32.dll. No crash due to vboxrem64.dll.
Forget to mention that all crashes starts with error c0000005 - error memory access.
I have two vdi images. One is image of system drive 25GB max, resizeable. Second is image for pagememory, 2GB max, resizeable. I can disable virtual memory but I don't know if that's a issue.

[Zygmunc]

EDIT3: (because I don't like so long posts, I hope that I didn't violate rules so much).
In summary, I tested a few version from 4.3 and from 4.2 series, with most recent version. The virtual xp constantly crashes. This crash is not even registered in log files. Only windows log can be provided which is in no way relevant. So I don't think I will create bug ticket because I don't have much evidences.
I tried to test different versions of VB on other system with Core2Duo on board. Most recent versions from 4.3, 4.2 and 4.1.30.
I have found that my virtual XP has become freaking slow and sluggish. It starts almost 7 minutes or more to be only operable, and it still doesn't give any feel to work. I know that io apic isn't give additional speed for virtual xp, but I installed it that way and working on it for some time on 4.0.x virtualbox without any big problems. It wasn't so slow as it is now.

So I tried 4.0.22 (latest of 4.0.x) on B75 and i3-2125 on the same settings as on 4.3.6 and no crash has been counted. I get all 79 updates from windows update and installed them without any crash or problem. I will try today 4.0.22 on my second machine with Core2Duo to see if the os will recover from all the slowness and sluggishnes.

EDIT4: 4.0.22 installed on Core2Duo, host is XP 32, the same vdi as before. All the slowness and sluggishness dissapeared (of course it is not so fast as on i3-2125 but it still works good). I don't know where the problem is but it is clear that I must stay for now on 4.0.22.