Hello,

I don't have the checked build installed, so is there a way to find out what
driver did this after bootup? Will Driver Verifier help with this? How can
I find which process have this physical memory mapped into their virtual
address space?

Thanks in advance, because people are blaming our driver for some random
problem, which could be true, so I want to eliminate this situation first.

************************************************** *****************************
*
* A driver is mapping physical memory 00097000->0009EFFF
* that it does not own. This can cause internal CPU corruption.
* A checked build will stop in the kernel debugger
* so this problem can be fully debugged.
*
************************************************** *****************************

Oh, Driver Verifier won't help because you need the name of the driver...



"Kevin" <kevin11@hutmail.org> wrote in message
news:ubGSB7qXIHA.4808@TK2MSFTNGP05.phx.gbl...

In the kernel debugger, do `Ctrl-K`, then `.reboot`

0: kd> ^K
Will request initial breakpoint at next boot.

At the initial breakpoint, `bp nt!MiMapViewOfPhysicalSection;g`
and watch who's calling that.

You can inspect `!arbiter` as well to get an idea of the resource
assignemnt by the bus-and-physical-resources-configuration arbiter

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Kevin" <kevin11@hutmail.org> wrote in message
news:uDx5trsXIHA.1132@TK2MSFTNGP06.phx.gbl...