Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://steamcommunity.com/sharedfiles/filedetails/?id=1574588004
https://steamcommunity.com/sharedfiles/filedetails/?id=1513505217
You have some reading to do. By the way all of these are in the "Guides" section of PCBS. Right at the top of this page.
As I wrote in the original post, I've read the guide for info regarding the clock interrupt BSOD, and already noted that I've not overclocked anything (not even the RAM) and encountered the error anyway.
By the second loop you meant the water cooler connectors right? Yeah I suppose it did seem strange to have to have a loop that goes around the whole setup.
When you mentioned that the video cards are connected incorrectly, did you mean that there are additional issues other than the water cooling loops? Is there something I need to do in-game to setup the SLI? Thanks
I wouldn't know exactly but I'm guessing by setting up the loop wrong, probably the coolant isn't completing the loop at all, likely not cooling the system and probably over heating and causing the blue screen. I'm just guessing though.
Here's a random image I found on the internet to give you a better idea of the proper way to loop two video cards together: https://www.overclock.net/photopost/data/1369931/c/c2/c2821864_WCflowdirection.PNG
Thanks! I couldn't get the old rig to run benchmark in the game, but a new one with the right water cooling loops worked.
Not sure what the issue with the old CLOCK INTERRUPT error was. But the new rig I built had a vDisplay.v error that I fixed with changing the looping. Still no idea what the problem was though.