More > Media Center 14 (Development Ended)

BSOD on Windows 7

<< < (2/2)

newsposter:
.96 is not the most current version, .101 is.

A 0xc0000005 is most often a corrupt/incorrect driver.  At least msft says that is is some 80% of the time.  You're not running a Vista driver on Win7 or a 32 bit driver on x64 are you?  Have you bothered to take the advice of trying to first delete, then reinstall your video drivers?

Touting your ever-so-impressive credentials as a 'systems engineer' is not the best way to get support from the community here.

glynor:

--- Quote from: eastmarw on November 27, 2009, 03:20:41 pm ---Well I really do disagree with you.  BSOD are NOT ALWAYS HARDWARE.  It could be the driver, it could be the software that access's the Driver to access the hardware.  So before you say it is a hardware problem take into consideration that this issue started when Mediacenter 14 was installed.  No BSOD before this time.  If I never open Mediacenter 14 then I have no issues.  The minute I open MC14 is when the issues start.  So when it comes down to it Mediacenter is the problem.  It was introduced when MC14 was installed.

--- End quote ---

It is quite likely that MC is using your hardware in ways that other software on your system may not (especially if your aren't a gamer and don't run GPU accelerated applications), so it may be exposing a problem that you wouldn't see in other software.  As newsposter indicated, though, a 0xc0000005 BSOD is almost always a Driver issue.  Specifically, it is a memory access violation.  In addition to drivers (or a hardware problem, like loose memory DIMMs) it could also be:

1. Anti-Virus software.
2. Third-party firewall software or network filtering software of some kind.
3. A bad codec or filter in DirectShow that fails when a certain media file is accessed.

I have also seen a number of reports of Windows 7 crashes, specifically in Windows Defender (svchost.exe_WinDefend), that started with the most recent automatic updates of Windows 7 that came out in November.  It could possibly be a virus/worm.  The faulting module "unknown" makes me suspicious.

Lastly, it could certainly be a hardware problem.  I'd suggest running a pass in Memtest86+ just to eliminate that possibility.

For the record, though... I have not had similar issues with MC14 on any of my many Windows 7 installations.

tizul91:

--- Quote from: newsposter on November 27, 2009, 03:35:49 pm ---.96 is not the most current version, .101 is.

A 0xc0000005 is most often a corrupt/incorrect driver.  At least msft says that is is some 80% of the time.  You're not running a Vista driver on Win7 or a 32 bit driver on x64 are you?  Have you bothered to take the advice of trying to first delete, then reinstall your video drivers?

Touting your ever-so-impressive credentials as a 'systems engineer' is not the best way to get support from the community here.

--- End quote ---

Hello, I'm curious about the kind of support JRiver offers to it's customers.
Are the customers entitled to receive official support from the supplier? If so, is it exclusively from this Forum ?

I have a similar problem ** with Windows 7 (32 bit) and I would like to report it.

Thanks for response(s).

** Event = APPCRASH
Version : MC 14.0.130 to 165
Module: netdll.dll
Exception code : c0000005
No blue screen though.

JimH:
I posted above.  I'm official JRiver.  Blue screens are not MC problems.

See the link called "Stability" in my signature for ideas.

Check for driver updates.  Especially video and network.

Navigation

[0] Message Index

[*] Previous page