experchange > multimedia.windows.mediaplayer

Robert Janik (02-18-10, 07:37 AM)
I have Vista Ultimate 64-bit. Microsoft High Definition Audio driver.
wmplayer.exe version 11.0.6002.18111

1. It takes for ever to start Windows Media Player
I have to use Cyberlink DVD player, it starts immediately. Windows Photo
Gallery seems to better too, because it starts quickly and sometimes can
play videos which wmplayer cannot play (I tried both wmplayer 32 and 64 to
be sure if one of them was missing codecs). Why wmplayer cannot play what
Windows Photo Gallery can play?

2. When clicking a file from explorer, player sometimes starts on the
background with no UI and I have to close it by killing the process (not
even the small UI in taskbar).

3. It randomly crashes when playing mp3 or other content especially 32-bit
version - example:

Download sample mp3 from website which sells CDs:

Save it to C: drive, open explorer and double click on the file. If you want
to repeat mp3 playback, clear wmplayer cache.

After wmplayer.exe and explorer.exe crashed, it now plays on second, third,
fourth attempt. Maybe it is related to cache, but I played this from C:
drive, not from the web. When playing this mp3 I looked at the stack trace
to see which binaries are loaded and everything is MS (I thought that
perhaps there is a mp3 codec of some other company used).

Instead of crashing and taking down explorer.exe with it, it should display
a message that something is wrong. It also says a lot about design and
coding of explorer.exe. It should never crash while using wmplayer and
internet explorer. This is very dangerous, because these 2 apps have lots of
security holes.

4. Why 32-bit wmplayer is used by default on 64-bit machine?
I have all codecs 64-bit. If audio or video codec does not exist in 64-bit
version I don't use it.
zachd [MSFT] (02-19-10, 12:44 AM)
"Robert Janik" <robert_janik> wrote in message
news:a32f
>I have Vista Ultimate 64-bit. Microsoft High Definition Audio driver.
> wmplayer.exe version 11.0.6002.18111


> 1. It takes for ever to start Windows Media Player
> I have to use Cyberlink DVD player, it starts immediately. Windows Photo
> Gallery seems to better too, because it starts quickly and sometimes can
> play videos which wmplayer cannot play (I tried both wmplayer 32 and 64 to
> be sure if one of them was missing codecs). Why wmplayer cannot play what
> Windows Photo Gallery can play?


That depends upon exactly what you're trying to play. What is that? One
precise and exact instance would be most useful to discuss.

> 2. When clicking a file from explorer, player sometimes starts on the
> background with no UI and I have to close it by killing the process (not
> even the small UI in taskbar).


That indicates that some attached device likely has started the player in
remote mode and then botched shutting itself down correctly, leaving the
player in a messy state.

> 3. It randomly crashes when playing mp3 or other content especially 32-bit
> version - example:


> After wmplayer.exe and explorer.exe crashed, it now plays on second,
> third, fourth attempt. Maybe it is related to cache, but I played this
> from C: drive, not from the web. When playing this mp3 I looked at the
> stack trace to see which binaries are loaded and everything is MS (I
> thought that perhaps there is a mp3 codec of some other company used).


What are the fault details?


> Instead of crashing and taking down explorer.exe with it, it should
> display a message that something is wrong.


If it's taking down Explorer with it, presumably something is extremely
wrong. If you know how to display an error message at that point - couldn't
you fix it? Seems more complicated than that.

> 4. Why 32-bit wmplayer is used by default on 64-bit machine?
> I have all codecs 64-bit. If audio or video codec does not exist in 64-bit
> version I don't use it.


On Vista you can switch to use the 64bit player by default by using a couple
tweaks out there.

It's not about you personally, it's about the global customer base, who
still has more invested in 32bit only tools / codecs / Flash than are
available in 64bit ... yet. =)
Robert Janik (02-20-10, 12:07 AM)
"zachd [MSFT]" <zachd> wrote in message
news:3536
> "Robert Janik" <robert_janik> wrote in message
> news:a32f
> That depends upon exactly what you're trying to play. What is that? One
> precise and exact instance would be most useful to discuss.


I don't remember what it was. I tried my videos captured by Cannon PowerShot
SD780 IS, but these work in wmplayer (actually in this case Windows Photo
Gallery is unable to play 720p video). The issue mentioned may have been
caused by audio coded which worked in Windows Photo Gallery, but not with
wmplayer (I assume that every coded which works with Photo Gallery, should
work with wmplayer, right?).

When I have some time I'll go over my videos and find one which didn't work
in wmplayer.

>> 2. When clicking a file from explorer, player sometimes starts on the
>> background with no UI and I have to close it by killing the process (not
>> even the small UI in taskbar).

> That indicates that some attached device likely has started the player in
> remote mode and then botched shutting itself down correctly, leaving the
> player in a messy state.


I don't have any device attached. This happened on laptop. This is happening
quite regularly and the only app calling wmplayer on my machine is Internet
Explorer. I think IE might in some cases leave wmplayer on the background.
When I start video or music by double-clicking in explorer, it finds this
existing instance of wmplayer without UI and starts playback.

