Topic: Media Center 19 has stopped working : StackHash_0a9e (Read 3845 times)

CiXel · « **on:** January 06, 2014, 03:19:32 pm »

Media Center 19 is crashing upon first load on a first time install.
No virus checkers et al are in running in the system and it has been rebooted.
I was able to select a folder on first program load, but am unable to do anything else in the software (it crashes within 10 seconds).
This happens if I load the main program or the media server.
When I reboot I use the default library et al to no avail.

I started on 19.054 and also tried 19.102
Here's the crash output, but I'm unsure what else to provide.
Is there a debug switch that would be useful to turn on?

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Media Center 19.exe
  Application Version:   19.0.102.0
  Application Timestamp:   52c5a672
  Fault Module Name:   StackHash_0a9e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   00000000
  OS Version:   6.1.7601.2.1.0.256.49
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

JimH · « **Reply #1 on:** January 06, 2014, 03:52:10 pm »

Do you have a virus checker installed but not running? If so, uninstall it.

Also try reinstalling your license.

CiXel · « **Reply #2 on:** January 06, 2014, 04:01:04 pm »

The only thing remotely close to a virus scanner is windows defender and that's built into windows and not actively running.
I have no license yet. Was just trying to check out the programs and evaluate.

glynor · « **Reply #3 on:** January 06, 2014, 05:04:59 pm »

Windows Defender certainly shouldn't be an issue (and definitely not making it crash like that), and obviously this isn't a widespread problem.

A few things to check:

