KERNEL32.DLL

[bballhounds31]

Whenever i play wmplayer the player freezes and i can't click on anything but my music is still playing. I get a message that says: Wmplayer has caused an error in KERNEL32.DLL. Wmplayer will now close...... if you continue to have problems try restarting your computer
and i want to know how i can get rid of it and use my media player because it won't work. Thanks

[Theoran]

Have you installed anything lately=?
Has this always happened or did it just start?

If it just started with in the last few days try this.

Start the PC and just after the first window changes to the next, Tap the F8 key until you see the Safe Boot menu.
Then select Command Prompt Only from the menu, press Enter.
At the C:\prompt
Now type in scanreg /restore and then press Enter.
A window will pop up, to scan the system and then you can select a Started Registry file just prior to the error from the next window.
Use the Up/Down arrow keys to select the Started Registry file and then press Enter, wait till the system has finished restoring the file and then you will be asked to re-start the PC.

***Warning***
Doing this may cause some data to be lost and possibly any programs that have been installed after the restore date

This will restore your system files to the way thet were before you started getting all the problems.

[Theoran]

The Kernel32.dll file is a 32-bit dynamic link library file that is found in Windows 95, Windows 98, or Windows Millennium Edition (Me). The Kernel32.dll file handles memory management, input/output operations, and interrupts. When you start Windows, Kernel32.dll is loaded into a protected memory space so that other programs do not take over that memory space.

On occasion, you may receive an Invalid Page Fault (IPF) error message. This error message occurs when a program tries to access the Kernel32.dll protected memory space. Occasionally, the error message is caused by one particular program, and other times the error message is provoked by multiple files and programs.

If the problem results from running one program, the program needs to be replaced. If the problem occurs when you access multiple files and programs, the damage is likely caused by damaged hardware.

You may want to clean boot the computer to help you identify the particular third-party memory- resident software. Note that programs that are not memory-resident can also cause IPF error messages.

The following conditions can cause Kernel32.dll error messages:

• Damaged swap file
• File allocation damage
• Damaged password list
• Damaged or incorrect version of the Kernel32.dll file
• Damaged registry
• Hardware, hot CPU, over clocking, broken power supply, RF noise, ground bounce, or bad hard disk controller
• BIOS settings for Wait states, RAM timing, or other BIOS settings
• Third-party software that is damaged or incorrectly installed
• .dll files that are saved to the desktop
• Non-existent or broken Temp folder
• A control panel (.cpl) file is damaged
• Incorrect or damaged hardware driver
• Incorrectly installed printer drivers or HP Jet admin drivers
• Damaged Java Machine
• Damaged .log files
• Damaged entries in the History folder
• Incompatible or damaged dynamic link library files
• Viruses
• Damaged or incorrect Msinfo32.exe file
• Low disk space

Install and run Lavasofts Ad-Aware to detect and remove spyware which runs in the background and causes many conflicts.
Ad Aware

**Remember**
kernel32 errors often deal with memory so you might try freeing up some of your RAM

The easiest way to get your resources up is to use msconfig. Using msconfig enables you to remove those programs that load when you boot the machine. Programs running in the background can eat away at your system resources especially if you aren't even using them.

To start the msconfig program,
Click Start
Select Run
Type msconfig in the text box
The "System Configuration Utility" window will open

After opening the MSCONFIG program, you can click on the Startup tab located at the top right of the window. Clicking Startup changes the window showing you all the programs that are capable of being executed during the windows boot process

+ Clicking on the check box in front of the program enables that program so it automatically loads during boot.
+ Un-checking the box (so it is blank) removes that program from the startup sequence so it does not load automatically.

Leave these checked:
+ScanRegistry
+SysTray
+Your Antivirus
+Your firewall if you use one

+ Unselect all of the rest
+ When you finish with the changes click the OK button to close the window
+ Reboot

You could also tyr deleting the win386.swp file and rebooting and letting Windows rebuild it.