|
Answer» BSOD could also be from a bad driver.
Does the BSOD reference a driver name, like something.sys? Ok, the problem is today solved! yay. Thought I'd log in and update this topic in case someone else needs it.
Turns out it was an issue with Microsoft Runtime libraries not being current.
It wasn't overheating. I had the AMD chip up to 68c during a warm SPELL and there was not a problem, no crashing UNLESS I again tried a vid file, so I eliminated overheating.
I entered the Event Viewer after the last crash and found an error message relating to this - VC80.MFCLOC - being missing. GOOGLED it, came up with MANY possible causes but the most common was the MS Runtime Libraries needed to be installed or updated.
Visit
http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en
to download and INSTALL the latest 2008 Runtime components. As soon as this was updated, no more crashing...
Thanks all for your posts! off to watch holiday vids...
Wonderful
Thanks for posting back, and watch those temps anyway.
|
