Hi, recently I commenced to receive the following message in Keil uVision: an unhandled win32 exception occurred in uv4.exe [11320]. This message commencing to appears from nothing and now it appears every time. The program closes, this is very annoying. I upgraded to the latest version, run as administrator, run in compatibility mode (win 7 and XP) and nothing. Any idea of how repair this issue?
I use Windows 10 x64, TivaC TM4C123GH6PM with STELLARIS ICDI, and the latest version of TIVAWARE (TivaWare_C_Series-2.1.3.156). Too I use the working folder inside of OneDrive. I tryed to close OneDrive to prevent updates to the cloud, but nothing. The error occurs when I try to program the TIVA!!!
It is torture that the program closes every time I want to program the microcontroller
i66.tinypic.com/2ymvj42.png i63.tinypic.com/2m6lb2a.png
I need help to solve this problem.
Thanks very much!
Seems more probable the issue is with the DLL/Drivers for the Stellaris debugger pod, suggest you make sure those are up to date and suitable for Win 10
Hello, thank you very much for responding. I have installed Windows 10 since it hit the market. I've never had problems, and use uVision because it is very comfortable, compile and program; It is for this reason that no use Code Composer Studio, because I have to use a separate programmer, CCS UniFlash. This problem started from nothing, from one moment to the other began to give those mistakes. I use the compiler uVision lot, and I can not install my system because it would be hell having to reinstall all programs that I use for work. I updated versions of java, I upgraded my operating system. Keil reinstalled. uVision change folder from SSD to HDD. And nothing, I accept all suggestions.
I upgraded to the latest version of the driver Stellaris ICDI (from 2012 to 2016). But the version of the dll remains 2012. The newest are those that come by default in uVision.
i68.tinypic.com/2w7ju5d.png i63.tinypic.com/302apo8.png i63.tinypic.com/52xsi0.png
Thanks Very Much.
>>I have installed Windows 10 since it hit the market. I've never had problems...
Odd that I always hear that refrain when some mission critical roadblock is hit. Microsoft doesn't care what it breaks or changes. May be your IT group can help you isolate the issue.
Win7 boxes are cheap, you might even be able to use Virtual Box, I do that when I want XP, and support for DOS or 16-bit apps.
I normally install a new OS on a new machine, and keep the old machine for a year or two. Just to make sure I have a backup solution in case something doesn't work out as expected.
M$ regularly "helps" the world, by removing or changing functionality that they think makes life hard for the computer-illiterate. That the changes breaks existing programs or makes a living hell for some computer professionals, isn't something M$ cares too much about.
Hence we now have an OS that makes a high-end workstation look and behave as a $100 cheap tablet, with the expectation that we should use our fingers to point on our multiple 27" monitors. And if I turn off the main monitor, then M$ treats it the same as a tablet being removed from a docking station moving all windows to the secondary monitor - but forgetting that the secondary monitor is in portrait mode... Combine this with a bit of remote desktop, and it's quick to get a program or two end up totally above or to the side of a monitor and so unaccessible unless zoomed full-screen...
I have to point out:
We are 5 people using µVision. All Win10 Machines.
Two of us experienced exactly this Problem. I think it is Project-dependent, one project is working while other' fail.
Please assist, it's for your good!
Simon
Can't you remove the personalization file? uVision creates multiple files - one with the source files, compiler settings etc. But a different file that keeps track of opened source files, and their size/position etc. I would assume the removal of this file would significantly affect how uVision behaves when it is started and loading the specific project.
So in this case - what happens if you move away the <projname>.uvui[.<username>] file?
By the way "Please assist, it's for your good!" is an intereting sentence - sometimes used as a friendly-sounding threat.
Sorry, this sounded rude!
I experience a strange Problem which makes me unable to work.
Using Silabs "USB Debug Adapter" makes my µVision crash with the following message:
"An unhandled win32 exception occurred in UV4.exe [2460]. Just In Time Debugging this exception failed with..." I have no Visual Studio...
Hi,
I know this files. But for a strange reason, in this Project they don't exist!
Dear all,
we have found a workaround.
If Keil uVision stops working as expected (crash when attempting to connect to a Silabs debugger for a second time) this behaviour can be resolved by recreating the Windows User account.
Maybe this happens when using Silicon Labs IDE in parallel? This is only a guess, not confirmed.
Hope this helps!
Best regards,
Simon Filgis
Dear, Thank you very much for helping to find a solution, I still can not solve the error and it really is very, very annoying. I work with other people around the world and most are having this type of error, and do not know how to remedy it. I will try the solution you propose and share the results. Best regards.
Recreating a windows account is just a way of resetting/destroying all local profile data.
Best would be to figure out exactly which appdata that is incorrect.
If you need further information...