## Atmel Studio 7.0.1931 crashing when docking windows in GUI

22 posts / 0 new
Author
Message

Hi folks,

I've got the following problem. When working with Atmel Studio, I normally got the I/O Debug window Attached on the right bar together with the solution explorer. A few days ago I accidently closed the I/O Window. After popping it up again with Debug -> Windows -> I/O, the window appeared undocked on screen. When trying to dock it via drag-and-drop to the place it was before, Atmel Studio crashes and restarts, generating a Windows error:

Name der fehlerhaften Anwendung: AtmelStudio.exe, Version: 7.0.0.3877, Zeitstempel: 0x5b2b6cb5
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x428607f9
ID des fehlerhaften Prozesses: 0x49bc
Startzeit der fehlerhaften Anwendung: 0x01d70047a0963377
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Atmel\Studio\7.0\AtmelStudio.exe
Berichtskennung: 98b70272-7b95-4081-a28f-b59b6266f519
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

The full log:

Version=1
EventType=APPCRASH
EventTime=132575025957487530
ReportType=2
Consent=1
ReportStatus=100
ReportIdentifier=8de2a99d-5f06-43b8-873c-dfa258e1cbb6
IntegratorReportIdentifier=98b70272-7b95-4081-a28f-b59b6266f519
Wow64Host=34404
Wow64Guest=332
NsAppName=AtmelStudio.exe
OriginalFilename=atmelstudio.exe
AppSessionGuid=000049bc-0002-0032-7733-96a04700d701
TargetAppId=W:0006857566f8abb38f40f3662d4d36d5836100000904!00006bf31772191ec48cc250f58e4cfc67e071d47962!AtmelStudio.exe
TargetAppVer=2018//06//21:09:15:33!8e4f3!AtmelStudio.exe
BootId=4294967295
TargetAsId=9453
IsFatal=1
EtwNonCollectReason=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=AtmelStudio.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=7.0.0.3877
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=5b2b6cb5
Sig[3].Name=Fehlermodulname
Sig[3].Value=StackHash_d037
Sig[4].Name=Fehlermodulversion
Sig[4].Value=0.0.0.0
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=00000000
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=PCH_7A_FROM_ntdll+0x000734CC
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.18363.2.0.0.256.48
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=d037
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=d0372301db6ec32d1d7391ba42516bf8
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=095f
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=095f51935d2f81e943d7d5d6eacf094f
UI[2]=C:\Program Files (x86)\Atmel\Studio\7.0\AtmelStudio.exe
LoadedModule[23]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\ShellExtensions\Platform\AppenvStub.dll
LoadedModule[44]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\msenv.dll
LoadedModule[54]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\1033\msenvui.dll
LoadedModule[82]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\ShellExtensions\Platform\1033\AppEnvmUI.dll
LoadedModule[126]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\vsdebug.dll
LoadedModule[129]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\1033\VSDebugUI.dll
LoadedModule[187]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\ShellExtensions\Platform\appenvmnu.dll
LoadedModule[217]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Compsvcspkg.dll
LoadedModule[218]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\1033\compsvcspkgui.dll
LoadedModule[221]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\encmgr.dll
LoadedModule[230]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\ProjectAggregator.dll
LoadedModule[240]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\1033\Microsoft.VisualStudioUI.dll
LoadedModule[243]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\VDT\1033\vdt80pui.dll
LoadedModule[244]=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\VS SCC\1033\VssProviderui.dll
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18363
OsInfo[3].Key=ubr
OsInfo[3].Value=1316
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1031
OsInfo[7].Key=geoid
OsInfo[7].Value=94
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=340613
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.1198.18362.0-11.0.220
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32696
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.1316.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=AC2B20AB-6186-4267-8D55-4B3CA35197D1.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].Flags=327682
File[0].Type=5
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=Atmel Studio 7.0
AppPath=C:\Program Files (x86)\Atmel\Studio\7.0\AtmelStudio.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=C8011494DCE04A8A99E6BE2B1AC19541
MetadataHash=1782956726

This also happens when trying to dock ANY window via drag-and-drop. Even opened files. I only wanted to change the order of opened files but could not move them as Atmel Studio crashed every time i released the mousebuttong to drop the file on a new position in the editors tab list. I have tried to completely uninstall atmel studio and its componments and reinstalling it (same version and different versions i know were stable).

