Assert connected to zwwritefile

Can anyone enlighten me as to what is behind the following assert shown below
on the windows 2003 checked build.

*** Assertion failed: FALSE
*** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322

I have created a thread which I put in a wait state with
KeWaitforSingleObject.
Then trigger it with kesetevent. I declare the Handle for the file locally
in
a function. This functions calls a couple wrapper functions to Zwcreatefile
and
ZwWriteFIle. I tried to follow the assembly shown in the debugger to track
the
assert. I beleive it was triggered by the following line.

test dword ptr [nt!MmInjectUserInpageErrors]

I could not find any documentation on MnInjectUserInpageErrors.

I have ensured this
thread is running ar IRQL of zero via the Windows Kernel Service that
provides
that functionality. I seen a suggestion on another thread related to
ZwWriteFile,
to trap the error. I like that suggestion but am unsure how it will give me
any
new inforamtion relevant to this problem.

Could anyone suggest what may be going on?



The stack trace is below.


kd> kp
ChildEBP RetAddr
f33c18e8 80ae2ba1 nt!DbgBreakPoint
f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
f33c1c5c 80a3e51d nt!KiSystemService+0x13f
f33c1d04 f8841f51 nt!ZwWriteFile+0x11
WARNING: Stack unwind information not available. Following frames may be
wrong.
f33c1d40 f8842b8e ssdLowerFltr+0x2f51
f33c1da0 f88415ce ssdLowerFltr+0x3b8e
f33c1dac 80d391d0 ssdLowerFltr+0x25ce
f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
00000000 00000000 nt!KiThreadStartup+0x16

Thanks for any help.






--

You are doing an unbuffered write with a non-sector-sized write length.

--

=====================
Mark Roddy
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com



"Bob_from_Corinth" <> wrote in message
news:9950D133-A3B4-43AC-BA42-...
> Can anyone enlighten me as to what is behind the following assert shown
below
> on the windows 2003 checked build.
>
> *** Assertion failed: FALSE
> *** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322
>
> I have created a thread which I put in a wait state with
> KeWaitforSingleObject.
> Then trigger it with kesetevent. I declare the Handle for the file
locally
> in
> a function. This functions calls a couple wrapper functions to
Zwcreatefile
> and
> ZwWriteFIle. I tried to follow the assembly shown in the debugger to
track
> the
> assert. I beleive it was triggered by the following line.
>
> test dword ptr [nt!MmInjectUserInpageErrors]
>
> I could not find any documentation on MnInjectUserInpageErrors.
>
> I have ensured this
> thread is running ar IRQL of zero via the Windows Kernel Service that
> provides
> that functionality. I seen a suggestion on another thread related to
> ZwWriteFile,
> to trap the error. I like that suggestion but am unsure how it will give
me
> any
> new inforamtion relevant to this problem.
>
> Could anyone suggest what may be going on?
>
>
>
> The stack trace is below.
>
>
> kd> kp
> ChildEBP RetAddr
> f33c18e8 80ae2ba1 nt!DbgBreakPoint
> f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
> f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
> f33c1c5c 80a3e51d nt!KiSystemService+0x13f
> f33c1d04 f8841f51 nt!ZwWriteFile+0x11
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> f33c1d40 f8842b8e ssdLowerFltr+0x2f51
> f33c1da0 f88415ce ssdLowerFltr+0x3b8e
> f33c1dac 80d391d0 ssdLowerFltr+0x25ce
> f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
> 00000000 00000000 nt!KiThreadStartup+0x16
>
> Thanks for any help.
>
>
>
>
>
>
> --
>

Thanks Mark, You were dead on correct, and further I think you saved my
marriage.

"Bob_from_Corinth" wrote:

