Hi all,
Please explaing me the below line :
*** STOP: 0xF00F00AB (0x0000033B,0x00000001,0x00000002,0x00000003)
Thanking in Advance,
Satish K.s
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I would suggest running on a checked build under the kernel debuger to see
if you get an assert. If so hit b to break and then kv to get a stack trace
and then resend the information. If the problem still occurs without the
assert and under the debugger then use the kv command along with .bugcheck.
The stop code of 0xF00F00AB is likely useless. Did the second line of the
bluescreen have any information on it? - Eric
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Tuesday, March 06, 2001 11:26 PM
To: File Systems Developers
Subject: [ntfsd] About Blue Screen Analysis
Hi all,
Please explaing me the below line :
*** STOP: 0xF00F00AB (0x0000033B,0x00000001,0x00000002,0x00000003)
Thanking in Advance,
Satish K.s
You are currently subscribed to ntfsd as: xxxxx@MICROSOFT.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I checked This is issuing from my Driver only( Some one developed this driver).
Intentionally they are issuing KeBugCheckEx Inside this FastIO :
PtrFastIoDispatch->AcquireFileForNtCreateSection
PtrFastIoDispatch->ReleaseFileForNtCreateSection
If they get control after hooking this they are issuing KeBugCheckEx intentionally. Anybody know the reason ?
Thanking in Advance…
Satish K.S
----- Original Message -----
From: Eric W Hanson
To: File Systems Developers
Sent: Thursday, March 08, 2001 6:27 AM
Subject: [ntfsd] RE: About Blue Screen Analysis
I would suggest running on a checked build under the kernel debuger to see if you get an assert. If so hit b to break and then kv to get a stack trace and then resend the information. If the problem still occurs without the assert and under the debugger then use the kv command along with .bugcheck.
The stop code of 0xF00F00AB is likely useless. Did the second line of the bluescreen have any information on it? - Eric
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Tuesday, March 06, 2001 11:26 PM
To: File Systems Developers
Subject: [ntfsd] About Blue Screen Analysis
Hi all,
Please explaing me the below line :
*** STOP: 0xF00F00AB (0x0000033B,0x00000001,0x00000002,0x00000003)
Thanking in Advance,
Satish K.s
You are currently subscribed to ntfsd as: xxxxx@aalayance.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Is this a filter driver? In NT 4.0, a filter’s
AcquireFileForNtCreateSection and ReleaseFileForNtCreateSection were not
called because the “IO Manager” sent these IRP’s to the base file system
device object intentionally bypassing all attached devices. That is why the
sfilter sample in the 4.0 IFS Kit replaced the underlying file system’s
AcquireFileForNtCreateSection and ReleaseFileForNtCreateSection function
pointers with its own. Consequently, the previous maintainer put in the
bugcheck because they didn’t expect these fast IO routines to be invoked in
their filter. I’m really curious to see the function call stack.
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Wednesday, March 07, 2001 11:44 PM
To: File Systems Developers
Subject: [ntfsd] RE: About Blue Screen Analysis
I checked This is issuing from my Driver only( Some one developed this
driver).
Intentionally they are issuing KeBugCheckEx Inside this FastIO :
PtrFastIoDispatch->AcquireFileForNtCreateSection
PtrFastIoDispatch->ReleaseFileForNtCreateSection
If they get control after hooking this they are issuing KeBugCheckEx
intentionally. Anybody know the reason ?
Thanking in Advance…
Satish K.S
----- Original Message -----
From: Eric W mailto:xxxxx Hanson
To: File Systems mailto:xxxxx Developers
Sent: Thursday, March 08, 2001 6:27 AM
Subject: [ntfsd] RE: About Blue Screen Analysis
I would suggest running on a checked build under the kernel debuger to see
if you get an assert. If so hit b to break and then kv to get a stack trace
and then resend the information. If the problem still occurs without the
assert and under the debugger then use the kv command along with .bugcheck.
The stop code of 0xF00F00AB is likely useless. Did the second line of the
bluescreen have any information on it? - Eric
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Tuesday, March 06, 2001 11:26 PM
To: File Systems Developers
Subject: [ntfsd] About Blue Screen Analysis
Hi all,
Please explaing me the below line :
*** STOP: 0xF00F00AB (0x0000033B,0x00000001,0x00000002,0x00000003)
Thanking in Advance,
Satish K.s
—
You are currently subscribed to ntfsd as: xxxxx@MICROSOFT.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@aalayance.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@nsisw.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mailto:xxxxx></mailto:xxxxx>
Satish,
These routines should never be called (as pointed out by Rob). Can you
please tell me what version of the OS you are running and is it possible
to get a stack backtrace so I can see how they were called?
Thanks,
Neal Christiansen
-----Original Message-----
From: Rob Fuller [mailto:xxxxx@NSISW.COM]
Sent: Thursday, March 08, 2001 07:36 AM
To: File Systems Developers
Subject: [ntfsd] RE: About Blue Screen Analysis
Is this a filter driver? In NT 4.0, a filter’s
AcquireFileForNtCreateSection and ReleaseFileForNtCreateSection were not
called because the “IO Manager” sent these IRP’s to the base file system
device object intentionally bypassing all attached devices. That is why
the sfilter sample in the 4.0 IFS Kit replaced the underlying file
system’s AcquireFileForNtCreateSection and ReleaseFileForNtCreateSection
function pointers with its own. Consequently, the previous maintainer
put in the bugcheck because they didn’t expect these fast IO routines to
be invoked in their filter. I’m really curious to see the function call
stack.
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Wednesday, March 07, 2001 11:44 PM
To: File Systems Developers
Subject: [ntfsd] RE: About Blue Screen Analysis
I checked This is issuing from my Driver only( Some one
developed this driver).
Intentionally they are issuing KeBugCheckEx Inside this FastIO :
PtrFastIoDispatch->AcquireFileForNtCreateSection
PtrFastIoDispatch->ReleaseFileForNtCreateSection
If they get control after hooking this they are issuing
KeBugCheckEx intentionally. Anybody know the reason ?
Thanking in Advance…
Satish K.S
----- Original Message -----
From: Eric W Hanson mailto:xxxxx
To: File Systems Developers mailto:xxxxx
Sent: Thursday, March 08, 2001 6:27 AM
Subject: [ntfsd] RE: About Blue Screen Analysis
I would suggest running on a checked build under the
kernel debuger to see if you get an assert. If so hit b to break and
then kv to get a stack trace and then resend the information. If the
problem still occurs without the assert and under the debugger then use
the kv command along with .bugcheck.
The stop code of 0xF00F00AB is likely useless. Did the
second line of the bluescreen have any information on it? - Eric
-----Original Message-----
From: Satish [mailto:xxxxx@aalayance.com]
Sent: Tuesday, March 06, 2001 11:26 PM
To: File Systems Developers
Subject: [ntfsd] About Blue Screen Analysis
Hi all,
Please explaing me the below line :
*** STOP: 0xF00F00AB
(0x0000033B,0x00000001,0x00000002,0x00000003)
Thanking in Advance,
Satish K.s
—
You are currently subscribed to ntfsd as:
xxxxx@MICROSOFT.com
To unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as:
xxxxx@aalayance.com
To unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@nsisw.com
To unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@Exchange.Microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mailto:xxxxx></mailto:xxxxx>