More > Media Center 14 (Development Ended)

BSOD on Windows 7

(1/2) > >>

eastmarw:
I installed v14 today and upgraded my v13 license on the new laptop with windows 7.  After about 30 seconds of opening MediaCenter 14 it BSOD's.  Wasn't sure if this was truly at fault so I restarted and then went into MediaCenter 14.  After about 1 mintue a BSOD.  I am going to do a repair of install.  Is anyone else getting this?

eastmarw:
Well a re-install without removing first.  I didn't BSOD but I had Mediacenter minimized and was on the internet searching for anyone else who might have seen this, and this time IE would shut down and then the system would lock up hard with a powerdown was the only remedy.

Restart and remove JRiver v14, and I'm back to having a happy Windows 7 installation.  I'll check registry for any remaing traces of v14 and then do another installation to see if this works.

eastmarw:
OK,  Another update,  After a clean installation of Mediacenter 14, it appears to be the import that is causing the issue.  If I stop the import the system doesn't APPEAR to lockup.  If I perform an import of just one directory of MP3, Mediacenter will shut down with an application error.  Each time I would perform an import the application would halt.  This appears to a J River issue.  I ran 13 with no problems on Vista (same laptop) but not on Windows 7.  And before I get asked this is not an upgraded install it is a fresh installation of Windows 7 Professional.

Currently running the most UpToDate version available from J River 14.0.96
Windows 7 with all the update that are available.


Faulting application name: svchost.exe_WinDefend, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000006bc8094
Faulting process id: 0x150
Faulting application start time: 0x01ca6ef2bc33e110
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: unknown
Report Id: f2639830-dae9-11de-9b58-001b24de86ca

Faulting application name: Media Center 14.exe, version: 14.0.96.0, time stamp: 0x4af8a087
Faulting module name: Media Center 14.exe, version: 14.0.96.0, time stamp: 0x4af8a087
Exception code: 0xc0000005
Fault offset: 0x00072507
Faulting process id: 0xedc
Faulting application start time: 0x01ca6ef592cac6b0
Faulting application path: C:\Program Files (x86)\J River\Media Center 14\Media Center 14.exe
Faulting module path: C:\Program Files (x86)\J River\Media Center 14\Media Center 14.exe
Report Id: efe0e4f0-dae9-11de-9b58-001b24de86ca

Faulting application name: Media Center 14.exe, version: 14.0.96.0, time stamp: 0x4af8a087
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b
Exception code: 0xc0000005
Fault offset: 0x00033913
Faulting process id: 0x10d8
Faulting application start time: 0x01ca6ef6b8ed5c30
Faulting application path: C:\Program Files (x86)\J River\Media Center 14\Media Center 14.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 0b3990d0-daea-11de-9b58-001b24de86ca

JimH:
A blue screen is a hardware problem.  Try updating your video driver. 

eastmarw:
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.

I read posts continuously from not only here but on other forums where instead of helping as the is a "Support" forum you automatically jump to conclusions as most technical support individuals do.  Believe me I am one of these individuals who have to deal with all levels of Technical expertise in my profession as a systems engineer.  I don't develop software but I do support it and work with it daily.

So lets start with something that is more tangible than "it's your hardware, update your video driver".  I've done a hell of alot to troubleshooting this issue including any driver updates if available and so far it points to Mediacenter as you can tell by me updating posts.  I even gone as far as installing the M$ debugging tools to try to determine the dmp file.

Navigation

[0] Message Index

[#] Next page