Probing memory block with invalid start address or size.

This stop is generated if Application Verifier detects an IsBadXXXPtr call with an invalid start address (e.g. a kernel-mode address, instead of a normal user-mode address) or invalid size for the memory buffer to be probed.

Parameter1 - Start address

Parameter2 - Memory block size

Parameter3 - Not used

Parameter4 - Not used

Description - Probing memory block with invalid start address or size

Verifier stop code 0607.

To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up with an invalid address or size. Many times, the address or size are plain bogus, for example un-initialized variables.

MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs:

• In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested.
  
  
• Dereferencing potentially invalid pointers can disable stack expansion in there threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information.
  
  
• Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner.
  
  

Because of all these reasons, it is recommended to never use these APIs.