system crashed big time !!! :(

scotslad

scotslad

scotslad

Associate
Joined
20 Jan 2009
Posts
811
I have had this self built and OC'd build since approx about a year or more now and this is the first I have ever had a sudden crash bang wallop with it :eek:

I was sitting here quite the thing and then next thing after it had been running maybe a few hours it just crashed and and instantly a big loud buzzing noise was coming from the case :eek:

I got the blue screen of death etc and I have added the screenshots of what it said etc so that you can see.

I dunno what it was, its a first for me, I don't know if the h100 pump seized for a second or something and caused it or what it was, but there was a crazy loud buzzing noise and I had to switch the machine off and hope that it rebooted, well I did and it seems to be back to normal, so I have no clue at all.

Do any of you guy have any suspicions on it ? Please let me know. thanks. :)

crash1.png

crash2.png


p.s
I thought it best to post this in this section because my system is overclocked etc.
 
Last edited:
Lol - you think that's a big crash?

Ask and serious overclocker about corrupted bios'es (that's why boards have dual bios now) and totally fubar'd OS installs when pushing for that last mhz ;-)
 
tamzzy said:
0x101 error = cpu related
Click to expand...

cheers mate, what could that mean then in realistic terms ?

p.s
although my signature says I have the cpu at 4.6 its actually only at 4.5 because 4.6 kept giving me too many problems, but as I say, its been totally stable for since the first days the i7 3770k came out whenever that was.

p.p.s, fixed my signature now, lol
 
Last edited:
BSOD Codes for LGA 1155 Ivy Bridge
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
 
tamzzy said:
BSOD Codes for LGA 1155 Ivy Bridge
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
Click to expand...

hmmm, strange that isn't it, all this time stable them crash bang wallop totally out of the blue and I haven't even been touching anything.

I can see your saying to increase cpu voltage = more heat etc as we all know, still seems all kinda strange to me though after so long with no probs, hmmmm :eek:
 
amigafan2003 said:
Lol - you think that's a big crash?

Ask and serious overclocker about corrupted bios'es (that's why boards have dual bios now) and totally fubar'd OS installs when pushing for that last mhz ;-)
Click to expand...

It was big to me mate, not used to crashes at all unless I am playing with the bios to get the speeds up etc etc, but for it to go so long stable and then this it was strange, and that big loud buzzing noise, what the heck was that man, lol ???
 
maybe just up the vcore by 0.005 and that'll solve the crashing.
maybe your current vcore is fine 99.5% of the time, just need the slight extra to get it 100% stable
 
tamzzy said:
maybe just up the vcore by 0.005 and that'll solve the crashing.
maybe your current vcore is fine 99.5% of the time, just need the slight extra to get it 100% stable
Click to expand...

cheers mate, thanks for that, what would you do though, leave it as it appears to be ok again ? or give it a little nudge up just for the sake of bearing in mind that even a slight nudge of cpu voltage on these jumps the heat up a few degrees etc.
 
tamzzy said:
depends on what your current vcore is i guess? if its like at 1.2v currently then an extra 0.005v wouldnt hurt?
Click to expand...

cant remember what its at mate, would need to have a look and get back to ya with the info, I know I have it offset etc so that the volts drop and temps drop when not stressed etc, but one thing I do know is its kinda on the low side compared to the crazy voltages that I see some of the peeps in here having to use, lol, but I know it all depends on each chip as they are all different etc.
 
Ok this is in the bios, I took some screenshots using my phone camera, so I hope you can view them proper, I have took 6 pics, hopefully if they are in the correct order you will see what is on the left side of the screen and then the values for that picture on the 2nd picture etc, I couldn't get them all in at once because I had to take close ups and its a 42inch sony smart tv I have, so that makes it a bit difficult to do that, hope you can still see them though and you can tell me what you think, remember this overclock as it is now has been solid stable since the 3770K first came out whatever date that was, I cant remember now.
______________________________________________________________
IMAG0994.jpg

IMAG0995.jpg

IMAG0996.jpg

IMAG0997.jpg

IMAG0998.jpg

