I had the same issue once, Tony. I resolved it by reinstalling the second card, booting into Windows, and turning off SLI before shutting down. That's all it took for me, next boot with single card Windows started fine.
I wonder if that's because of the fact that your SLI string is in the registry. I didn't find this thread until I was almost finished with the SLI mod on my BlackOps. I started here, and AndyP inserted the SLI string into the DSDT table in the BIOS and sent it to me. Maybe Everest only shows...
Velvet Wafer, what version of Everest are you using? I'm using 5.30.1901 Beta. This is the first version to check for the SLI string in the DSDT table.
Here's what I was talking about:
Notice the chipset shows X58? This is on an X48 board. This is the HAL mod that wouldn't work for me. The only thing I changed for the next picture is the hal.dll. I used version 0.9a for the next picture.
Notice the chipset here correctly shows X48...
I had trouble with the hal.dll mod at first, I was using version 0.8. Once I got rid of that and tried version 0.9a SLI was available. This is on a Foxconn BlackOps X48 with 2 x 8800GTs on 191.03 drivers. The one that didn't work for me showed as X58 on CPUz and Everest. The one that did...
Me too, same situation. No SLI with 195, but return to 191.07 and SLI is available again.
FWIW, my SLI certificate string is inserted into the DSDT table in the BIOS, not inserted into the registry. Doesn't seem to make a difference.
I just tested the 195.39 drivers with my BlackOps with the SLI string in the BIOS rather than in the registry, and the beta drivers disabled SLI on that, too. I was hoping they were just seeing the string in the registry, but I guess that was too simple...
Hi guys! I just registered to ask a question: Has anyone with an SLI cert string inserted into the DSDT table in the BIOS tried the 195.39 drivers? That's how I'm running SLI on my Foxconn BlackOps, but I'm using 191.07 drivers. If I get a chance, I'll test it tonight if nobody else has.