Trusteer Rapport causing XP to BSOD

[sparky05084]

Hey all. Well, this is a new one for me and I'm hoping for some help please.

Basically, I am currently running Win 7 64 Home Premium as my primary OS on a master drive. Now, Win XP is secondary and on its own seperate drive (use dual boot option set by BIOS to choose between the 2 everytime system boots up or restarts).

Recently, when booting into XP the system suffers from a BSOD about 5 mins into windows interface loading up. You barely get a chance to do anything then all of a sudden it crashes out and starts the usual reboot loop and thus, takes me back to the select OS screen.

It is worth mentioning that presently, the problem (thankfully) seems to be only with XP as Win 7 seems to be running fine. So, with a little luck and trying my best to utilise the 5 mins or so before it crashes I disabled automatic restart on system error and this is what I get when it BSOD's:

Problem File: RapportCerberus32_32029.sys

PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0x00000050 (0xE5262AB0, 0x00000001, 0xB2D73756, 0X00000001)

Rapport Cerberus Address: B2D73756, Base: B2D66000, Datestamp: 4e79c343

Now, navigating explorer and going into my Win XP hard drive (to obviously avoid booting into the OS itself and experiencing yet another shutdown as it happens everytime) I managed to navigate the culprit file by the following:

Local Disk F (Win XP) > Documents and Settings > All Users > Application Data > Trusteer > Rapport > Store > Exts > RapportCerberus > 32029 > RapportCerberus32_32029.sys

Now, I am rather reluctant to delete this file becuase I read a while back (on another forum) that someone else had a problem with Rapport but not exactly as this. Anyway, he deleted it and all hell broke loose to a point where he couldn't boot into his OS.

This obviously worries me. I will say that I've been using Trusteer Rapport for well over 8 months now (not on Win 7 at the moment due to this reason) and previous to this XP didn't have any issues at all.

I have no idea whats changed and XP is used to simply be a back up drive and I am still in the process of saving all my files, folders and settings etc to an external usb via XP and then loading back into Win 7.

So, yes I could still do with using XP and it rebooting constantly is some what annoying.

Any suggestions would be appreciated and sorry for the long winded post, I'm very descriptive

 

[sparky05084]

I haven't actually but I will certainly consider it. Yes I will probably delete it anyway but can you see my point?

Reading about that fella that couldn't boot his system at all after removing a similar file (think it ended .sys too if I remember correctly) has me concerned. If I couldn't boot into XP I'd be screwed as I am still using it (or at least i was until this problem started) to copy over data.

What do you think?

Just do it anyway and hope for the best?

 

[sparky05084]

Ok guys an update for you. I booted into safe mode, removed the culprit file, crossed my fingers and waited.

I managed to get into XP but got a bit of a fright when it went to that bright blue screen with a "Please Wait" in the top left corner (like CHKDSK screen) and a loading bar.

Seemed very strange as then immediately after it went to the XP logon screen, it loaded windows and all was normal.

Now, as I write this I am actually in XP so I am happy to rapport (lol) that it hasn't crashed yet so fingers still crossed.

Incidentally, to those who feel it's actually a bad thing and causes problems, would I be better off removing it completely then?

Ive had it over 12 months (put in a previous post it was 8 months but I was incorrect) and this recent problem is the only thing that went wrong with it. Could my online banking (with Santander) be comprimised?