On a scale from 1 to 10, how bad are Blue Screens?

[UnAdmin]

My overclock is 4.5 GHz at 1.33 v. I get occasional blue screens. About 1 or 2 a month. It's only when I'm playing higher end games. Never when I'm browsing the internet and similar activities (which is why I'm sure my overclock has something to do with it). 

 

[Anthony10]

well that probably means your components are overheating, if you are letting this happen a lot then a 10

[_ASSASSIN_]

windows is dumb and just bluescreens out of spite, my overclock not actually causing the problem (since the CLOCK_WATCHDOG_TIMEOUT isn't the error message)

[UnAdmin]

well that probably means your components are overheating, if you are letting this happen a lot then a 10

I have a closed loop liquid cooling on my CPU. I wouldn't think it's that. It never goes above 50 C, but I haven't checked in a while. My GPU can get pretty hot though.

[Anthony10]

I have a closed loop liquid cooling on my CPU. I wouldn't think it's that. It never goes above 50 C, but I haven't checked in a while. My GPU can get pretty hot though.

I would monitor your gpu temps on a stress test, is it an oced gpu?

[GeTecknics]

depends usually around 7-8 sometimes a 10

[Wats]

BSODs are pretty easy to solve. Download Bluescreenview, Google your stop code and make the changes.

 

 

These are the most common overclocking related Stop codes

 

0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

 

 

 

 

EDIT: BSODs are never good, to answer the question, 10/10

[Rashy]

BSODs are pretty easy to solve. Download Bluescreenview, Google your stop code and make the changes.

 

 

These are the most common overclocking related Stop codes

 

0x101 = increase vcore

0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is

0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

 

 

 

 

EDIT: BSODs are never good, to answer the question, 10/10

OT: Oooh Helpful when rebuilding my old system. +1

 

On Topic: Bad, from what i learn in old school gaming before i turn next gen is bad. Eeeeevil/10 

[flibberdipper]

10/10. Bluescreens are bad news.

[UnAdmin]

I would monitor your gpu temps on a stress test, is it an oced gpu?

No overclocking. But here's a GPUZ stress test result.

 

 

 

 

BSODs are pretty easy to solve. Download Bluescreenview, Google your stop code and make the changes.

 

 

These are the most common overclocking related Stop codes

 

0x101 = increase vcore

0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is

0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

 

 

 

 

EDIT: BSODs are never good, to answer the question, 10/10

 

I get different codes sometimes but the most often one is 0x00000124. Some are 0x1000007e and 0x0000001a. So I think my next course of action would be to decrease the GHz and a little voltage because 1.33v is the highest I can go.

[ttam]

Blue screens really aren't that bad. They just tell you something went wrong and shut down before anything happen. So more of a 2/10 really.

 

1.33 on a 4770k might be pushing it a little to far. Mine gets higher clocks at a lower voltage.

 

Check out WhoCrashed program and it gives more info on Bsod's

[Wats]

 

I get different codes sometimes but the most often one is 0x00000124. Some are 0x1000007e and 0x0000001a. So I think my next course of action would be to decrease the GHz and a little voltage because 1.33v is the highest I can go.

Go back to default everything. Run chkdsk /r and sfc /scannow. Might take awhile. Then back to overclocking! Copy>Paste that list, keep it handy.

[Bagmup]

Well, they're not good, a bit annoying.

[NInety]

What's a blue screen? - Linux User

[airdeano]

My overclock is 4.5 GHz at 1.33 v. I get occasional blue screens. About 1 or 2 a month. It's only when I'm playing higher end games. Never when I'm browsing the internet and similar activities (which is why I'm sure my overclock has something to do with it). 

I have a closed loop liquid cooling on my CPU. I wouldn't think it's that. It never goes above 50 C, but I haven't checked in a while. My GPU can get pretty hot though.

I get different codes sometimes but the most often one is 0x00000124. Some are 0x1000007e and 0x0000001a. So I think my next course of action would be to decrease the GHz and a little voltage because 1.33v is the highest I can go.

 

4.5GHz @ 1.33v with only 50° max? either you have gold or some temp

app is lying to you.

0x124 BSOD is low vcore voltage. so occasional BSOD is still unstable.

raise the voltage one step and retest.

[Leonard]

My overclock is 4.5 GHz at 1.33 v. I get occasional blue screens. About 1 or 2 a month. It's only when I'm playing higher end games. Never when I'm browsing the internet and similar activities (which is why I'm sure my overclock has something to do with it). 

I am quiet sure your OC has something to do with it. Most BSODs are no higher than a level 4.

[UnAdmin]

4.5GHz @ 1.33v with only 50° max? either you have gold or some temp

app is lying to you.

0x124 BSOD is low vcore voltage. so occasional BSOD is still unstable.

raise the voltage one step and retest.

I use SpeedFan to measure temps. Each core is only ever around 15C-20C on idle. I did however have to remove a temperature from the listing because before it would say my CPU would be 150C (which I assume is wrong or else my CPU would melt or something).

 

If all comes to worse then I can just use the OC genie in my BIOS for a lower overclock at 3.8 GHz.

 

Edit: Ran a CPU stress test. It goes up to 65C. Not 50C. A bit of a difference there.

[Biased Opinion]

lol my system blue screens about once a week, probably because of my stupid memory OC.

[vm'N]

BSOD isn't good, this is windows way to interrupt all processes.

 

This can happend for various reasons, some might not be anything serious (Driver-problems often), meanwhile other can cause some trouble (Corrupt OS files and so on).

 

Tip; Google the BSOD error code, check what causes it, and then fix it.

[ProKoN]

My overclock is 4.5 GHz at 1.33 v. I get occasional blue screens. About 1 or 2 a month. It's only when I'm playing higher end games. Never when I'm browsing the internet and similar activities (which is why I'm sure my overclock has something to do with it). 

core frequency \voltage X101 increase voltage or drop frequency

 

uncore frequency \ voltage X124 increase voltage or drop frequency

 

 

memory frequency \ voltage \timings X9C increase voltage if frequency and timings are set for xmp.

 

BSOD is not the end of the world, however for me its very annoying. the most annoying is flash or gfx driver being the root of instability.

 

my guide stresses the importance of isolating and stabilizing each variable one by one.

 

http://linustechtips.com/main/topic/41234-intel-haswell-4670k-4770k-overclocking-guide/

[Faa]

*

Thats pre BCLK

Proper one starting from Sandy bridge:

BSOD Codes for SandyBridge

0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)

0x101 = add more vcore

0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT

0x1E = add more vcore

0x3B = add more vcore

0xD1 = add QPI/VTT voltage

“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”

0X109 = add DDR3 voltage

0x0A = add QPI/VTT voltage

[Wats]

Thats pre BCLK

-snip-

But that was the Z77 list. Your statement confuses me a little to be honest. I guess if we want more... Here's the X58

 

 

 

BSOD Codes for i7 x58 chipset

0x101 = increase vcore

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is

0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

 

 

They're all pretty similar. And these work on Z87 too. We should prolly just combine them all