> Can anyone enlighten me as to what is behind the following assert shown below
> on the windows 2003 checked build.
>
> *** Assertion failed: FALSE
> *** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322
>
> I have created a thread which I put in a wait state with
> KeWaitforSingleObject.
> Then trigger it with kesetevent. I declare the Handle for the file locally
> in
> a function. This functions calls a couple wrapper functions to Zwcreatefile
> and
> ZwWriteFIle. I tried to follow the assembly shown in the debugger to track
> the
> assert. I beleive it was triggered by the following line.
>
> test dword ptr [nt!MmInjectUserInpageErrors]
>
> I could not find any documentation on MnInjectUserInpageErrors.
>
> I have ensured this
> thread is running ar IRQL of zero via the Windows Kernel Service that
> provides
> that functionality. I seen a suggestion on another thread related to
> ZwWriteFile,
> to trap the error. I like that suggestion but am unsure how it will give me
> any
> new inforamtion relevant to this problem.
>
> Could anyone suggest what may be going on?
>
>
>
> The stack trace is below.
>
>
> kd> kp
> ChildEBP RetAddr
> f33c18e8 80ae2ba1 nt!DbgBreakPoint
> f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
> f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
> f33c1c5c 80a3e51d nt!KiSystemService+0x13f
> f33c1d04 f8841f51 nt!ZwWriteFile+0x11
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> f33c1d40 f8842b8e ssdLowerFltr+0x2f51
> f33c1da0 f88415ce ssdLowerFltr+0x3b8e
> f33c1dac 80d391d0 ssdLowerFltr+0x25ce
> f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
> 00000000 00000000 nt!KiThreadStartup+0x16
>
> Thanks for any help.
>
>
>
>
>
>
> --
>

Risking reduncy I wanted to make sure you were aware of my gratitude.
Thanks Mark. (refer to attempt at humor in my other response.)

"Mark Roddy" wrote:

> You are doing an unbuffered write with a non-sector-sized write length.
>
> --
>
> =====================
> Mark Roddy
> Windows 2003/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com
>
>
>
> "Bob_from_Corinth" <> wrote in message
> news:9950D133-A3B4-43AC-BA42-...
> > Can anyone enlighten me as to what is behind the following assert shown
> below
> > on the windows 2003 checked build.
> >
> > *** Assertion failed: FALSE
> > *** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322
> >
> > I have created a thread which I put in a wait state with
> > KeWaitforSingleObject.
> > Then trigger it with kesetevent. I declare the Handle for the file
> locally
> > in
> > a function. This functions calls a couple wrapper functions to
> Zwcreatefile
> > and
> > ZwWriteFIle. I tried to follow the assembly shown in the debugger to
> track
> > the
> > assert. I beleive it was triggered by the following line.
> >
> > test dword ptr [nt!MmInjectUserInpageErrors]
> >
> > I could not find any documentation on MnInjectUserInpageErrors.
> >
> > I have ensured this
> > thread is running ar IRQL of zero via the Windows Kernel Service that
> > provides
> > that functionality. I seen a suggestion on another thread related to
> > ZwWriteFile,
> > to trap the error. I like that suggestion but am unsure how it will give
> me
> > any
> > new inforamtion relevant to this problem.
> >
> > Could anyone suggest what may be going on?
> >
> >
> >
> > The stack trace is below.
> >
> >
> > kd> kp
> > ChildEBP RetAddr
> > f33c18e8 80ae2ba1 nt!DbgBreakPoint
> > f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
> > f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
> > f33c1c5c 80a3e51d nt!KiSystemService+0x13f
> > f33c1d04 f8841f51 nt!ZwWriteFile+0x11
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > f33c1d40 f8842b8e ssdLowerFltr+0x2f51
> > f33c1da0 f88415ce ssdLowerFltr+0x3b8e
> > f33c1dac 80d391d0 ssdLowerFltr+0x25ce
> > f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
> > 00000000 00000000 nt!KiThreadStartup+0x16
> >
> > Thanks for any help.
> >
> >
> >
> >
> >
> >
> > --
> >
>
>
>

I'm happy to have saved somebody's marriage. Want an extra wife?

--

=====================
Mark Roddy
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com



