Mr Tweaks - Back to homepage
 
   

Shop | How to | Reg Edit Tips | Got An Error? | Mac Tips | About Us | Products Page | Tips | Cable & ADSL | News & Events | Strange Tips | Contact Us | Links | Security | Mail | Modems

   

Windows 98 Troubleshooting: Kernel32.dll Errors

Here are a few of the more common causes of Kernel32 errors:

Bad memory modules

Insert 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 in the Open box and press OK, select the Config.sys tab and add the HIMEM.SYS line 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.

It may take several reboots over a period of days for this to show up. You can also download diagnostic software from BCM, BCM Diagnostics [3.87MB], or from AMI, you have to register to download a free demo version.

There is no 100% certain way to test memory except to either substitute known good modules or to use a hardware tester.

  • CPU, bus speed or multiplier overclocking. If you are overclocking... what do you expect?
  • Graphic acceleration set too high. 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. Repeat as necessary.
  • Bad or outdated drivers, especially video drivers. Check with your card manufacturer for an updated set of drivers. Video drivers are updated constandly, it pays to have the latest release, specially if you find yourself having problems with Internet Explorer.
  • Faulty or dirty cooling fans on your CPU or power supply. The CPU fan can be cleaned with a small paintbrush and some compressed air. The power supply fan should be cleaned only by someone who is comfortable working around high voltage components.

 

   
[an error occurred while processing this directive]
Click Here!