Prev: IRP Tracker
Next: Sharing COM1 with WinDbg
From: Sushma on 7 May 2008 07:35
Thanks for the reply Doron. I really dint know this fact.

I was not able to trace out anything from call stack. It did not show
anything in my driver. Can you help out find the bug from above call
stack? Is there anything additional information i need to provide.

As i told earlier, this bug is caught only in Intel x64 PCs with
either XP 32-bit or Vista 32-bit OS'es.

Thank You.

Regards,
Sushma
From: chris.aseltine on 7 May 2008 09:40
On May 7, 6:35 am, Sushma <sushma.ye...(a)gmail.com> wrote:

> I was not able to trace out anything from call stack. It did not show
> anything in my driver.

What? You're saying "RootMdm" isn't you?

> 9ef97c48 81827f83 82f23030 8bd3a920 8bd3a920 RootMdm!RootModemPassThrough+0x21
From: Sushma on 8 May 2008 09:38

> What?  You're saying "RootMdm" isn't you?
>

A fax-modem device is connected to my virtual COM port. The fax-modem
driver is a standard one. So, i dont think it does have any problems.
When i use an app for communication i get this bug check.


From: chris.aseltine on 8 May 2008 09:42
On May 8, 8:38 am, Sushma <sushma.ye...(a)gmail.com> wrote:

> > What? You're saying "RootMdm" isn't you?
>
> A fax-modem device is connected to my virtual COM port. The fax-modem
> driver is a standard one. So, i dont think it does have any problems.
> When i use an app for communication i get this bug check.

Well, fine, but your claim was that your driver did not appear in the
stack backtrace. Meanwhile, "RootMdm" (which sounds like a root-
enumerated virtual modem) appeared right where I might expect it to be
in the stack. So is RootMdm your driver or not?
First  |  Prev  | 
Pages: 1 2
Prev: IRP Tracker
Next: Sharing COM1 with WinDbg