![]() |
|
|||||||
| Hardware & Software Help Hardware & Software related questions & help. |
![]() |
|
|
Thread Tools |
|
|
#16 |
|
Moderator
![]() ![]() |
Quote:
As for the grounding: I always ground myself since I fried 2 SIMM modules back in 1996. It's better be overcautious than damage perfectly good equipment. |
|
|
|
| Thanked by: |
|
|
#17 |
|
Passed the Turing Test
![]() |
Thanks for the great tutorial Gary. I think I'll try assembling my own PC if I find need/want for a desktop this fall. I'm going off to college and getting $1500 cash "for a laptop" but I already have a laptop more than capable of practical work.
Just one thing: When you get the chance, if you could fix the typos in the tutorial, I would feel much more confident in trying it out.
|
|
|
|
| Thanked by: |
|
|
#18 |
|
Orbinaut
|
All this is very good information.
Regarding static.. it cannot be emphasized enough to take good static precautions. There was a time last year, I *think* I *might* have mis-handled some ram, and sure enough, a few months later it had random bit errors in a certain location/address. I checked my maintenance log and found the suspect module was the one noted. The problem had presented itself in filing system operations. Large files being copied would sometimes get corrupted. And when it came time to back-up the system, the imaging program would report disk errors, but Check Disk would only sometimes correct a seemingly innocuous error in the $MFT, if that. Extensive use of Memtest86 verified the problem. I changed the module and everything was fine. No more corrupted files. Memtest86 could now run for hours without reporting a failure. So on and so forth. The point being is that static, like overclocking (but by different mechanisms) can cause latent damage that takes its time "eroding" the circuit pathways. The problem can show up months or years later and can be very insidious. Worse than spyware and malware. At least with nefarious viruses you kinda see something going obviously wrong and the ohh- moment is quite recognizable. You can take definitive action clearly and concisely. But with subtle static damage the problem creeps in on you slowly. You may not observe anything other then that there are unexplained CTD's happening or similar "strange" things going on at random intervals.
Last edited by Keatah; 04-09-2012 at 11:36 PM. |
|
|
|
| Thanked by: |
|
|
#19 |
|
Orbinaut
|
Regarding screwdrivers - magnetic bits can be quite helpful, because holding those screws in place within the tight confines of some motherboards can become awkward... if not potentially damaging to connectors.
|
|
|
|
|
|
#20 |
|
Orbinaut
|
I've done a little of this myself -- built a few PCs from scratch and worked on several others. I'm far from being an expert; I'm a guy who knows a few things and who has several friends who know less than I do, so I end up being the "go to" guy. Anyway, my comments, for what they're worth:
Quote:
1) install CPU, CPU fan, and RAM into motherboard. 2) install the motherboard + those things, as one unit, into the case. 3) install the power supply into the case. There's nothing wrong with doing it either way (it all ends up being hooked together the same way in the end), but by doing it in this order I can easily view the CPU from all sides while installing it into the motherboard (easier to see the pins that way), I don't have to hold the power supply cables out of the way while installing the motherboard into the case, etc. Quote:
|
|
|
|
| Thanked by: |
![]() |
|
| Thread Tools | |
|
|
|||||
| Quick Links | Need Help? |