Kernal32.dll+Error

Problem
I receive the following error: VWS has caused and error in Kernel32.DLL VWS will now close

Discussion
This error is not directly caused by Virtual Weather Station, but is due to an external DLL module called from the Windows operating sytem.

Solution
The potential problems are: > You can test your memory modules by inserting the command: DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:ON into your Config.sys file. You can use the System Configuration Utility: > Select Start>> Run and type: msconfig [Enter] > Next, select the Config.sys tab and add the HIMEM.SYS line (above) by pressing the New button. > Windows will tell you to reboot your computer. > Watch your screen for a message; "HIMEM has detected unreliable memory at address xx:xxxxxx" which will certainly indicate that there's a memory problem. > Note: Memory problems may not immediately surface from the result of this test. It may take many reboots or even a few days for the above message to appear. > Select Control Panel > System, then select the Performance tab, click the Graphics button. Turn down Hardware acceleration by moving the slider a notch to the left, reboot, try again. > Check with your card manufacturer for an updated set of drivers. Video drivers are updated constantly, it pays to have the latest release, especially if you find yourself having problems with Internet Explorer.
 * 1) File allocation damage
 * 2) Damaged password list
 * 3) Damaged or incorrect version of the Kernel32.dll file
 * 4) Damaged registry
 * 5) Hardware, hot CPU, over clocking, broken power supply, RF noise, ground bounce, or bad hard disk controller
 * 6) BIOS settings for Wait states, RAM timing, or other BIOS settings
 * 7) .dll files that are saved to the desktop
 * 8) Non-existent or broken Temp folder
 * 9) A control panel (.cpl) file is damaged
 * 10) Incorrect or damaged hardware driver
 * 11) Incorrectly installed printer drivers or HP Jetadmin drivers
 * 12) Damaged Java Machine
 * 13) Damaged .log files
 * 14) Damaged entries in the History folder
 * 15) Incompatible or damaged dynamic link library files
 * 16) Viruses
 * 17) Damaged or incorrect Msinfo32.exe file
 * 18) Low disk space
 * 19) CPU, bus speed or multiplier overclocking
 * 20) Bad memory modules:
 * 1) Graphic acceleration set too high:
 * 1) Bad or outdated drivers, especially video drivers: