Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Can't use 64bit wavpack in windows 10. (Read 20913 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Can't use 64bit wavpack in windows 10.

I'm using the latest official wavpack 2.75.2 on windows 10 pro x64(alse the latest official build).
32bit works fine here.
But sseems that 64bit version doesn't work.
Even use the command wavpack.exe -h . →Get the error message wavpack.exe has stopped working.

Sorry about that I can't check on other windows version.

Anyone use win10 with the 64bit version wavpack fine?

Can't use 64bit wavpack in windows 10.

Reply #1
Working fine for me on W10 x64.
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.


Can't use 64bit wavpack in windows 10.

Reply #3
Possibly the compile you are using requires an unsupported CPU feature.

Can't use 64bit wavpack in windows 10.

Reply #4
Possibly the compile you are using requires an unsupported CPU feature.

My CPU is i7-4510u. Not too old...
And the compile I'm using is downloaded from the Official Web Site.

 

Can't use 64bit wavpack in windows 10.

Reply #5
Working fine for me on W10 x64.

Weried.
I've reproduced the same problem on other windows 10 pc.

Unfortunately I don't have a Windows 10 system yet, but maybe you can answer a couple questions.

First, does “wavpack --help” work, or does it only crash if you try to compress audio?

Also, can you check if the previous version crashes too (it's been out for almost 5 months)? It's located here.

In the meantime, of course, you can use the 32-bit version. It's actually almost as fast as the 64-bit version, and sometimes even faster.

Thanks for the help, and sorry for the trouble!

--David

Can't use 64bit wavpack in windows 10.

Reply #6
Working fine for me on W10 x64.

Weried.
I've reproduced the same problem on other windows 10 pc.

Unfortunately I don't have a Windows 10 system yet, but maybe you can answer a couple questions.

First, does “wavpack --help” work, or does it only crash if you try to compress audio?

Also, can you check if the previous version crashes too (it's been out for almost 5 months)? It's located here.

In the meantime, of course, you can use the 32-bit version. It's actually almost as fast as the 64-bit version, and sometimes even faster.

Thanks for the help, and sorry for the trouble!

--David


"wavpack --help" crashes too.
and same with the previous version.



Can't use 64bit wavpack in windows 10.

Reply #7
No problem running it here on Win 10 Pro x64 (upgraded from Win 7).

I also checked with depends, and I see that it only depends on kernel32.dll, so I discard runtime dependency problems.

This is on an old core 2 duo, so it also discards requing sse4 or something.

Can't use 64bit wavpack in windows 10.

Reply #8
What's the full path (incl. filename) of the encoder?


Can't use 64bit wavpack in windows 10.

Reply #10
Try to put the files in a different directory/folder and run Command Prompt as Administrator before running wavpack.exe. It might be some kind of Permission issue

Can't use 64bit wavpack in windows 10.

Reply #11
Try to put the files in a different directory/folder and run Command Prompt as Administrator before running wavpack.exe. It might be some kind of Permission issue

* run Command Prompt as Administrator .
*put wavpack to D and run Command Prompt as Administrator.
both Crashed,too.

Really strange...

Can't use 64bit wavpack in windows 10.

Reply #12
Corrupted download or broken windows install?

Can't use 64bit wavpack in windows 10.

Reply #13
There's only one tricky thing that wavpack.exe does before displaying the help message, and I've eliminated that for a test (it has to do with the debug mode).

Could you please try the attached executable with either just "wavpack" or "wavpack --help"?

Thanks!

Can't use 64bit wavpack in windows 10.

Reply #14
There's only one tricky thing that wavpack.exe does before displaying the help message, and I've eliminated that for a test (it has to do with the debug mode).

Could you please try the attached executable with either just "wavpack" or "wavpack --help"?

Thanks!

with the test version "wavpack" and "wavpack --help" both crashed,too.

Can't use 64bit wavpack in windows 10.

Reply #15
Corrupted download or broken windows install?


I'm using a clean install of the official ISO.
And Another Win 10 PC occured this too.
I'm not using the English version windows, so maybe the language Compatibility problem?

Can't use 64bit wavpack in windows 10.

Reply #16
I built Wavpack 4.75.2 with 3 different compilers. Maybe one of them will work?

Can't use 64bit wavpack in windows 10.

Reply #17
There is one thing that bugs me on that screenshot, that "Y"-like symbol.

Is that a chinese/japanese Windows?  If so, maybe the problem is related to unicode support. (in the multibyte sense of the term).

Btw, to further help on the diagnosis, it would be nice that you report the real error.
To do so, open the Event viewer (you can do that easily writing eventvwr on the search box).
there, open the "Windows Logs" folder, Applications, and locate the error for wavpack

Can't use 64bit wavpack in windows 10.

Reply #18
https://en.wikipedia.org/wiki/Code_page_932

Quote
Notice that in the CP932.TXT mapping table linked below, code 0x5C is mapped to U+005C REVERSE SOLIDUS (\). This is often a source of confusion because in many Japanese fonts, this code is displayed as a Yen symbol, which would normally be represented as U+00A5 YEN SIGN (¥) in Unicode. However, on Windows systems, code 0x5C in code page 932 behaves as a reverse solidus (backslash) in all respects other than how it is displayed by some fonts.

Can't use 64bit wavpack in windows 10.

Reply #19

There is one thing that bugs me on that screenshot, that "Y"-like symbol.

Is that a chinese/japanese Windows?  If so, maybe the problem is related to unicode support. (in the multibyte sense of the term).

Btw, to further help on the diagnosis, it would be nice that you report the real error.
To do so, open the Event viewer (you can do that easily writing eventvwr on the search box).
there, open the "Windows Logs" folder, Applications, and locate the error for wavpack

Yes, Japanese windows.


Here is the real error.
-----------------------------------------------------------------------------------------------

Faulting application name: wavpack.exe, version: 0.0.0.0, time stamp: 0x561d35ca
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffde3aced90
Faulting process id: 0x2724
Faulting application start time: 0x01d106d06d7fe478
Faulting application path: C:\wavpack.exe
Faulting module path: unknown
Report Id: 317caac4-2ae6-4c87-9660-08033811575a
Faulting package full name:
Faulting package-relative application ID:

Can't use 64bit wavpack in windows 10.

Reply #20
I built Wavpack 4.75.2 with 3 different compilers. Maybe one of them will work?




msvc2010 and msvc2013 both crashed.

But the gcc version works!

Can't use 64bit wavpack in windows 10.

Reply #21
Fault offset: 0x00007ffde3aced90

One thing that comes to mind: download VMMap, then:
1) run wavpack
2) start VMMap, choose wavpack.exe process, then File -> Save As... and save wavpack.mmp file.
3) Open Event viewer, and find the event for this crash.
4) post the contents of the event and wavpack.mmp.

Can't use 64bit wavpack in windows 10.

Reply #22
Error code 0xc0000005 means access to an invalid address.

Usual for uninitialized pointer variables, or for retreiveing something that is usually obtained without problems, but that this time failed and is not checked against this fact when used afterwards. (Guess it's more like the later than the former).
Still a shot in the dark, but it could have been other error codes.


Can't use 64bit wavpack in windows 10.

Reply #23
Fault offset: 0x00007ffde3aced90

One thing that comes to mind: download VMMap, then:
1) run wavpack
2) start VMMap, choose wavpack.exe process, then File -> Save As... and save wavpack.mmp file.
3) Open Event viewer, and find the event for this crash.
4) post the contents of the event and wavpack.mmp.


wavpack.mmp
https://mega.nz/#!qo4wkCSD

Faulting application name: wavpack.exe, version: 0.0.0.0, time stamp: 0x560e131d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8c9c2ed90
Faulting process id: 0x118c
Faulting application start time: 0x01d107bc7636aac1
Faulting application path: C:\wavpack.exe
Faulting module path: unknown
Report Id: 69498379-5d08-4038-9d14-19b41db8e8c4
Faulting package full name:
Faulting package-relative application ID: