Please register or login. There are 0 registered and 1321 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s December 15 - 01:26am EST 
Hardware Analysis
      
Forums Product Prices
  Contents 
 
 

  Latest Topics 
 

More >>
 

    
 
 

  You Are Here: 
 
/ Forums / Overclocking /
 

   Yesterday I had a blue screen  
 
 Author 
 Date Written 
 Tools 
Calvin Cutts Sep 01, 2014, 03:28am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List Replies: 6 - Views: 1485
And I was wondering if there's any way to determine if it was because of my overclock or not?

I'm running Window 8 64-bit.


Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
Rhort Sep 01, 2014, 03:39am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> .
What was the code for the "blue screen" error?

Also, what have you done to overclock your system, and by how much have you overclocked it (i.e. what percentage)?

_________________________________________________________________________________
~ The manual said "Requires Windows '95 or better" ...so I installed Linux!
Calvin Cutts Sep 01, 2014, 03:55am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Yesterday I had a blue screen
Well I don't remember the code, isn't there way to check like in Event Viewer?

I have an i7 4770K overclocked to 4.4ghz at 1.17v.

Rhort Sep 01, 2014, 04:04am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> .
The code on the error message will be the key to starting on a solution for this, and yes, it should be in Event Viewer.

I have 2500k o/c'd at 4.4, so it's probably not a straight 'too far' scenario, however, what was the process you used to overclock? What steps did you increase in; simply returning to the last stable one you used should at least get you back to a working machine.

_________________________________________________________________________________
~ The manual said "Requires Windows '95 or better" ...so I installed Linux!
Calvin Cutts Sep 01, 2014, 04:19am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List

Edited: Sep 01, 2014, 04:19am EDT

 
>> Re: Yesterday I had a blue screen
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.

john albrich Sep 01, 2014, 04:50am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List

Edited: Sep 01, 2014, 04:54am EDT

 
>> Re: Yesterday I had a blue screen
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.


You might 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.

john albrich Sep 01, 2014, 11:59am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Another Possibility blue screen
.
Just in case...

Since you just recently saw the BSOD, I thought you should also know about this as another possible cause.

Note:
BSOD flaw originally released to public in a security patch on Microsoft's "Patch Tuesday" 20140812
Corrected patch was RE-ISSUED 20140827


http://www.tomsguide.com/us/microsoft-faulty-security-patch,news-19351.html
UPDATED 12 pm Aug. 28, 2014, with Microsoft reissuing the patch without bugs.
One of Microsoft's recent security patches has created an even worse bug than it patched: Under certain circumstances, the faulty patch causes Windows computers to crash, reboot and then get stuck in an infinite rebooting loop.
Microsoft has since recalled the patch. For people already caught in the perpetual "blue screen of death" (as Windows crash screens are often called) the company has issued a workaround that people can use to get their computers up and running again.


Write a Reply >>


 

    
 
 

  Topic Tools 
 
RSS UpdatesRSS Updates
 

  Related Articles 
 
 

  Newsletter 
 
A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.