Announcing Windows 10 Insider Fast+Skip Ahead Build 17040 for PC Insider

Same to you magilla.

Henry

magilla said:

If we actually get a new build today, pre-Thanksgiving activities preclude me from installing it until Friday. Hope all of my fellow Americans enjoy a happy Thanksgiving.

In the UK, PC has taken over so much, we would probably ban Thanksgiving on grounds it is offensive to other religions. Hell in Aberdeen, the council no longer permits use of word Christmas, and refers to it as "The Winter Festival". I find that offensive as the true Winter Festival was hijacked by religious people anyway :-D.

Seriously, enjoy your day.

Ah the UK has embraced Political Correctness

Henry

- thanks for letting the Christians share it with you..

OH man!
You all in the UK, are getting just as bad as the PC's in the States, with their Starbucks coffee cup fetish!

Spectrum said:

Looks like the memory manager was initially mapping a file into memory (NT calls this a section object), it does this by allocating memory from pools of kernel memory. After that, it attempted to deallocate a block of pool memory with some specific tag (ExFreePoolWithTag). The evidence points towards a double free, in other words the memory manager is trying to free something that is no longer there, which leads to undefined behavior and often a crash.We see that the pool header and the first parts of the pool header contents are zeroed out. Combine this with the fact that the function that called ExBugCheck (which is the function that creates the blue screen among other things) was an attempt to free a pool allocation, so I think it was likely an attempt to free something that was already freed.For reference, a pool header is the metadata Windows kernel adds to requests when allocating/deallocating memory from a pool. You can view this data structure in windbg from a live kernel session:

Code:

dt nt!_pool_header   +0x000 PreviousSize     : Pos 0, 8 Bits   +0x000 PoolIndex        : Pos 8, 8 Bits   +0x002 BlockSize        : Pos 0, 8 Bits   +0x002 PoolType         : Pos 8, 8 Bits   +0x000 Ulong1           : Uint4B   +0x004 PoolTag          : Uint4B   +0x008 ProcessBilled    : Ptr64 _EPROCESS   +0x008 AllocatorBackTraceIndex : Uint2B   +0x00a PoolTagHash      : Uint2B

You see, this is what I have never understood about computer os's. If this indeed is the case, knowing all we know about AI, why does the computer crash when it tries to free something that is already freed???? Why don't they write code that is smart enough to recognize that it was already freed, and make a note of it, so this isn't a problem in the future, INSTEAD OF CRASHING???? Why do we get codes that we need to look up when there is a problem in our OS? Given the advances with text to speech as well as AI, why doesn't the computer just tell us in plain language what was wrong and how to fix it, or better yet, go ahead and fix it??? Computer OS's should be self correcting, and have the ability to diagnose their own code, or any other problems within it. This is the 21st century, and you have to wonder why it isn't already happening?

Cliff S said:

OH man!
You all in the UK, are getting just as bad as the PC's in the States, with their Starbucks coffee cup fetish!

FWIW.... I hate Starbucks coffee, and I'm hardly what you would call PC!