There are a couple of quick and easy tests that you can do to find out what is happening:
1. Configure "movedaddrtrap" globally and per port to see if there are any mac moves. If there are unexpected mac moves then you will most likely have a loop on the network. The syslogs will tell you where the macs are moving to/from.
2. Take an open port and configure to egress all vlans on that port. Then put a wireshark analyser on the port and you will quickly see any broadcast , unscoped multicast or any flooded unicast traffic. This should give you an good idea of what the issue is as well.
Here is an article that deals with recommended L2 configurations to make the L2 environment resilient. Especially consider Loop Protect as this can isolate many issues that can fool spanning tree such as unidirectional forwarding on a link or looping behind a port.
https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Bes...
Also the following article may help tracking this down :
https://gtacknowledge.extremenetworks.com/articles/Solution/High-switch-packet-processing-CPU-use-on...
If you continue to have issues and need more in depth support you may want to consider opening a case with us.
Hope this helps
Glyn