ProtoTypical writes:
I am on a 10 yr old laptop with half the letters worn off the keyboard.
Chances are, you could find a more advanced machine (can do everything you're current laptop does, but faster and lighter) for about $100 to $200 from Walmart.
But... if you did that, it would probably break in a year or so... 'cause it's from Walmart.
Even "good, new laptops" for $400-$700 will be hit-or-miss for lasting 4-5 years.
Anything over $1000 doesn't mean it's built to last either... it likely just means it has fancier video-card equipment or solid state drive technology or something else that has a decent chance of not lasting more than 3 or 4 years anyway.
"They don't make 'em like they used to"
Generally I prefer old familiar things over shiny new things.
If you like what you have, I would advise sticking with it as long as possible (although it sounds like that time is coming, unfortunately). All computers eventually malfunction. It's just what happens.
Percy's suggestion seems like it may be promising in removing the issue.
You can start on page 1 at the post marked "Posted 03 June 2013 - 04:27 AM" by Psychotic
Although, I'd try reading through it first if I were you.
I don't understand why he created the "fixlist.txt" file a few posts after that.
Likely those are locations he thinks may be causing the issues.
Something in the log files jumped out at him and I don't personally understand what or why (but I wouldn't, either... this isn't exactly my sort of thing).
If you create the same log files, and the things in that list are located in your log files as well... then I would assume that you should include the same things.
However, if your log files don't include certain things in that list... then I would guess that you shouldn't include them (may cause an error when the script is ran).
The one 2437DF07D3CB4D858397ED8AE9ED26D5.TMP file may be different per machine, though... that would be tricky if it's something you're supposed to have in that fixlixt.txt file... but hopefully it just shows up in your logs too. Then there's nothing to worry about.
Hopefully your understanding of the log files and the procedure he's trying to do is better than mine?
Good luck.