Discussion in 'General Hardware' started by fullinfusion, Aug 30, 2014.
Can someone tell me what this means?
Ok so whats that mean? I read about the dead locks and such but what would be the problem?
Overclocking, psu bad, mb bad, cpu bad, overheating, cpu/memory settings ?
Try running linpac or OCCT and memtest to narrow down the cause also check system log.
Reduce your clocks to stock and try it. If no fail then your oc was too much bro
With high clocked intel rigs this can point to cache voltage (ring) I would start their before playing with drive strengths and core voltage.
even though running the cache at stock 4ghz at stock cache volts?
degradation maybe? I cant be sure its just something iv seen.
Yeah thats what Im thinking but really so soon?
This chip is not even 2 months old and never had more then 1.40v's to it. @4.9ghz I used to run at 1.32-34v's and never had it above 80c
have you changed ram or timings? Maybe its memory controller related.
Nope I haven't changed a thing... all I did was run H-264 video benchmark then that's when shit hit the fan
this is good news. since H264 is hardware level on the CPU since SB. can you
A: recreate this with the software you used to do the original encoding?
B: If yes or no can you trigger this using another program to record/play/encode h264?
this might be an actual issue with the software itself passing something the hardware did not like.
No actually I cant... I do think the board is toast as my audio is now flaking out driver wise..
Try running linpac or OCCT
Drop your clock to 4.8/4.7
Try a different CPU, if you can.
And, you may want to run "msconfig". Then find the "number of processors" and set it to one (1). Check the box. Then,reboot & test it.
It is possible you may have a bad (failing) or dead core... If that is the case RMA the processor.
definitely buss related
give the uncore/qpi some more voltage lower the core multi one peg if that doesn't do it bump the pll voltage one step
that stop-code means that one of he cores fell out of sync in a multithreaded operation usually that means the uncore/qpi is unstable remember even if you haven't touched the base clock at higher frequencies you need to feed the uncore more voltage
This isnt good as audio and ethernet are usually the first things to go during board failure.
@fullinfusion if you installed viper's audio uninstall it I had a issue with it randomly cutting out on 2.75 ALC982 the older drivers are fine tho
Well problem is *I think fixed*
Windows updates wasnt installing straight from a clean OS install. The web was full of the error code porblems ppl were having and Microsoft needed to fix it.
Yesterday I was able to get 166 updates installed and my 4.9 stable again but sadly the cpu degraded a tad. I needed to up the vDIO and vAIO a bit and that smartened it up.
I just backed down to 4.8ghz and use way less vcore now and the other voltages I set to auto and are running way less on auto. So far i've been stressing and shes holding up *for now*
This chip works well @ 4.8 but needs a lot more voltage just to get that extra 100mhz but hey I can live with that lol..
I'll report if anything else pops up and thanks for the suggestions guys
auto voltages can be REALLY bad make sure they don't swing way out of spec and smoke the proc
Next step, pop the lid, shim it and lap the heatsink.
Yeah I checked and they're real low so no problems there.
Auto voltages on Z87 boards seem to be pretty damn good from my findings, especially on Asus boards. ASrock seem to beef voltages up higher under Auto, along with GB. The last MSI board I played with performed very similar to my Asus Z87 Pro...both kept voltages pretty minimal or where I would have manually set them anyways. I wouldn't be too concerned about AUTO with these newer chipsets and boards.
Glad you're getting it sorted man.
Separate names with a comma.