Perhaps the word 'spindump' isn't applicable to the situation you've experienced,
because Spindump is the name of a process that a user would seldom initiate
and could be dangerous for an inexperienced person to run this.
You'd have to investigate the Console logs for the time/date (exact) to see what
other processes may have been running at the interval you had witnessed this.
The spindump process should be able to show a log of all activity in a cycle.
So if you had not initiated the actual Spindump process, please outline the
point using other words to describe what your Mac was doing before this.
The following is an example of running Spindump would mean... a slightly
different page exists for 10.10; this covers older OS X 10.9:
Here's a section from the Developer Library that covers Spindump processes (10.9)
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/spindump.8.html
•Mac Developer Library:
https://developer.apple.com/library/mac/navigation/
The basics generally may help, so to start the Mac up in Recovery (command+R)
then choose Disk Utility, then repair disk, and repair disk permissions, & then restart
may be helpful. - There are methods of using command-line code to help see what
parts of the system were taking part in the erratic time you noted, and that kind of
helpful information requires a depth of understanding the unix code; or the ability
for someone such as Linc Davis to reply and ask you to enter certain lengthy lines
of code into your computer, so it will spit out a huge or large report file. That would
then be posted in the discussion, where he may see it & reply. That is testing as
part of advanced troubleshooting the system, using console utility system logs.
Usually you can tell if a problem is based on software or hardware, by using basic
troubleshooting techniques that are part of the OS X. Some users set up a second
drive and a clone or a bootable USB, for use in troubleshooting, archiving, and
other tasks that may include restoring the computer content from backups, too.
Since I'm not sure what it is you've witnessed your relatively new computer do.
If you could set up an appointment with an Apple Genius, to have them check
into it, that may (or may not) be of some help. There should be certain logs from
the system in Console that would tell quite a bit about what happened, then. And
if the causes are in hardware, or not.
Sometimes software a user has installed may promote odd issues, or troubles.
IF there were not enough RAM installed, then perhaps the system really went
into overtime trying to shuffle temporary files on the hard disk drive, and sort
out a pile of stuff; and that would also have generated some heat & fans.
In any event... it's nearly 2AM here.
Good luck & happy computing! 🙂
