scout_03 said:
it could be the psu you need to have another one for test also for the hdd use the drive maker test tools on short and long test to find it fitness .
Trying to get my hands on another PSU to test, as well as a PSU tester.
I used the WD HDD tools to do both quick and extended tests on the boot drive. It came back fine.
johnbl said:
there can be other causes of this error code (hard drive starting to fail) but here is what I would start with:
if the problem is sporatic: I would remove any external boot devicea and reboot. (sometimes a thumb drive can cause the system to change the default drive letters around on you) I would also check the BIOS and see that the correct date and time are displayed (sometimes battery backup fails)
also, the master boot record is a target of some virus programs. I would run a virus scan, maybe malwarebytes to confirm
that any virus has been removed.
if the system boots I would run a full chkdsk on the drive, then do a system file check
sfc.exe /scannow.
basically error code 0xc000000d is unreadable boot configuration data
i would guess that File: \BOOT\BCD is corrupted
if the problem continues I would:
if you can boot into safe mode you would run cmd.exe
then run
Bootrec.exe /FIXMBR
bootrec.exe /FIXBOOT
bootrec.exe /REBUILDBCD
if that fails you might have to run the diskpart.exe command
diskpart.exe
list volume
select volume (then correct drive letter from the above command)
active (marks the selected drive as the active drive)
exit (quits the tool)
now you would run the bcdboot commands
bcdboot.exe c:\windows /s c: (where c: is the drive letter that you want your config file located)
bootsect.exe /nt60 all /mbr (writes a new master boot record)
now reboot and see if you can access your system.
I spent most of the weekend running all of these tests except for rebuilding the MBR.
As I stated above, the HDD test came back clean.
A chkdsk /r fixed a seemingly minor error and came back fine.
Virus scan of the MBR came back fine.
SFC came back fine.
Everything appears to be in order in the BIOS.
I also did a memtest which came back clean.
In the meantime, the constant crashing that I was experiencing on Friday has stopped (for now, at least). I haven't left it on overnight but it has at least remained stable for the past two days. I'd be shocked if the whole issue was caused by whatever small error was corrected in the chkdsk.
If I can get my hands on a PSU tester I'm going to try that. I suspect it won't be conclusive in this case though. I'll see if it crashes again this week. Maybe try leaving it on overnight to see if it makes it through the night... If it doesn't, I can try the MBR rebuild since I am still getting the 0xC000000D for Microsoft-Windows-Setup on start-up.
The only other error I see is:
The AODDriver4.3 service failed to start due to the following error:
The system cannot find the file specified.
Looking back through the Event Viewer shows that I've had such errors going back years w/ the AMD drivers, and a google search doesn't turn up anything problematic with it...
Any thoughts on something else I should do in the meantime?
Thanks!!