New
#11
Good. That means that the backup copy (in the store) is corrupted but the copy in sytem32 is good. Causes are many.
that script uses wininit.dll
Go ahead and run about 6 passes of MemTest86+.
That will test your memory and also is not a short test. You might want to run it overnight.
The only other general piece of advice has to do with your CPU and Graphic temps. Here I monitor temps if I'm not in a climate-controlled location as the unit can get too hot. Heat causes first wierd bsods and then shuts the computer down.
Memtest86+ - Advanced Memory Diagnostic Tool
RAM - Test with Memtest86+
Should I run the test with both sticks as is now, or like it says and do every stick singularly in every slot?
If i do the latter, how am i meant to do it overnight.
My approach is to first run with all modules in and just before hitting the rack to see if an error has already been found. If yes, then I start immediately with the stick by stick testing.
If no errors show at that first check, just let it run overnight, just make sure that you don't have a heat problem which will complicate matter. In other words, in a warm environment, take the cover off and direct a fan at the unit to help keep the temps down.
I ran 6 or so passes and it came up clear, I'll do another longer test another time.
Since then i've had a few more blue screens, which i've uploaded.
I've had a couple of more BSODS since.
Hope these help...
I ran the SFDiag Tool, and uploaded the results.
Please Help!
Bump, Is anyone going to analyse my dump files, I really need to know what's up.
Please Help!