Recommended Posts

Hi,

 

probably a dumb question, but I'm building a new PC for my brother, been a long time since my last one, and I'm hooking up a Corsair H115i. For the life of me I cannot figure out where to connect this cable to (attached picture). The manual is pretty useless, apart from the sentence "Now connect the cables" it provides no clues. I think I've seen these before, maybe with Fan Headers? But I do not find the counterparts to these two cables. Also couldn't find any instructional videos online for the H115i, only for older models.

 

The Corsair H115i as a USB cable that goes to the motherboard USB header. A SATA Power connector that goes to the PSU cable for SATA Power. A fan header that you can connect to the motherboard CPU header. I have the ASUS VIII Hero and it has a dedicated Water Pump header, so the cable when in there.

But I can't figure out these two. I have no other place to hook them up to. Am I missing something obvious?

 

For reference, the parts I have are:

Be Quiet Dark Base 900 (case)

Be Quiet Dark Power Pro 11 650W (PSU)

ASUS ROG Maximus VIII Hero

Corsair Vengeance LPX DDR4-3000 DIMM CL15-17-17-35 Dual Kit

Samsung Evo 850 500GB

 

Many thanks in advance!

 

 

IMG_20160710_213718.jpg

^^Thanks for the hint!!

 

You are right, they are supposed to be connected to the two fans of the radiator. Seems that the SATA connector provides all the required power, which is also looped through the CPU heatsink and the two cables coming out of it, where the fan headers of the radiator connect to.

 

I guess I'm too tired and should take a break before I misconnect something else :)

 

Thanks a lot!!!

 

Just now, Odom said:

^^Thanks for the hint!!

 

You are right, they are supposed to be connected to the two fans of the radiator. Seems that the SATA connector provides all the required power, which is also looped through the CPU heatsink and the two cables coming out of it, where the fan headers of the radiator connect to.

 

I guess I'm too tired and should take a break before I misconnect something else :)

 

Thanks a lot!!!

 

No worries, I just looked at their manual and I can see why you might have overlooked it, their instructions are somewhat confusing. Good luck!

What is the USB connection for?  

I looked it up.

Built-in Corsair Link for monitoring, customization and control

Attach the included Corsair Link cable to a USB header on your motherboard and download the free Corsair Link software to unlock even more power.

You can customize cooling performance, monitor coolant and CPU temperatures, and change the color of the RGB LED lighting from the default white to match your system, or to change color based on temperature readings and other inputs.

fluff.

 

:)

It's my first attempt at watercooling, I was excited to get it going. Had to fiddle around with the case to make the radiator fit. The plastic on the motherboard guarding the ports sticks out a lot and I couldn't put it in as the fan on the radiator was blocking the way. Thankfully the case allows the motherboard tray to be adjusted so I moved it down 1 cm, now things fit perfectly. The Radiator has two 140mm fans pulling the air into the case and through it. I thought it should go the other way around, but that was the recommendation I read everywhere. Also makes sense, when you think about it.

19 minutes ago, Odom said:

:)

It's my first attempt at watercooling, I was excited to get it going. Had to fiddle around with the case to make the radiator fit. The plastic on the motherboard guarding the ports sticks out a lot and I couldn't put it in as the fan on the radiator was blocking the way. Thankfully the case allows the motherboard tray to be adjusted so I moved it down 1 cm, now things fit perfectly. The Radiator has two 140mm fans pulling the air into the case and through it. I thought it should go the other way around, but that was the recommendation I read everywhere. Also makes sense, when you think about it.

Per corsair you should have one fan blowing cold air in on the back of the radiator and one blowing towards the other fan. That is what the call the push pull

 

 

2 hours ago, Gary7 said:

Per corsair you should have one fan blowing cold air in on the back of the radiator and one blowing towards the other fan. That is what the call the push pull

 

 

Just adding a note in case your comment might confuse people.

 

The Corsair instructional video has a fan on either side of the radiator and both fans are blowing out of the case. This is the standard configuration for these devices because it works well enough and does not generate any controversy.

 

