There are 64 'tiles' per chip and 16 engines per tile for a total of 1024 engines per chip. I've not run across a pair of chips that have all 1024 running, I think the closest was around 2028.
Ok, so each "tile" is kind of like a little BFL chip of yore. Those had 16 little engines in each chip, but were addressed in software as a single "chip". Different chips had different numbers of engines running, a few had all 16, most had 14-15 and a really crappy chip would have only 8 engines (65nm chips).
Question in my mind is what makes a "B" chip. I'd kind of expect engines to be out at random, some cortexes with all engines, some dead as rocks based on the variations in manufacture. Or maybe the missing engines will run at lower clocks, and this is the best balance of power to performance.
Meantime today's runs included stopping the BFGMiner and restarting a few times without powering down the Monarch. I'm running on a single 500 watt Corsair power supply with both plugs plugged in, keeping it simple. No errors at all with the exception of the queue errors that pop up because of stale jobs left when you stop and start. It hums quietly, does not change the hum, does not pop any errors once running. Likewise speed is a solid 690gh, solid as a rock.
So I think I can say the following:
- if the unit is running and hashing normally the odd errors do not pop up
- If I restart BFGMiner when there are no errors, the errors do not show up again once running with one exception
- If I power the unit off then on, the pitch of the FET/Chokes changes and the errors start popping up at random
- If I leave it off for over an hour the errors go away upon restart and the FETs are quieter
Never dull.
C