Computer Builders, What's Your Testing Procedure?

[TIGR]

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?

[Papahyooie]

depends on what they are going to use it for. Office work? Test it with openoffice. Media? Test it with your media player of choice (cough* VLC) Gaming? Run crysis, 3dmark, whatever game they want to play on it. Plus your stress test of choice if its overclocked. Tailor each one to its specific use.

[TIGR]

No checking temps, doing a memory sweep, testing CPU, checking voltage, etc. (overclocked or not)?

Just to clarify: not judging, just clarifying!

[p_o_s_pc]

I would use a stress test like linpack and memtest and leave the computer run overnight to make sure its fine.

Also I would want Coretemp or Realtemp used to check CPU temp Speed fan for system temps

[hat]

OCCT is a great tool. It has Linpack and a rigorous GPU stability test. I've gotten into LinX recently though, it's cpu-only but it's really nice.

[TIGR]

Speaking of temps, p_o_s_pc (and anyone else), how do you decide what temps are within "acceptable" limits for various components? Simply experience, manufacturer's claims, Google....

And is there any definitive info out there on what program(s) is/are the most accurate for checking temps of the different components? For every piece of software out there for checking temps, I've heard people say it's the best and the worst when it comes to accuracy.

[newtekie1]

Basically it depends on the system.

If it is just a low end office computer, any problems that might come out will probably come out while I'm installing software. I still run OCCT Linpack overnight to make sure temps stay in acceptable ranges(though since I'm usually using stock cooling, they get pretty high for my standards...) I'll accept under 80°C here after running all night.

If it is a higher end computer, I'll do OCCT Linpack overnight and make sure temps are acceptable. What is acceptable depends on the cooling I'm using. I'll also run at least 4 hours of Vantage looping if the machine is going to be used for gaming. Keeping an eye on both CPU and GPU temps.

Though pretty much you can just tell if a machine is good or not by using it for a while and getting the software installed. I don't overclock anything that I'm selling to a customer, unless they specifically ask for it without me bringing it up and they understand that I'm not responsible if something goes wrong or is unstable, so since most of my machines are stock there isn't much worry about temps or stability.

[p_o_s_pc]

Originally Posted by TIGR

Speaking of temps, p_o_s_pc (and anyone else), how do you decide what temps are within "acceptable" limits for various components? Simply experience, manufacturer's claims, Google....

And is there any definitive info out there on what program(s) is/are the most accurate for checking temps of the different components? For every piece of software out there for checking temps, I've heard people say it's the best and the worst when it comes to accuracy.

The rule of thumb i go by is
AMD CPU 50c or lower
Intel 60c or lower

Chipset ~50-60c or less for Intel,AMD,Nvidia doesn't matter to me
GPU temp Max i like is 85c
Case temp doesn't matter much to me if everything else is running cool. I would also google the components in question to be sure there safe. I try to keep everything bellow the what the manufacture says by a fair amount

as for programs Speed fan,Everest,Hardware moniter, Coretemp,realtemp NextSenser are all good software for temps and for me they seem to be the same temp on each of them

[SummerDays]

I doubt system builders do very much to your system besides running it for 24 hours with a test program, and that's if you're lucky.

The end user is the one who will usually discover whether or not a system has problems, and usually the more time the user spends with the system, the better they will know it.

[Melvis]

When i build a new system, the first thing i do is go into the BIOS and watch the CPU temp, fan speed, HDD connected, ram Speed etc. I watch this for about 30mins. Then once that passes i install windows, drivers, etc. Then i retest temps by what ever program im running. Then id give the computer a stress test, and most of the systems i build are for gaming so i ether run 3DMark06 a few times then i might even install a game and flog it all day. If i get no issues, then its a go. Of course i check temps at all times as the tests are been done.

Thats how i do it anyway, and i run a business from home building computers.

[TIGR]

Thanks guys, good responses here. I like hearing what others are doing.

Melvis, I do the same thing as you, going straight to the hardware monitor in the BIOS (gotta go in anyway to check voltages, timings, boot settings and miscellaneous other anyway).

[p_o_s_pc]