1. Does it crash immediately, or load and then crash?
2. Does the machine have an active network connection?
3. Any kind of software that might be blocking a network connection (firewall stuff or anything)?
4. Is there any log created here:
C:\Users\glynor\AppData\Roaming\J River\Media Center 19\Log.txt
5. Is there anything else you can think of funky about the machine or your install? Are you trying to run it as an admin (don't) or ran the Installer using a different account or as an admin, or anything else?

I don't think MC logs by default, though, so you might not have one if it is crashing on first-ever run and you can't even enable it. I might be able to get you a REG file you can import that will turn on logging and then we can look at a real log.

Also, so you know, crashes in module StackHash means that Windows was not able to determine what module caused the fault. This makes debugging the crash extremely difficult. This can often indicate hardware issues (often low memory or memory hardware faults, power supply issues), DEP related crashes (which shouldn't apply here), filesystem corruption, or malware activity. In this case, I can see it also indicating a GPU issue (though you'd be more likely to see that when entering Theater View or playing Video).

You might be able to work around it by disabling DEP for this application, though this ABSOLUTELY should not be required. It might let you run MC long enough to get us a good log, though.

And, unless you're absolutely positive the machine is rock-solid, it would be worth doing a Memtest 86+ check on it (using a known-clean CD/USB stick made on another computer) and at least one pass of Prime95, just to rule out basic hardware issues. Also, if you haven't done so, I'd do an chipset drivers update (from Intel, not Windows Update, assuming it is an Intel board/CPU).

glynor · « **Reply #4 on:** January 06, 2014, 05:09:06 pm »

Oh yeah, and try running sfc /scannow:
http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm

JimH · « **Reply #5 on:** January 06, 2014, 05:48:13 pm »

Quote from: CiXel on January 06, 2014, 04:01:04 pm

I have no license yet. Was just trying to check out the programs and evaluate.

Make sure you get a "genuine" copy from this site.

glynor · « **Reply #6 on:** January 06, 2014, 06:23:10 pm »

Quote from: JimH on January 06, 2014, 05:48:13 pm

Make sure you get a "genuine" copy from this site.

Good point. If you know how to generate them (get HashTab, it is actually the coolest thing ever*), here are the file hashes for the MediaCenter190102.exe installer I downloaded:

Code: [Select]

CRC32: 86739F6C
MD5: 2E1D84D6B6F0536B0FD53E4BD331432D
SHA-1: 48C74404D379EA0D7D2C9B207D15DFD217C53104

* Okay, maybe not ever. But it is pretty cool, free (for personal use), and useful.

CiXel · « **Reply #7 on:** January 07, 2014, 09:51:42 am »

Thanks Gang-
I'm away form the machine at the moment, but will check tomorrow.
The version is definitely legit (and I think you can only get 19.102 from the forum anyway)
The UI loads and displays for about 5 seconds at which point the crash occurs. Windows firewall is enabled, but there is no warning about port blockage. I will try to disable it and try again.

I'll see if there is any log and what running a memtest has to say.
Appreciate the things to try.

glynor · « **Reply #8 on:** January 07, 2014, 12:26:52 pm »

The Windows built in firewall won't cause that, I don't think. I have it turned on on my machines...

CiXel · « **Reply #9 on:** January 08, 2014, 09:23:55 am »

I don't have any log.txt in my %appdata%\j River\ folder, but there was a crash.dmp sitting there which I've attached.
My file hashes for 19.102 match

86739F6C
2E1D84D6B6F0536B0FD53E4BD331432D
48C74404D379EA0D7D2C9B207D15DFD217C53104
vs
CRC32: 86739F6C
MD5: 2E1D84D6B6F0536B0FD53E4BD331432D
SHA-1: 48C74404D379EA0D7D2C9B207D15DFD217C53104

Network connection is active
Turning off the firewall has no impact
There's nothing too funky elsewise that I can tell. My other music apps seems to run successfully.

JohnT · « **Reply #10 on:** January 08, 2014, 09:57:45 am »

Did you go into Help / Logging and check "enable logging"?

Try that, then after a crash send us the logs. (logs at jriver dot com). Thanks.

glynor · « **Reply #11 on:** January 08, 2014, 10:06:11 am »

Quote from: JohnT on January 08, 2014, 09:57:45 am

Did you go into Help / Logging and check "enable logging"?

He can't. It crashes before it loads, and it is first-ever run.

I'm trying to find the registry entry that enables this, John, but I haven't found it yet. If I can find that, I can make a REG file that will enable logging.

For, CiXel, if you haven't, this is absolutely worth trying:

1. Uninstall MC (remove everything since it is broken anyway).
2. Reboot. Don't skip this because you are lazy.
3. Reinstall.

Also, did you try the System File Checker? That would be good to know. If it finds corruption there, then something is probably badly borked on the system.

glynor · « **Reply #12 on:** January 08, 2014, 10:16:14 am »

Found it.

Download this file, unzip it, and then double-click the Reg file. This will add the needed Registry entry to enable MC's built-in logging.

http://glynor.com/files/jriver/MC19-LoggingOn.reg.zip

I'd still do the other steps I mentioned above, as well. But at least this will make it generate a log file, assuming it doesn't crash before that stuff would even happen at all.

Hendrik · « **Reply #13 on:** January 08, 2014, 10:17:06 am »

Which kind of CPU do you happen to have? It wouldn't happen to be something especially ancient, would it?

glynor · « **Reply #14 on:** January 08, 2014, 10:18:53 am »

Quote from: Hendrik on January 08, 2014, 10:17:06 am

Which kind of CPU do you happen to have? It wouldn't happen to be something especially ancient, would it?

Ahh, yes. SSE2 is required, right?

CiXel · « **Reply #15 on:** January 09, 2014, 08:46:00 am »

It's a little old, but not particularly so. It's a core 2 duo e4400. Should handle SSE2 fine.
I was able to race in and enable logging after a couple of trys. I've attached the log.txt.

Code: [Select]

0004313: 260: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0004313: 260: General: TopLevelExceptionFilter: Message: 34768, wParam: 20345804, lParam: 0

Hendrik · « **Reply #16 on:** January 09, 2014, 08:57:48 am »

I saw something in the crash dump from earlier about a driver somehow involved in the crash.
Do you have a driver installed for a device from "AudioScience", and if so, might you be able to remove it temporarily for testing purposes?

CiXel · « **Reply #17 on:** January 09, 2014, 09:10:17 am »

Quote from: Hendrik on January 09, 2014, 08:57:48 am

I saw something in the crash dump from earlier about a driver somehow involved in the crash.
Do you have a driver installed for a device from "AudioScience", and if so, might you be able to remove it temporarily for testing purposes?

AudioScience is one of my audio cards. I can try disable the driver and/or pull the cards.

CiXel · « **Reply #18 on:** January 09, 2014, 09:36:31 am »

When I just disable, I get an crash based off that driver.
Let me try to uninstall next.

Problem signature:
Problem Event Name:   APPCRASH
Application Name:   Media Center 19.exe
Application Version:   19.0.102.0
Application Timestamp:   52c5a672
Fault Module Name:   asiwav32.dll_unloaded
Fault Module Version:   0.0.0.0
Fault Module Timestamp:   4d80f114
Exception Code:   c0000005
Exception Offset:   6bd15322
OS Version:   6.1.7601.2.1.0.256.49
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

CiXel · « **Reply #19 on:** January 09, 2014, 09:59:53 am »

Interesting. If I uninstall the Audioscience drivers MC19 loads as expected.
On the bright side you've found the culprit / oddity.
On the downside, any idea how this can be worked around so I can get my outputs back.

Anything I can provide?

INTERACT FORUM

Author Topic: Media Center 19 has stopped working : StackHash_0a9e (Read 3845 times)