Hey guys, I played Crysis recently and am playing Warhead now, and I was using XPx64, but decided to change to Vista64. When trying to run either game I was having the 1080p @ 24Hz problem when using the DX10 executable and my HDTV.
I have a nVidia GTX260 and while looking for a solution I saw someone who had the same problem with an ATI card and solved it in the ATI control panel by adding support manually for different modes, so I went looking in the nVidia control panel to see if I could do something similar. I managed to add a custom 1080p60 mode and now both games work properly in DX10, so here's the steps for the 181.22 drivers control panel:
1-open the nvidia control panel
2*-if you're currently at 1080p60 in Windows, change the desktop resolution to something else temporarily, like 1280x720, in Change resolution under "Display" on the task list
3-go to manage custom resolutions also under "Display"
4-(not sure if this is really needed), deselect Force HD Res. and select Allow modes not exposed by the display
5-click create, and insert 1920, 1080, 60 refresh rate and 32 bpp(bits per pixel can probably be different)
6-click test, press ok in the dialog that shows up, the "new" 1080p mode will be set and assuming all went well, it should say "if it looks correct please press yes". So press it lol.
7-you should now have the new resolutin under the Custom resolutions list.
8-exit the control panel and play the game, it should now be at 1080p60
*I needed step 2 because I was already in 1080p in the windows desktop and when I tried to test the custom resolution it'd say "test failed" or something similar, so I changed to 720p beforehand.
Before the 1080p24 problem, I was having the "game starts in window mode" and "mouse offset in the menu" problems, which I got rid of by opening the game in DX9 mode, changing to 1080p full screen, exiting and restarting in DX10 mode. After that, it was at 1080p but 24...
I'm gonna post this too in the Warhead thread. It's a bit weird because a few days ago I'd already tried Crysis in Vista64 DX10 and did not have this problem. This was a new installation (with all updates done), so I'm not sure what caused it.