Anyone care to supply me with a screenshot of the list of devices under "System Devices" in Device Manager for this MB? I'd appreciate it.![]()
Anyone care to supply me with a screenshot of the list of devices under "System Devices" in Device Manager for this MB? I'd appreciate it.![]()
24/7 Cruncher #1
Crosshair VII Hero, Ryzen 3900X, 4.0 GHz @ 1.225v, Arctic Liquid Freezer II 420 AIO, 4x8GB GSKILL 3600MHz C15, ASUS TUF 3090 OC
Samsung 980 1TB NVMe, Samsung 870 QVO 1TB, 2x10TB WD Red RAID1, Win 10 Pro, Enthoo Luxe TG, EVGA SuperNOVA 1200W P2
24/7 Cruncher #2
ASRock X470 Taichi, Ryzen 3900X, 4.0 GHz @ 1.225v, Arctic Liquid Freezer 280 AIO, 2x16GB GSKILL NEO 3600MHz C16, EVGA 3080ti FTW3 Ultra
Samsung 970 EVO 250GB NVMe, Samsung 870 EVO 500GBWin 10 Ent, Enthoo Pro, Seasonic FOCUS Plus 850W
24/7 Cruncher #3
GA-P67A-UD4-B3 BIOS F8 mod, 2600k (L051B138) @ 4.5 GHz, 1.260v full load, Arctic Liquid 120, (Boots Win @ 5.6 GHz per Massman binning)
Samsung Green 4x4GB @2133 C10, EVGA 2080ti FTW3 Hybrid, Samsung 870 EVO 500GB, 2x1TB WD Red RAID1, Win10 Ent, Rosewill Rise, EVGA SuperNOVA 1300W G2
24/7 Cruncher #4 ... Crucial M225 64GB SSD Donated to Endurance Testing (Died at 968 TB of writes...no that is not a typo!)
GA-EP45T-UD3LR BIOS F10 modded, Q6600 G0 VID 1.212 (L731B536), 3.6 GHz 9x400 @ 1.312v full load, Zerotherm Zen FZ120
OCZ 2x2GB DDR3-1600MHz C7, Gigabyte 7950 @1200/1250, Crucial MX100 128GB, 2x1TB WD Red RAID1, Win10 Ent, Centurion 590, XFX PRO650W
Music System
SB Server->SB Touch w/Android Tablet as a remote->Denon AVR-X3300W->JBL Studio Series Floorstanding Speakers, JBL LS Center, 2x SVS SB-2000 Subs
^^ Thanks Bullet!!!
24/7 Cruncher #1
Crosshair VII Hero, Ryzen 3900X, 4.0 GHz @ 1.225v, Arctic Liquid Freezer II 420 AIO, 4x8GB GSKILL 3600MHz C15, ASUS TUF 3090 OC
Samsung 980 1TB NVMe, Samsung 870 QVO 1TB, 2x10TB WD Red RAID1, Win 10 Pro, Enthoo Luxe TG, EVGA SuperNOVA 1200W P2
24/7 Cruncher #2
ASRock X470 Taichi, Ryzen 3900X, 4.0 GHz @ 1.225v, Arctic Liquid Freezer 280 AIO, 2x16GB GSKILL NEO 3600MHz C16, EVGA 3080ti FTW3 Ultra
Samsung 970 EVO 250GB NVMe, Samsung 870 EVO 500GBWin 10 Ent, Enthoo Pro, Seasonic FOCUS Plus 850W
24/7 Cruncher #3
GA-P67A-UD4-B3 BIOS F8 mod, 2600k (L051B138) @ 4.5 GHz, 1.260v full load, Arctic Liquid 120, (Boots Win @ 5.6 GHz per Massman binning)
Samsung Green 4x4GB @2133 C10, EVGA 2080ti FTW3 Hybrid, Samsung 870 EVO 500GB, 2x1TB WD Red RAID1, Win10 Ent, Rosewill Rise, EVGA SuperNOVA 1300W G2
24/7 Cruncher #4 ... Crucial M225 64GB SSD Donated to Endurance Testing (Died at 968 TB of writes...no that is not a typo!)
GA-EP45T-UD3LR BIOS F10 modded, Q6600 G0 VID 1.212 (L731B536), 3.6 GHz 9x400 @ 1.312v full load, Zerotherm Zen FZ120
OCZ 2x2GB DDR3-1600MHz C7, Gigabyte 7950 @1200/1250, Crucial MX100 128GB, 2x1TB WD Red RAID1, Win10 Ent, Centurion 590, XFX PRO650W
Music System
SB Server->SB Touch w/Android Tablet as a remote->Denon AVR-X3300W->JBL Studio Series Floorstanding Speakers, JBL LS Center, 2x SVS SB-2000 Subs
DON'T try F4 :
- Cold BOOT
- Lower score CPU Score VANTAGE -700 pts
After doing some pretty intense testing over the last three days, I'm going to have to agree with Gaul.
I initially thought F4 was good to go, but I started noticing some oddities here and there such as random BSOD and instability problems. I finally decided to fire LinX up and run it against my 4.8Ghz settings with the F4 BIOS. Three times in a row LinX failed within 7 seconds of being started on my 2500k. I upped the vcore from 1.38v all the way to 1.43 and still couldn't get it past 7 seconds. It passed 3DMark loops just fine and had no problems with SuperPI 32M.
I switched back to F3D and my initial 4.8GHz settings...and what do you know it passed 25 loops of LinX without breaking a sweat and my hottest core reached 51C according to HWMonitor. From now on, I'll be using F3D until something better comes along and I'm going to keep pushing this chip. I thought I had reached its max, but it was probably the F4 BIOS causing the majority of my headaches.
Full specs in case anyone was interested (same used for F3D and F4):
Multi: 48X
Blck: 1005 (100.5)
Mem: 1600MHz @ 9-9-9-24 1T
Vcore: 1.38v (1.37v under load F4 / 1.36v under load F3D)
QPI/vtt: 1.12v
VCSSA: 0.945v
PCH: 1.05v
PLL: 1.7v
Shock'D:
CPU: Intel 2500k @ 5.0GHz
Motherboard: ASUS MIVE
RAM: GSKill 1866 @ 7-9-7-24
Video: 2 x HD6970 @ 940/1425
PSU: Corsair AX1200W
Case: Custom TJ07
Cooling: Cooled by EK and HWLabs
@ ^ = ha ha ha, then u must try F5 beta, better than F3D
I have F5b on my BIOS flash drive, just haven't tested it since I was told it simply fixes S3 sleep functions.
What sort of improvements does F5b offer over F3d? Does it have better vdroop control or enhanced stability? My vcore is already somewhat low so I think expecting it to be lower through a BIOS change is a bit unrealistic. I'm curious as to what your input is regarding F5b.
Thanks
Shock'D:
CPU: Intel 2500k @ 5.0GHz
Motherboard: ASUS MIVE
RAM: GSKill 1866 @ 7-9-7-24
Video: 2 x HD6970 @ 940/1425
PSU: Corsair AX1200W
Case: Custom TJ07
Cooling: Cooled by EK and HWLabs
And what were those values set to on the F3 betas? Did you actually test them? I highly doubt a BIOS would suddenly let you use lower values....
did you measure those voltages with DMM or they are just what you set in the bios?
i'm asking that because with UD5 i see that with bios F3 real VDIMM was 0.12 volt higher of bios setting, with bios F4 or F5 it was 0.15 volt higher.
maybe that's because you need lower voltages.
You SURE About that???
0.12v HIGHER means, 1.50v is 1.62v, and 0.15v higher is 1.65v.
Do you mean 0.012? Decimal places matter !
Did you test this on F3G (f3h)?
Because that's the first I ever heard anyone say the vdimm was that high. Sin tested it and it was almost spot on (that may have been UD7, though).
@Gaul
I've played around those voltages and my CPU doesnt seem to respond to any aside from just vcore.. Im actually concerned if lowering those values aside from PLL voltage would cause instabilities.. They dont seem to reduce temps or anything.
@ ^ = Which BIOS ?
F3b
EDIT:
Does upping the vcore increase power provided to the IMC or make it stable at higher multipliers or thats plainly controlled by the vDIMM ?
Last edited by Demo; 05-21-2011 at 09:37 AM.
NOT exactly.
I found out the difference between BSOD 101 and 124.
BSOD 101 only happens if one of the processors crashes at high load due to not enough vcore or too high temps. I've NEVER seen a BSOD 101 at idle or light load--ever---its always 124.
Likewise, I've never seen a BSOD 124 at max load...(like prime 8 threads), always seems to be 101.
BSOD 124 happens if the processor is at medium, light load or idle or unable to function at that voltage at light or medium load. Since 0124 can also occur if using 4 dimms at low VTT, I think it happens if the CPU crashes while communcating with the IMC itself, while 0101 is purely an instruction/cache error.
Bookmarks