DbgView crashes the system on checked build win2k.

Hi,

I follows following steps to intall checked build version as given at MS
site
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh
/ddtools/checked_7njn.asp):

From cheked build cds (comes with msdn)

  1. expand ntoskrnl.ex_ ntoskrnl.chk
    expand hal.dl_ hal.chk
    and copied them to system32 system directory
  2. in boot.ini added new entry as suggested.

system boots and works finely till i start dbgview. it creates BSOD with
KMODE_EXCEPTION_NOT_HANDLED.

Any ideas?

Amit Manocha

What was the exception code with the bugcheck (KMODE_EXCEPTION_NOT_HANDLED)?

i.e. 0x80000003 or 0xC0000005 or something else? I am guessing it is 0x80000003
which is an int3 a common occurrence in a checked build…

Ian

I find DbgView crashes the system if I have a debugger attached. Do you
have a debugger attached at the time?

Marc Reinig
System Solutoins

“Amit Manocha” wrote in message
news:xxxxx@ntdev…
>
> Hi,
>
> I follows following steps to intall checked build version as given at MS
> site
>
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh
> /ddtools/checked_7njn.asp):
>
> From cheked build cds (comes with msdn)
> 1. expand ntoskrnl.ex_ ntoskrnl.chk
> expand hal.dl_ hal.chk
> and copied them to system32 system directory
> 2. in boot.ini added new entry as suggested.
>
> system boots and works finely till i start dbgview. it creates BSOD with
> KMODE_EXCEPTION_NOT_HANDLED.
>
> Any ideas?
>
> Amit Manocha
>
>
>
>

Use DebugMon from OSR on checked builds. DebugView doesn’t work for me
either.

  • Nick Ryan

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Amit Manocha
Sent: Friday, May 30, 2003 10:02 PM
To: NT Developers Interest List
Subject: [ntdev] DbgView crashes the system on checked build win2k.

Hi,

I follows following steps to intall checked build version as
given at MS site
(http://msdn.microsoft.com/library/default.asp?url=/library/en
-us/ddtools/hh
/ddtools/checked_7njn.asp):

From cheked build cds (comes with msdn)

  1. expand ntoskrnl.ex_ ntoskrnl.chk
    expand hal.dl_ hal.chk
    and copied them to system32 system directory
  2. in boot.ini added new entry as suggested.

system boots and works finely till i start dbgview. it creates BSOD with
KMODE_EXCEPTION_NOT_HANDLED.

Any ideas?

Amit Manocha


You are currently subscribed to ntdev as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Yes Ian, I am getting same exception. I don’t have any debugger attached.
How do I proceed from here ? I want to just print the internal debugging
messages. I also tried to use DebugMon as suggested by Nick, but of no use.
It doesn’t print anything.

Amit Manocha

“Ian Costello” wrote in message news:xxxxx@ntdev…
>
> What was the exception code with the bugcheck
(KMODE_EXCEPTION_NOT_HANDLED)?
>
> i.e. 0x80000003 or 0xC0000005 or something else? I am guessing it is
0x80000003
> which is an int3 a common occurrence in a checked build…
>
> Ian
>
>
>
>
>
>
>
>

Mmmm, DebugMon should work? Stating the obvious, are you capturing events? or
have you setup a filter which is not displaying the trace you want to see?
another thing you may have a dud font ( that one is out there :wink: )

If you can’t get DebugMon to work then the only other thing I can think of is
attaching a debugger to your machine… I suppose the issue here is how verbose
you debug is, as a serial connection tends to be rather slow (unless you have
firewire?)…

If your driver/application dumps a small amount of trace then all will be fine,
although I regularly dump vast amounts of trace from a filesystem which has some
rather critical timing issues at stake and I don’t have any problems with WinDbg
over a serial link.

If you don’t have another machine to attach a debugger to then that is a
problem. I have actually tried DebugMon with and without a debugger attached,
and have had no problems with it (however this is on a free build of w2k)… On
a checked build I have had problems (i.e. the checked build generating int3’s
due to invalid operations performed by some application and that type of thing)
in the past and have reverted back to WinDbg…

Ian

Yes Ian, I am getting same exception. I don’t have any
debugger attached.
How do I proceed from here ? I want to just print the
internal debugging
messages. I also tried to use DebugMon as suggested by Nick,
but of no use.
It doesn’t print anything.

Amit Manocha