Calvin Cutts said:
It might have nothing to do with OC. I though I was stable at least. I don't know how to find the blue screen error in event viewer.
I just need to know if I should increase the volts a little or not that's all.
Overclocking however, IS a major culprit in BlueScreens, freezes, and other aberrant computer behavior, and it can take anywhere from a few seconds to weeks of power-on state for an major error to occur due to overclocking that results in a BlueScreen.
By its very nature, an error due to overclocking can be entirely unpredictable.
You even can have a 'stable' system where errors are occurring, and the system may even manage to recover from them (or stupidly ignore them) and they remain hidden from the user...until they aren't.
One could also have a lot of undetected data corruption, because data that was corrupted before it's sent to the hard drive for storage isn't detected as corrupted data by the hard drive controller. Remember that your memory modules do NOT have ECC.
EventViewer may help, however keep in mind that even if it points to a 'driver' it may still be due to the overclocking as ANY kind of error may occur, including data detecting and reporting errors.
get some idea if that was an overclocking induced error by very slightly overclocking just a tiny bit more, and see if the time to failure decreases. If it does, then overclocking (or heat due to overclocking) is the likely cause. Undervolting can also contribute to such errors when overclocking. However, in any testing, be sure to backup and archive critical data because there's always a chance you could lose it. You may also end up having to reinstall the operating system one or more times.
I suggest you read up a LOT on overclocking. There are many technical articles and tutorials on this and other websites (like tomshardware.com
) and YouTube. Preferably find information pertaining to your specific CPU and your specific motherboard.