I am running Windows 7 64 pro. When I start VMware player, with Windows XP service pack 3 installed, I get the error message "this application has requested runtime to terminate it in an unusual way" Microsoft visual C++.
I have dug into the event log and it is telling me that splwow64.exe is the faulting application. I was concerned at first but now that I know that it is a 32 bit print spooler it does not seem like such a big deal but it is annoying. Any thoughts on how to correct the problem?
splwow64 has issues with vmware (leaks memory). Remove printers from the guest machine on vmware, should work normally.
Related
I am developing a software for windows embedded standard x64 (win 7) and keep getting a ucrtbase.dll crash. I would like to know how to solve this.
The application is going to receive data via TCP from a client and foreward it to a different application. The application works fine on the development maschine (Win 10 with Visual Studio 2017 ...).
When the application is copied to the windows embedded system environment it is not working. When the Server-Client connection is established, some data is received and printed to the console, but finally my application will crash within a few seconds (5s or less).
I am using the Visual Studio 2015 - Windows XP (v140_xp) toolset
Platform version 10.0.17763.0
I have tested it with a multi threaded runtime library (Multi-threaded DLL) and also with staticly linked multi-threaded runtime library, because i thought it is a environment error.
The application uses a socket-library from here https://github.com/DFHack/clsocket
I have also observed that when i connect to my target and send data at slower datarates i do not get this error. But running the software on my development maschine will run in all configurations. The cpu of my target should be fast enough Core i7-3xxxQE, 4GB RAM and i have installed many redistributables installed 2010, 2012, 2013, 2015-2019, non of which match the platform version number. The closest is 10.0.30319. Is there a way to determine the correct redistributable for my application?
Here is the fault that i am getting.
Problem signature:
Problem Event Name: APPCRASH
Application Name: t50adapter.exe
Application Version: 0.0.0.0
Application Timestamp: 5d52aabc
Fault Module Name: ucrtbase.DLL
Fault Module Version: 10.0.10586.788
Fault Module Timestamp: 5879aa7b
Exception Code: 40000015
Exception Offset: 0008469a
OS Version: 6.1.7601.2.1.0.320.65
Locale ID: 1033
Additional Information 1: 1c3c
Additional Information 2: 1c3cee0f1ec6458708cdeeeb1a339ee4
Additional Information 3: 204a
Additional Information 4: 204a8c5270b5b704eeac649e2bb5f58c
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I was expecting, that my application will work when the correct redistributable packages are installed. What am i missing?
Please tell me, in case you need more information.
In case someone stumbles upon this question, i have found my problem.
My software uses 4 circular buffers for incoming data (RX,TX) and outgoing data (RX, TX) when monitoring the buffer loads, i was seeing that one buffer fills up and reaches its maximum. It seems like that communication line can not handle the amount of data. When i reduce the traffic for that buffer everything works fine.
So in conclusion the error was in my circular buffer that somehow did not send me a "buffer full" and let my application crash. This crash only occurred when a specific client is connected that could not handle the traffic.
Hope this will help someone else seeing ucrtbase.dll errors.
I'm trying to run an OpenCV 2.3.1 application through Microsoft Visual C++ 2008. I have generated the release exe file correctly, and it works fine on my windows 8 - 64 bits. In addition I would like to run it on Win XP, so I have tested it on a Win XP SP3 and it ran ok. However, when I try to run this exe on Win XP SP2, which is the target O.S. for my app, I get the following message:
unable to start correctly (0xc000001d). Click Accept to finish the
application
Any idea please?
Finally I have solved the issue: 0xC000001D: Illegal instruction, which was related to the SSE instruction used in the code. Some new SSE instruction are not implemented at some different CPU; In this case, the problem was related with my CPU: "via nehemiah". I tested the software again on a XP SP2 with CPU Intel and it worked perfectly. Finally I have to say that there is a great post which was helpful in order to fix the issue:
Unhandled exception at 0x52f9e470 in project1.exe : 0xC000001D : Illegal instruction
I see the following error whenever I try to debug "Cross Platform" under "C++" category: "Unable to start debugging. Unexpected GDB output from command "-target-select remote :5039". Remote connection closed"
I've installed all of the contents when I downloaded Visual Studio 2015 community and I ran it on Windows 10 Pro which supports Hyper-V.
I've been searching a solution for this and I've found an assumption:
"What is your debug target, the VS Android Emulator? When we saw this before it turned out to be a bad emulator image. Do you have this problem with all targets (e.g. if you try a physical device) or just one?"
In my case, I just tried this via Emulator(VS Emulator 5" Lolipop (5.0) XXHDP Phone (0x86 -...)
So I've sent an Email to VS 2015.
And the answer was like this:
"Sorry for the delay in responding we were looking at an emulator image of another user that ran into this problem so I was waiting until we had the results of that investigation to report back. We actually were not able to find anything wrong the emulator itself, our current hypothesis is that it is a network or adb problem interfering with GDB’s ability to connect to GDB server on the remote machine. Do you see this error every time you try to debug, or if you reboot the emulator will it work sometimes right after the reboot? Next time you see the error, can you open the emulator’s console mode by going go the Hyper-V manager and double clicking the emulator. Then find the location your app installed to and run “gdbserver --version" from the app path and let me know what it says? This will validate if the correct version of gdbserver is on the device."
So we are trying to solve this problem but I'm also asking here just in case.
Is there anyone who has magical solution for this problem?
I'll put a comment on this if I figure out how to solve this.
Thanks in advance.
** Following answer is from the manager of Visual Studio 2015:
You are only the second person who has run into this issue, and the first person that ran into it provided their everything works correctly when we run their .vhd on our machines so it appears to be some strange problem where gdbserver (which comes from the Android NDK provided by Google) crashes only when running on certain machines. Unfortunately the .vhd you provided does not appear to be the correct one it won’t boot for me. You can see the .vhd file being used by the emulator if you look under the settings of the emulator in your Hyper-V manager. .However given we got the other person’s .vhd you can hold off providing any additional information at this point. I’m waiting to hear back from the emulator team on if they have any ideas since this appears to be an issue only on specific machines since.
If you don’t mind my asking, if you don’t have a background in computers what inspired you to try C++ on Android? That scenario will be significantly more complicated than doing Java on Android.
It's been almost two months since I got this answer but I haven't got any additional response from them yet. So, I ended up quitting developing an application by using VS2015.
If you run into this problem, there are only two ways to go. Change your computer or stop developing application via VS2015.
If the project name contains spaces, the whole remote debugging fails. Visual Studio also creates weird paths. When checking out the "Blink1 for Raspberry Pi" template, I named the Project "Blink1 for Pi", which resulted in a path like this:
~/projects/Blink1?/for/pi/PI/for/pi....
And all the debugging failed. When I recreated this keeping the project name "Blink1", everything worked fine. It's a pity, that spaces aren't handled here...
I'm working on Visual Studio 2012 running on Windows 8 (32 bit), developing Windows Store app with C++
The app runs smooth on "local machine". But when I try to run it on the simulator, Build and Deploy succeeds but the simulator keeps loading forever! (dots coming from left and leaving at right)
When I close the simulator from the taskbar, VS gives me the following error: Unable to start the simulator. Cannot process request because the process (####) has exited.
I've been searching everywhere for a solution for a week now. The possible solutions I found were:
1. Changing the fDenyChildConnections registry.
2. Checking the "Automatically use my Windows logon name and password (and domain if any)" checkbox from the security tab of the network.
3. Updating graphics driver.
4. Disconnecting all networks.
5. Restarting VS/making new project.
6. Launching simulator from C:\Program Files\Common Files\microsoft shared\Windows Simulator\11.0\Microsoft.Windows.Simulator.exe
7. Updating VS.
The problem is still there. Does anybody have a solution?
I performed a clean install of Windows 8.1 x64 and the simulator is running smoothly. I guess running 32 bit windows on a 64 bit architecture was the cause of this issue.
Try to see if "Remote Desktop Services" is enabled, if no enable it as manual and start it.
I had the same issue and the reason was lack of Hyper-V. I installed Hyper-V and the simulator worked.
i've written a small application using c++, Qt and Visual Studio 2010. It's working on Windows XP (32bit) but it crashes on Windows 7 (64 bit) right after start-up. I see a "The program has stopped working..." error. Do I have to recompile the application for Windows 7? And is it possible to get more information why it crashes?
Thanks
In general you wouldn't have to recompile for windows 7, but it depends on your application which you haven't provided details of.
The easiest way to find out is either debug it in windows 7 or put more error handling in, so that it lets you know what has gone wrong, or where it has gone wrong
I agree with what martiert said, also, if you are using some external elements, images. sound files, video files, etc ... be sure of the file location asd this was a problem for me when I was presenting my graduation project, I moved the whole solution from a directory to another and it crashed because it was reading a not found directory ... so be sure of the links of the images, videos, sounds etc ...
You might have to recompile for Windows 7/64bit. It might not even work after a recompile, since Windows 7 is not XP, and a program written for 32 bit might not work for 64. Often one don't have to recompile, but sometimes one have to, and some times a program which works on XP won't work on Windows 7.