stand__sure

On Vista Enterprise, XPS Viewer crashes for all documents with the following details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: XPSViewer.exe
Application Version: 3.0.6913.0
Application Timestamp: 4530574a
Fault Module Name: PresentationHostDLL.dll
Fault Module Version: 3.0.6913.0
Fault Module Timestamp: 4530574f
Exception Code: c0000005
Exception Offset: 0000e084
OS Version: 6.0.6000.2.0.0.256.4
Locale ID: 1033
Additional Information 1: 6fb9
Additional Information 2: 3d36c87c5b00e639d947ffcd63f462b4
Additional Information 3: 488a
Additional Information 4: 2bfe2c361790c1c53d874207a9a44f33

***This does not appear to be a failure in all WPF applications.***

This looks like an access violation to me, but beyond that I am at loss.

Does anyone know of a resolution to this issue




Re: XML Paper Specification (XPS) Vista XPS Viewer Crashing? Turning feature off then on does not resolve.

stand__sure

more information:

(5f8.15ac): Access violation - code c0000005 (!!! second chance !!!)
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=003c3630 edi=00000001
eip=6b1be084 esp=0025f3b0 ebp=0025f3dc iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
PresentationHostDLL!COleDocument::RunServerHelper+0x57:
6b1be084 8b18 mov ebx,dword ptr [eax] ds:0023:00000000=






Re: XML Paper Specification (XPS) Vista XPS Viewer Crashing? Turning feature off then on does not resolve.

stand__sure

update: XAML Browser also fails. Apps that use WPF but do not rely upon MSIE hosting seem to work properly.




Re: XML Paper Specification (XPS) Vista XPS Viewer Crashing? Turning feature off then on does not resolve.

stand__sure

Update:

1) sfc was unable to find a problem

2) I tried the following and it seems to have resolved the XPS Viewer issue (the XAML Browser still faults but with a security exception): Boot from CD; manually remove all entries from the GAC that also have assemblies in C":\Program Files\Reference Assemblies\Microsoft\Framework\v3.0"; re-install the assemblies to the GAC.

The outstanding questions are:

1) Why did this happen

2) Why did the approach employed yield results (the dates, versions, etc. of the removed/installed assemblies all appeared to be the same)