- Joined
- Sep 7, 2013
I'm having a serious issue with corruption here, and I can't stop it.
Chkdsk /f always comes back clean when it does the boot scan. (The first time it ran though, it came back with lots of issues which it said it fixed.)
Interestingly enough though, the boot scan will fail with "Autochk cannot lock the disk for direct access due to a recently installed software package" -_- I haven't installed anything i didn't have before I switched to AMD.
Also, the OC in question is a RAID0 on the built in AMD motherboard RAID using 2 WD green drives. (WD ERZX Sata 3 and WD EARS Sata 2, both 1Tb) I cannot see the WD ERZX drive in HD Sentinel... I was able to see the drive before with Intel RAID on the Intel mobo I was running.
I first noticed this when I was overclocking and when I was setting the FSB to 250. It wasn't quite stable at 250 yet until I upped the CPU/NB volts. It did freeze few times until I upped the volts. I've now set the system back to stock, leaving the Cool 'n' quiet and virtualization + all that other crap off. I also still have core 5 and 6 disabled. (Core 5 is weak and want more Vcore to be rock stable so I disabled it)
Previously I was running 4.7 Ghz. 1.568 Vcore, 1.15 NB volts, 1.300 CPU/NB v, 1.65 RAM volts, NB was @ 2300 Mhz, HT link @ 2700 Mhz, PLL (VDDA) was set to 2.8 Volts.
Temps were warm yes, but I was still prime stable for 8+ hours blend.
Since Chkdsk is always coming back clean, would it be safe to ignore this?
Or is one of the drives dying?
Any way to safely check the drives without destroying the RAID array? (IDE mode then run Hiren's DOS tools to check the SMART data on both drives?)
Some pics:
The latter being brand new (The AHCI warning one) - never seen this until I checked before I typed this post.
EDIT: If it also matters, the RAM passes memtest without issue. I loosened the RAM as I am unable to run it any lower - not even at XMP settings 9-9-9-24 @ 1600. last time I did that memtest failed. Perhaps I can try again since I'm stock now.
Chkdsk /f always comes back clean when it does the boot scan. (The first time it ran though, it came back with lots of issues which it said it fixed.)
Interestingly enough though, the boot scan will fail with "Autochk cannot lock the disk for direct access due to a recently installed software package" -_- I haven't installed anything i didn't have before I switched to AMD.
Also, the OC in question is a RAID0 on the built in AMD motherboard RAID using 2 WD green drives. (WD ERZX Sata 3 and WD EARS Sata 2, both 1Tb) I cannot see the WD ERZX drive in HD Sentinel... I was able to see the drive before with Intel RAID on the Intel mobo I was running.
I first noticed this when I was overclocking and when I was setting the FSB to 250. It wasn't quite stable at 250 yet until I upped the CPU/NB volts. It did freeze few times until I upped the volts. I've now set the system back to stock, leaving the Cool 'n' quiet and virtualization + all that other crap off. I also still have core 5 and 6 disabled. (Core 5 is weak and want more Vcore to be rock stable so I disabled it)
Previously I was running 4.7 Ghz. 1.568 Vcore, 1.15 NB volts, 1.300 CPU/NB v, 1.65 RAM volts, NB was @ 2300 Mhz, HT link @ 2700 Mhz, PLL (VDDA) was set to 2.8 Volts.
Temps were warm yes, but I was still prime stable for 8+ hours blend.
Since Chkdsk is always coming back clean, would it be safe to ignore this?
Or is one of the drives dying?
Any way to safely check the drives without destroying the RAID array? (IDE mode then run Hiren's DOS tools to check the SMART data on both drives?)
Some pics:
The latter being brand new (The AHCI warning one) - never seen this until I checked before I typed this post.
EDIT: If it also matters, the RAM passes memtest without issue. I loosened the RAM as I am unable to run it any lower - not even at XMP settings 9-9-9-24 @ 1600. last time I did that memtest failed. Perhaps I can try again since I'm stock now.
Last edited:
