In krnl386 exe

This problem can occur if the WIN EXE file is located in the Windows folder. This file is run by WIN. SYS files. Make sure that your path statement does not contain more than characters. If you are running a shared copy of Windows, make sure the file is in the shared Windows directory. If you are using a shared installation of Windows on a network server, make sure that your personal Windows directory and the shared Windows directory are on your MS-DOS path and are listed in that order.

Ensure you don't have any upper memory block UMB conflicts. For more information, query on the following words in the Microsoft Knowledge Base: troubleshooting and emm INI file. As a last resort, reinstall Windows. Remove the WIN This compensation may impact how and where products appear on this site including, for example, the order in which they appear.

TechnologyAdvice does not include all companies or all types of products available in the marketplace. Remember Me? Advanced Search. Results 1 to 9 of 9. Thread: krnl March 4th, , PM 1. Join Date Mar Location richmond va Posts 3. The thing is; I don't know how to get it to run in the 95pc. March 4th, , PM 2. Now, if you can get into Windows, copying it should be easy March 4th, , PM 3. If so, what can I do about it since I can't get any virus software to load?

I would try starting in safe mode and back up all your important stuff. You may need to resort to using floppies. Then boot with your emergency boot disk, wipe the system clean and reload Windows.

The instructions are here:. Thanks for your reply. Luckily I just transfered most of my files to a new laptop, so I have them backedup. But for some reason the link you gave does not work for me, it just directs me back to the dell support home page. Is there another way I can find these instructions? You're right, sorry.

Go to the support home page and enter your service tag, then you'll have the main support page for your system. Click the Solutions tab, then up toward the top, click Reinstall Guide, select your OS and you'll have it. I actually managed to resolve my problem last night without having to wipe everything clean.

I searched for the files and discovered they were relatively new, dated a few days before my problem started. Figuring they were some sort of spyware, I saved them to a floppy in case they were important and then deleted the files. After restarting I was then able to get into msconfig and start the system in safe mode, and then run my Ad-aware. It picked up quite a lot of apparently very nasty spyware, and after I got that cleaned off I was able to run spybot and my anti-virus software.

I've got my system cleaned out now, and everything seems to be working fine. But thanks for all the advice. I had the same error problem.