- Joined
- Aug 17, 2008
- Messages
- 2,190 (0.38/day)
- Location
- Minnesota, USA
System Name | TaichiTig |
---|---|
Processor | i7 6800K |
Motherboard | ASRock X99 Taichi |
Memory | 32GB DDR4 3200 |
Video Card(s) | RTX 4070 |
Storage | SSD + Misc. HDDs in DrivePool |
Display(s) | BenQ PD3200U, Samsung C32HG70 |
Case | Antec Twelve Hundred |
Audio Device(s) | Behringer UMC404HD, LSR308, Shure SRH840, AKG K612, Etymotic HF5 |
Power Supply | Corsair 750TX |
Mouse | Logitech G502 |
Keyboard | Deck Legend Ice Tactile |
Software | Win10 |
For those of you who make your living (or part of it) building computers: what is your procedure for testing the system once its built, before turning it over to the customer?
What software do you use?
How long do you spend testing?
How often does your testing find an issue and prevent potential later problems?
What are the thresholds you consider acceptable for various things (max temps, max voltage ripple, etc.)?
I've known a number of builders who slap a system together, leave it on overnight, and if it's still running in the morning, call it good.
If you were the customer, what kind of testing would you want to know your computer went through before you bought it?
What software do you use?
How long do you spend testing?
How often does your testing find an issue and prevent potential later problems?
What are the thresholds you consider acceptable for various things (max temps, max voltage ripple, etc.)?
I've known a number of builders who slap a system together, leave it on overnight, and if it's still running in the morning, call it good.
If you were the customer, what kind of testing would you want to know your computer went through before you bought it?