"Reached daily quota of 6 results" - WTF?

Nov 24, 2010, 05:48 AM

I know I've seen this message before but shit if I can remember what causes it.

It just turned up on the new X6 and now that machine is just sitting there with no wu's.

Anyone remember what this is about?

Nov 25, 2010, 08:45 PM

I can't believe no one has ever had this problem.

Anyway, it turns out that for some unknown reason, the machine getting this error had dumped errors on a couple of dozen wu's. Virtually all of them however showed up with no CPU time, so obviously they weren't machine errors. Just to be sure I did a quick 5 IBT run on max which came up fine - actually generated slightly lower temps than when I ran it a few weeks ago.

Apparently when the servers see that a device has too many errors, they limit the number of wu's you can have until the problem is resolved. I guess last nights run of 6 units was fine since I have a full queue today.

I had trouble tracking down the error because I included the "6" in the quoted string. That number will reflect the number of cores running. When I did the search without the 6, I got some hits that were useful and helped me figure out what was going on.

[Ion] · Nov 30, 2010, 01:19 PM

Is it working now?

Nov 24, 2010, 05:48 AM	#1
twilyth Guest Posts: n/a (0/day)	"Reached daily quota of 6 results" - WTF? I know I've seen this message before but shit if I can remember what causes it. It just turned up on the new X6 and now that machine is just sitting there with no wu's. Anyone remember what this is about?

Nov 30, 2010, 01:19 PM	#3
[Ion] WCG Team Assistant Join Date: Sep 2009 Location: North Carolina, US Posts: 10,798 (7.86/day) Thanks: 8,306 Thanked 9,490 Times in 4,322 Posts System Specs	Is it working now? __________________ Ion's WCG Essentials Thread Crunching (64 Threads + 896 CUDA Cores + 6272 Shaders): i3-2100@ 3.1 + HD7850 -- Atom D510 @ 1.66 -- C2D-M T9600 @ 2.8 -- i7-3612QM @ 2.8 -- i7-860 @ 2.9 + HD7950 -- i7-2700k @ 4.4 + 2xGTX470 -- PentDC-M T4200 @ 2.0 -- i7-920 @ 3.83 + 3xHD7770 -- DP Xeon E5420 @ 2.5 + HD7930 -- E1600 @ 2.4

System Name:	Peenemunde/Salzburg/Osnabruck/Rostock/
Processor:	i7-860 @ 2.9GHz / i7-2700k @ 4.4GHz / i7-920 @ 3.83GHz / Core i3-2100
Motherboard:	Asus Maximus III Gene / Asus Maximus IV Gene / EVGA X58 SLI / Asus P8H77-I
Cooling:	Xigmatek Gaia / Xigmatek Gaia / Antec H2O-620 / Stock
Memory:	4x2GB G.SKILL / 2x4GB Crucial / 1x2GB Corsair / 2x4GB G.SKILL
Video Card:	Powercolor HD7930 / PNY GTX470 + nV GTX470 SLI / 3x MSI Radeon HD7770 GHz Edition / Sapphire HD7950
Hard Disk:	Western Digital 320GB / Western Digital 320GB / Western Digital 250GB / 320GB
Optical Drive:	None
CRT/LCD Model:	Asus VH242H (23.6")
Case:	None / NZXT Source 210 / NZXT Source 210 / Cooler Master Elite 120
Sound Card:	Onboard
PSU:	Antec TruePower New 650w / Antec TPN 650w / Antec Earthwatts 650w / Antec 430w
Software:	Windows 7 Professional x64

Nov 25, 2010, 08:45 PM	#2
twilyth Guest Posts: n/a (0/day)	I can't believe no one has ever had this problem. Anyway, it turns out that for some unknown reason, the machine getting this error had dumped errors on a couple of dozen wu's. Virtually all of them however showed up with no CPU time, so obviously they weren't machine errors. Just to be sure I did a quick 5 IBT run on max which came up fine - actually generated slightly lower temps than when I ran it a few weeks ago. Apparently when the servers see that a device has too many errors, they limit the number of wu's you can have until the problem is resolved. I guess last nights run of 6 units was fine since I have a full queue today. I had trouble tracking down the error because I included the "6" in the quoted string. That number will reflect the number of cores running. When I did the search without the 6, I got some hits that were useful and helped me figure out what was going on.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)