BSOD when enabling SLI in Nvidia Control Panel

erm1970

Reputable
Feb 23, 2015
4
0
4,510
So a couple of weeks ago I downloaded and installed the newest driver (347.52) for my 2 gtx 550ti video cards. I rebooted the PC and went into the nvidia control panel to enable SLI. The Apply box comes up but then the screen goes black and then the PC restarts. When windows loads and I log in I get the message that windows has recovered from a serious error.

022215-17986-01.dmp
2/22/2015 8:35:32 PM

Bug Check Code-----------0x00000116
Parameter 1-----------------fffffa80`075c14e0
Parameter 2-----------------fffff880`057a1978
Parameter 3-----------------00000000`00000000
Parameter 4-----------------00000000`00000002
Caused By Driver---------- dxgkrnl.sys
Caused By Address--------dxgkrnl.sys+5ccbc
Processor--------------------x64
Crash Address--------------ntoskrnl.exe+71f00
C:\Windows\Minidump\022215-17986-01.dmp
4
15
7600
666,840
2/22/2015 8:36:49 PM

my PC:
Operating System Microsoft Windows 7 Ultimate SP1
CPU Type: QuadCore AMD Phenom II X4 Black Edition 940, 3000 MHz (15 x 200)
Motherboard: Asus Crosshair II Formula (2 PCI, 2 PCI-E x1, 3 PCI-E x16, 4 DDR2 DIMM, Audio, Video, Dual Gigabit LAN, IEEE-1394)
Motherboard Chipset: nVIDIA nForce 780a SLI, AMD K10
Memory: Corsair XMS2 CM2X1024-6400C4 4 GB DDR2-800 DDR2 SDRAM
Video Adapter: (2) NVIDIA GeForce GTX 550 Ti (2 GB)



I have been online with Nvidia chat and phone and they have no help for me except the obvious process of elimination trouble shooting steps. other than the SLI not working the PC is running fine graphics are good etc.. Only when I Enable SLI do I get the error. The Following are the steps I have taken already
1) per nvidia tech support--- re-flashed bios
2) uninstalled new driver and re-installed (clean install) of the previous working driver (to no avail).
3) checked for newer chipset drivers there were none.
4) removed video cards and installed one at a time in all 3 PCI E slots they both worked fine.
5) Bought a new SLI Bridge..no dice.
6) reformatted and re-installed windows 4 times (thinking i may have messed it up)

I use a program called blue screen view to view the dmp files and it says its caused by
driver: dxgkrnl.sys
crash address is ntoskrnl.exe+71f00

Thanks in advance for any/all your help!
 

erm1970

Reputable
Feb 23, 2015
4
0
4,510
Sorry Its a:

LSP Ultra 750W ATX
Model number: ULT- LSP750 (Brand new)

Previously I have been running this set up for about 3 years with no issues with a bfg tech 650w the reason I bought this was because of a T_R_D error message I was getting and Nvidia said it was the PSU..
Below is the WinDbg check I ran which Nvidia said was from the PSU:

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT <- (this was after I did a clean install of driver 347.52 from 340.52 and tried to enable SLI in nvidia control panel)
BUGCHECK_STR: 0x116
PROCESS_NAME: csrss.exe
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+15393c
fffff880`0f24893c 48ff256d6d7200 jmp qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f96f6b0)]
SYMBOL_NAME: nvlddmkm+15393c
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc}
Followup: MachineOwner

Thanks for taking time to look at this!
 

erm1970

Reputable
Feb 23, 2015
4
0
4,510
Well i guess it was one of the video cards causing the issue. I recently bought a new mobo (msi 970 Gaming) new processor ( AMD FX 6300) and new memory (8 gigs corsair Vengeance 1600MHZ). got everything installed windows loaded up new current drivers, open nvidia control panel, clicked enable SLi ready to start gaming again and boom blue screen. I tried each card again individually again and when i switched to the second card and booted up i could see small multi colored lines in the screen. So looks like i will need to upgrade to a better card since i upgraded everything else.