- Joined
- Jun 16, 2009
- Messages
- 5,123 (0.91/day)
- Location
- North of Germany
System Name | Nexus PC |
---|---|
Processor | Intel Xeon E3-1231 v3, 3600 MHz |
Motherboard | Gigabyte GA-H97-HD3 |
Cooling | Thermalright Macho V2 |
Memory | 24GB DDR3, 1400MHZ CL8 |
Video Card(s) | Sapphire Radeon R9 290 |
Storage | Samsung EVO 960 250gb, EVO 850 250gb, Vertex 3 128gb. 2 TB of Rotational. |
Display(s) | 1xAsus MX299, 2x Asus MX239, Oculus Rift CV1 |
Case | Sunflower Tower |
Audio Device(s) | C-Media CMI8738/C3DX |
Power Supply | Corsair TX850 |
Mouse | Cyborg R.A.T. 7 |
Software | Win7 64Bit Ultimate |
Guys!! The reason that we run WCG on the computer when they are idle is that even in solid state circuits, you still have the basic PN junction for each transistor switching component layed out on the die. When a PN junction is left idle for too long, the charge threshhold float balance (CTFB) starts to swing toward the stronger of the two (which is always present as the junction characteristics are determined by the physical properties of the die). This means that when the processor is left to idle for extended periods of time, the likelyhood of PN junction freeze (producing switching errors) grows exponentially, and will result in premature processor failure. The only way to ensure this does not happen is to keep the junctions in a continuously transitioning state. The only reliable way of doing this is by making sure the processor does not enter the idle state too often, which is exactly what the WCG software does. We are just trying to make the company's computers more reliable and a better investment overall.
... and remember, if you can't dazzle them with brilliance, baffle them with bullshit.
oh man, that made me laugh