No, there's no way for me to be sure. It's just in a kernel allocator, and it was an educated desk. If you've got some seriously corrupt folders, it's quite possible that those errors are causing the kernel to do something wrong in memory allocation... but since you didn't mention the fact that things were corrupt there was no way for me to guess that. (All you said was that, since the update, SD! is crashing your system -- but it doesn't seem isolated to SD! any more...)
__________________
--Dave Nanian
|