IMAG0999.jpg
 
Just incase you cant see the digits clear enough the cpu voltage is approx hovering around 1.060 and 1.068 and is set to offset + at 0.010 so that I can keep temps as low as poss and also the voltages too, but as I mentioned, that OC has been rock solid until that one time just now and then It crashed and gave that crazy loud buzzing sound that ive never heard before, never ever, hmmmm.....apart from that it seems to be back to normal again though, so I really dunno if I should just leave it as a one off or tweak bits ?
 
post ur load vcore.
but if you've not experienced any crashes before, i'd be tempted to say to leave it.
unless the crashes become more frequent
you know, if it ain't broke and all...
 
@ tamzzy , you were spot on mate with your first suggestion of upping the voltage by 0.005 :)

I never use prime as it takes far too long in my opinion, I have always settled for the latest versions of Intel burntest and run that on maximum level for 10 runs, as far as I hear it is said that intel burntest really does hammer the cpu but its far quicker man, and I would never try it if I was running volts close to maximum and things like that as it could easily kill the cpu as you know.

Anyways, for some strange reason (I don't know why, maybe just months and months of time taking its toll), for some reason my OC you can see in the pics there always passed the maximum intel burntest option, but I ran it a few times tonight and to my surprise it failed the test after about 4 runs.

So I took your tip and I increased the offset + volts from 0.010 to 0.015 and it passed the whole test no problem at all, lol, so good on ya mate for helping me with that.

All it done to the Core Voltage in CPU-Z was raise it a fraction so that it sat mostly at 1.200v to 1.208 (max) where-as before at the very slightly lower offset it was hanging about slightly less than that and then obviously cause it is offset once the stressing is done the voltages and temps all drop away down.

At the max stress the temps were not getting any higher than low 80's on a couple of cores but about 75% of the test they would hang about the low or mid 70's, and that's with clogged up dirty mesh filters too because I have been too lazy to give them a clean, lol.

So thanks mate for the tip and the fix :)

Still wonder what that big buzzing noise was though ? and also why this all decided to happen anyway after all that time with no problems ? any Ideas ?

Thanks again ;)

p.s
those temps are in a room that is 21.6c degrees at floor temperature and at about 3ft high the temperature in the room is approx 27.2, the PC sits on the floor by the way and its a concrete floor with laminate on it.
 
Last edited:
scotslad said:
Still wonder what that big buzzing noise was though ?
Click to expand...

did it come from the speakers? if so, if you were playing an audio track (music/video/game) at the time it crashed it would be the repeat loop of that 1ms of audio, making it sound like a buzz

scotslad said:
why this all decided to happen anyway after all that time with no problems ? any Ideas ?
Click to expand...

no idea ;p
 
tamzzy said:
did it come from the speakers? if so, if you were playing an audio track (music/video/game) at the time it crashed it would be the repeat loop of that 1ms of audio, making it sound like a buzz



no idea ;p
Click to expand...

No mate, the loud buzzing noise was coming from the pc base unit, I dunno what it was, that's what I'm saying, I was like "what the heck is that man", I thought for a few minutes when it happened and thought hmmmm, if Ive never heard a noise like that in all my years with computers then I guessed it could only be one of two things, one being a fan jamming which I thought no way would it make a noise like that, there again maybe it could, Dunno ?

Then I thought hmmm, wait, since I made this build when the i7 3770K came out whenever that date was, this is the first ever time I have had any type of liquid cooling (the H100 first edition), so I thought hmmm, possibly the pump jammed on the heatsink ? Again I don't know.

All I do know is that when I switched it all off and then rebooted it seemed to be fine (touch wood for luck) and then I done that little bit of bios tweaking you suggested too and it seems to be fine all last night and now again tonight :)
 
Have you checked the motherboard for any signs of damage? blown caps etc? I would normally just say this is what happens when you don't do proper stability testing (unstable systems are bound to crash eventually) but the noise you describe sounds a bit strange. If you don't have an internal PC speaker (old school!) then I'd suspect the PSU would be the prime source of a noise like that?

Did the noise appear after the crash? or before?
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom