Home > General > Win87em.dll


After you have successfully uninstalled your WIN87EM.DLL-associated program (eg. Since win87em.dll is a system process it should not be stopped. program, uninstalling and reinstalling your WIN87EM.DLL-related program will likely be the solution to your problem. Please Note: Click the [ ] image to expand the troubleshooting instructions for each step below.

Particularly appreciated are the details about HOW to implement the hide87.com. When we switch between the virtual machine monitor and the host operating system, we use the primitive hardware instructions to save and restore the FPU state. DLL errors, such as those associated with WIN87EM.DLL, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. Drivers can work one day, and suddenly stop working the next day, for a variety of reasons.

win87em.dll In order to ensure your files and data are not lost, be sure to back up your files online. Reply Masai says: April 19, 2016 at 3:51 am Excellent solution! Friday, August 19, 2011 3:45 PM Reply | Quote 0 Sign in to vote TryLinux - I think you basically hit the Nail on the Head. win87em.dll, File description: Errors related to win87em.dll can arise for a few different different reasons.

This process is considered to be CPU intensive. When you run any DOS or Windows 3.1 executable, Windows XP first boots up (if one isn't already running) a mini-MSDOS 5 environment called NTVDM.exe. Wednesday, August 17, 2011 11:24 PM Reply | Quote 1 Sign in to vote A virtualized CPU isn't 100% feature complete, so there are edge cases where things don't work. Click Programs.

Click the Uninstall/Change on the top menu ribbon. Just like I did to show you. I've updated the Virtual Machine Guest drivers on the machine. Get More Information Basically the issue is that when you try to run a legacy 16-bit application in Windows XP and above you will receive the GPF (General Protection Fault).

Reply newlife007 says: January 5, 2016 at 9:36 pm Find the file called c:\windows\system32\autoexec.nt on your Windows 7 install and add the line lh c:\windows\system32\HIDE87.com to it. Below is a list of troubleshooting steps to resolve your WIN87EM.DLL problems. Without proper management, CPU intensive processes can manipulate system resources causing speed loss. IBM ThinkPad 240) under the Name column.

I've run traces, but it's hard to really tell whats going on as Process Monitor appears to only see 32-bit process therefore all activity appears to be coming from ntvdm.exe. All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. Add to lh c:\windows\system32\autoexec.nt file for the first line: Reply newlife007 says: February 7, 2015 at 3:31 pm I had a typo in there, thanks for bringing that up. Process name: Windows 80x87 floating-point emulation library Application using this process: Windows Recommended: Scan your system for invalid registry entries.

Use Registry Editor at your own risk. Thanks Al Monday, March 10, 2014 12:29 PM Reply | Quote 0 Sign in to vote Hi Al, we fixed the problem with the solution from Bruce! Eating Skittles Like a Normal Person How to generate all string's suffixes after split? Followers Blog Archive ► 2016 (5) ► November (1) ► July (1) ► April (1) ► February (1) ► January (1) ▼ 2015 (19) ► December (1) ► October (1) ►

Click Programs and Features. The issue that tstock_sjc had was NTVDM.exe looks for %WINDIR%\system32\autoexec.nt and %WINDIR%\system32\config.nt instead of autoexec.bat and config.sys. Left-Click the tab at the top that says Hardware Left-Click the button that says Device Manager. Several programs can share the same WIN87EM.DLL file, but when these programs are uninstalled or changed, sometimes "orphaned" (invalid) DLL registry entries are left behind.

Now I can use my old software in Virtual Box. Thus, these invalid DLL registry entries need to be repaired to fix the root of the problem. I attribute this configuration to the crash because I have used this same 16-bit software on tons of other windows 7 machines for years now.

Copy HIDE87.com to C:\Windows\System32\ 4.

The old version can be found her: http://support.microsoft.com/kb/86869/de Good luck! While holding CTRL-Shift on your keyboard, hit ENTER. Even if you are experienced at finding, downloading, and manually updating drivers, the process can still be very time consuming and extremely irritating. Click Control Panel on the right side menu.

Lion or Yosemite Clean Install Hangs at 'Loading Installation Information' In my case, the system time had been reset. Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse. Reply Tanner says: April 21, 2015 at 2:52 pm Thanks for your steps. When I go to perform certain activities, the program crashes and gives me a"P3 caused a General Protection Fault in module WIN87EM.DLL at 0001:02C6." As the program runs fine on a

Based on my research, I have found "The Windows 80x87 emulator library, WIN87EM.DLL, works at the 16-bit-Windows level to virtualize the coprocessor among multiple Windows-based applications that run inside the system Type "command" in the search box... win87em.dll is a safe process Can I stop or remove win87em.dll? congratulation and nice job.