Linked by Howard Fosdick on Mon 31st Dec 2012 20:26 UTC
Hardware, Embedded Systems Last month, I explained why I use generic desktops and laptops running open source software. They're reliable and inexpensive. But this presumes you can fix them. I believe that even those with no hardware training (like me), can identify and fix most hardware problems. To prove it, here's a quick guide. Feel free to add whatever I've missed.
Thread beginning with comment 546834
To read all comments associated with this story, please click here.
Sometime it's just a mistery
by renox on Wed 2nd Jan 2013 16:17 UTC
Member since:

When I launch Chrome too early after the computer started, Windows XP gives me a blue screen of death quite often, if I wait some minutes most of the time it's okay.

Memtest86 shows nothing.

Note that I'm not asking for suggestions: I've given up on solving this issue, I just leave the computer alone a few minutes after I enter my password: Windows doesn't give enough enough information to help when it is crashing!

Reply Score: 2

Alfman Member since:


Some hardware problems can be ruled out using a linux live cd. I follow this rule for issues I'm unable to solve:

If, after reinstalling the OS with the latest drivers, the problem continues, I assume it's likely a hardware problem. If the problem disappears, then we know it was an OS glitch.

Reply Parent Score: 2