Vista - Feb CTP Crash on AMD Athlon 64 X2 Dual

Hi,

I recal that somewhere there was a posting about the January CTP of WPF
crashing on AMD machines due to an unsupported instruction being called. I
also believe that it was said that it should be fixed in the "next" CTP which
is the February CTP. When I run that build on my AMD machine I still get a
crash deep within milcore. I actually end up on an int 3 but one level above
on the call stack I am at "53229897 movsx eax,byte ptr [ebp-4]". I have a
crash dump that I have collected but I don't know where to send it.

I can also reproduce the problem all the time. For example when I load
Interactive Designer the bug can happen before the application loads or soon
afterwards. In some cases it loads but soon as I do something, say move a
windows it happens.

Just let me know where to send the crash dumps.

Cheers,
Clint

Hi Clint!

What you are experiencing is very likely to be a known issue. Here are steps
for suggested workaround, I will also make sure that Release Notes get
updated.

- launch VS and/or XamlPad
- launch task manager (right click on toolbar, select task manager) find
whichever process you launched: e.g. devenv.exe for VS or XamlPad.exe
right
- click on that process and select "Set Affinity"
- if you have more than one CPU selected, unmark all CPUs but one (shouldn't
matter which one) now try to repro. There should be no crashes anymore.

If these steps do not solve your problem, please feel free to reply with
your dump file attached to this address - I'd be happy to take a look at it
for you (preferably if you could RAR and ZIP it).


Thanks!


On 3/10/06 8:45 AM, in article
484CB29F-79C1-4ACD-9FFE-1ED893840EEA@microsoft.com, "clintsinger"
<clintsinger@discussions.microsoft.com> wrote:

> Hi,
>
> I recal that somewhere there was a posting about the January CTP of WPF
> crashing on AMD machines due to an unsupported instruction being called. I
> also believe that it was said that it should be fixed in the "next" CTP which
> is the February CTP. When I run that build on my AMD machine I still get a
> crash deep within milcore. I actually end up on an int 3 but one level above
> on the call stack I am at "53229897 movsx eax,byte ptr [ebp-4]". I have a
> crash dump that I have collected but I don't know where to send it.
>
> I can also reproduce the problem all the time. For example when I load
> Interactive Designer the bug can happen before the application loads or soon
> afterwards. In some cases it loads but soon as I do something, say move a
> windows it happens.
>
> Just let me know where to send the crash dumps.
>
> Cheers,
> Clint

Hi Clint!

What you are experiencing is very likely to be a known issue. Here are
steps
for suggested workaround, I will also make sure that Release Notes get
updated.

- launch VS and/or XamlPad
- launch task manager (right click on toolbar, select task manager) find
whichever process you launched: e.g. devenv.exe for VS or XamlPad.exe
right
- click on that process and select "Set Affinity"
- if you have more than one CPU selected, unmark all CPUs but one
(shouldn't
matter which one) now try to repro.

If these steps do not solve your problem, please feel free to reply with
your dump file attached to this address - I'd be happy to take a look at it
for you (preferably if you could RAR and ZIP it).


Thanks!


> On 3/10/06 8:45 AM, in article
> 484CB29F-79C1-4ACD-9FFE-1ED893840EEA@microsoft.com, "clintsinger"
> <clintsinger@discussions.microsoft.com> wrote:
>
>> Hi,
>>
>> I recal that somewhere there was a posting about the January CTP of WPF
>> crashing on AMD machines due to an unsupported instruction being called.
>> I
>> also believe that it was said that it should be fixed in the "next" CTP
>> which
>> is the February CTP. When I run that build on my AMD machine I still get
>> a
>> crash deep within milcore. I actually end up on an int 3 but one level
>> above
>> on the call stack I am at "53229897 movsx eax,byte ptr [ebp-4]". I
>> have a
>> crash dump that I have collected but I don't know where to send it.
>>
>> I can also reproduce the problem all the time. For example when I load
>> Interactive Designer the bug can happen before the application loads or
>> soon
>> afterwards. In some cases it loads but soon as I do something, say move
>> a
>> windows it happens.
>>
>> Just let me know where to send the crash dumps.
>>
>> Cheers,
>> Clint
>

Hi Gennady,

The crash was happening before I was able to set the affinity on the
application in question. I ended up getting another suggestion from Unni in
the EID team to open a cmd.exe prompt and set its affinity, then start the
WPF application. This solved my problem.

Cheers,
Clint

"gennady wexler" wrote:

> Hi Clint!
>
> What you are experiencing is very likely to be a known issue. Here are
> steps
> for suggested workaround, I will also make sure that Release Notes get
> updated.
>
> - launch VS and/or XamlPad
> - launch task manager (right click on toolbar, select task manager) find
> whichever process you launched: e.g. devenv.exe for VS or XamlPad.exe
> right
> - click on that process and select "Set Affinity"
> - if you have more than one CPU selected, unmark all CPUs but one
> (shouldn't
> matter which one) now try to repro.
>
> If these steps do not solve your problem, please feel free to reply with
> your dump file attached to this address - I'd be happy to take a look at it
> for you (preferably if you could RAR and ZIP it).
>
>
> Thanks!
>
>
> > On 3/10/06 8:45 AM, in article
> > 484CB29F-79C1-4ACD-9FFE-1ED893840EEA@microsoft.com, "clintsinger"
> > <clintsinger@discussions.microsoft.com> wrote:
> >
> >> Hi,
> >>
> >> I recal that somewhere there was a posting about the January CTP of WPF
> >> crashing on AMD machines due to an unsupported instruction being called.
> >> I
> >> also believe that it was said that it should be fixed in the "next" CTP
> >> which
> >> is the February CTP. When I run that build on my AMD machine I still get
> >> a
> >> crash deep within milcore. I actually end up on an int 3 but one level
> >> above
> >> on the call stack I am at "53229897 movsx eax,byte ptr [ebp-4]". I
> >> have a
> >> crash dump that I have collected but I don't know where to send it.
> >>
> >> I can also reproduce the problem all the time. For example when I load
> >> Interactive Designer the bug can happen before the application loads or
> >> soon
> >> afterwards. In some cases it loads but soon as I do something, say move
> >> a
> >> windows it happens.
> >>
> >> Just let me know where to send the crash dumps.
> >>
> >> Cheers,
> >> Clint
> >
>
>
>