Exact audio copy 1.3 crashes -access error violation unhandled exception

[str8arrow]

Hi all....
I have been using EAC for years on Windows 7 - uneventfully. When my PC died a painful death, I was forced over to Windows 10 - the new laptops only came with Windows 10 (and no drivers were available for Windows 7). So I was exceedingly frustrated to find that EAC dd not work on my BRAND NEW Windows 10 OS. I had an essentially fresh slate/ new system....yet EAC would not run. I finally found the following solution...I hope it helps those of you who find yourself in my shoes. (I swear I was almost bald by the time I got to this point....I don't have any hair left to pull out.)
*NB I have uploaded the requisite file here so anyone that needs it can just click /download.
]
PROBLEM:
Exact Audio Copy 1.3 (EAC1.3) on Windows 10 Professional 64-bit: Crashes and will not start
- Many popups - message boxes read "Unhandled exception" "Access Error Violation at <insert # here>". A number of error boxes mention "ASPIProc2570".

SOLUTION:
- Download wnaspi32.dll (attached here)
- copy it to Windows\System32
- copy it to Windows\sysWOW64 AS WELL - if you have a 64-bit OS
- reboot PC
- try running EAC now. It should work.
NOTE: EAC's website insists that wnaspi32.dll is not required as of EAC version 1.1 - that is apparently incorrect. I had a heck of a time trying to resolve the problem - because I believed them, I tried EVERYTHING else I could think of first. I almost did NOT try inserting wnaspi32.dll...it was a last-ditch effort, before discarding EAC entirely.

DETAILS:
Here are the things I tried prior to finding the above solution:
I tried numerous things, including but not limited to:
- deleted Codecs/ installed K-Lite codec pack
- removed other audio software, closed other programs, cleared the temp files/cache,
- changed to another account (attempted to run EAC there),
-created another (new) account and attempted to run EAC in this account
- ran EAC as administrator,
- uninstalled EAC/re-installed EAC1.1,
- uninstalled EAC/removed registry settings/re-installed EAC,
- re-installed EAC as administrator,
- ran EAC with various compatibility settings (Windows XP Service pack 1.3, Windows 7, etc), ran EAC as Administrator
NOTHING WORKED!

I then downloaded wnaspi32.dll from another website and placed it in Windows\syswow64, rebooted and ran EAC. No dice.
(There were fewer message boxes - this time, they all read Access Error Violation" and cited "ASPIProc2570".) I figured maybe I was getting somewhere. I copied wnaspi32.dll to Windows\System32 AS WELL. and then rebooted and tried running EAC again.

THIS TIME IT WORKED!!

CONCLUSION:
So for everyone else /anyone else who runs into this AGGRAVATING problem....try this solution. I hope it will save you some time.

NOTE: EAC's website insists that as of version 1.1, EAC does NOT require wnaspi32.dll. That is obviously incorrect. So ....I am uploading wnaspi32.dll here for those of you that need it. Ignore EAC. They apparently don't know their own software.

click below to download wnaspi32.dll - in .7z file (*in case the forum link does not work you can also download it from the links below)
http://www83.zippyshare.com/v/WkF4gqj7/file.html
-or-
https://filescdn.com/n165f2vb3yts

FILE HASH FOR VERIFICATION:
CRC32: EC0EC952
MD5: 83F388EB0C94B34A1FBF07FD35AFA7A7
SHA-1: 669C7528E48BAAAAA893A37201A3ED57B752E72E

[Keyser]

What is that? Nero ASPI?

Anyway, installiung a 32-bit ASPI layer on a 64-bit OS might not be the best idea. It will probably cause some problems with other applications.

Have you tried a more elegant solution, like this: http://www.duplexsecure.com/en/downloads? It'a a SCSI interface like ASPI and SPTI (included in Windows), but maybe it works with EAC.

Another thing you could try is to put "wnaspi32.dll" in EAC folder instaed of system folders. This way you enable access to tha ASPI layer to EAC, without exposing it to the whole system.

[hech54]

Just use CDex instead of PITA EAC.

[Keyser]

Just use CDex instead of PITA EAC.

Sure! If you don't mind getting something that is not an exact copy of the original...

I may be wrong, but AFAIK CDex doesn't even use AccurateRip or CUETools to validate extraction.

[hech54]

Just use CDex instead of PITA EAC.

Sure! If you don't mind getting something that is not an exact copy of the original...

I may be wrong, but AFAIK CDex doesn't even use AccurateRip or CUETools to validate extraction.

I'll rip a .wav file using both softwares, send both files to you, and you(your ears) WILL NOT be able to tell me which software ripped which file.

[Keyser]

Just use CDex instead of PITA EAC.

Sure! If you don't mind getting something that is not an exact copy of the original...

I may be wrong, but AFAIK CDex doesn't even use AccurateRip or CUETools to validate extraction.

I'll rip a .wav file using both softwares, send both files to you, and you(your ears) WILL NOT be able to tell me which software ripped which file.

You'd be surprised. Pops and glitches in files ripped with non-secure modes are a fairly common thing.

[hech54]

You'd be surprised.

No....you could not tell the difference.

[TuNk]

I agree 100% with Keyser here

You'd be surprised. Pops and glitches in files ripped with non-secure modes are a fairly common thing.

In my experience with software that does not use secure ripping, can cause glitches, especially with rippers that use burst mode.

I have used various software for ripping CD's in the pasts 17 years and EAC works best for me.

I would not recommend placing wnaspi32.dll in your system folder. Placing wnaspi32.dll in the folder that contain EAC.exe should work.