Originally Posted by TIGR

Thanks guys, good responses here. I like hearing what others are doing.

Melvis, I do the same thing as you, going straight to the hardware monitor in the BIOS (gotta go in anyway to check voltages, timings, boot settings and miscellaneous other anyway).

I forgot to tell you about the BIOS I just recently started doing that its a great idea but sometimes i forget about having the hardware monitor in the bios

[TIGR]

Haha I hear ya. I always go straight there because no matter how many I build, I'm always concerned I might have messed up a heatsink, or that something might have been jarred loose in shipping. It's actually saved me a lot of time on a few motherboards, realizing there was a problem right away as opposed to installing the OS and then finding out....

[hat]

AMD cpu: under 60c
Intel cpu: same... unless it's an i7, then under 80c
GPU: I like to see under 70c
Chipsets... 50c-60c

[DirectorC]

When I build a computer I just slap it together and if everything goes well through OS, driver & software install I call it stable. If it's overclocked, I used to prime95 it all night like everyone else, but last year I discovered Linpack and that's what I use for stability testing now (with LinX). If an overclock can handle about 20 runs using the max amount of RAM then I call it stable.

[Melvis]

Originally Posted by TIGR

Thanks guys, good responses here. I like hearing what others are doing.

Melvis, I do the same thing as you, going straight to the hardware monitor in the BIOS (gotta go in anyway to check voltages, timings, boot settings and miscellaneous other anyway).

Yea its defiantly the first and best thing to do when you first boot a new system.

Im always nervous when i first hit the power switch, is it going to POST or not lol

[Sensi Karate]

If its your job to build a computer I think that they'd just slap it all together and see if it booted. Most computer shops who also have the option to build a computer would usually have to build multiple copies of the same computer for a company. If they have a deadline with X amount of computers to be built then they don't really have the time nor patience to do a thorough test of the systems stability, if it runs, it runs.

However don't take my word on it, I'm only speculating what would seem the most plausible.

[assaulter_99]

Originally Posted by Sensi Karate

If its your job to build a computer I think that they'd just slap it all together and see if it booted. Most computer shops who also have the option to build a computer would usually have to build multiple copies of the same computer for a company. If they have a deadline with X amount of computers to be built then they don't really have the time nor patience to do a thorough test of the systems stability, if it runs, it runs.

However don't take my word on it, I'm only speculating what would seem the most plausible.

Yes thats the way it goes. Seriously, just enthusiasts will test (prime95, OC it or whatever). If its a rig with high end, latest hardware, well maybe then, otherwise they just get sick of seeing and building computers, the quicker they are done, the better!

[HookeyStreet]

Press the power button. If it boots up without smoke bellowing out of it, its good to go

[SoulTribunal]

I think my Total Client Builds now exceed 300 but what I do is this.

OCCT for PSU Stress Test (Which In reality stresses your entire system to the brink).
3Dmark and Furmark.
Intel Burn Test.
Prime 95 Overnight.
FAH GPU Memory Tester
MemTest

When the build is complete I run all components for 48 Hours before releasing to the customer.

Haven't had an issue yet.

ST

[pantherx12]

I install all my usual crap, run the system as if it was my own for a few days.

Generally puts it under enough stress.

Then I wipe reinstall windows and give the rig to the customer : ]

[kylzer]

LinX Max ram usage @ 10 Rounds

Then rthdribl at max settings for 20-30mins.

[douglatins]

OMG lots of you guys make money out of building rigs? Maybe i should try that over here.

Though i have a strict policy of only touching new and high end hardware LOL

[SoulTribunal]

Originally Posted by douglatins

OMG lots of you guys make money out of building rigs? Maybe i should try that over here.

Though i have a strict policy of only touching new and high end hardware LOL

No Not really.
Profits from the Gaming builds help me subsidise builds for people who can't afford computers but need them.

I break even, thats good enough for me.

ST

[TIGR]

Originally Posted by SoulTribunal

No Not really.
Profits from the Gaming builds help me subsidise builds for people who can't afford computers but need them.

I break even, thats good enough for me.

ST

Soul, that's a kind and neat idea.