OK, the other shoe finally dropped. I was recently reminded that it is best have the BIOS set to optimized defaults. I had mine set to fail safe defaults, back when I couldn’t figure out why the SSD/SATA/HD drives weren’t showing up properly in windows. I finally got that solved, thru SATA/AHCI/Tim etc… settings, but never went back to optimized defaults.
My System - New Build:
Mobo: Gigabyte 970A-UD3 (2nd Hand)
CPU: Phenom II X4 965 (2nd Hand)
CPU Cooler: Noctua NH-U9B SE2 (New)
System Drive: Crucial M500 SSD 240GB (New)
Data Drive: WD Blue 1TB (New)
Ram: G.Skill Aries Orange 8GB (2x4GB Kit (New)
Graphics: MSI Radeon 6450 - Newest Drivers (New)
Case: Diablotech Titan
- - 2ea 120mm Intake fans
- - 1ea 120mm Exhaust and PsU Exhaust
Last night I decided to switch to optimized defaults, but then when the boot up process came to the point of loading the operating system, Windows began to load, but then stopped, a blue screen was displayed for about a second, and then it rebooted, and came up with a screen that said windows was unable to load due to files being corrupted, and asking to either run the repair utility, or start windows normally, neither of which works. The repair utility can’t fix the issue, and windows still will not load.
I tried going back to fail safe defaults, but with the same results, as the windows files are more than likely corrupted.
As an experiment, I set back to optimized defaults, and reimaged the computer with a fresh windows install image, and still no go, again, becaues the windows files are probably corrupted.
The images were all made with FAIL SAFE settings, so the next thing I plan to do is to switch back to fail safe defaults, where the images were all made, reimag the clean windows install image again. My logical mind says that should work, but I won’t be able to try it until tonight.
QUESTIONS:
1) What exactly is the difference between FAIL SAFE DEFAULTS, and OPTIMIZED DEFAULTS, and is it normal for switching between them to mess up windows files?
2) I did have a Prime 95 error on core 4 after 8.5 hours, could that be showing a weak CPU, motherboard, ram, etc…. or some other issue that could cause errors under optimized defaults?
NOTE: I never got an opportunity to run Memtest to check the RAM, re-run Prime 95, or anything else. I will have to do these tests on Saturday.
Thanks for any and all thoughts and comments,
Roger
My System - New Build:
Mobo: Gigabyte 970A-UD3 (2nd Hand)
CPU: Phenom II X4 965 (2nd Hand)
CPU Cooler: Noctua NH-U9B SE2 (New)
System Drive: Crucial M500 SSD 240GB (New)
Data Drive: WD Blue 1TB (New)
Ram: G.Skill Aries Orange 8GB (2x4GB Kit (New)
Graphics: MSI Radeon 6450 - Newest Drivers (New)
Case: Diablotech Titan
- - 2ea 120mm Intake fans
- - 1ea 120mm Exhaust and PsU Exhaust
Last night I decided to switch to optimized defaults, but then when the boot up process came to the point of loading the operating system, Windows began to load, but then stopped, a blue screen was displayed for about a second, and then it rebooted, and came up with a screen that said windows was unable to load due to files being corrupted, and asking to either run the repair utility, or start windows normally, neither of which works. The repair utility can’t fix the issue, and windows still will not load.
I tried going back to fail safe defaults, but with the same results, as the windows files are more than likely corrupted.
As an experiment, I set back to optimized defaults, and reimaged the computer with a fresh windows install image, and still no go, again, becaues the windows files are probably corrupted.
The images were all made with FAIL SAFE settings, so the next thing I plan to do is to switch back to fail safe defaults, where the images were all made, reimag the clean windows install image again. My logical mind says that should work, but I won’t be able to try it until tonight.
QUESTIONS:
1) What exactly is the difference between FAIL SAFE DEFAULTS, and OPTIMIZED DEFAULTS, and is it normal for switching between them to mess up windows files?
2) I did have a Prime 95 error on core 4 after 8.5 hours, could that be showing a weak CPU, motherboard, ram, etc…. or some other issue that could cause errors under optimized defaults?
NOTE: I never got an opportunity to run Memtest to check the RAM, re-run Prime 95, or anything else. I will have to do these tests on Saturday.
Thanks for any and all thoughts and comments,
Roger
Facebook
Twitter
Instagram