• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Stable overclock but alarming behavior on boot

Einzige

Weaksauce
Joined
Sep 2, 2016
Messages
82
Recently installed a Xeon x5650 in to a gigabyte x58 ud3r rev 2 Mobo and naturally went straight to overclocking.

I easily raised clock speeds to 4.2ghz, but when I boot the first thing I see is a bunch of crazy random colors that just screams something is wrong. Then a bunch of information concerning my drives pops up, then windows boots.

I've ran prime 95 for about 3hrs and my max temps are 60c with the cooler fan not even blowing full speed. Not even close. No problems. I played fallout 4 for several hours. No issues and massive performance gains. On grim Dawn I went from 100-110 fps to 135-145 and upper 50's to mid 80's in town max settings, 1440p.

What the hell is up with that crazy color static on boot? Why is everything fine thereafter?
 
Random colors/garbage on screen usually means memory corruption (particularly video memory) or some other damage to the video card, but not always. Any chance we could get a picture of it?
 
Random colors/garbage on screen usually means memory corruption (particularly video memory) or some other damage to the video card, but not always. Any chance we could get a picture of it?

It ONLY happens when I overclock. If I scale back it stops.

I'll see if I can get a picture later.
 
Maybe the PCIe bus is unstable at that speed? What kind of oc are you doing, fsb, multiplier...?
 
http://i66.tinypic.com/20uvb6r.jpg

So that's what my screen does for about 2 seconds before posting, then windows loads.

I ran prime 95 all night no problem, temps reaching a high of 60 only because that's where the fan keeps it at.

I dont think it's my graphics card because this only happens when I overclock the processor above 4ghz, otherwise things are normal. I want to push my OC further because I have good temps but I seem to be at my limit with a simple OC and it's doing this at boot.
 

Attachments

  • IMG_20160915_095011.jpg
    IMG_20160915_095011.jpg
    161.9 KB · Views: 46
what settings/voltage are you using? it looks like the OC is throwing off you pci-e bus and the video card is freaking out. try multi only, check that your pci-e is locked at 100 and maybe check for a bios update. also test you cmos battery as the board is getting older and ive seen a dying battery do all sorts of weird things. good luck!
 
what settings/voltage are you using? it looks like the OC is throwing off you pci-e bus and the video card is freaking out. try multi only, check that your pci-e is locked at 100 and maybe check for a bios update. also test you cmos battery as the board is getting older and ive seen a dying battery do all sorts of weird things. good luck!

Voltage is 1.35 on the cpu and I have to do bclk there is no other way to OC a Xeon x5650.

Pci-e is locked at 100 already.

But like I said this little freak out only happens at boot then everything is stable after.
 
Would like more input. Ill post a pic later showing my screen after the colors but unfortunately I'm on my phone and my 4g data is all gone this month.
 
Update: OK so apparently this issue only appeared whilst overclocking but is actually unrelated.

I swapped my GPU for another and got rid of the corrupted graphics. The screen was th x58 ud3r boot screen--first time I ever saw it.

So apparently my GPU might be damaged. Strange thing is I have absolutely no issues after the boot screen--only the boot screen is corrupted. After that everything is A-OK.

The card is brand new and I'm pretty sure I haven't damaged it. I haven't done anything that would cause such a thing. Is this a technical hiccup that I should ignore or should I attempt to swnd it in under warranty.
 
Back
Top