BSOD with MediaPlayer

[brj]

hi,

when i want to play a dvd with media player, i immediatle get a bsod.
playing with vlc works.

please analyze the attached minidump.

thanks
jakob

 

[zigzag3143]

hi,

when i want to play a dvd with media player, i immediatle get a bsod.
playing with vlc works.

please analyze the attached minidump.

thanks
jakob

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds
\

BEST GUESS AS TO CAUSE IALMDD5.DLL (part of you video driver)

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\040310-20250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82c0d000 PsLoadedModuleList = 0x82d4c570
Debug session time: Sat Apr  3 11:35:42.868 2010 (GMT-4)
System Uptime: 0 days 0:09:45.883
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image ialmnt5.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmnt5.sys
*** ERROR: Module load completed but symbols could not be loaded for ialmnt5.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80dd7750, 0, 0}

Unable to load image ialmdd5.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmdd5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdd5.DLL
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ialmnt5.sys ( ialmnt5+30897 )

Followup: MachineOwner
---------

 

[brj]

hi zigzag,

thanks for your quick answer.

i use a genuine windows 7 home premium installed from an original dvd. and win 7 is activated. so i don't know why there are no symbols ?

the machine on the other side is a rather old hp business desktop with an onboard intel video chip. the driver is downloaded from intel. maybe i should try the one shipped with win 7, or play dvd with vlc only.

jakob

 

[zigzag3143]

hi zigzag,

thanks for your quick answer.

i use a genuine windows 7 home premium installed from an original dvd. and win 7 is activated. so i don't know why there are no symbols ?

the machine on the other side is a rather old hp business desktop with an onboard intel video chip. the driver is downloaded from intel. maybe i should try the one shipped with win 7, or play dvd with vlc only.

jakob

Jacob

the current release from MS is called RTM. (version 7600) In yours it does not say RTM nor is it described as 32bit like this
Built by: 7600.16481.x86fre.win7_RTM.091207-1941


It is described like this
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Persona

Because of that and the fact that the core OS files are the
wrong size is why there are no symbols for it

Ken

 

[DT Roberts]

We may not need the symbols after all. I've been having problems with symbols intermittently for weeks, not really sure why.

Still, what I can see without them is that the driver that zigzag3143 flagged - IALMDD5.SYS - is very out of date, among others.

8f870000 8f952000   ialmdd5  ialmdd5.DLL  Tue Sep 20 13:59:53 2005 (43304E19) - [B]Intel DirectDraw[/B]
9ffb0000 9ffe40a0   ialmdev5 ialmdev5.DLL Tue Sep 20 13:52:20 2005 (43304C54) " "
9ff60000 9ff82000   ialmdnt5 ialmdnt5.dll Tue Sep 20 13:52:31 2005 (43304C5F) - " "
94417000 94554ec0   ialmnt5  ialmnt5.sys  Tue Sep 20 14:00:52 2005 (43304E54) - " "
9ffa0000 9ffae000   ialmrnt5 ialmrnt5.dll Tue Sep 20 13:52:37 2005 (43304C65) - " "
94655000 9468af40   smwdm    smwdm.sys    Mon Mar 28 10:19:36 2005 (42481278) - [B]SoundMAX Integrated Digital Audio[/B]
8dbfa000 8dbfb800   avgio    avgio.sys    Thu Feb 22 09:57:32 2007 (45DDAF5C) - [B]Avira Antivirus[/B]

Try updating your graphics and chipset drivers from your manufacturer's website and see if BSODs persist.

 

[brj]

hi,

my has an intel 865 integrated graphics chip. for this chip intel does not provide drivers for win 7. so the one i installed is for xp professional.
today i uninstalled the drivers from intel and replaced them with the generic vga from win7.

i'll have to test if the bsod still occurs.

jakob

 

[DT Roberts]

hi,

my has an intel 865 integrated graphics chip. for this chip intel does not provide drivers for win 7. so the one i installed is for xp professional.
today i uninstalled the drivers from intel and replaced them with the generic vga from win7.

i'll have to test if the bsod still occurs.

jakob

You may be able to get away with the drivers from Vista, but XP is just too old. Let us know how you do with the generic VGA drivers.

 

[brj]

i just installed the generic drivers shipped with win7.
with these drivers media player refuses to play the dvd and thus it can not cause a bsod.
i can still play the dvd with vlc, so i'll stick with it.

jakob

ps: afaik there are no drivers for vista for this old chipset.

 

[DT Roberts]

Maybe it's time to save up for an upgrade?

I'm glad you found your little workaround, but there is a point that things become obsolete. Good luck with everything.

 

[brj]

well it's the machine of my youngest daugther. for browsing and facebook it's still sufficient

thanks for your help
jakob