DxDiag Crash – DirectShow Problem

Problem Description

When I open DxDiag I get the following error:
“DxDiag has detected that there may have been a problem accessing DirectShow
the last time this program was used. Would you like to bypass DirectShow this
time?�
If I click ‘Yes’ DxDiag appears to run normally. If I click ‘No’ DirectX
Diagnostic Tool crashes.


My System Info:

• Windows Vista™ Home Premium (6.0, Build 6000) (6000.vista_gdr.070627-1500)
- Upgraded from Windows XP Media Center 2005 (I had this same problem in
this OS too).
• System: Dell Dimension 5150.
• Video Card name: Radeon X1300.
• Audio: SigmaTel High Definition Audio.
• TV Card: Hauppauge WinTV PVR PCI II (26xxx) (PVR-150).

DirectX Info:
• DirectX Version: DirectX 10 (6.00.6000.16386 32bit Unicode)
• DxDiag Previously: Crashed in DirectShow (stage 1)
• DirectShow: 0/6 (retail)

I have noticed the file ‘dxdllreg.exe’ is not on my system.

Windows Error Report:
Product
Microsoft DirectX Diagnostic Tool

Problem
Stopped working

Date
21/09/2007 1:24 PM

Status
Report Sent

Problem signature
Problem Event Name: BEX
Application Name: dxdiag.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b474
Fault Module Name: StackHash_8d13
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 02bdd0f0
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 3081
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

Extra information about the problem
Bucket ID: 85456596

Any solutions?
I will provide more information if requested.

I don't see any interesting data around this crash. You may want to get the
Windows Debugging SDK (or whatever externally gets you WinDBG) and look at
the crash dump file in that. I don't see any crash dumps for your crash,
sorry.

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"goorambatman" <> wrote in message
news:BA317B1F-4E98-45B7-A150-...
> Problem Description
>
> When I open DxDiag I get the following error:
> "DxDiag has detected that there may have been a problem accessing
> DirectShow
> the last time this program was used. Would you like to bypass DirectShow
> this
> time?"
> If I click 'Yes' DxDiag appears to run normally. If I click 'No' DirectX
> Diagnostic Tool crashes.
>
>
> My System Info:
>
> . Windows VistaT Home Premium (6.0, Build 6000)
> (6000.vista_gdr.070627-1500)
> - Upgraded from Windows XP Media Center 2005 (I had this same problem in
> this OS too).
> . System: Dell Dimension 5150.
> . Video Card name: Radeon X1300.
> . Audio: SigmaTel High Definition Audio.
> . TV Card: Hauppauge WinTV PVR PCI II (26xxx) (PVR-150).
>
> DirectX Info:
> . DirectX Version: DirectX 10 (6.00.6000.16386 32bit Unicode)
> . DxDiag Previously: Crashed in DirectShow (stage 1)
> . DirectShow: 0/6 (retail)
>
> I have noticed the file 'dxdllreg.exe' is not on my system.
>
> Windows Error Report:
> Product
> Microsoft DirectX Diagnostic Tool
>
> Problem
> Stopped working
>
> Date
> 21/09/2007 1:24 PM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BEX
> Application Name: dxdiag.exe
> Application Version: 6.0.6000.16386
> Application Timestamp: 4549b474
> Fault Module Name: StackHash_8d13
> Fault Module Version: 0.0.0.0
> Fault Module Timestamp: 00000000
> Exception Offset: 02bdd0f0
> Exception Code: c0000005
> Exception Data: 00000008
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 3081
> Additional Information 1: 8d13
> Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
> Additional Information 3: 8d13
> Additional Information 4: cdca9b1d21d12b77d84f02df48e34311
>
> Extra information about the problem
> Bucket ID: 85456596
>
> Any solutions?
> I will provide more information if requested.
>
>

Any luck with this yet? I have the same problem. I reinstalled DirectX 10 and
the message still appears. I have updated all my drivers to the latest
versions with no luck. What system components would affect the DirectShow
portion of DirectX?

Are you referring to me?
What's your *exact* crash information? It would be unusually for your
information to match precisely.

DirectShow can be affected by alllllllllllllll sorts of things - it's a
generally very open system for multimedia which is both a blessing and a
burden.

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"StodgyWaif" <> wrote in message
news:6761DB48-7889-45A5-A98F-...
> Any luck with this yet? I have the same problem. I reinstalled DirectX 10
> and
> the message still appears. I have updated all my drivers to the latest
> versions with no luck. What system components would affect the DirectShow
> portion of DirectX?

Well I ran Dxdiag today to try and get the crash information. The dialog
asking if I wanted to skip the DirectShow portion popped up and I clicked no.
Surprise! It didn't crash this time. I've tried it several times and now the
dialog no longer pops up. I really have no idea how this was resolved either.
I haven't worked on this problem since I left this posting.

Thanks anyhow.

"zachd [MSFT]" wrote:

>
> Are you referring to me?
> What's your *exact* crash information? It would be unusually for your
> information to match precisely.
>
> DirectShow can be affected by alllllllllllllll sorts of things - it's a
> generally very open system for multimedia which is both a blessing and a
> burden.
>
> --
> Speaking for myself only.
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
>
> "StodgyWaif" <> wrote in message
> news:6761DB48-7889-45A5-A98F-...
> > Any luck with this yet? I have the same problem. I reinstalled DirectX 10
> > and
> > the message still appears. I have updated all my drivers to the latest
> > versions with no luck. What system components would affect the DirectShow
> > portion of DirectX?
>
>
>