Anybody has a clue what can cause this error? If you need any further Information, just tell me :)

Windows 10 Professional 1909 Build 18363.1316 (Tried upgrading to 20H2, didnt change)

Atmel Studio 7.0.1931 (tried versions 7.0.594, 7.0.1931, 7.0.2542)

~ HannesD

This topic has a solution.
Last Edited: Sat. Feb 13, 2021 - 07:02 AM

:: Morten

(yes, I work for Microchip, yes, I do this in my spare time, now stop sending PMs)

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Oh great. My machine updated to Win10 1909 about 5 minutes ago :-(

Doesnt seem to be systemic... I'm on latest and greatest and it works fine...

:: Morten

(yes, I work for Microchip, yes, I do this in my spare time, now stop sending PMs)

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

I did a rollback from 20H2 to 1909 again where KB4598301 wasnt installed. The issue still occurs. Do you have a hint how I could solve this?

Should I update to 20H2 again with everything up to date and then uninstall KB4598301 manually afterwards if the issue still exists?

"Dare to be naïve." - Buckminster Fuller

HannesD_zp wrote:
I did a rollback from 20H2 to 1909 ...
fyi, 2004 is also in broad deployment (not yet for 20H2)

Another Win_10 rant of frustration-part 3 | Page 5 | AVR Freaks

"Dare to be naïve." - Buckminster Fuller

This reply has been marked as the solution.

Using Microsoft's documentation as a guide, I solved this problem by adding entries to the system registry as follows:

Using the Registry Editor, find the following existing key:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework


Under this key, add the new key: AppContext

Within this key, add a new string value named:  Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix

Set the data for this string value to the string: True

Add a second new string value named:  Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix

whose value is also the string: True

Out of interest, what do they do? What is the actual problem that they solve?

Top Tips:

1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...

You can read the "Known issues" with the Windows update on the Microsoft's web site.  This link is already mentioned in a previous post:

https://support.microsoft.com/en...

DosMan wrote:

Using Microsoft's documentation as a guide, I solved this problem by adding entries to the system registry as follows:

Using the Registry Editor, find the following existing key:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework


Under this key, add the new key: AppContext

Within this key, add a new string value named:  Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix

Set the data for this string value to the string: True

Add a second new string value named:  Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix

whose value is also the string: True

Unbelievable -> this really solved the issue just freaking out ... thx a lot

Thanks man!!!

Another vote of thanks.

Ever time I tried to dock a floating "I/O" view in the debugger/simulator it would completely crash MCS7 but after applying the fix in #8 it now happily docks.

It does make you wonder why, if Microsoft know about this prevalent crash, they don't push a KB patch to fix it for everyone ?

"Dare to be naïve." - Buckminster Fuller

Your'e a genius.

I had exactly the same problem and this solved it perfectly.

Cheers for that!

I encountered the same thing the other day trying to dock the registers window.

Let's see if I can fix it with the above, but doesn't Win 10 do the updates automatically?

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

js wrote:
... but doesn't Win 10 do the updates automatically?
No if configured to pause, defer, or cease quality updates; feature updates can be delayed.

Windows Update: FAQ

[mid-page]

"Dare to be naïve." - Buckminster Fuller

The updates were installed on the 12th of February, so did the update break things?

now installing KB5001391

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

js wrote:
so did the update break things?
Yes; KB4601050 (9-Feb'21) has the .NET WPF defect.

js wrote:
now installing KB5001391
April 28, 2021—KB5001391 (OS Builds 19041.964 and 19042.964) Preview

Preview updates are for OEM and third parties (the ones at Microchip Technology)

Operators can install the Patch Tuesday updates (not preview updates, ie quality updates) though these commonly have defects; can pause or defer quality updates as the ones at Microsoft need up to a few weeks to correct these defects.

"Dare to be naïve." - Buckminster Fuller

Hippyeee it fixed it.

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

DosMan wrote:

Using Microsoft's documentation as a guide, I solved this problem by adding entries to the system registry as follows:

Using the Registry Editor, find the following existing key:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework


Under this key, add the new key: AppContext

Within this key, add a new string value named:  Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix

Set the data for this string value to the string: True

Add a second new string value named:  Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix

whose value is also the string: True

Yoho!!!
Thanks, it helped me!