Gridseed blade 80 chip scrypt miner - what are these errors?

[sunsetblues]

Hello everyone, I just got my first ASIC miner yesterday. A little used but its hashing steady at 5.692Mh/s on avg. I solo mined with it for a couple of hours this morning and hit one altcoin twice. I've been running it in a pool and payments are coming in steady so everything seems great. But under the hood I keep seeing these errors and I can' figure out what they mean. Would someone be kind enough to explain these errors?

[2017-10-08 18:12:21] < (no data)
[2017-10-08 18:12:21] GSD0: GetResults (amt=0 err=-7 ern=0)
[2017-10-08 18:12:21] < (no data)
[2017-10-08 18:12:21] [thread 0: 621954 hashes, 2.8 mhash/sec]
[2017-10-08 18:12:22] GSD1: GetResults (amt=0 err=-7 ern=0)
[2017-10-08 18:12:22] < (no data)
[2017-10-08 18:12:22] [thread 1: 630501 hashes, 2.9 mhash/sec]
[2017-10-08 18:12:22] GSD0: GetResults (amt=0 err=-7 ern=0)
[2017-10-08 18:12:22] < (no data)

I also use this command to start the blade:  cgminer --scrypt -o stratum+tcp://miningpool.thruhere.net:7998/#xnsub -u KSDDbiASUGSIdfouAhfohufchoduhvosdvh -p x --gridseed-options=baud=115200,freq=850,chips=40 --hotplug 80

I'm not sure if chips=40 should be set at 40 or 80. I tried it at chips=80 and it hashed just fine at 11.5Mh/s but I worried it might burnout the chip.

I'm also not sure if the --hotplug should be changed from 80 to something else. Any suggestions?

Thanks in advance for any help...

[1714699801]

1714699801

[1714699801]

1714699801

[1714699801]

1714699801

[QuintLeo]

freq at 850 is probably causing you a LOT of hardware errors.
 Those miners were "stock" at 700 but THAT was already a fairly hefty overclock, and tended to overstress the power delivery system.

[sunsetblues]

freq at 850 is probably causing you a LOT of hardware errors.
 Those miners were "stock" at 700 but THAT was already a fairly hefty overclock, and tended to overstress the power delivery system.

That was very helpful thank you! I'd hate to burn those chips out.

[not.you]

I haven't run one of these in a while but I am pretty sure the chip=xx is telling the software how many chips you have so it needs to equal what the blade actually has which according to your subject is 80.

[QuintLeo]

The "Blades" actually were 2 40-chip units, not a single 80 chip - so chips=40 would be correct.

 They hashed in the rough ballpark of 2.6 Mhash/sec (a little over as I recall) at their "stock" 700 Mhz setting.