VA crashes a lot...

[janjan]

Hi,
This has been happening for me from the 1st time I in stalled it.
With and without Vaicom plugin.
I get this error in windows event manager:

Code: [Select]

Faulting application name: VoiceAttack.exe, version: 1.8.5.1, time stamp: 0x5e8cd24f
Faulting module name: ntdll.dll, version: 10.0.18362.778, time stamp: 0x3dcfaabb
Exception code: 0xc0000374
Fault offset: 0x000dfa1d
Faulting process id: 0x12fc
Faulting application start time: 0x01d616447708b33f
Faulting application path: C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e730181d-2562-4a65-9616-8e36d076fb21
Faulting package full name:
Faulting package-relative application ID:

Code: [Select]

- System
- Provider

   [ Name]  Application Error
 
  - EventID 1000

   [ Qualifiers]  0
 
   Level 2
 
   Task 100
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2020-04-19T16:32:48.716126100Z
 
   EventRecordID 131727
 
   Channel Application
 
   Computer
 
   Security
 

- EventData

   VoiceAttack.exe
   1.8.5.1
   5e8cd24f
   ntdll.dll
   10.0.18362.778
   3dcfaabb
   c0000374
   000dfa1d
   12fc
   01d616447708b33f
   C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe
   C:\Windows\SYSTEM32\ntdll.dll
   e730181d-2562-4a65-9616-8e36d076fb21
   
   
I am running win10, newest version of VA and the crashes happen either if I work on VA (creating commands) or mostly leave it for some time on.
With/without enabling the listening mode.

Any suggestions?

[Gary]

It looks like it's crashing on ntdll.dll.  You've got something corrupted/out of sorts in the component chain on your system that you're going to need to fix (VoiceAttack will not be able to get around this).

Ntdll.dll is a base Windows component - in the cases where VA is crashing due to problems with this component, VA is either itself broken (can be remedied by reinstalling VA), a driver or Windows component that VA or its components depends on is out of sorts or ntdll.dll itself (or one if the components it depends on) is out of sorts.  You can first try making sure that your drivers are up to date.  Next, you will want to do a system file scan:  https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker  (you may want to do this before you work on the drivers, as it's much easier).  This is good to do from time to time, even if you do not perceive issues with your system.

[janjan]

I'll do this and monitor the problem for a few days.
Thanks

[janjan]

I followed your suggestion and i still get crashes:

Code: [Select]

VoiceAttack.exe
   1.8.5.5
   5e9e19cb
   ntdll.dll
   10.0.18362.815
   2995af02
   c0000374
   000dfa1d
   4064
   01d61d1afdffab9c
   C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe
   C:\Windows\SYSTEM32\ntdll.dll
   1ce58f5a-63b4-42f5-9215-f4db4e224664

Code: [Select]

Faulting application name: VoiceAttack.exe, version: 1.8.5.5, time stamp: 0x5e9e19cb
Faulting module name: ntdll.dll, version: 10.0.18362.815, time stamp: 0x2995af02
Exception code: 0xc0000374
Fault offset: 0x000dfa1d
Faulting process id: 0x4064
Faulting application start time: 0x01d61d1afdffab9c
Faulting application path: C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1ce58f5a-63b4-42f5-9215-f4db4e224664
Faulting package full name:
Faulting package-relative application ID:
What else Can i check?

[philcart]

I'm getting these crashes too. Seems to occur mainly when VA is sitting idle for a time.

Is there anything else to look at to resolve this issue?

[Pfeil]

If the crash also occurs with plugin support disabled, and especially if it's related to ntdll.dll, you'll want to run the file system scan first.

If that doesn't alleviate the issue, consider repairing your Windows installation using installation media, which will allow you to keep your files and applications, provided you choose that option (note that as the linked article mentions, you'll want to make a backup of your files; This is at your own risk), while making sure Windows itself is in working order.

[Gudfark]

Hi, I've been using VA with 3x HCS voicepacks just fine until yesterday, where I'm now getting the same error as the OP, with the ntdll.dll

I've done SFC, and tried to repair the file, checked I have no virus/malware issues etc., and everything else works fine.

If the dll has got corrupted, why? What might cause it? The common denominator I see so far is VoiceAttack, but that's just the sceptic in me

I have a lot of stuff installed on my PC, all of which works flawlessly, until this. I've also used Revo Uninstaller Pro to fully remove VA+HCS, including the registry entries, but still no joy.

[Gary]

My assumption is that a Windows update is causing the problem.  VoiceAttack and its components only read from that file and its components and never write to them or install them - they can't actually (try deleting something like NTDLL.DLL while Windows is running and you'll see that you can't even do that).

The only writes that VA makes on its own are to its own .dat file, its .config file and the registry from time to time.


The reason why everything else works flawlessly is because other things are not using certain aspects of your system.  Kind of like how your car will keep running even though the windshield washer fluid line is cut - the rest of the car will work but once you try to wash your windshield, that functionality will not work.  Hope that makes sense o_O

[Gudfark]

I have not let windows update for about a month (usually check on it around the beginning of each), as I set my network to metered just so that Windows cannot update automatically.
I unchecked the plugins option, and VA stayed on ok, but then if it has no plugins to work with, would it actually be trying to work as normal?

I'm going to try booting in safe mode to see if I can delete & reinstall the offending dll, but I'm doubting it'll work.

[Gary]

I wouldn't advise deleting NTDLL.DLL (even if you could) as it is a core component.

Either ntdll.dll or a component between VoiceAttack's components and ntdll.dll has become corrupted.  Could possibly be a driver.  Might want to try updating your drivers to see if that makes a difference.

I noticed you've had VA for quite a few years - has this been a problem all along?

[Gary]

Take a look in your installation folder for a VoiceAttackFault.txt file.  You'll most likely see the offending plugin in there.  If that file does not make sense, just post it here so someone can look at it.


https://forum.voiceattack.com/smf/index.php?topic=2730.0