redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 215645474 | Release Date | 2026/04/12 | List Price | $36.00 | Model Number | 215645474 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
Specification:Item Type: CPU Cooler FanModel: SNK-P0050AP4Type: RadiatorILM Type: square, narrowCPU Radiator Size: Approx. 105 x 93 x 126mm / 4.1 x 3.7 x 5inApplication: 4U X9 UP DP serverSocket Type: LGA 2011Supported CPU: For Intel Xeon processor E5-1600/E5-1600 v2/E5-1600 v3 series, For Intel Xeon processor E5-2600/E5-2600 v2/E5-2600 v3 /E5-2600 v4 seriesSupported CPU TDP: Up to 165 wattsCooling Fan:Speed Control: 4Pin PWMRated Voltage: 12.0 VDCRated Speed: 3,800 RPMNoise: 38.0 dB (A) at rated speedCooling Fan Size: Approx. 92 x 92 x 25mm / 3.6 x 3.6 x 1inLocation: Front How To Use:1. Take out SNK-P0050AP4 from the package. SNK. poo50AP4 supports for Intel Socket LGA2011 (SocketR) square and narrow independent loading mechanism (ILM). Before installing the heat sink, please check which ILM is equipped on the motherboard.2. By default, the square ILM mounting bracket is fixed on the bottom of the radiator. If the motherboard is equipped with a narrow ILM, follow the instructions in Figure 1 to replace the default square ILM mounting bracket with a narrow ILM mounting bracket.3. Remove the protective cover of the thermal interface material (TIM). The required amount has been pre-applied on the bottom of the heat sink. Check the pre-coated TIM for damage.Package List:1 x Cooling Base1 x Cooling Fan1 x User Manual
| Wattage | 165 watts |
|---|---|
| Brand Name | Pilipane |
| Unit Count | 1.0 Count |
| Item Weight | 0.82 Kilograms |
| Noise Level | 38 Decibels |
| Manufacturer | Pilipane |
| Compatible Devices | Radiator |
| Power Connector Type | 4-Pin |
| Maximum Rotational Speed | 3800 RPM |
| Item Dimensions L x W x H | 4.13"L x 3.66"W x 4.96"H |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form