Boot message device driver mapped memory it does not own
- From: "Kevin" <kevin11@xxxxxxxxxxx>
- Date: Thu, 24 Jan 2008 09:30:01 -0800
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.
*
*******************************************************************************
.
- Follow-Ups:
- Prev by Date: Re: GetOverlappedResult failed...
- Next by Date: Re: Screen flash on Vista 64 with XPDM video drivers
- Previous by thread: Re: 1394 debug with two host controller
- Next by thread: Re: Boot message device driver mapped memory it does not own
- Index(es):
Relevant Pages
|