Windows 10: How CreateDIBSection deallocate the **ppvBits?

From the documentation, it mentioned that "if hSection is NULL, the system allocates memory for the DIB. The system closes the handle to that memory when you later delete the DIB by calling the DeleteObject function."


Does this means that the memory allocated for the **ppvBits will be automatically deleted, following the call of DeleteObject? Thanks.


P.S. The reason I asked this is because I doubt that the memory is not cleared completely at the background of this API after calling DeleteObject, because when I run several time for my program, which calling the CreateDIBSection to capture the bitmap of the same image, the bitmap bit values are changing.

:)

 

Customize to avoid Clock Watchdog timeout

It would be a great benefit to all receiving Blue Screen error Clock Watchdog Timeout if you fixed the Windows dispatcher to utilize ALL available CPUs. This is not a USER responsibility. Windows needs to fix the dispatcher code to deal with CPU allocation
and deallocation. Not a USER issue. Bad code in Windows needs to be repaired.

 

Adding to a Raid 0 array

Hope so too, all I know is that in my raid create menu, there is an option to "allocate spare drive" and to "deallocate spare drive". I guess I'll do a major backup first...

 

Win 10 Upgrade Drives Not Mounted but Visible

I put my solution into my thread, if you interested to recover your data check it out:

drive letter missing, disk migrated to GPT and half of it deallocated

Hope you'll fix it too.