Selim Gürsu Posted 6 hours ago Posted 6 hours ago Greetings, I previously mentioned experiencing BSODs after updating to version 5.99. However, the administration was helpless in resolving this issue. Today, I submitted both versions 5.99 and 8.25 of the "kerneld-x64.sys" file, which is causing the problem, to the "claude.ai" website. The site found the problem, and I kindly request that you fix it. Respectfully. Quote "I compared kerneld-x64.sys between v5.99 and v8.25. In 5.99 the driver uses MDL method: IoAllocateMdl + MmBuildMdlForNonPagedPool + MmMapLockedPagesSpecifyCache. In 8.25 these were replaced with ExAllocatePoolWithTag + ExFreePoolWithTag. The pool memory allocated during OSD session is likely not freed properly on driver unload, causing BAD_POOL_CALLER BSOD." Method used in version 5.99 (problem-free): IoAllocateMdl → MmBuildMdlForNonPagedPool → MmMapLockedPagesSpecifyCache These three functions work together with the MDL (Memory Descriptor List) method. It is a secure, controlled method for accessing physical memory. Windows manages this method very well. Method changed in version 6.x+ (problematic): ExAllocatePoolWithTag → ExFreePoolWithTag In the new version, the MDL method has been completely removed and replaced with direct kernel pool memory management. The problem is exactly this: When AIDA64 is closed while the OSD panel is open, the memory allocated with ExAllocatePoolWithTag is either not freed or is double-freeed. The Windows kernel detects this and calls KeBugCheckEx → BSOD. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.