Error code, C000000D

NTDEV
1

Hi All,

I am getting the error code, C000000D. It might be due to USBD_STATUS_BUFFER_UNDERRUN from usb.h or STATUS_INVALID_PARAMETER from ntstatus.h file. I am not sure what is returning this code. Is there any way, I can print out USBD_STATUS_BUFFER_UNDERRUN or STATUS_INVALID_PARAMETER rather than the value of error code?

Thanks,
Harsha

Brings words and photos together (easily) with
PhotoMail - it’s free and works with Yahoo! Mail.

2

Harsha Inamdar wrote:

I am getting the error code, C000000D. It might be due to
USBD_STATUS_BUFFER_UNDERRUN from usb.h or STATUS_INVALID_PARAMETER
from ntstatus.h file. I am not sure what is returning this code.

You’re not sure what is returning this code??? What does that mean? If
you printed out the error code, then you know exactly where you got it
from. If it was NTSTATUS returned from an API, then it is the
STATUS_INVALID_PARAMETER. If it was returned in a URB in
UrbHeader.Status, then it is USBD_STATUS_BUFFER_UNDERRUN.

Is there any way, I can print out USBD_STATUS_BUFFER_UNDERRUN or
STATUS_INVALID_PARAMETER rather than the value of error code?

Sure, but if you’re not sure now, how would you write code to decide?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Hi Tim,

Thank you for your reply. I know which function is getting called & returning this status. But that function is getting called by some other function. Can you please tell me how to print out USBD_STATUS_BUFFER_UNDERRUN or
STATUS_INVALID_PARAMETER rather than the value of error code?

Thank you.

Harsha

Tim Roberts wrote:
Harsha Inamdar wrote:

>
> I am getting the error code, C000000D. It might be due to
> USBD_STATUS_BUFFER_UNDERRUN from usb.h or STATUS_INVALID_PARAMETER
> from ntstatus.h file. I am not sure what is returning this code.

You’re not sure what is returning this code??? What does that mean? If
you printed out the error code, then you know exactly where you got it
from. If it was NTSTATUS returned from an API, then it is the
STATUS_INVALID_PARAMETER. If it was returned in a URB in
UrbHeader.Status, then it is USBD_STATUS_BUFFER_UNDERRUN.

> Is there any way, I can print out USBD_STATUS_BUFFER_UNDERRUN or
> STATUS_INVALID_PARAMETER rather than the value of error code?

Sure, but if you’re not sure now, how would you write code to decide?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

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

---------------------------------
Brings words and photos together (easily) with
PhotoMail - it’s free and works with Yahoo! Mail.

4

If you’re using WPP to display messages, it supports %!STATUS! to display
status names as well as their codes.

Ken

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Harsha Inamdar
Sent: Friday, February 03, 2006 9:51 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Error code, C000000D

Hi Tim,

Thank you for your reply. I know which function is getting called &
returning this status. But that function is getting called by some other
function. Can you please tell me how to print out
USBD_STATUS_BUFFER_UNDERRUN or
STATUS_INVALID_PARAMETER rather than the value of error code?

Thank you.

Harsha

Tim Roberts wrote:

Harsha Inamdar wrote:

>
> I am getting the error code, C000000D. It might be due to
> USBD_STATUS_BUFFER_UNDERRUN from usb.h or STATUS_INVALID_PARAMETER
> from ntstatus.h file. I am not sure what is returning this code.

You’re not sure what is returning this code??? What does that mean?
If
you printed out the error code, then you know exactly where you got
it
from. If it was NTSTATUS returned from an API, then it is the
STATUS_INVALID_PARAMETER. If it was returned in a URB in
UrbHeader.Status, then it is USBD_STATUS_BUFFER_UNDERRUN.

> Is there any way, I can print out USBD_STATUS_BUFFER_UNDERRUN or
> STATUS_INVALID_PARAMETER rather than the value of error code?

Sure, but if you’re not sure now, how would you write code to
decide?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

________________________________

