Hello,
I have problems like this

iexplore.exe when calling some ActiveX

Faulting application iexplore.exe, version 8.0.6001.18813, time stamp
0x4a6621ae, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id
0x2890, application start time 0x01ca14ee0db44e69.

or WScript.exe when calling some ActiveX

Faulting application WScript.exe, version 5.7.0.18068, time stamp
0x48235878, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id
0x19c0, application start time 0x01ca14edec259ba9.

on WINXP the same ActiveX no problem,
ntdll.dll version on WinXP 5.1.2600.5755.

what can I do ?

mike

That information by itself isn't decipherable. Generally for any
non-submitted data report the data you have will be missing a potentially
useful data point.

You could potentially use the Windows Debugging SDK to track this down
further. =\

--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Michal Valent" <valent@spirit.sk> wrote in message
news:ewe6THPFKHA.4220@TK2MSFTNGP02.phx.gbl...[color=blue]
> Hello,
> I have problems like this
>
> iexplore.exe when calling some ActiveX
>
> Faulting application iexplore.exe, version 8.0.6001.18813, time stamp
> 0x4a6621ae, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
> 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id
> 0x2890, application start time 0x01ca14ee0db44e69.
>
> or WScript.exe when calling some ActiveX
>
> Faulting application WScript.exe, version 5.7.0.18068, time stamp
> 0x48235878, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
> 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id
> 0x19c0, application start time 0x01ca14edec259ba9.
>
> on WINXP the same ActiveX no problem,
> ntdll.dll version on WinXP 5.1.2600.5755.
>
> what can I do ?
>
> mike[/color]

I have rebuilded affected ActiveX under Vista,
and the problem is solved.
It seems to be some incompatibility in ntdll.dll betveen XP and Vista
versions.
mike


"zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
news:u9OyNlVFKHA.4316@TK2MSFTNGP02.phx.gbl...[color=blue]
>
> That information by itself isn't decipherable. Generally for any
> non-submitted data report the data you have will be missing a potentially
> useful data point.
>
> You could potentially use the Windows Debugging SDK to track this down
> further. =\
>
> --
> Speaking for myself only.
> See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --
> "Michal Valent" <valent@spirit.sk> wrote in message
> news:ewe6THPFKHA.4220@TK2MSFTNGP02.phx.gbl...[color=green]
>> Hello,
>> I have problems like this
>>
>> iexplore.exe when calling some ActiveX
>>
>> Faulting application iexplore.exe, version 8.0.6001.18813, time stamp
>> 0x4a6621ae, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
>> 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process
>> id 0x2890, application start time 0x01ca14ee0db44e69.
>>
>> or WScript.exe when calling some ActiveX
>>
>> Faulting application WScript.exe, version 5.7.0.18068, time stamp
>> 0x48235878, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
>> 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process
>> id 0x19c0, application start time 0x01ca14edec259ba9.
>>
>> on WINXP the same ActiveX no problem,
>> ntdll.dll version on WinXP 5.1.2600.5755.
>>
>> what can I do ?
>>
>> mike[/color]
>
>[/color]