rundll

[Jerrry]

Iget the following error on booting up my win98se sysRUNDLL32 caused an invalid page fault in
module KERNEL32.DLL at 0167:bff7b992.
Registers:
EAX=10015bc4 CS=0167 EIP=bff7b992 EFLGS=00010246
EBX=10015bcc SS=016f ESP=0063f7bc EBP=0063f7d8
ECX=0063f88c DS=016f ESI=00000000 FS=379f
EDX=d0146c70 ES=016f EDI=00000000 GS=0000
Bytes at CS:EIP:
80 3e 04 74 0f 33 c0 50 50 50 68 05 00 00 c0 e8
Stack dump:
00000000 1000b794 00000000 10015bc4 00000000 0063f88c 0063f88c 0063f898
tem:
How do I get rid of it?

[Theoran]

MSKB: Troubleshooting Windows 98 Startup Problems (http://support.microsoft.com/support/kb/articles/Q188/8/67.ASP?)

Rundll32 loads and runs 32-bit DLLs. Rundll32.exe is an essential Windows file, used internally to activate a wide variety of system functions, from formatting floppy disks to handling Open with... on the right-click pop-up menu.

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 (http://www.lavasoft.de/)

**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.

[Jerrry]

Thanks. I fixed the problem by running msconfig and startup, then unchecking all but essential programs. :)

[Theoran]

Glad to here that! :)

[tweakthis]

Hey, Theo, nice job. I've copied that info. :)

[Theoran]

tweak,

My above post was a combination of three posts I made at three different forums. :D

VDr, HFT, CTH.

[tweakthis]

Well it's nice to know that you're keeping out of trouble. ;) *lol* :)