Monitor Causing Low FPS???

I had a 17" CRT that would run over 100+ FPS easy @ 1280x1024 w/ all settings maxed. 2 weeks ago I bought a 22" LCD. Initially, after installation, it was only running at 15-30 FPS @ 1680x1050. I thought that was low, so I tried running it at a couple different resolutions and lowering the eye candy, but to no avail. I rebooted a couple times and voila it was back up to 100+ FPS.
A couple days later I rebooted my PC and it was back to down to 15-30FPS when I started up GW. Again after a couple of reboots it came back up to 100+FPS.
I've had this scenario happen three times so far in the last two weeks. Yesterday I updated the Nvidia drivers to the newest ones and no help. It's currently stuck at the low FPS after 3 reboots last night.
Anyone have any thoughts or suggestions on why this would happen and how to correct? It never did this with the CRT. I have not re-attached the CRT to confirm that it goes back to normal (will try that this evening). I would not think the LCD monitor would cause this.

I have a similar thread in the Nvidia forums, but no luck yet. Thanks in advance for any help.

System specs:

Core 2 Duo 6320
Gigabyte 965P-DS3
BFG 7950 GT
2 GB Crucial DDR2
Samsung 226BW

I have the same monitor as you and the same problem, but mine is caused by latency ....... (I think), because I never had any problem before and I had the monitor since last Christmas.
Only about a month ago I started to have very bad lag's spikes!

My advise to all: Don't buy any Samsung products .... I had so many problems with them and their so called custumer service is ##@%%%**!!!!

/Angelica

You were running the game before on a 17" CRT (aspect 4:3) using a resolution of 1280x1024 (aspect 5:4)? Fail.

I've never heard of a monitor by itself causing a game to run slow. Are you sure it's not your video card overheating now that you are running it at a higher resolution? That 7950 GT probably never ran at 100% load just running Guild Wars on your old CRT.

A monitor can't make your computer slow down. I'm more apt to agree with lordpwn on this one, your card is now pushing over 30% more pixels and is getting stressed more. But not enough to tank your FPS that much. Try other 3D apps besides Guild Wars and see how they perform as well.

Changing resolution from 1280x1024 to 1680x1050 is a pretty big jump. If anything is affecting your fps, its that. I don't know what other resolutions you tried, but I'm going to guess your new LCD (which is 16:10 aspect ratio) can't display 1280x1024 (5:4) for you to try it. I bet all of the resolution options it gives you are higher than the 1280x1024 you're used to.

Anyway, the monitor itself can't really be the problem. It doesn't have any functions that would directly affect the way your computer runs. Your video card processes data and transmits it at whatever resolution through a DVI port to whatever happens to be plugged into it. Beyond that, your computer doesn't care what you're looking at.

I tried the old CRT and the FPS went back up. So I manually deleted all the nvidia .dll's and re-installed the new Nvidia drivers. Put on the new monitor and switched the DVI cable over to the other connector on the video card as well when doing so. Botted it up and its back to high FPS with the new monitor. Played for 2 hours without a hitch. I'll try re-booting it tonight and see if it holds.
I realize I'm not using the scientific method by changing a lot at once but oh well.
Granted the video card is trying to push more pixels, but I have monitored the temps and they don't go up to an extreme level. Plus, when I have had it running at the high FPS with the new monitor I have played for a couple hours with no issues. Not to say that its not the problem, though. I will try to load another 3d game and see what happens as well.
GW did let me try to run it on the LCD with like 900x600 or something, and 1280x1024, though it looked smashed. The FPS didn't change. Still hovered around 30 (this was before the chages I made yesterday).
Thanks for all the input so far. Still don't know if it's fixed, but I will post if I find anything else out.