-
Good thread indeed, thanks for sharing.
My observation with stop code 124 was that I needed to increase vcore to get past large fft tests in prime95, but it definitely does relate to qpi too. Anyone else notice this?
Gigabyte EX58A-UD3R F6 : i7 920 D0 4.4GHz 1.4v : 4Gb G.Skill ECO 6-8-6-24 1.54v
Apogee XT & MCW30 : XSPC Dual 750 w/DDC+18W : RX120 & RX240 : Tygon tubing : Corsair HX 850
2x750Gb 7200.12 RAID0 : 2x500Gb 7200.12 RAID1 : Samsung DVD-RW : LG BD-R
Antec P182 with 5 x Noctua NF-P12 & 1 x Akasa Apache
M-Audio Delta 1010 (Rack) : Behringer Truth B2031A
XFX 5770 + 8600GTS (physx) : 2x Samsung Syncmaster 710n
Lappy: Asus C90s & E7500 @3.17GHz w/ 4Gb RAM & top scoring 8600m GT DDR2

-
The 0x124
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore.
On i7 32nm SB, usually means too little vCore. I've been getting it specifically when the vCore is too far from the target, but have been getting 0x101 when it was closer.
Last edited by Sam_oslo; 02-10-2011 at 01:49 PM.
► ASUS P8P67 Deluxe (BIOS 1305)
► 2600K @4.5GHz 1.27v , 1 hour Prime
► Silver Arrow , push/pull
► 2x2GB Crucial 1066MHz CL7 ECC @1600MHz CL9 1.51v
► GTX560 GB OC @910/2400 0.987v
► Crucial C300 v006 64GB OS-disk + F3 1TB + 400MB RAMDisk
► CM Storm Scout + Corsair HX 1000W
+
► EVGA SR-2 , A50
► 2 x Xeon X5650 @3.86GHz(203x19) 1.20v
► Megahalem + Silver Arrow , push/pull
► 3x2GB Corsair XMS3 1600 CL7 + 3x4GB G.SKILL Trident 1600 CL7 = 18GB @1624 7-8-7-20 1.65v
► XFX GTX 295 @650/1200/1402
► Crucial C300 v006 64GB OS-disk + F3 1TB + 2GB RAMDisk
► SilverStone Fortress FT01 + Corsair AX 1200W
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks