New
#11
Run SFC /SCANNOW Command - System File Checker in Safe Mode. You may need to run it up to three times to fix all errors. Report back the outcome.
Run SFC /SCANNOW Command - System File Checker in Safe Mode. You may need to run it up to three times to fix all errors. Report back the outcome.
I ran that command through a command prompt and it said, "Windows Resource Protection did not find any integrity violations."
What I see from post #4 is that you're having BSODs from multiple independent kernel components. This is often indicative of memory problems or a buggy driver (never, ever the one listed in the BSOD dumps) stepping on kernel memory.
First thing I'd do with this is download memtest86 on a working computer, burn a CD, boot the broken computer from the CD, and run a complete memory test. This will identify or rule out memory problems.
Since you have ATI graphics, the next step would be to upgrade your video drivers. I've had "a few" problems with older ATI video drivers causing widespread kernel memory corruption, leading to BSODs seemingly caused by other system drivers. Upgrading to the latest ATI drivers resolved the problem.
Next thing after that would be chkdsk /f followed by sfc /scannow.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
I also note that one of your blue screen errors was caused by CCC.exe; Try uninstalling that program by uninstalling the AMD Install Manager and all AMD software, etc through add/remove programs in control panel. CCC.exe can sometimes overclock graphics cards without the user's consent.
Okay, I put memtest86+ on a usb key (the installer did all the formatting and the installing for me) and then I tried to boot from the usb key but it throws me into a reboot loop before I can do anything.
I'm running the Windows Memory Diagnostics Tool at the moment and will report what happens in the morning. But if any of you find any other solution(s), please post. Would be appreciated.:)
EDIT:
Okay I ran the WMDT for two passes and it didn't find anything. I'll try running it for a few more?
Last edited by sh0td0wn; 09 Jan 2012 at 23:30. Reason: More action taken
You could try running on one Dimm - and then on the other(s) - one by one if there are more than two. If a Dimm is defunct, you would see that pretty soon.
That is a lot faster and more reliable than those memory tests that take forever.
And keep the power button down for 30 seconds with the PC disconnected from all power sources including the battery.