OK - I seem to have stabilized the goings on with the hangups and dropouts with this particular project on this particular computer.
 
I am not finished testing and trying to reduce things that I changed, but I thought I would at least indicate that it now seems to play back from start to finish with no dropouts or crashes or any of that.
 
I am, however, to bleary-brained to continue testing at the moment, so will take a big giant nap and see what that does.  :)
 
By the way, in addition to making sure all was patch current and all of that sort of thing, the other changes I have recently done were:
 
1. Added 8 GB memory (bringing total to 24 GB)
2. Cleaned up temporary files/folders all drives
3. Tested with Kore 1 audio interface
4. Switched to FocusRite Scarlet 2i2
5. Tested with all effects bypassed
6. Bunch of other tests various configurations
7. Switched USB Cable to interface
8. Switched USB 2.0 port for interface
9. Disabled FIOSTV entries in Software Devices
10. Disabled all HD audio entries in Sound, Video, and Game Controllers
11. Adjusted Registry Paramater for AMD as follows, to simulate core parking:
 
      AMD Core Parking Equivalent
      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251=82be-      4824-96c1-47b60b740d00\0cc5b647-c1df-4637-891a-dec35c318583]
     Attributes = dword: set to 00000000
     Reboot System
 
12. Enabled a single HD Audio to allow Windows sound and HDTV connection
 
 
The song has thus far played back 4 times completely through with no weirdness at all.  Tomorrow, I will add additional tasks, like adding new tracks, other edits, etc., to see if things still hold up.
 
Bob Bone
 

I just wanted to thank all who stuck through the above thread - this whole thing has been quite a brain drain.
 
It DOES seem to be holding up, thus far, and I will either add more tomorrow or mark it solved, depending on how tonight's testing goes.
 
I DO want to point out that the current C: primary drive is a solid-state, and it is running with only a very small amount of freespace - which seems like a bad idea.
 
I will seek to remedy that, as well - but first it's NAP TIME :) zzzzzzzzzzzzzzzzzzzzzz
 
Bob Bone
 

If your SSD is a Samsung you probably need a magician...

http://www.samsung.com/gl...support/downloads.html

It's actually a Kingston.
 
The thing about it is that I have not yet figured out why there is so little free space left on the drive, as most things were moved off of it.  I mean like CRAZY little space left.
 
I'll start taking a look at it right after I blast some folks in Black Ops 2, after spending the past 2 days working on the other things going on with this computer.......
 
Bob Bone
 

Be sure that drive is not set up to index on. The indexing file can be large with default settings and shouldn't be put on an SSD anyway.

Because of a reinstall I had 300GB of index files on my data HDD that were no longer accessible. I had to move files and format the partition to get rid of it.