OK guys here we go, another SOF2 crash sob story.  I will give you all the facts and I hope you're all up for the challenge.

I bought a new computer one week ago specifically to get better game play from SOF2.  My old computer (1.4 T-bird, MSI mobo w/via chipset) ran the game flawlessly and NEVER crashed.  First of all here is what I have.

-AMD XP 2400 cpu
-ASUS A7N8X mobo w/onboard sound and nic (bios updated to latest version)
-Nvidia NForce 2 chipset (latest drivers)
-512mb 400 speed DDR RAM (moved around and optimized by shop)
-Western Digital 80 gig HD
-PNY GeForce 4 4400 128 mb DDR ram video card (I've tried Nvidia 41.09 and 43.45 drivers)
-Volcano 9 cpu fan
-Logitech MX 500 mouse (w/mouseware 9.73 drivers, the 9.75s make my mouse act weird when Team Speak is running. The same thing happened w/my old computer)
-Logitech Internet Navigator keyboard (w/the latest 215 drivers)
-Windows XP home SP1 and all other updates
-DirectX 9.a
-Comcast Cable Broadband

Here is what happens, after playing anywhere from 5 minutes to 2 hours a window pops up that says something like "SOF2 has encountered a problem and needs to close...blah, blah, blah, do you want to send a report?"  I have to then restart my machine, if I just restart the game the window pops up sooner.  I tried to play for 3 hours tonight and got 4 crashes:

1-the notice above
2-a code, which I didn't write down...sorry.
3-a crash which shut down my computer then a restart.
4-I lost all sound and had to restart the game.

I have reinstalled SOF about 7 times all different ways with the same results.  I kept my old install of SOF2 and tried using different versions of that, but YES I have done a fresh install and just used everything from the new install.

Normally I just get the "...SOF2 has encountered a problem..." notice which indicates a software issue not a hardware issue right?  We all know this game is VERY stable.  I HAD a machine which ran it great (which I gave to my fiance', can't get it back), and now I'm stuck w/the fancy machine that crashes.  I use this machine for work, and to write my Master's Thesis in addition to gaming so OS reinstalls aren't too fun and I don't have the time.  I'm willing to reinstall the OS one more time, but I really doubt that's the problem. The game did this before I installed any other software other than that listed above.

Any ideas???  I'm willing to exchange any of the stuff above if you think there is more stable hardware.

Thanks in advance,

{LLC}Jaroom

have u run wiser2 to check ur files.

does it happen in both sp and mp??

Nice rig.  You might want to double check and make sure that you really have 400 speed ram.  Some companies are labeling it as such... and it really isn't.  If you ram is greatly overclocked to hit that speed it might make the game dodgy.

Hi,

I have same motherboard (deluxe), AthlonXP 2000+, gf4ti4200 128, 512 pc2700 HighPerfII (mushkin), Maxtor HD, winxp.
And I have the same problem with SP or almost...MP works fine and I CAN play the RMG maps from the SP mode...but as soon as i go into the "normal story"...after 5, 10 or 30 min i get the same error as Jaroom.
Wiser2 checked it and all is good.
Now I've had this problem since I bought this PC but since I don't really play SP I didn't care. But a friend of mine who also has the a7n8x reports the same problem.
:S

First of all I must say "I love this forum!"  The quick and helpful responses ROCK!

Here are my responses thus far:

-I have run wiser2 and everything checks out.
-I only play MP, I've never even started SP on my new rig
-The RAM has been checked and double checked by the shop I bought it from.

Could it be the mobo?  

I'm still ready for more helpful hints  

try sp, or try an non pb server after u disable pb (just incase its the problem)

Shouldnt be the board...

I am running the same CPU and the Deluxe model of that board with no problems what so ever.

When I get home from work I'll try a mp server w/out pb.  

Could someone please tell me how to disable pb?

Thanks

either, turn it off from the server browser or type
pb_cl_disable
in the console.