Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 292
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 166
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 235
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 315
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 356
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/demoynapstest/public_html/all/scl/application/controllers/Main.php
Line: 8
Function: __construct
File: /home/demoynapstest/public_html/all/scl/index.php
Line: 289
Function: require_once
Welcome To Scl Gaming
Product Model: NT-H1-10G Availability: In Stock
free shipping on all us order
Contact us 24 hours a day
You have 30 days to Return
We ensure secure payment
Features
Noctua’s NT-H1 is a renowned hybrid thermal compound that has received more than 150 awards and recommendations from international hardware websites and magazines. Thanks to its excellent performance, exceptional ease of use and outstanding long-term stability, it has become an established favourite among overclockers and enthusiast users worldwide. Whether it’s air- or water-based cooling, CPU or GPU applications, overclocking or silent systems: NT-H1 is a proven premium paste that’s guaranteed to deliver great results.
Award-winning performance
Bundled with Noctua’s premium-grade CPU coolers since 2007, NT-H1 has proven its excellent performance in countless of tests and reviews. Chosen again and again by overclockers and hardware enthusiast around the globe, it has established itself as a benchmark for premium-quality thermal interface materials (TIMs).
Easy to apply
Thanks to its excellent spreading properties, there is no need to manually spread NT-H1 before installing the cooler: Simply apply some paste onto the CPU (see instructions for details), put on the heatsink and you’re ready to go!
Easy to clean
NT-H1 is one of the easiest to clean thermal compounds on the market: Simply wipe it off the CPU and heatsink with a dry tissue or paper towel, then wipe them clean with a moist tissue or towel. No cleaning alcohol or solvent required!
Not electrically conductive, non-corroding
While some high-end thermal compounds and pads are risky to use due to their electrical conductivity or corroding properties, there’s no risk of short-circuits with NT-H1 and it’s completely safe to use with any type of CPU cooler, regardless of whether it’s made from copper or aluminium and whether it’s nickel-plated or not.
Excellent long-term stability
NT-H1's unique formula is highly stable over time, even after longer periods of usage. It can be stored at room temperature for at least 3 years and due to the compound’s exceptional curing, bleeding, dry-out and thermal cycling characteristics, it can be used on the CPU for 5 years or more
No break-in or burn-in required
Some thermal compounds need a longer break-in period or cure time until they reach their full performance and some thermal pads must undergo a dedicated burn-in process. By contrast, NT-H1 is ready to go right away and doesn’t require any special preparations.
Extra-large 10g package for 9-60 applications
Sufficient for around 9-60 applications (depending on the size of the CPU or GPU, e.g. around 9 applications for large CPUs such as TR4 and around 60 for small CPUs such as LGA1151), the extra-large 10g packaging size is ideal for power users who install coolers frequently.
Specifications
| Weight | 10 g |
| Volume | 4,0 ml |
| Density | 2,49 g/cm³ |
| Colour | Grey |
| Recommended storage time (before use) | up to 3 years |
| Recommended usage time (on the CPU) | up to 5 years |
| Recommended storage temperature | room temperature |
| Operating temperature | -50 to 110°C |
| Note | *** Features, Price, Specifications are subject to change without notice. |