> What are the fault details?
>


I couldn't find any dump for this issue. Nothing in C:, C:\Windows,
C:\Windows\Minidump. Usually when app crashes OS shows the screen where you
can decide if you want to debug or send info to microsoft, but in this case
it just shuts down without any information. It may have displayed an error
message (I'm not really sure what that glitch was), but it disappeared
instantly as explorer.exe crashed.

> If it's taking down Explorer with it, presumably something is extremely
> wrong. If you know how to display an error message at that point -
> couldn't you fix it? Seems more complicated than that.
> On Vista you can switch to use the 64bit player by default by using a
> couple tweaks out there.
> It's not about you personally, it's about the global customer base, who
> still has more invested in 32bit only tools / codecs / Flash than are
> available in 64bit ... yet. =)


I always choose hardware which has 64-bit drivers, codecs etc. But there are
still companies which are able to provide only 32-bit, like Adobe (flash
player), so I have to switch between 64-bit and 32-bit applications
depending on what content I want to play/use.
[..]
Tim De Baets (02-20-10, 03:35 PM)
Robert Janik wrote:
> 4. Why 32-bit wmplayer is used by default on 64-bit machine?
> I have all codecs 64-bit. If audio or video codec does not exist in 64-bit
> version I don't use it.


There shouldn't be any noticeable difference between the 32-bit and
64-bit version of WMP, so I don't really understand your reluctance to
run the 32-bit version. Do you have any specific reasons for this?

Regards
Robert Janik (02-22-10, 06:16 AM)
I didn't find any wmplayer.exe dumps, only following info related to the
explorer crash:

Problem signature
Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.0.6002.18005
Application Timestamp: 49e02a1e
Fault Module Name: wmp.dll
Fault Module Version: 11.0.6002.18111
Fault Module Timestamp: 4aa933f7
Exception Code: c0000005
Exception Offset: 00000000001345b7
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Additional Information 1: f91d
Additional Information 2: 612ddbe3a1b0203bcd35acde6f85cc36
Additional Information 3: 7005
Additional Information 4: a1de54f69fd13c4dc84ab52e83dfd80a

Files that help describe the problem
Version.txt
-------------
Windows NT Version 6.0 Build: 6002 Service Pack 2
Product (0x1): Windows Vista (TM) Ultimate
Edition: Ultimate
BuildString: 6002.18160.amd64fre.vistasp2_gdr.091208-0542
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033

