For bios caps, if you need to use a cam to doit, set the cam's exposure lv to the lowest it can go, in the neg's.
That will help with taking screens of the monitor.
It increases the shutter speed but also reduces the total light.
I also recommend totally not using flash, because it's showing up in the middle of your pics(monitor pics, the hardware pics are fine).
The plastic shielding thing...
I wish board makers were more serious about this, a meshed metal shield on the board would do fine, and allow heat to escape.
The chipset thing, pcie 3.0 and 2.0.
From what I understand, the cpu is 3.0 16x (actually I think it was 20x), and the chipset is 2.0.
Which is fine for most things, other then maybe m2 cards perhaps (even in that case, "in theory" it should not make a difference).
Your latency bug...
That's an odd one, I don't believe removing the mem should do anything.
However depending on how you boot up settings could make a difference.
Say or ex, you set 2133 mem, and it shuts down to reboot.
After that you set 2666 mem, and say it just resets, it doesn't power cycle, in this case there could be a prob.
Either the mem is gonna be hella fast, stuck with 2133 timings in 2666 mode, or it could go wrong.
My intel has an issue like this, at 100mhz bclk, 2400mhz div is ok, the 2666 div is not ok.
The 2666 has a mem write bandwidth bug.
However, if you manually power cycle it the bandwidth is normal.
I wrote about this a few years back.
Ok lemme see what I can pull up for notes (I don't have these sorted apparently).
;;;;;;; bios bug update 06/18/14
Set cpu to 42 and ram to 2133
Reset, after post I powered off
Powered back on, set cpu to 43 and ram to 2400
Reset...
No mem bandwith bug.
bios bug 08/28/14
messed around with 125mhz strap, 125mhz bclk
21.33 mem div, 2333mhz, good bandwith
set to 24x mem div, 2666mhz
after saving setting it didn't power cycle, but got bad bandwith
to verify this I messed around with the 1666mhz strap, 166mhz bclk
used 21.33 mem div, 2666mhz
good bandwith
so it's defenitely the 24x mem div
# 08/31/14
original fix + alt fix:
110mhz, assuming 40x cpu
set cpu to 38 (4180mhz)
after save manually power off if it doesn't.
set cpu to 40 (4400mhz) at 110 and set ram div lower at same time
after save manually power off if it doesn't.
set ram div higher and bandwith is good
alt fix:
100mhz, cpu set to 44x, ram set to 2400
set cpu to 42 (4200mhz)
after save manually power off if it doesn't.
set cpu to 44 (4400mhz) and set ram to 2133
after save manually power off if it doesn't.
set ram to 2400, good bandwith
newer fix:
100mhz, mem set to 2400 and cpu 44, or 43 who knows
set mem to 2133
after save manually power off if it doesn't.
set mem to 2400, good bandwith
long and through ver, if it works it might beable to be shortend:
set mem div to 24x
after save manually power off if it doesn't.
set cpu to 35x
after save manually power off if it doesn't.
set cpu to 37x and mem div at 21.33x
after save manually power off if it doesn't.
set mem to 24x
good bandwith?
loaded 114 profile, it power cycled
set mem timings to 10-12-12
it did not power cycle on it's own so I did it manually
after powering back on, set ram div to 24x 2736mhz and mem volts to 1.7v
badnwith was good, bsod'ed on me after the bench but ohwell, it's a ram thing
I have to figure that out later, I haven't tested those speeds yet
....
Blah blah, etc etc.
Just pay attention to how it sets certain settings, if it power cycles a ram div or cpu multi.
And if it didn't power cycle when it was suppose to.
Something like that I think, it's actually been a while.
Only reason I mention it is just incase...
To simplify it, the correct method:
newer fix:
100mhz, mem set to 2400 and cpu 44, or 43 who knows
set mem to 2133
after save manually power off if it doesn't.
set mem to 2400, good bandwith
Reply With Quote
Bookmarks