New hardware! Crysis crashes now...

[ExAm]

Okay, so I just installed a new motherboard, CPU and RAM - all the drivers have been installed, and the new MoBo uses the same chipset as the last one, meaning I don't have to reinstall Windows. I'm using the same video card as before, an 8800GT, and all the drivers are installed already, the same ones I've been using for ages. The new motherboard has integrated video, but that (apparently) was disabled. It doesn't show up in the hardware monitor.

Anyways, when I start a game in Crysis, the framerate seems below what it was with my old hardware, which was vastly inferior, and then it crashes to desktop about 20 seconds later.

The lowered framerate puzzles me, since my new CPU is a dual core AMD X2 2.6ghz, and my old one was an overclocked single core AMD. Maybe Crysis isn't multithreading? I don't know.

This is all just really weird.

[Xetsuei]

Could you list the mobo, cpu, and ram?

[beele]

When you get a new mobo (or other very big changes in harware, like a switch from an intel to AMD mobo) the best thing to do is reinstall windows, even if it uses the same chipset ect.

[Since you have XP, there might be another option. There's a dev tool on the installation cd which gives you the option, to re-seal windows (will recreate HAL on first reboot), so you can install mayor hardware changes, and when you boot windows again, the new Hardware Abstraction Layer (HAL) wil be created, so no conflicting can happen between the old and the new one. google it and there are a lot of websites who give you a step by step procedure of doing it.]

[ExAm]

Now this is interesting. When I start a new game as opposed to continuing from an old save file, everything's fine. Only a minor increase in framerate from before, though. Now, since my CPU runs at 22c most of the time, I can overclock this baby from 2.6 to at least 3.2 :D

[Roostervier]

I've had problems with the saves too. I always just use the "map mapname" command in the console to get to whatever map I want in the game.