XP Service Pack 2 STOP: MACHINE_CHECK_EXCEPTION (BLUE SCREEN)

Hello,

I am receiving a MACHINE_CHECK_EXCEPTION (blue screen) on a fresh
install of XP SP2. After doing a little research, I found that this
exception is created by calling the kernel function "KeBugCheckEx".
Since this is a kernel routine available to all device drivers, I am
assuming that any of my device drivers could be calling this function.


According to the prototype of the function (and the help docs) , the
BugCheckParameters(1-4) can contain anything the driver programmer
decides to put into it (most commonly high and lower order bits of a
memory address).

My question is simple...is thier any way to determine which device
driver is calling this function???

TIA,

Tommy

<> wrote in message
news: ups.com...
> Hello,
>
> I am receiving a MACHINE_CHECK_EXCEPTION (blue screen) on a fresh
> install of XP SP2. After doing a little research, I found that this
> exception is created by calling the kernel function "KeBugCheckEx".
> Since this is a kernel routine available to all device drivers, I am
> assuming that any of my device drivers could be calling this function.
>
>
> According to the prototype of the function (and the help docs) , the
> BugCheckParameters(1-4) can contain anything the driver programmer
> decides to put into it (most commonly high and lower order bits of a
> memory address).
>
> My question is simple...is thier any way to determine which device
> driver is calling this function???


Often the third-parameter seems to be a pointer within the failing
driver. This fact is documented for some stop codes but seems
to work for others where it isn't documented too.

To find the load addresses of your driver you could use the pstat
command line tool. (Actually I have found pstat -s is sufficient.)

<title>KB314084 - How to gather information after a memory dump in Windows XP</title>


BTW such diagnosis is off-topic for this newsgroup.
You could probably get better help from a newsgroup which
specializes in your OS.



>
> TIA,
>
> Tommy
>


Good luck

Robert Aldwinckle
---