kernell32.dll question

[shadypac]

I dont exactly have any problems...but i have seen them often. I read somewhere that if u delete the windows swap file that it should take care of frequent kernell errors because after reboot the swap file recreates itself. If this is true can anyone tell me why that would fix the errors. elaborate....

[L43x]

not really...i had those errors all the time with me, i think it is a major windows problem, just get used to it

sorry i had no help...

l43x

[TonyKlein]

In fact, kernel32.dll errors rarely have anything at all to do with kernel32.dll itself.

It is Windows' memory manager, and as such it's often the first to 'notice' something's amiss.

To quote MS:

"A Kernel32.dll page fault 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."

Hence, there a innumerable different Kernel32.dll error messages, and everything depends on the application involved.

There's no single fix.

[janusz]

As mentioned, "no single fix." Kernel32 problems can be due to many possible causes . . . did I say many? Yup.

Look at this long list of possible causes/solutions:
http://www.all-windows.com/kernel32.html

http://aumha.org/win4/a/kernel32.htm
http://www.************.com/info/kernel32.htm

I found cause/solution not on any list! Several months ago I had a problem over a couple of weeks with WINDOWS Explorer crashing with kernel32 error. Windows 98SE. I tried very possible solution listed in the links above. Nothing worked. I resorted to using TrayManager to keep tray icons from disappearing during the crashes. I just did not accept it that it's a quirk of Windows. Besides, it had been working fine up until then.

I did a lot of Ctrl-Alt-Dels. Of course, on restart it would go through the regular scandisk check. However, I decided to do my regular monthly scandisk check through Start-Programs-Accessories-System Tools. Surprise! It seems that the scandisk on forced reboot is not a thorough check. In any case, it found a problem and I was presented with error:

"The drive's boot area contains important information that is damaged or invalid. This can cause windows to report the free space incorrectly or slowly. Scandisk repairs the boot area by recording the correct values in this area."

Yikees! What's this all about?

From the scandisk.log I found this: "In a FAT32 partition, the FAT32 extended boot sector keeps track of the amount of free space left on the drive. The value in the boot sector can easily become out of sync with the amount of free space left on the drive. It's usually not a sign of a more serious problem, and a tool like scandisk fixes the problem by recalculating the amount of free space and updating the boot sector."

I elected to have scandisk repair the error.

Message returned:

"File system: The free space was being reported incorrectly.
ScanDisk successfully fixed the free space count."

All okay. Problem solved. No more Window Explorer crashes. I thought I'd share this . . . and add it to the possible cause/solution lists.



Janusz
Age doesn't always bring wisdom. Sometimes age comes alone.