Ketxxx
Heedless Psychic
- Joined
- Mar 4, 2006
- Messages
- 11,521 (1.74/day)
- Location
- Kingdom of gods
System Name | Ravens Talon |
---|---|
Processor | AMD R7 3700X @ 4.4GHz 1.3v |
Motherboard | MSI X570 Tomahawk |
Cooling | Modded 240mm Coolermaster Liquidmaster |
Memory | 2x16GB Klevv BoltX 3600MHz & custom timings |
Video Card(s) | Powercolor 6800XT Red Devil |
Storage | 250GB Asgard SSD, 1TB Integral SSD, 2TB Seagate Barracuda |
Display(s) | 27" BenQ Mobiuz |
Case | NZXT Phantom 530 |
Audio Device(s) | Asus Xonar DX 7.1 PCI-E |
Power Supply | 1000w Supernova |
Software | Windows 10 x64 |
Benchmark Scores | Fast. I don't need epeen. |
It's something I've always pondered, and I concluded the manufacturer can't conclude the modder has invalidated his \ her warrenty, but heres just one of many ramblings that goes on up in my head.
Youve just gone and bought a new component..(hey good for you!) for sake of argument we will use a graphics card for the example. Now as a modder worth any weight in his salt you inspect the card in detail before putting it in, making a note of the type of memory you have. Googling reveals your memory to be better than the card actually needs to run at stock frequencies (we will say for sake of argument the card requires 1.4ns memory for stock frequencies, but the card is equipped with 1.1ns memory) So you decide to OC the memory to 1.7GHz. (still within the frequencies set by the memory manufacturer of 1.8GHz)
Now heres the most interesting bit, we will say for sake of argument the card you bought is unstable due to poor memory timings being set in the cards BIOS, and even changing the timings to reference frequencies the memory manufacturer recommends does not work. You contact the graphics card manufacturer requesting a BIOS update, explaining the issue and as your confident in your skills (for sake of argument we will say you can proficiently program with HEX and your job is system memory tech support - so you are well versed in how memory works and what each timing does) You get a reply back from the manufacturer stating they will not help as you have "invalidated" your warrenty.
and heres the posed question, by increasing your memory frequency (yet still keeping it below the memory manufacturers specification) how have you "invalidated" your warrenty? As technically, you have not OCd the card at all - in fact the frequency set for the memory is still under spec and not being pushed beyond.
Just thought it might be an interesting point to duke out
Youve just gone and bought a new component..(hey good for you!) for sake of argument we will use a graphics card for the example. Now as a modder worth any weight in his salt you inspect the card in detail before putting it in, making a note of the type of memory you have. Googling reveals your memory to be better than the card actually needs to run at stock frequencies (we will say for sake of argument the card requires 1.4ns memory for stock frequencies, but the card is equipped with 1.1ns memory) So you decide to OC the memory to 1.7GHz. (still within the frequencies set by the memory manufacturer of 1.8GHz)
Now heres the most interesting bit, we will say for sake of argument the card you bought is unstable due to poor memory timings being set in the cards BIOS, and even changing the timings to reference frequencies the memory manufacturer recommends does not work. You contact the graphics card manufacturer requesting a BIOS update, explaining the issue and as your confident in your skills (for sake of argument we will say you can proficiently program with HEX and your job is system memory tech support - so you are well versed in how memory works and what each timing does) You get a reply back from the manufacturer stating they will not help as you have "invalidated" your warrenty.
and heres the posed question, by increasing your memory frequency (yet still keeping it below the memory manufacturers specification) how have you "invalidated" your warrenty? As technically, you have not OCd the card at all - in fact the frequency set for the memory is still under spec and not being pushed beyond.
Just thought it might be an interesting point to duke out