Problem repro: create a new windows application fx project, create button on the grid, drag it to another location.
After about 0.5 seconds visual studio throws an error and asks me if I want to debug. If i choose yes, I can get to this call stack:
> ntdll.dll!7c901230()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
milcore.dll!53216a95()
milcore.dll!5316ba53()
milcore.dll!530d9318()
milcore.dll!530d5b1b()
milcore.dll!530d5b38()
milcore.dll!530d93c2()
milcore.dll!530d9204()
milcore.dll!530d9464()
milcore.dll!530d94b3()
milcore.dll!530d57be()
milcore.dll!530d57c8()
milcore.dll!530d588a()
milcore.dll!5315d097()
kernel32.dll!7c80b50b()
kernel32.dll!7c8399f3()
milcore.dll!5315d082()
At first I thought it was windows xp 64 bit that just wasn't working right, but I just did a complete clean install of xp 32 bit, vs2005 and all the januari bits and I get the exact same problem. At work I do not have this, so it must be my machine.
It's an athlon 64 X2 dual core, with nvidia 6600GT and whql forceware 81.98.
I have tried setting hardware acceleration off.
Any pointers this is really bugging me bigtime.
Regards,
Ruurd Boeke
dragging control will immediately crash visual studio
NixonX
If you happen to have a copy of the appropriate .pdb file, could you possibly mail it to me at ceiled@hotmail.com A zip file would probably be best so it doesn't get blocked. I tried setting up the symbol server, and it's not pulling down milcore.pdb.
-- Ryan Milligan
BigT
try rolling back v81.98 of the driver to the driver that comes with the OS as that is probably the most supported scenario. I see that nvidia is testing new beta versions of this driver but didnt find anything availabe for xp64 as of yet.
Allen Bergst
lets start by providing the complete callstack for original failure.
please follow instructions here on how to setup public symbols server, then try to repro and get a callstack with complete function names:
http://support.microsoft.com/default.aspx scid=kb;EN-US;q319037
if symbols still dont come out - we can look into why that happens.
migichen
It took sometime to download all the symbol files, but the proces worked fine. Except that the issue lies in milcore apparently, which is not available on your symbol store. I still hope this can be of help ;-)
I'm debuggin on the x64 btw.
Call stack:
> ntdll.dll!DbgBreakPoint()
milcore.dll!000000005318d13a()
[Frames below may be incorrect and/or missing, no symbols loaded for milcore.dll]
milcore.dll!00000000531391f7()
milcore.dll!00000000531390dc()
milcore.dll!0000000053138d60()
milcore.dll!0000000053138e03()
milcore.dll!0000000053138f85()
milcore.dll!0000000053138ea3()
milcore.dll!0000000053138f50()
milcore.dll!000000005313932d()
kernel32.dll!BaseThreadStart() + 0x3a bytes
After I break to copy the above callstack, I can press F5 again to continue and then this callstack appears:
> ntdll.dll!DbgBreakPoint()
milcore.dll!000000005318d13a()
[Frames below may be incorrect and/or missing, no symbols loaded for milcore.dll]
milcore.dll!0000000053138fc8()
milcore.dll!0000000053138ea3()
milcore.dll!0000000053138f50()
milcore.dll!000000005313932d()
kernel32.dll!BaseThreadStart() + 0x3a bytes
After that I'm in a loop, alternating between these two callstacks.
What can I do next to help
Bjarne K
i just wanted to add that the example given of dragging a control is only to show how easy it is to crash visual studio. I have the same problem with Aurora or samples i have downloaded..
I can crash anything 'avalon' within 10 seconds..
It just seems that the avalon part of winfx won't work well with my computer.
Any pointers greatly appreciated.. should I look into getting another gfx card
ePeter
I don't have access to my XP installation disk at the moment, but the Properties window in Explorer tells me I have version 6.0.5300.0 of milcore.dll. Is there anywhere we can get symbols for this DLL Thanks for your help!
-- Ryan Milligan
BrettSchroeder
I'm having the same problem as described in the original post, and have the same hardware configuration: 32-bit XP on an AMD 64 X2 with a GeForce 6600 GT. I tried rolling back my graphics driver as suggested earlier, but the version number didn't change -- the driver before 81.98 (or 8.1.9.8 as the Device Manager calls it) wasn't backed up, if there was one. Any other ideas Avalon applications worked fine prior to the January CTP -- what might have changed there to break this hardware configuration Thanks!
-- Ryan Milligan
Paramjyot
Yes, I did..
With the februari release, the behaviour did not change: it still crashes. I can start Xamlpad, put a button in, start dragging the splitter and it will crash the same way as I described.
In visual studio, cider will not show anything now (this is new). It will just report that it can't find certain types: assembly, grid etc. in the error pane.
This is new. However, I can do a rebuild without a problem (the errors dissapear then).
Any other pointers
DonnaJ
Well, I'm very happy that at least someone is experiencing the same problem as I have.
Don't bother with the driver of your gfx card: I've tried almost all versions, and also the suggested clean windows drivers.
My friends have reported some athlon related issues to be indeed fixed, but mine is still there.
I would really like someone from microsoft commenting on this issue. If I can help on debugging, I would be more then happy to do so.
vhalexxs01
soli3d
not sure if you needed to download symbols, just creating this environment variable:
_NT_SYMBOL_PATH
and setting it to:
Francois Geldenhuys
Another thought...the really odd thing is how sporadic the problem is. Sometimes Visual Studio manages to create a new Avalon project (complete with showing Cider), and sometimes it doesn't. Attempting to drag a button from its original location on the form is a 100% instant crash.
Sometimes I can hit ctrl-F5 and actually display the resulting application. When it works, I can drag it around and resize it all I like, and it won't crash. When it doesn't work, it crashes with the call stack in the original post on start-up.
-- Ryan Milligan
Andrew_42_2
I am interested in the value for "File Version" when you look at version info properties in explorer Version tab.
symbols for this release should be available via public symbols store.
Mads Brink Hansen
have you tried installing latest drivers for this video card for 64bit machine from nvidia.com
I've had some some problems with this video card and outdated drivers before - maybe this will work for you