Doubts on KMODE_EXCEPTION_NOT_HANDLED!

Hello

I am getting this KMODE_EXCEPTION_NOT_HANDLED quiet intermittently. The
exception code which comes is 0x80000003 (STATUS_BREAKPOINT). Can somebody
suggest what might possbily be the reasons for this kind of a bug? How can I
track this BSOD?

I am not able to judge anything based on the stack trace.
Any inputs regarding this will be greatly appreciated,

Warm regards,
Venky


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Do you have a DbgBreakPoint() KdBreakPoint() or _asm int 3/int 1 anywhere in
your code?

-----Original Message-----
From: Varadan Venkatesh [mailto:xxxxx@tataelxsi.co.in]
Sent: Monday, September 10, 2001 4:39 AM
To: NT Developers Interest List
Subject: [ntdev] Doubts on KMODE_EXCEPTION_NOT_HANDLED!

Hello

I am getting this KMODE_EXCEPTION_NOT_HANDLED quiet intermittently. The
exception code which comes is 0x80000003 (STATUS_BREAKPOINT). Can somebody
suggest what might possbily be the reasons for this kind of a bug? How can I
track this BSOD?

I am not able to judge anything based on the stack trace.
Any inputs regarding this will be greatly appreciated,

Warm regards,
Venky


You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Varadan:

This is most likely because you’re running a checked build of your driver
(or there are other “checked” drivers) without debugger. If the debugger was
present (in case of SoftIce you have to make sure that int3=on) then int 3
(which is breakpoint exception) would break your code into debugger.
You can protect your driver from BSODing on int 3 if the debugger is not
present by placing DbgBreakPoint inside __try __except clause: __try {
DbgBreakPoint(); } __except(EXCEPTION_EXECUTE_HANDLER) {}
In this case, if debugger is present it will break into your code. If
debugger is not present this exception will be handled, so BSOD will not
happen.

Regards,

Vladimir

-----Original Message-----
From: Varadan Venkatesh [mailto:xxxxx@tataelxsi.co.in]
Sent: Monday, September 10, 2001 4:39 AM
To: NT Developers Interest List
Subject: [ntdev] Doubts on KMODE_EXCEPTION_NOT_HANDLED!

Hello

I am getting this KMODE_EXCEPTION_NOT_HANDLED quiet intermittently. The
exception code which comes is 0x80000003 (STATUS_BREAKPOINT). Can somebody
suggest what might possbily be the reasons for this kind of a bug? How can I
track this BSOD?

I am not able to judge anything based on the stack trace.
Any inputs regarding this will be greatly appreciated,

Warm regards,
Venky


You are currently subscribed to ntdev as: xxxxx@Starbase.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

While Daniel and Vladimir point out things that you should check, in my
experience on an SMP target, this error is very frequently associated with
faulty synchronization and serialization of critical code and data. Make
sure that you are not releasing a spin lock when you shouldn’t, and that you
are not touching critical data with out holding a spin lock. I would almost
be willing to bet that you are also seeing IRQL_NOT_Xxxx errors, and maybe
even multiple IRP completion BSODs.

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com

-----Original Message-----
From: Varadan Venkatesh [mailto:xxxxx@tataelxsi.co.in]
Sent: Monday, September 10, 2001 4:39 AM
To: NT Developers Interest List
Subject: [ntdev] Doubts on KMODE_EXCEPTION_NOT_HANDLED!

Hello

I am getting this KMODE_EXCEPTION_NOT_HANDLED quiet intermittently. The
exception code which comes is 0x80000003 (STATUS_BREAKPOINT). Can somebody
suggest what might possbily be the reasons for this kind of a bug? How can I
track this BSOD?

I am not able to judge anything based on the stack trace.
Any inputs regarding this will be greatly appreciated,

Warm regards,
Venky


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I was getting weird access violations when had breakpoints set from a prior session with an older windbag version.
Ignoring this would cause a blue screen.
I would work around this by deleting the breakpoints before starting the driver, adding a breakpoint in DriverEntry,
then adding the real breakpoints after it stopped at the first one.

-DH
----- Original Message -----
From: “Gary Little”
To: “NT Developers Interest List”
Sent: Monday, September 10, 2001 12:03 PM
Subject: [ntdev] RE: Doubts on KMODE_EXCEPTION_NOT_HANDLED!

> While Daniel and Vladimir point out things that you should check, in my
> experience on an SMP target, this error is very frequently associated with
> faulty synchronization and serialization of critical code and data. Make
> sure that you are not releasing a spin lock when you shouldn’t, and that you
> are not touching critical data with out holding a spin lock. I would almost
> be willing to bet that you are also seeing IRQL_NOT_Xxxx errors, and maybe
> even multiple IRP completion BSODs.
>
> Gary G. Little
> Staff Engineer
> Broadband Storage, Inc.
> xxxxx@broadstor.com
>
> -----Original Message-----
> From: Varadan Venkatesh [mailto:xxxxx@tataelxsi.co.in]
> Sent: Monday, September 10, 2001 4:39 AM
> To: NT Developers Interest List
> Subject: [ntdev] Doubts on KMODE_EXCEPTION_NOT_HANDLED!
>
> Hello
>
> I am getting this KMODE_EXCEPTION_NOT_HANDLED quiet intermittently. The
> exception code which comes is 0x80000003 (STATUS_BREAKPOINT). Can somebody
> suggest what might possbily be the reasons for this kind of a bug? How can I
> track this BSOD?
>
> I am not able to judge anything based on the stack trace.
> Any inputs regarding this will be greatly appreciated,
>
> Warm regards,
> Venky
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@broadstor.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com