What causes a BSOD with BugCheckCode = 0?

Mike Bates

unread,

Sep 12, 2001, 4:54:46 PM9/12/01

to

We have seen a number of blue-screen crashes with a bug check code
of zero. I can't find anything in MSDN documenting that value.
Does anyone know what that means and what the parameters mean?
Parameters 3 and 4 appear to be addresses and seem to correspond
to a loaded module. Here's the DUMPCHK output for one of the
minidump files:

****************************************************************
**
** Windows 2000 Crash Dump Analysis
**
****************************************************************
*
Filename . . . . . . .Mini082901-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x820bf000
PsLoadedModuleList . .0x8046ccf0
PsActiveProcessHead. .0x8046dbe0
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x00000000
BugCheckParameter1 . .0x0000000d
BugCheckParameter2 . .0x00000000
BugCheckParameter3 . .0xbe8d6ed4
BugCheckParameter4 . .0xbe8d6e6c

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0xf20f98c8

-------------------------------------------------------------------------
Mike Bates FlightSafety Simulation
Staff Engineer 2700 North Hemlock Circle
Computer Systems Group Broken Arrow, Oklahoma 74012
-------------------------------------------------------------------------

Andre Vachon

unread,

Sep 14, 2001, 10:10:42 AM9/14/01

to

Yes, bugcheck code of 0 is unusual.

Use the debugging tools at http://www.microsoft.com/ddk/debugging.
Load te dump file in the debugger and that should give you a better idea as
to what is causing the crash.
The docs will give you details on how to do this.

-Andre

"Mike Bates" <mike...@ssdZZZ.fsiZZZ.comZZZ> wrote in message
news:3B9FCB96...@ssdZZZ.fsiZZZ.comZZZ...

Mike Bates

unread,

Sep 18, 2001, 12:37:23 PM9/18/01

to

Andre Vachon wrote:
>
> Yes, bugcheck code of 0 is unusual.

I understand that it's unusual, since I was unable to find it in
any of the lists of "common bugcheck codes". Is this bugcheck
code documented anywhere?

So what does bugcheck code == 0 mean? And what do the parameters
mean?

Thanks for the pointer to the debugging tools.

Slava M. Usov

unread,

Sep 18, 2001, 5:06:11 PM9/18/01

to

"Mike Bates" <mike...@ssdZZZ.fsiZZZ.comZZZ> wrote in message

news:3BA77843...@ssdZZZ.fsiZZZ.comZZZ...

>
>
> Andre Vachon wrote:
> >
> > Yes, bugcheck code of 0 is unusual.
>

> I understand that it's unusual [...]

I missed the original post, but anyway. I think [sic!] I've seen a couple of
times when bugcodes stored in the dump were completely bogus, while those
recorded in the system log were correct.

Slava

Mike Bates

unread,

Sep 18, 2001, 6:19:10 PM9/18/01

to

In this case, the bugcodes in the dump and those in the system log are
identical.

Leo Havmøller

unread,

Sep 19, 2001, 12:54:23 AM9/19/01

to

> ExceptionCode. . . . .0x80000003
> ExceptionFlags . . . .0x00000001
> ExceptionAddress . . .0xf20f98c8

Investigate these.

Best regards Leo Havmøller.

DMU

unread,

Oct 1, 2001, 1:25:15 PM10/1/01

to

It is very possible that the bugcheck code is bad, especially if you
were in something like PspUnhandledException or some routine
whose name looks like that.

There are some general debugging articles once you get a look
at the actual stack that will tell you how to get the actual stack
and what was running if it's possible.

I think you need to go into the dump with windbg and get the
stack and either post it or search microsoft to see what articles
come up based on what function is at the top!

And don't forget kdex2x86.dll.

DMU

"Mike Bates" <mi...@ssd.fsi.com> wrote in message
news:3BA7C85E...@ssd.fsi.com...