And Win XP cracked.

[Max Payne]

I installed Win XP in my precious MBP. Everything was going great apart from 3 crashes a day, which is normal for win xp. Today I experienced the first major problem.

As soon as I log in to win xp, I get this error.

svhost.exe - Application Error

The instruction at 0x745f2780 referenced memory at 0x00000000. The memory could not be "read"

Click OK to terminate the program.
Click CANCEL to debug the program.

Pressing OK will crash the Win XP, pressing cancel will allow me to continue using the crappy win xp.

What do you guys think is the problem?

Feel free to ask any question and also feel free to abuse me. I deserve it because I am already a fool, installing XP.

 

[garfield2002]

Three crashes a day is still a bit worrisome even for Win XP. I had two computers that crashed often and gave svchost.exe and memory address errors similar to the ones you got. The first problem was a failing HD that was corrupting system files as they were being written. Run disk utility on your HD to check for errors. The second computer had a bad RAM stick. I would also run memtest to check for this possibility. Replaced the HD on the first machine and got a new RAM stick for the other, plus a fresh XP install cleared up the problems.

 

[balamw]

Note too that there are many spywares that try to masquerade as svhost/svchost so you think they are important....

Are you running the usual virus/spyware protection.

3 crashes a day is NOT normal for XP.

B

 

[Max Payne]

Nothing wrong with Mac OS X though. Although FireFox is running kind of slow now. I hope it's not that serious. I am in Mac OS X now. I'll check utility disk and memory check.

Thank you.

Balamw, I am using Sophos anti virus and windows firewall.

 

[Sesshi]

The issue is probably Sophos. I have 1 crash a week on my least reliable Windows box which I've not really bothered to keep working properly.

I have had Boot Camp / Windows running reliably on all of the Macs I've tried it on. In fact on the MBP it's more reliable than the OS X side if you include the lid-closed sleep issue that I have under X.