I am also having this problem with the arithmetic overflow error. I am using SQL Check version 3.5.2012.1005. I ran profiler and caught the error. It occurs in the code below and is specifically in this line:

sum(convert(bigint, case when wait_type='ASYNC_DISKPOOL_LOCK' or wait_type='ASYNC_IO_COMPLETION' or wait_type='IO_COMPLETION' or wait_type like 'PAGEIOLATCH%'
then wait_time_ms - signal_wait_time_ms else 0 end)) as 'I/O',

sum(convert(bigint, case when wait_type like 'LATCH%' or wait_type like 'TRAN_MARKLATCH%'
then wait_time_ms - signal_wait_time_ms else 0 end)) as 'Non-Page Latch',

sum(convert(bigint, case when wait_type='ASYNC_NETWORK_IO ' or wait_type like 'BROKER%' or wait_type='CURSOR' or wait_type='CXPACKET' or wait_type='EXCHANGE'
or wait_type='PAGESUPP' or wait_type like 'PREEMPTIVE_%' or wait_type like 'SLEEP%' or wait_type='SOS_SCHEDULER_YIELD' or wait_type='TEMPOBJ'
or wait_type='THREADPOOL' or wait_type='XE_%'
then wait_time_ms - signal_wait_time_ms else 0 end)) as 'Other',

The Problem has been resolved by "chance". We had to reboot the DB Server and thus all the Counters were reseted, particularly the "Cumulative ..." Counters (eg. Cumulative Wait Time).
Now all those Counters are back within the INT realm !

We received your files, and we analyzed them thoroughly. Indeed, as you suggested, the problem appears to be due to cumulative counters overrunning their limits on busy instances over a long time. We added this issue to our issue tracking system.

Peter, some progress on this issue? We have this problem constantly with IDERA SQL Check (new version 3.6 and in old versions too) and we can´t reboot the server when this occur. This cumulative counters can be cleaned in another way??

I checked using TraceX log and this error occurs on "Get online statistics" method. Bellow is where the error occur, in RED:

Fernando, thanks for the detailed analysis. Your observations match those of Lee further up in this forum thread (posted Thursday, October 6, 2016). I added the details of this forum thread to our issue tracking system.

Unfortunately, we are not able to update the source code of SQL Check anytime soon. So, for the foreseeable future, SQL Check will continue to suffer from this limitation on busy instances.