Men like to build and create. I’ve never been profoundly interested in or skilled at carpentry or stonework or automobile mechanics or, uh, spacklecraft. I do like to cook, but I’ve never constructed any kind of pastry.
I also do a little bit of gardening (mostly herbs), but I have kind of a brown thumb. Plants under my care have probably a 50-50 shot of surviving.
My creative tendency has been most manifest in my PC building efforts. The first time I built a computer, I made some unfortunate mistakes that wound up costing me. But when I got the thing working, man. Such a feeling of satisfaction – making something that not everyone can, and then putting it to good, honest use.
This second time I fared better on the front end, but over the past two or three weeks I’ve been getting a string of game crashes and blue screens of death. These kinds of setbacks can be profoundly disappointing and frustrating; computers are complex machines with all kinds of moving parts. You can look at dump files and event logs and errors messages, and sometimes you’ll be able to quickly or luckily diagnose the problem.
Often, however, the root cause of your troubles is elusive. Is it a driver? Bad RAM? Corrupted system files? Faulty PSU/not enough juice? Hard Disc error? Apps that just don’t want to cooperate with your operating system?
At least I’ve discovered a number of useful diagnostic utilities and system tools. System File Checker, Driver Verifier, Windows Memory Diagnostics, and Memtest86+ in particular strike me as good tools for any IT Guy or Gal to be aware of.
I also can’t overstate the importance of taking the time to check manufacturer websites for updated drivers, and becoming familiar with the Device Manager. I thought I had updated everything, but over the weekend I found that I had an old ethernet driver. Yesterday I checked out the support webpage for my motherboard and found that I was way behind on my BIOS version. That was a little more tricky to update, but relatively painless.
I haven’t been able to pinpoint any bad hardware so far, though I was suspicious of the RAM and the SSHD for a while. After I updated my BIOS yesterday I played the Witcher 2 for a few hours and didn’t get any BSOD or game crashes, so that’s a good sign. Fingers crossed I’ve stumbled upon the solution to my woes. Having a gaming machine that won’t run games is the absolute pits.
On Monday I couldn’t run Heroes of the Storm for more than a couple minutes without crashing to desktop, and I was branded with my very first “leaver” status. I’m apprehensive, but tonight I’ll give it a go and see if the BIOS update did it. Can an outdated BIOS cause other drivers to crash programs (my HOTS crash event log entry seemed to indicate a GPU driver-related incident)? I guess I’ll find out.