• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Error in kernel32.dll

Fabio

Senior member
I am getting this error quite often that says something along the line of IE created an error in kernel32, if this problem persists you may have to restart your computer. This happen with IE as well as some other programs. Anyone know what casues it? Is this file corrupt? If so, how do I go about fixing it. Could some sort of hardware becausing this? Or is it software only? I am running Me on a PIII800 Asus CUSL2-c.


Thanks,

Fabio
 
It's your unstable "Genuine Intel Processor" 😛

Sorry... had to be said with all the AMD is unstable crap floating around.
 
It is a common error, there are fixes for it.. for one, try reinstalling IE.. if that doesn't help, goto microsoft's knowledge base and search there, i'm sure you will find a fix for it.
 
That never goes away. hahahah are you suing WIN ME? hahahah
j/k
No it seems that no matter what MS OSes always get that error once in awhile. Especially WIN ME. Try Win2k
 
Kernal errors are usually a very good sign that a sub-system isn't working correctly or is unstable.

Generally when Windows kernal32.dll errors occur, a system only needs to meet only one of the following criteria.
1. The system is overclocked
2. Memory sub system is set up incorrectly ( if CAS3 ram is running at CAS2 for example )
3. Generic memory is used ( Unfortunately this happens a lot.)
4. RAM has been mis-matched ( PC100, PC66 or PC133 combined)
5. The PCI bus is overclocked.
6. There is an IRQ conflict between 2 or more devices.
These aren't the only causes, but really are some of the main ones.

I would start by changing my memory timings so they aren't as agressive. Then work from there..
 
try jfall's idea. you can repair IE by going to add/remove progams,select IE, click add/remove & a new dialogue box will come up giving you 3 options. choose repair option!
 
Silver is on the right track. I would try to switch out the memory first. If you cannot switch it out, try using just one stick of memory, and then the other. If you only have one stick of memory, try it in another slot. Kernel32 errors can be a b!tch to track down. Good luck.
 
How would I know if there was an IRQ conflict. Device manager does not show any conflicts. My IRQ's are as follows:


00 System Timer
01 Keyboard
02 Programmable interrupt controller
03 Winbond PCI Ethernet Adapter
03 ACPI IRQ holder for PCI IRQ steering
04 COM1
05 SB LIve SB16 Emulation
06 standard floppy disk controller
07 ACPI IRQ holder for pci irq steering
08 System CMOS
09 Intel 82801BA/BAM USB Universal Host controller 2
09 Adaptec AHA-294X/AIC-78XX PCI SCSI Controller
09 Realtek PCI Ethernet Adapter
09 Creative SB Live! Value
09 ACPI IRQ Holder for PCI IRQ Steering
09 ACPI IRQ Holder for PCI IRQ Steering
09 ACPI IRQ Holder for PCI IRQ Steering
09 ACPI IRQ Holder for PCI IRQ Steering
09 SCI IRQ used by ACPI bus
10 Intel 82801BA/BAM SMBus Controller - 2443
10 ACPI IRQ Holder for PCI IRQ Steering
11 All-in-Wonder Radeon
11 ACPI IRQ Holder for PCI IRQ Steering
13 Numeric data processor
14 Intel 82801BA Ultra ATA Storage Controller
14 Primary IDE controller (dual fifo)
15 Intel 82801BA Ultra ATA Storage Controller
15 Secondary IDE controller (dual fifo)

Is there something I need to change here?


Thanks for al lof the ideas,

Fabio
 
hehe, free beer on irq 9!!
IMO, first thing is disable sb emulation in device manager! will give you a free irq at minimum & hopefully one of your devices on irq 9 will move over! try disabling com 1 in bios as well then check your irq "spread".
Alteratively,you can force irqs to specific slots in bios!
 
I kept on getting that error a little while ago. It turned out it is VERY BAD to run your hrad drive at 40 pci bus on a highpoint ata66 controller. hehe. It corrupted about 2 gigs of my hard drive but after endless hours in scandisk and a reinstall of windows I fized the problem. 🙂
 
I tried what bacillus suggested and one NIC moved to 5 and so did one ACPI IRQ Holder for PCI IRQ steering. I'll try this for a little whil and see what happens.



Fabio
 
Back
Top