3DMark11 wont see my pair of MSI GeForce GTX550ti Video Cards

  • Question
  • Updated 3 years ago
  • Answered
I am having trouble getting 3dMark11 Advanced Edition detecting both of my video cards to run with multi-gpu. The GeForce Control Panel, and OpenGL benchmarks detects the multiple GPUs.

I have also tried editing the profile by hand using a import/export tool, and by editing the profile in the GeForce Control Panel and telling 3dMark11 specifically that that are 2 video cards in crossfire.

I am running the latest GeForce 270.61 drivers, and the latest patch to 3DMark Version 1.01, and SystemInfo 4.0.

Here are the specs on the System:

MSI 890FX-GD70 Motherboard
AMD Phenom II X6 - 1100T - Black Edition
16GB Ram
(2) MSI / GEForce GTX550ti (1GB) Video Cards
Windows 7 Professional 64Bit
1000w Power Supply
4TB of Seagate 7200RPM SATA 6.0GB
30GB Kingston SSD Boot Drive
LG BluRay Burner
Corsair H60 Hyrdro CPU Cooler

Below is system info from various tests:

[Display]
Operating System: Windows 7 Professional, 64-bit
DirectX version: 11.0
GPU processor: GeForce GTX 550 Ti
Driver version: 270.61
DirectX support: 11
CUDA Cores: 192
Core clock: 950 MHz
Shader clock: 1900 MHz
Memory clock: 2150 MHz (4300 MHz data rate)
Memory interface: 192-bit
Total available graphics memory: 4095 MB
Dedicated video memory: 1024 MB GDDR5
System video memory: 0 MB
Shared system memory: 3071 MB
Video BIOS version: 70.26.20.00.00
IRQ: 24
Bus: PCI Express x16 Gen2
GPU processor: GeForce GTX 550 Ti
Driver version: 270.61
DirectX support: 11
CUDA Cores: 192
Core clock: 950 MHz
Shader clock: 1900 MHz
Memory clock: 2150 MHz (4300 MHz data rate)
Memory interface: 192-bit
Total available graphics memory: 4095 MB
Dedicated video memory: 1024 MB GDDR5
System video memory: 0 MB
Shared system memory: 3071 MB
Video BIOS version: 70.26.20.00.00
IRQ: 32
Bus: PCI Express x16 Gen2

[Components]

easyUpdatusAPIU64.DLL 1.1.34.0 NVIDIA Update Components
WLMerger.exe 1.1.34.0 NVIDIA Update Components
Nvlhr.exe 1.1.34.0 NVIDIA Update Components
daemonu.exe 1.1.34.0 NVIDIA Update Components
ComUpdatusPS.dll 1.1.34.0 NVIDIA Update Components
ComUpdatus.exe 1.1.34.0 NVIDIA Update Components
NvUpdtr.dll 1.1.34.0 NVIDIA Update Components
NvUpdt.dll 1.1.34.0 NVIDIA Update Components
nvui.dll 7.17.12.7061 NVIDIA User Experience Driver Component
nvxdsync.exe 7.17.12.7061 NVIDIA User Experience Driver Component
nvxdplcy.dll 7.17.12.7061 NVIDIA User Experience Driver Component
nvxdbat.dll 7.17.12.7061 NVIDIA User Experience Driver Component
nvxdapix.dll 7.17.12.7061 NVIDIA User Experience Driver Component
NVCPL.DLL 7.17.12.7061 NVIDIA Compatible Windows Vista Display driver, Version 270.61
nvCplUI.exe 3.6.750.0 NVIDIA Control Panel
nvWSS.dll 6.14.12.7061 NVIDIA Workstation Server
nvViTvS.dll 6.14.12.7061 NVIDIA Video Server
NVSTVIEW.EXE 7.17.12.7061 NVIDIA GeForce 3D Vision
NVSTTEST.EXE 7.17.12.7061 NVIDIA 3D Vision Test Application
NVSTRES.DLL 7.17.12.7061 NVIDIA 3D Vision Module (0)
NVMCTRAY.DLL 8.17.12.7061 NVIDIA Media Center Library
nvDispS.dll 6.14.12.7061 NVIDIA Display Server
PhysX 09.10.0514 NVIDIA PhysX
NVCUDA.DLL 8.17.12.7061 NVIDIA CUDA 4.0.1 driver
nvGameS.dll 6.14.12.7061 NVIDIA 3D Settings Server

And then the output for the profile for 3Dmark11.

Profile "3DMark11"
ShowOn GeForce
ProfileType Application
Executable "3dmark11.exe"
Executable "fmsiscan.exe"
Executable "3dmark11cmd.exe"
Executable "3dmark11demo.exe"
Executable "3dmark11workload1.exe"
Executable "3dmark11workload2.exe"
Setting ID_0x00a06946 = 0x080000f5
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033cec2 = 0x00000002
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1033dcd3 = 0x00000004
Setting ID_0x1095def8 = 0x02c00005
Setting ID_0x20441369 = 0x00000001
Setting ID_0x209746c1 = 0x04280001
Setting ID_0x20ebd7b8 = 0x00000020
EndProfile

Everything is properly cooled, and powered.

I don't know why 3dMark refuses to see both cards... when other tools do.

azpyroguy

  • 3 Posts
  • 0 Likes
  • confused.

Posted 3 years ago

  • 1

FM_Jarnis, Official Rep

  • 6250 Posts
  • 400 Likes
3DMark automatically uses SLI/Crossfire cards. Only way I could see this happening is if you have set one of the cards as dedicated PhysX card in NVIDIA settings.

Can you provide a link to a result in 3dmark.com from this system that shows the issue?

azpyroguy

  • 3 Posts
  • 0 Likes
Hi.
Yes. I just ran a quick test this morning (only 2 of graphics tests).. but it does show this error.. and now I am even getting a 0 score, and non recognized processor....

http://3dmark.com/3dm11/1128757

FM_Jarnis, Official Rep

  • 6250 Posts
  • 400 Likes
You are getting zero score because the benchmark run was not done with default settings, that's not related.

CPU detection issue is our bad, will get it fixed.

As to the SLI detection, everything in this data points to a single GPU only but we'll investigate further (obviously I believe if you say you have two cards - it is just that our SLI detection routines seem to disagree with the reality)

azpyroguy

  • 3 Posts
  • 0 Likes
Thanks for the update. I only had time this morning before work to run those 2 quick tests.

Is there anything specific you need to me get (as far as system info) goes to help your figure out why the SLI detection routines are not detecting my pair of video cards.

I just tested with Portal 2, and set everything to the highest settings and pretty sure its finding both cards... as performance in the game is great. Though its my first game (I am not a "normal" gamer - I built the system to do 3D Animation, and Video Production), but bought a couple of games as a diversion.

FM_Jarnis, Official Rep

  • 6250 Posts
  • 400 Likes
Portal 2 runs perfectly with a single GTX 260 so it isn't really a good test.

I believe the current 3dmark.com score has all the details needed - I've forwarded them to the code guys.

One thing you could try is to manually switch the SLI detection code.

This thread tells you how to get debug data out of SystemInfo that includes the SLI detection. You could send that file to me (to fm.jarnis [at] futuremark.com)

http://futuremark.yougamers.com/forum...

FMSIDiag.exe can also be used to switch between two different SLI detection routines. By default the legacy routine is enabled but if you disable it and enable the other routine, this could, in theory, change things.

The reason we still use the legacy routine by default is that otherwise SLI detection breaks for a large number of configurations (for reasons we honestly haven't figured out yet)