AppCompat.txt
------------------
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">
<MATCHING_FILE NAME="advapi32.dll" SIZE="1065472" CHECKSUM="0x7F550ED"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6002.18005" FILE_DESCRIPTION="Advanced Windows 32 Base
API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="6.0.6002.18005 (lh_sp2rtm.090410-1830)"
ORIGINAL_FILENAME="advapi32.dll.mui" INTERNAL_NAME="advapi32.dll"
LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved."
VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x110002" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:03:39"
UPTO_LINK_DATE="04/11/2009 07:03:39" EXPORT_NAME="ADVAPI32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="gdi32.dll" SIZE="389632" CHECKSUM="0x93D5A9CC"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6002.18005" FILE_DESCRIPTION="GDI Client DLL"
COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="6.0.6002.18005 (lh_sp2rtm.090410-1830)"
ORIGINAL_FILENAME="gdi32" INTERNAL_NAME="gdi32" LEGAL_COPYRIGHT="© Microsoft
Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0"
VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x6B0D3" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:04:52"
UPTO_LINK_DATE="04/11/2009 07:04:52" EXPORT_NAME="GDI32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="kernel32.dll" SIZE="1217536" CHECKSUM="0xE995048F"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="Windows NT BASE API
Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
Windows® Operating System" FILE_VERSION="6.0.6001.18000
(longhorn_rtm.080118-1840)" ORIGINAL_FILENAME="kernel32"
INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All
rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004"
VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x138952"
LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:08:01"
UPTO_LINK_DATE="04/11/2009 07:08:01" EXPORT_NAME="KERNEL32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="ntdll.dll" SIZE="1582792" CHECKSUM="0xFB33ACA9"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="NT Layer DLL"
COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="6.0.6001.18000 (longhorn_rtm.080118-1840)"
ORIGINAL_FILENAME="ntdll.dll.mui" INTERNAL_NAME="ntdll.dll"
LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved."
VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x187A5E" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:09:17"
UPTO_LINK_DATE="04/11/2009 07:09:17" EXPORT_NAME="ntdll.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="ole32.dll" SIZE="1915392" CHECKSUM="0x8C6660CD"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Microsoft OLE for
Windows" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
Windows® Operating System" FILE_VERSION="6.0.6000.16386
(vista_rtm.061101-2205)" ORIGINAL_FILENAME="OLE32.DLL.MUI"
INTERNAL_NAME="OLE32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All
rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004"
VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1E38DA"
LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:07:59"
UPTO_LINK_DATE="04/11/2009 07:07:59" EXPORT_NAME="ole32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="oleaut32.dll" SIZE="847360" CHECKSUM="0xEE6F2F8D"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6002.18005" COMPANY_NAME="Microsoft Corporation"
FILE_VERSION="6.0.6002.18005" INTERNAL_NAME="OLEAUT32.DLL"
LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved."
VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0xD3C2E" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:08:02"
UPTO_LINK_DATE="04/11/2009 07:08:02" EXPORT_NAME="OLEAUT32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="shell32.dll" SIZE="12897792" CHECKSUM="0xF8C93FC8"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="Windows Shell Common Dll"
COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="6.0.6001.18000 (longhorn_rtm.080118-1840)"
ORIGINAL_FILENAME="SHELL32.DLL.MUI" INTERNAL_NAME="SHELL32"
LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved."
VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0xC50A41" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:08:31"
UPTO_LINK_DATE="04/11/2009 07:08:31" EXPORT_NAME="SHELL32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="user32.dll" SIZE="820224" CHECKSUM="0x8FCFFD68"
BIN_FILE_VERSION="6.0.6002.18005" BIN_PRODUCT_VERSION="6.0.6002.18005"
PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="Multi-User Windows USER
API Client DLL" COMPANY_NAME="Microsoft Corporation"
PRODUCT_NAME="Microsoft® Windows® Operating System"
FILE_VERSION="6.0.6001.18000 (longhorn_rtm.080118-1840)"
ORIGINAL_FILENAME="user32" INTERNAL_NAME="user32" LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0"
VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0xCB1C6" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="6.0.6002.18005"
UPTO_BIN_PRODUCT_VERSION="6.0.6002.18005" LINK_DATE="04/11/2009 07:09:02"
UPTO_LINK_DATE="04/11/2009 07:09:02" EXPORT_NAME="USER32.dll"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="wininet.dll" SIZE="1147904" CHECKSUM="0xD922EA8B"
BIN_FILE_VERSION="8.0.6001.18882" BIN_PRODUCT_VERSION="8.0.6001.18882"
PRODUCT_VERSION="8.00.6001.18702" FILE_DESCRIPTION="Internet Extensions for
Win32" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Windows® Internet
Explorer" FILE_VERSION="8.00.6001.18702
(longhorn_ie8_rtm(wmbla).090308-0338)" ORIGINAL_FILENAME="wininet.dll.mui"
INTERNAL_NAME="wininet.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All
rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004"
VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x12607A"
LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="8.0.6001.18882"
UPTO_BIN_PRODUCT_VERSION="8.0.6001.18882" LINK_DATE="01/02/2010 07:09:29"
UPTO_LINK_DATE="01/02/2010 07:09:29" EXPORT_NAME="WININET.dll"
VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="wmp.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="wmp.dll" SIZE="13428224" CHECKSUM="0x9649BA46"
BIN_FILE_VERSION="11.0.6002.18111" BIN_PRODUCT_VERSION="11.0.6002.18111"
PRODUCT_VERSION="11.0.6002.18111" FILE_DESCRIPTION="Windows Media Player"
COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="11.0.6002.18111 (vistasp2_gdr.090910-0436)"
ORIGINAL_FILENAME="wmp.dll" INTERNAL_NAME="wmp.dll" LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0"
VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32"
PE_CHECKSUM="0xCD224B" LINKER_VERSION="0x60000"
UPTO_BIN_FILE_VERSION="11.0.6002.18111"
UPTO_BIN_PRODUCT_VERSION="11.0.6002.18111" LINK_DATE="09/10/2009 17:14:31"
UPTO_LINK_DATE="09/10/2009 17:14:31" EXPORT_NAME="wmp.DLL"
VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
Robert Janik (02-22-10, 06:40 AM)
Why should I run 32-bit through SysWOW64, when I can run 64-bit apps. Who
knows maybe one day wmplayer will be playing movies on holographic projector
and it will need 16GB RAM. Now seriously, I think there is tiny perf issue
when running WOW64. I have Dual Core 2.4GHz, but when playing high-def (like
1080) video in wmplayer, there are constant glitches in video and sound. For
last 2 years I'm trying to squeeze any CPU I can by stopping some services,
avoiding WOW64 etc. I always see high kernel times (even 80% of CPU). I
think it could be related to drivers for Mobile Intel 965 Express graphics.
I guess you can never really replace nVidia or ATI graphics with dedicated
memory by some integrated graphics.

Anyway, if we stay on 32-bit we will never make the transition. MS and
hardware companies should be happy that there are people like me out there
pushing hardware/software, friends and our customers into upgrading
technologies.

"Tim De Baets" <tdebaets> wrote in message
news:3536
[..]
zachd [MSFT] (03-02-10, 12:37 AM)
Did you send that crash data to Microsoft? There's no bucket ID there:

, which often can be helpful. =\
Similar Threads