From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Durrant Subject: Re: =?GB2312?B?tPC4tDogW1hlbi1kZXZlbF0gTG9vayBmb3Igc29tZSBoZWxwIA==?= =?GB2312?B?YWJvdXQgV2luZG93cyBwdiBkcml2ZXI=?= Date: Tue, 22 Dec 2009 11:43:24 +0000 Message-ID: <4B30B0DC.8020102@citrix.com> References: <000601ca82f2$9a9c6e00$e538a60a@china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <000601ca82f2$9a9c6e00$e538a60a@china.huawei.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: fanliang Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org fanliang wrote: > Thanks a lot. > I can understand what you said , But what puzzled me is that I saw nothing > about my windows pv driver from the output of !analyze -v inside windbg .I > am not sure that the BSoD had nothing with the windows pv driver. WLK goes > very well in other windows system without pv driver ,so I guess the pv > driver cases the BSod. > Just because you did not get a direct stack backtrace into a PV driver does not, of course, mean it's not at fault. You need to find out the exact nature of the object that terminated to have a clue as to what happened. Paul -- =============================== Paul Durrant, Software Engineer Citrix Systems (R&D) Ltd. First Floor, Building 101 Cambridge Science Park Milton Road Cambridge CB4 0FY United Kingdom ===============================