Recycle your Computers & Technology with us.

Now get an error message:"Procedure entry point Thunk Connect 32 couldn't be located in dll KERNEL32.dll

Posted By : Raymond of Katharine Gibbs School - New York on June 22, 2004

Follow us on Facebook   Follow us on Twitter   Follow us on LinkedIn

Let Data Doctors be your personal IT department today

After trying to install an HP photo printer which wouldn't install for unknown reasons & changes were made to the registry, my external zip drive, into which my regular HP printer connects, no longer is recognized. I tried to reinstall it but now get an error message:

"Procedure entry point Thunk Connect 32 couldn't be located in dll KERNEL32.dll. When I called Gateway about this file, I was told Thunk Connect has something to do w/ spyware. I did a Google search & found little except that others are getting this error message in other circumstances. What do I do now?

This question was answered on June 22, 2004. Much of the information contained herein may have changed since posting.


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 Jetadmin 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

Other problems that depend on the Kernel file

Note: The changes that were made in your registry can be the reason why you're having the error message.

About the author

Posted by Raymond of Katharine Gibbs School - New York on June 22, 2004

Need Help with this Issue?

We help people with technology! It's what we do.
Contact or Schedule an Appointment with a location for help!