Brings words and photos together (easily) with
PhotoMail
http:.com> - it’s free and works with Yahoo! Mail. — Questions? First check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are
currently subscribed to ntdev as: xxxxx@comcast.net To unsubscribe send a
blank email to xxxxx@lists.osr.com</http:>

5

On Fri, Feb 03, 2006 at 06:51:07PM -0800, Harsha Inamdar wrote:

Thank you for your reply. I know which function is getting
called & returning this status. But that function is getting called
by some other function. Can you please tell me how to print out
USBD_STATUS_BUFFER_UNDERRUN or STATUS_INVALID_PARAMETER rather than
the value of error code?

Look, the point is that there is NO WAY to do this! I would think this
would be obvious: when all you have is a number, there is absolutely
no way for the operating system to know whether it is
STATUS_INVALID_PARAMETER or USBD_STATUS_BUFFER_UNDERRUN or
MY_PRIVATE_ERROR_CODE_THAT_I_JUST_MADE_UP. It's just a number.

The meaning of the code depends on the context -- on where the code came
from. It is up to YOU, the driver programmer, to know where that was.
The operating system cannot untangle this after the fact. The message
cannot have been created from thin air; you got the code in YOUR driver,
which is entirely under YOUR control. YOU need to figure out where the
error code came from. Given that, plus the advice I gave in my original
reply, you should be able to decide what is going on.

USBD_STATUS_BUFFER_UNDERRUN is an indication of a rather unusual
situation. Without knowing any more, I would be 99% sure that it is
STATUS_INVALID_PARAMETER, but YOU are the only one who can know this
for sure.

Personally, I think it was idiotic for the authors of the USBD driver
to choose error code that overlap with the standard NTSTATUS codes,
especially when they had 32 bits to choose from, but it's way too late
to fix that now.

6

On Sat, Feb 04, 2006 at 08:30:39AM -0500, Ken Cross wrote:

If you're using WPP to display messages, it supports %!STATUS! to display
status names as well as their codes.

That's not necessarily good advice here. The %!STATUS! formatter assumes
that the value you pass it is an NTSTATUS. Thus, it is always going to
show STATUS_INVALID_PARAMETER, even if the error code came from the USBD
error value in a URB.

As I said before, the operating system doesn't know where the C000000D
came from. The driver writer is the only one who knows this.

7

Thank you Tim.

-Harsha

xxxxx@probo.com wrote:
On Fri, Feb 03, 2006 at 06:51:07PM -0800, Harsha Inamdar wrote:

Thank you for your reply. I know which function is getting
called & returning this status. But that function is getting called
by some other function. Can you please tell me how to print out
USBD_STATUS_BUFFER_UNDERRUN or STATUS_INVALID_PARAMETER rather than
the value of error code?

Look, the point is that there is NO WAY to do this! I would think this
would be obvious: when all you have is a number, there is absolutely
no way for the operating system to know whether it is
STATUS_INVALID_PARAMETER or USBD_STATUS_BUFFER_UNDERRUN or
MY_PRIVATE_ERROR_CODE_THAT_I_JUST_MADE_UP. It's just a number.

The meaning of the code depends on the context -- on where the code came
from. It is up to YOU, the driver programmer, to know where that was.
The operating system cannot untangle this after the fact. The message
cannot have been created from thin air; you got the code in YOUR driver,
which is entirely under YOUR control. YOU need to figure out where the
error code came from. Given that, plus the advice I gave in my original
reply, you should be able to decide what is going on.

USBD_STATUS_BUFFER_UNDERRUN is an indication of a rather unusual
situation. Without knowing any more, I would be 99% sure that it is
STATUS_INVALID_PARAMETER, but YOU are the only one who can know this
for sure.

Personally, I think it was idiotic for the authors of the USBD driver
to choose error code that overlap with the standard NTSTATUS codes,
especially when they had 32 bits to choose from, but it's way too late
to fix that now.

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

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

Relax. Yahoo! Mail virus scanning helps detect nasty viruses!