From: Paul Durrant <paul.durrant@citrix.com>
To: fanliang <fanliang@huawei.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Look for some help about Windows pv driver
Date: Tue, 22 Dec 2009 09:38:19 +0000 [thread overview]
Message-ID: <4B30938B.8020809@citrix.com> (raw)
In-Reply-To: <000101ca82a7$7cc3da80$e538a60a@china.huawei.com>
fanliang wrote:
> Is there any body have used GPL Windows pv driver ? Or WLK tools ? After
> I installed GPL windows pv driver in my windows vm, I run WLK for a
> while, and a few minutes later, I got a BSoD with error code
> STOP0X000000F4 . Used windbg to debug, I got some call stack about the
> system proccess .It is strange that the call stack include nothing about
> the pv driver. I'm wandering how can I fix this problem ? Many thanks if
> some one gave me some suggestions.
First, have a look at
http://msdn.microsoft.com/en-us/library/ms789516.aspx and look up the
bugcheck code. In your case it's CRITICAL_OBJECT_TERMINATION. If you
look at http://msdn.microsoft.com/en-us/library/ms797140.aspx you'll see
that parameter 1 of the bugcheck tells you the object type (process or
thread), parameter 2 points to the object, parameter 3 points to the
process image file name and parameter 4 points to an ASCII string
telling you what happened.
If you didn't already, then run !analyze -v inside windbg as it will
also tell you most of this and decode some of the info for you.
Paul
--
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
===============================
next prev parent reply other threads:[~2009-12-22 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 1:38 Look for some help about Windows pv driver fanliang
2009-12-22 9:38 ` Paul Durrant [this message]
2009-12-22 10:36 ` 答复: [Xen-devel] " fanliang
2009-12-22 11:43 ` Paul Durrant
2009-12-22 11:55 ` James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B30938B.8020809@citrix.com \
--to=paul.durrant@citrix.com \
--cc=fanliang@huawei.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.