"Bob_from_Corinth" <> wrote in message
news:2F53F63F-043E-4086-87F0-...
> Thanks Mark, You were dead on correct, and further I think you saved my
> marriage.
>
> "Bob_from_Corinth" wrote:
>
> > Can anyone enlighten me as to what is behind the following assert shown
below
> > on the windows 2003 checked build.
> >
> > *** Assertion failed: FALSE
> > *** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322
> >
> > I have created a thread which I put in a wait state with
> > KeWaitforSingleObject.
> > Then trigger it with kesetevent. I declare the Handle for the file
locally
> > in
> > a function. This functions calls a couple wrapper functions to
Zwcreatefile
> > and
> > ZwWriteFIle. I tried to follow the assembly shown in the debugger to
track
> > the
> > assert. I beleive it was triggered by the following line.
> >
> > test dword ptr [nt!MmInjectUserInpageErrors]
> >
> > I could not find any documentation on MnInjectUserInpageErrors.
> >
> > I have ensured this
> > thread is running ar IRQL of zero via the Windows Kernel Service that
> > provides
> > that functionality. I seen a suggestion on another thread related to
> > ZwWriteFile,
> > to trap the error. I like that suggestion but am unsure how it will give
me
> > any
> > new inforamtion relevant to this problem.
> >
> > Could anyone suggest what may be going on?
> >
> >
> >
> > The stack trace is below.
> >
> >
> > kd> kp
> > ChildEBP RetAddr
> > f33c18e8 80ae2ba1 nt!DbgBreakPoint
> > f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
> > f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
> > f33c1c5c 80a3e51d nt!KiSystemService+0x13f
> > f33c1d04 f8841f51 nt!ZwWriteFile+0x11
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > f33c1d40 f8842b8e ssdLowerFltr+0x2f51
> > f33c1da0 f88415ce ssdLowerFltr+0x3b8e
> > f33c1dac 80d391d0 ssdLowerFltr+0x25ce
> > f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
> > 00000000 00000000 nt!KiThreadStartup+0x16
> >
> > Thanks for any help.
> >
> >
> >
> >
> >
> >
> > --
> >

I gave much thought to your offer, and after considering all the pro's and
con's,
here is my response:

" I might consider a trade."

"Mark Roddy" wrote:

> I'm happy to have saved somebody's marriage. Want an extra wife?
>
> --
>
> =====================
> Mark Roddy
> Windows 2003/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com
>
>
>
> "Bob_from_Corinth" <> wrote in message
> news:2F53F63F-043E-4086-87F0-...
> > Thanks Mark, You were dead on correct, and further I think you saved my
> > marriage.
> >
> > "Bob_from_Corinth" wrote:
> >
> > > Can anyone enlighten me as to what is behind the following assert shown
> below
> > > on the windows 2003 checked build.
> > >
> > > *** Assertion failed: FALSE
> > > *** Source File: d:\srv03rtm\base\ntos\io\iomgr\write.c, line 322
> > >
> > > I have created a thread which I put in a wait state with
> > > KeWaitforSingleObject.
> > > Then trigger it with kesetevent. I declare the Handle for the file
> locally
> > > in
> > > a function. This functions calls a couple wrapper functions to
> Zwcreatefile
> > > and
> > > ZwWriteFIle. I tried to follow the assembly shown in the debugger to
> track
> > > the
> > > assert. I beleive it was triggered by the following line.
> > >
> > > test dword ptr [nt!MmInjectUserInpageErrors]
> > >
> > > I could not find any documentation on MnInjectUserInpageErrors.
> > >
> > > I have ensured this
> > > thread is running ar IRQL of zero via the Windows Kernel Service that
> > > provides
> > > that functionality. I seen a suggestion on another thread related to
> > > ZwWriteFile,
> > > to trap the error. I like that suggestion but am unsure how it will give
> me
> > > any
> > > new inforamtion relevant to this problem.
> > >
> > > Could anyone suggest what may be going on?
> > >
> > >
> > >
> > > The stack trace is below.
> > >
> > >
> > > kd> kp
> > > ChildEBP RetAddr
> > > f33c18e8 80ae2ba1 nt!DbgBreakPoint
> > > f33c1bc4 80c6ce3d nt!RtlAssert+0xa3
> > > f33c1c5c 80afbbf2 nt!NtWriteFile+0x2bf
> > > f33c1c5c 80a3e51d nt!KiSystemService+0x13f
> > > f33c1d04 f8841f51 nt!ZwWriteFile+0x11
> > > WARNING: Stack unwind information not available. Following frames may be
> > > wrong.
> > > f33c1d40 f8842b8e ssdLowerFltr+0x2f51
> > > f33c1da0 f88415ce ssdLowerFltr+0x3b8e
> > > f33c1dac 80d391d0 ssdLowerFltr+0x25ce
> > > f33c1ddc 80b00c92 nt!PspSystemThreadStartup+0x2e
> > > 00000000 00000000 nt!KiThreadStartup+0x16
> > >
> > > Thanks for any help.
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
>
>
>