Can you please list your Windows version and maintenance level?
 
Thanks, 
 
Bob Bone
 

Windows 7 Pro 32bit SP1
Terratec ews88d ASIO.
 
Dell Precision 760? quad xeon if I remember right.
Automatic Corruptdates off by design since it installed.
No themes, No aero.
No AV as it is just a glorified multitrack tape recorder. (Aint it great?)
 
Every so often I run ComboFix and ADWCleaner.
 
 
 

bitman
Automatic Corruptdates off by design since it installed.

I had mentioned running Windows update earleir.

There's your issue right there. If you run windows update several times (Inc optional updates) I place bets the issue should be resolved assuming your virus scanning precautions are good enough (if you install new software,and if you get data from the outside world, even via USB key, you need a virus scanner), and assuming you are running the latest audio interface firmware and drivers.

As an IT engineer you should know you need to keep your software dependencies up to date. If you install newer software it's gonna need to access newer libraries. I also assume you also run backups.

On the other hand if you ran chkdsk and the behaviour changed this smells of HD corruption (caused by viruses, hardware defect or turning off machine prematurely, maybe not keeping drivers up to date such as chipset, or in need of hard drive firmware or motherboard bios updates). Hence sfc /scannow

It could be all the reasons above.

Update everything then start troubleshooting. Otherwise you are looking for a needle in a haystack. Make sure you backup first.

Thanks...

Hi - thanks for the OS information. StackHash is not a real application, but a made up thing - and the extension you see at the end of yours (e1ae) is actually a representation of a numeric identifier of the actual name of the failing application.
 
Here is a link with some information about that - perhaps there is some information within the link's content that would help figure out what is happening to you:
 
http://infopurge.tumblr.com/post/10438725843/what-is-stackhash (look below for info from this link, to save you from having to read a bunch of stuff at the beginning of the link's content)
 
Here is the relevant information about StackHash, from the above link:
 
A program is made up of smaller units called functions. Functions call each other to do work (e.g. display an icon or work out some calculation). A called function may call other functions which themselves call other functions. The information about who has called whom is stored in what is known as a Stack. Every application thread has its own stack and, when a crash occurs, the stack contains useful information that identifies who was calling whom at the time of the crash. This stack information is combined into what is known as a Hash to create a “semi” unique number for the crash. The prefix StackHash_ is added to the number (which is in hexadecimal (base 16) form) giving a module name that appears in the crash information as shown below.
Problem Event Name: APPCRASH
Application Name: iexplore.exe
Application Version: 7.0.6000.16757
Application Timestamp: 48e4238e
Fault Module Name: StackHash_1ea1
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdf8
Exception Code: c0000374
Exception Offset: 000aa0fb
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Therefore, StackHash is not a real module. It is a constructed name because the Instruction Pointer was pointing to a known module at the time of the crash. The number after the StackHash_ is a semi-unique number calculated at the time of the crash such that if the same crash occurred on multiple PCs then they have a reasonable chance to be correlated.
For a programmer to successfully track down the cause of the problem, he needs either to be able to reproduce the problem or he needs a copy of the Stack at the time of the crash. The stack will be included in a minidump which is a file automatically generated and stored at the time of the crash and sent to Microsoft as part of the crash information if the PC is configured to do so.
Some of the reasons for StackHash crashes include…

• The application itself has a fault causing it to call a function in a piece of memory that does not contain any code as in the example above.
• A virus checker, virtual drive S/W, security systems (or other application) has injected a piece of code into the address space of the application that crashes for some reason. In this case there is no identifiable module so a StackHash_XXXX will be created.
• A virus has infected the machine and the virus code is executing in the context of the faulting application.
• There is a bug in the operating system or other shared component on the system.
• The application has become corrupted either by a disk error or virus.

What to do if you get a StackHash?

