High cooling efficiency is the foundation, but with the BioniX P14 A-RGB fans, Arctic has also made efforts on other fronts. In addition to the clever daisy-chaining method (with the aim of reducing cabling to a minimum), this includes, for example, illumination as intense as possible. The light is guided not only through the entire impeller, but also through the surface of the frame, from the side. There are light guides in these areas as well.
Everything changes with obstacles
So far, we have described how static pressure and airflow measurements are made under conditions where the fan has no obstacles in its path. In practice, however, fans do not usually blow into an empty space, but have a filter, grille or radiator in front of or behind them, the fins of which need to be pushed through as efficiently as possible.

We will also measure both airflow and pressure through practical obstacles for the reasons stated above. These include two types of filters that are usually used in PC cases. One fine—nylon and the other plastic with a thinner mesh. One other obstacle is the hexagonal grille perforated at 50%, on which the vast majority of fans—intake and exhaust—are installed. In some cases, we measure the effect of the obstacles on the results at positions (behind or in front of the impeller) that are used in practice. All obstacles are both pushed through to detect pressure drops, but also pulled through, which in turn speaks to the impact on airflow.
We use two radiators that differ in thickness and fin density. The EK CoolStream SE120/140 is 28 mm thick and the FPI is 22, the Alphacool NexXxoS XT45 v2 is thicker (45 mm) but with less FPI. CoolStream’s fin disposition is also similar in parameters to AIOs. The results on the NexXxoS will again be attractive for those who build their own water cooling loops, where the fans should work well even at low speeds—hence the lower fin density.
These obstacles and especially the radiators, but also the grilles, increase the mechanical resistance in front of the fan, resulting in higher noise levels. However, we will still tune the fan speeds to the specified noise levels of 31 to 45 dBA. Naturally, the speeds will always be lower than when testing without obstacles, but we will maintain the noise levels for clarity. The different noise levels with and without obstacles will only be at maximum power. In this mode it will also be nice to see how the fan design works with the obstacle and in which case the noise level increases more and in which less.









And next time, shall we do the Seasonic MaxFlow fan? 🙂
Me again. Still none of tables do show up. Instead only error messages show. I did check using three devices and two different browsers. Only your newest Arctic BioniX test is affected.
Could you please give me some examples of pages where the charts aren’t displaying correctly? I’ll take a look afterwards and we’ll incorporate the fix—I’ll fix them. Thanks! 🙂
Hey, it might be an issue on my end but several pages of this test don’t load correctly on two devices of mine. Apart from that, thanks a lot for the test. It did perform exceptionally well in the hwbusters-test, too.
Personally, I would like to see a test of the “Noiseblocker NB-eLoop X B14-P ARGB”, since I own several of them. However, testing them probably wouldn’t be interessting to you, since they are really old and I know only of one vendor still selling them
https://www.caseking.de/search?q=eloop+B14&search-button=&lang=de_DE
They used to cost 25 or even 30€ per fan, if I remember correctly. I think, the noiseblocker fans were one of the first to use an outer ring on the impeller.
Thanks for the contribution. Yeah, there were a few charts that weren’t displaying correctly, or weren’t showing up at all. If you spot anything like that, please let me know. Everything should be there completely now, but…
The NB-eLoop X B14-P ARGB is definitely worth testing, of course, but our capacity… Anyway, one Noiseblocker fan will definitely appear in our tests down the line, as it has been planned for quite some time and we already have the samples. 🙂
The issue regarding the results pages not loading is still ongoing – even without VPN and no ad blocker.
The div-container usually containing the result tables shows:
“Oops! That page can’t be found.
It looks like nothing was found at this location. Maybe try one of the links below or a search?”