Odom is reversing that so both fans are blowing into the case with a fan on either side. This is a more efficient way to cool the CPU since the input air is often much cooler than the standard method. People sometimes find this odd since other fans elsewhere in the case might also be blowing inward but that's just because humans are not wired up to visualize air flows properly.

 

In my case, in addition to blowing inward, I also mount the radiator on the outside of the case which really makes a nice difference when working on the inside.

 

 

 

Just ensure fresh air is being pushed/pulled through the rad for the most efficient temps. Realistically the differences are minimal in temp (push/pull vs pull vs push) this was researched on XS forums you can visit there to see the data. But, again, fresh air is the best no matter the configuration. 

 

 

d8641d6f_vbattach201757.png

Hi Circaflex, Gary7, DevTech,

 

Thanks for the information and instructional video :)

 

The reason I set up the fans on the radiator that way was because I followed DevTech's advice in another thread that I had posted (Link here). His explanation made lots of sense to me, even though it was contrary to all my previous builds so far.

This time I put the radiator at the inside of the top of the case and underneath it the two fans, side by side, pulling air in. I have another fan at the back pulling air out of the case, two fans at the front pulling air into it.

I am considering of attaching another 140mm on the side panel and pulling air out, as that one will be right on top of the GPU. Or maybe it is better for it to pull fresh air in on top of the GPU? This makes me think that the fresh air will go over the GPU, getting hotter and then be spread around the case. I guess I'll just have to try it and measure the temps. See what works best.

 

 

4 hours ago, Odom said:

Hi Circaflex, Gary7, DevTech,

 

Thanks for the information and instructional video :)

 

The reason I set up the fans on the radiator that way was because I followed DevTech's advice in another thread that I had posted (Link here). His explanation made lots of sense to me, even though it was contrary to all my previous builds so far.

This time I put the radiator at the inside of the top of the case and underneath it the two fans, side by side, pulling air in. I have another fan at the back pulling air out of the case, two fans at the front pulling air into it.

I am considering of attaching another 140mm on the side panel and pulling air out, as that one will be right on top of the GPU. Or maybe it is better for it to pull fresh air in on top of the GPU? This makes me think that the fresh air will go over the GPU, getting hotter and then be spread around the case. I guess I'll just have to try it and measure the temps. See what works best.

 

 

In general it is a waste of fan noise to pull air out of the case, you will see better performance taking those fans out and throwing them away. That is because you never end up with an actual suction in a typical case. Always blow cool air in where it will do some good. (You can always put your hands on the things that get hot and see how you are doing.)

 

For the GPU you have to look at the design of your GPU cooling. Where does it need cool intake air? If you can give it cool air, that's great. Blowing air out near the GPU is more likely to just starve it of air flow. Either way, it is testable.

 

The most you should ever need is 4 fans:

 

1) CPU Radiator blowing cool air in

 

2) Disk drives blowing cool air in over drives but blowing hot air across them is ok as well, drives just need a bit of airflow of any type.

 

3) Side fan or internal fan blowing on mobo to give air flow to the chipset and the CPU power components. Cool air is good, some air is required since there is no other airflow on the mobo due to water cooling the CPU.

 

4) Blow cool air on the GPU if the GPU card wants to cooperate with you.

 

With everything blowing in, the air finds it's way out and ripping out the exhaust fans gives extra holes for that. Leaving the exhaust fans in place can skew the airflow in unpredictable ways, usually for the worse.

^I understand what you are saying but Corsair seems to disagree with you. That being said your point has been argued for years. All I can say is that I have my H-75 fans set per Corsair and it seems to be working.  I have 4 fans as you said a 200mm bringing in cool air from the front of my HAF-912 case , the two fans on the cooler and a 120 mm fan taking hot air out of the top. I used to have a 200mm fan there but with addition of the H-75 it would not fit. Well I did not count the fan on my GPU as it is built in.

This topic is now closed to further replies.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      594
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      74
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!