NVIDIA
problem with new install of Grid K2- Control Panel crashes
I'm doing a project integrating third-party software which uses CUDA acceleration when available. So we've installed a Grid K2 in a Cisco UCS C240-M3S2 v03 server, running Windows Server 2008 R2 (bare metal not virtualized). We've been unable to get the Grid to work. Windows Device manager shows the board is there, but the Nvidia Control Panel always crashes on startup and the 3rd-party software does not see the Grid. I double-checked the hardware installation today against http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240/install/C240/replace.html#pgfId-1372776 The only discrepancy I found is that we're using the Y-power cable with a single board. Everything else should be good (according to the referenced doc): CIMC/BIOS version 1.5.3b.0 Installed in slot 5, option ROM is enabled We're using the latest driver version 333.11 (and same results with earlier driver versions). We have also tried deleting the driver and reinstalling, with no luck. Any advice to resolve this problem?
I'm doing a project integrating third-party software which uses CUDA acceleration when available. So we've installed a Grid K2 in a Cisco UCS C240-M3S2 v03 server, running Windows Server 2008 R2 (bare metal not virtualized). We've been unable to get the Grid to work. Windows Device manager shows the board is there, but the Nvidia Control Panel always crashes on startup and the 3rd-party software does not see the Grid.

I double-checked the hardware installation today against
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240/install/C240/replace.html#pgfId-1372776
The only discrepancy I found is that we're using the Y-power cable with a single board.
Everything else should be good (according to the referenced doc):
CIMC/BIOS version 1.5.3b.0
Installed in slot 5, option ROM is enabled

We're using the latest driver version 333.11 (and same results with earlier driver versions). We have also tried deleting the driver and reinstalling, with no luck.

Any advice to resolve this problem?

#1
Posted 06/11/2014 12:40 AM   
Hi, We have the same issue here. Did you find a fix to your problem? Thanks
Hi,

We have the same issue here. Did you find a fix to your problem?

Thanks

#2
Posted 07/09/2014 05:21 PM   
If you haven't resolved this already I would say it's likely a power issue. A K2 uses a ton of juice so if you're not following the Cisco guide exactly in terms of power then you will likely run into issues.
If you haven't resolved this already I would say it's likely a power issue. A K2 uses a ton of juice so if you're not following the Cisco guide exactly in terms of power then you will likely run into issues.

Mike Barnett
Sr. Systems Engineer, End User Computing Specialist
VMware
Twitter: MikeBarnett_

#3
Posted 08/23/2014 06:53 PM   
Scroll To Top

Add Reply