(new) games won't play in Vista x64

purchbit

Junior Member
Sep 13, 2008
2
0
0
I just completed a building a computer running Windows Vista Business x64.

It's running the following hardware:
-Intel BOXDP35DPM
-Intel Core 2 Quad Q6600
-8GB Mushkin DDR2 800
-EVGA GeForce 9800GT
-500GB Seagate Barracuda hard drive

It has all the latest drivers, windows patches, and latest DirectX installed. It's been running for a week doing nothing beyond MS Office 2007 tasks, surfing the internet, etc. (I have a had a couple random crashes of Explorer.exe, but no major issues)

I installed Company of Heroes the yesterday and it loaded the game to the menus but I could not find the cursor and it was very slow. So I tried reinstalling this but it did not resolve the issue, so I installed Company of Heroes Opposing Fronts. When I tried to start this program it would go to a black screen and never load the game. So installed all the patches but with no change. CTRL+ALT+DEL doesn't work, and I ultimately have to hit the reset button on the machine to bring it back to life.

Next installed Call of Duty 4...same thing happens I go to open the game, it displays the splash screen and goes to a black screen. I've tried reinstalling the game with the same results. Trying to launch in safe mode did not help either.

I just installed World in Conflict, it starts to play in the Sierra intro movie but then minimizes to the taskbar, when I click on it goes to the infamous black screen.

I reinstalled the NVIDIA drivers, DirectX. I've disabled the UAC, I've disabled antivirus (ESET NOD32).

What have I messed up on this machine or does anyone have any suggestions?
 

brandonb

Diamond Member
Oct 17, 2006
3,731
2
0
The only thing I can think of that you can try is to right click on the game icon and select "Run as Administrator"...
 

purchbit

Junior Member
Sep 13, 2008
2
0
0
Alright so I made some progress...I have two 20" L201P's on this machine, and when I unplug the secondary monitor the games seem to load properly and work...

My next steps will be figuring out why this happens, but I'm guessing it's related to setting up the NVIDIA control panel properly.