Re: Windows Explorer keeps crashing on video files

Well first it seems like I solved the problem with Explorer itself
crashing. After digging through some more Windows help files following
the reboot, I ran into something mentioning corrupt codec's and it
dawned on me about the AngelPotion codec I had installed long ago.
After removing that, the explorer stopped crashing on viewing media
files in explorer.

However, the reset problem when trying to play WMV's continues (I've
been playing them in Windows Media Player). Could this still be a
codec problem? Not having the right one, a corrupt one, or something
else? I've tried uninstalling all codec's I have, didn't help. I
tried the verifier, had the computer crash while the verifier was
running, and have the minidump files now. Doesn't seem too technical
for me to handle what you describe below if I can get the files to work
correctly. Unfortunately my computer didn't come with any XP cd's, it
was one of those that had all the Windows files installed on a
partitioned off portion of my hard drive. So I tried downloading the
file you mention at
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx and
get stuck there. When I open the self-extracting file, I get the error
"Extracting file failed. It is most likely caused by low memory or
corrupted cabinet file". Huh? I have 704 mb of ram, plenty of space
on my hard drive (80 gb free) and 1 gb free on the partitioned part of
the hard drive. And its not a cabinet file to begin with, its a
downloaded exe. Also tried restarting the computer with no success.



David Candy wrote:
> That's good news. Do this.
>
> Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
>
> If you can't start after enabling verifier
> choose Last Known Good Configuration at the Failed Boot menu (which will
> start without verifier).
>
>
> You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
>
> Then
>
> If you have the XP SP2 Security Update CD (else see
> http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
> )
>
>
> Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
>
> Download
> http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
>
> Load the crash dump file into windbg
> and read what it says. You may need to tell it where the symbols are. Read it.
> Type
> !Analyze -v
> into Windbg's command line.
> (this will hopefully tell you the faulty component)
>
> If the above is too technical then email the crash dump files to david @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
>
> You can look up specific details here
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp
>
> If it indicates faulty memory might be the cause you can get a memory tester
> here
> http://oca.microsoft.com/en/wi­ndiag.asp
>
>
> If it mentions a core windows system file, meaning it a MS fix is required,
> upload a minidump to
>
> http://oca.microsoft.com
>
> Also try typing the main error code in Help while online (ie,
> Stop 0x50
> and also try in the 8 digit form
> stop 0x00000050)
> and if there are too many hits use a filename if available. Generally memory
> addresses are different for each computer (as each computer has a different
> mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).
>
> If this doesn't work try
>
> Get your XP CD and install Windows Support Tools.
>
>
> Type in start run after installing and rebooting
>
>
> pstat > "%userprofile%\desktop\driverl­ist.txt"
>
>
> The last table in this file is a list of loaded drivers. Other things apart
> from hardware uses drivers. Post the list of drivers (the last table only -
> REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.
>
> This will allow you to match memory addresses to a driver.
>
>
>
> --
> --------------------------------------------------------------------------------------------------
> Read David defending the concept of violence.
> http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
> =================================================
> "Scott269" <bulldog269@xxxxxxxxxxx> wrote in message news:1133919968.095649.271810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Well, another new symptom. Now when I try to play WMA's or the screen
> > saver kicks in, the computer instantly resets itself. I mean literally
> > as soon as it attempts to play, bam, its as if I hit the reset button,
> > no error or anything. After the restart, I get the error:
> >
> > The system has recovered from a serious error.
> >
> > When I look at the information....
> >
> > BCCode : 1000007f BCP1 : 00000008 BCP2 : 80042000 BCP3 :
> > 00000000
> > BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 768_1
> >
> > When I send the error to Microsoft, it comes back with a page about an
> > error caused by a device driver, but it could not determine a direct
> > cause. The first time I got this error, it said it was my video driver
> > and directed me to Nvidia's site for a new driver, I installed that but
> > continue to get the same error with this new more generic device driver
> > error. It also suggested I turn off hardware accelaration and disable
> > write combining which I have now done.
> >
> >
> >
> > Scott269 wrote:
> >> Ah, ok, well nothing happened on the ntsd screen after the crash.
> >>
> >>
> >> David Candy wrote:
> >> > You want to look at the NTSD screen when it crashes. There's nothing to worry about all the stuff you posted.
> >> >
> >> > --
> >> > --------------------------------------------------------------------------------------------------
> >> > Read David defending the concept of violence.
> >> > http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
> >> > =================================================
> >> > "Scott269" <bulldog269@xxxxxxxxxxx> wrote in message news:1133829438..610531.82090@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> > > After running the ntsd explorer, I received this (before a list of "Mod
> >> > > Load" with a bunch of memory addresses):
> >> > >
> >> > > Command Line : explorer
> >> > > Loaded dbghelp extension DLL
> >> > > The call to LoadLibrary(ext) failed with error 2.
> >> > > Please check your debugger configuration and/or network access
> >> > > Loaded exts extension DLL
> >> > > The call to Load Library(uext) failed with error 2.
> >> > > Please check your debugger configuration and/or network acess
> >> > > Loaded ntsdexts extension DLL
> >> > > Symbol search path is : *** Invalid *** : Verify _NT_SYMBOL_PATH
> >> > > setting
> >> > > Exexcutable search patch is:
> >> > >
> >> > > Then got the list of ModLoad's, then:
> >> > > Break instruction exception - code 800000003 (first chance)
> >> > > [then another bunch of memory addresses]
> >> > > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> >> > > for ntdl
> >> > > l.dll -
> >> > > ntdll!DbgBreakPoint:
> >> > > 7c901230 cc int 3
> >> > > 0:000>
> >> > >
> >> > > [then I typed in g]
> >> > > [another bunch of mod loads followed by some memory addresses]
> >> > >
> >> > > And that's about it, it opened Explorer back in XP, still got the same
> >> > > error when I browsed to one of the directories with the "bad" media
> >> > > files.
> >> > >
> >> > >
> >> > >
> >> > > David Candy wrote:
> >> > >> Try
> >> > >>
> >> > >> typing in Start Run
> >> > >>
> >> > >> regsvr32 shmedia
> >> > >>
> >> > >> Doubt it will help but can't hurt.
> >> > >>
> >> > >> Also try
> >> > >>
> >> > >> ntsd explorer
> >> > >>
> >> > >> You need to press G for Go after loading and on exit. When you crash this may show more info.
> >> > >>
> >> > >> Also see
> >> > >>
> >> > >> http://windowsxp.mvps.org/slowrightclick.htm
> >> > >> --
> >> > >> --------------------------------------------------------------------------------------------------
> >> > >> Read David defending the concept of violence.
> >> > >> http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
> >> > >> =================================================
> >> > >> "Scott269" <bulldog269@xxxxxxxxxxx> wrote in message news:1133825593.022644.243130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> > >> > Hmm new symptom just came up, I'm now getting the same error after
> >> > >> > having the screen saver come up, I haven't changed the screen saver at
> >> > >> > all for the past few weeks.
> >> > >> >
> >> > >> >
> >> > >> > Scott269 wrote:
> >> > >> >> Running XP Home Edition with SP2. Got some issues with Explorer
> >> > >> >> crashing in certain situations when I try and look at video files.
> >> > >> >> Here's the error:
> >> > >> >>
> >> > >> >>
> >> > >> >> Windows Explorer has encountered a problem and needs to close. We are
> >> > >> >> sorry for the inconvenience.
> >> > >> >>
> >> > >> >> I click to see the error report and get Error signature AppName:
> >> > >> >> explorer.exe AppVer : 6.0.2900.2180 ModName: unknown ModVer: 0..0.0.0
> >> > >> >> Offset 00000000
> >> > >> >>
> >> > >> >>
> >> > >> >> I get this error when:
> >> > >> >> Just viewing any directory with a *.wmv file (as soon as I enter the
> >> > >> >> directory)
> >> > >> >> left or right clicking on a *.mpg file (but not until I click on it)
> >> > >> >>
> >> > >> >> But I have no problems when visiting directories with *.avi or any
> >> > >> >> other media format as far as I know. I can still open the *.wmv or
> >> > >> >> *.mpg file as long as I don't close the error window. As soon as I
> >> > >> >> click "send" or "don't send" on the error window, it kicks me back out
> >> > >> >> of Explorer.
> >> > >> >>
> >> > >> >> I've tried virus scanning, AdAware, and Windows Media Player and
> >> > >> >> Windows Updates.
> >> > >> >>
> >> > >> >> Any ideas what could be causing this? Some type of spyware/virus?
> >> > >> >> Corrupt registry or dll file?
> >> > >> >
> >> > >
> >

.