1. First configure Problems Reports and Solutions in Control panel to Check for Solutions automatically and Automatically send more information. Then check if there are fixes available for your application. If there are then download and install them.
2. Make sure your Window Operating system has all the latest service packs, security updates and other fixes installed.
3. Most applications have a Check for Updates feature. Use it to make sure you have the latest version of the S/W. Alternatively visit the company website and check for new versions and patches.
4. Run an up-to-date virus checker on the machine and fix any issues. If a virus is detected in the application then you may need to reinstall the application.
5. Re-install the application. Through Control Panel \ Programs \ Uninstall a program. Right click the application and click Uninstall / Change. This should launch the installer which may give the option to Repair the installation. If not then you will need to uninstall and reinstall - make sure you have the original installation discs available before uninstalling.
6. Disable any Virtual Drive software that may be hooking in to the application. If the problem goes away, contact the developer of the Virtual Drive software.
7. Disable any Virus checkers on your machine (temporarily) and run the application again. If the problem goes away, contact the developer of the Virus Checking software.
8. Check if the problem is reproducible (after a reboot). If it is, then attempt to narrow down the exact steps that cause the fault, write them down and contact the support department for the company that developed the application providing as much information about the crash and what you have done so far to attempt to resolve the issue.

 
I think if we work through information and symptoms, we may be able to figure out what might be causing your problems.  I have to go get some sleep, but wanted to post the above, so that you had some info to look through that might help.  :)
 
I'll circle back in the morning, and see what else I can figure out - or ask you about.
 
Bob Bone
 

Thanks Bob.

M$ article is basically reiterating my advice. So there you go. Cheers..

I posted what I did to explain StackHash a little bit, in response to the original post, as that had not been really part of the thread posts.  It explains why the OP only got a couple of hits when looking on the web for guidance/info on the error code he was given.  His search terms included a numeric identifier for the failing module, but that identifier really only applies to his particular system.  A search for simply StackHash returns more usable information about both what StackHouse is, as well as what that appended code is, etc.
 
The generic advice at the bottom of that info was just that - though quite valid.  I DO agree with a philosophy of keeping maintenance current - and do apply the steps necessary to do that.
 
Bob Bone
 
 
Bob Bone

BTW Bob, I just updated my dev 32 windows 7 pc (which also has no updates on it) to Gloucester as with
the DAW all is well (for now).
 
The daw was running it without error for a week before it started doing this.
 
I have reason to suspect my dear old C: drive needs replacement as while chkdsk /r found no issues, it is stutter-y while in stage 4 of 5 (the data area) and in the beginning of the drive. The second half of the data area check was checking cluster without pausing. So read retrying may be going on.
 
I have ordered a new SSD drive to clone to but it wont get here for a week.

Thank you for the additional info - and I certainly hope your system doesn't fail prior to your tossing in a nice shiny new SSD.
 
If I understand you correctly, and you really have no Windows maintenance applied whatsoever, then I really really really really really urge you to consider running Windows update until both computers are completely up to date.  I have a fundamental disagreement with the notion of that large of a maintenance gap, as the Sonar development IS being done on current Windows maintenance levels, and in fact they DO at times build in explicit dependencies on certain maintenance that has to be in place for Sonar to run properly.
 
If there WERE Windows-caused functional problems in Sonar, due to maintenance of Windows, then you would most certainly see all kinds of people freaking out in the forums about it.  The very fact that this is not happening gives weight to the notion that the application of Windows maintenance does not cause Sonar to fail.
 
Create a restore point prior to running your Windows maintenance, and you will be able to put it back, should you decide there are issues after the application of all of the missing Windows updates.
 
Bob Bone
 
 
 

Ok kids!
 
The SSD arrived I cloned my system drive to it and this made my system run faster than a scalded cat but did not fix the problem. Nor did a reinstall of Splat.
 
However, I said to myself "That does it", and no Doktor Update I did not do any windows updates, but, I did delete all Splat from the file system and registry and (It's a miracle!) reinstalled Splat-cester and we're running again - for now. :-)
 
Thanks for all the help and concern.
Back to your regularly scheduled programs.
 
I'm going to call this solved for reasons of forum etiquette.
 
Rock on Y'all.