Re: How to troubleshoot bugchecks on my own?

Hi, thx for your response. I read some pages meanwhile, but still don't
know how to start. Well, I know that 0x8e is
KERNEL_MODE_EXCEPTION_NOT_HANDLED. The Exception is 0xc000001d which
means "illegal instruction". So, "test ebx,ebx" is illegal? Do I have
to look for the assembler reference and/or lookup the opcode?

nt!IopXxxControlFile+37e
8057f39a 85db test ebx,ebx

Now, if I look at the stack and try to interpret it, I'm not even able to find out the driver or whatever causes the fault. The error is in module nt.dll. Nice, but what now?

You wrote "- to use verifier ON for suspicious driver". I didn't know what it means. I've searched and think that I'll be able to handle it, though, I don't know which driver might be suspicious.

I'd be glad if you could give me a hint.

Armin
PS: using the MSFT symbol server, I guess I do have the latest symbols.


"Volodymyr Shcherbyna" <v_scherbina@xxxxxxxxxxxxxxx> schrieb
General recommendations are:

- to use verifier ON for suspicious driver
- to use WinDbg (or SoftIce) + latest symbols of windows binaries - to have much time to spend on analysys

--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx

"Armin Zingler" <az.nospam@xxxxxxxxxx> wrote in message
news:%23bZcZWSUIHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
> "Armin Zingler" <az.nospam@xxxxxxxxxx> schrieb
> > I'd do the work on my own. But, where to start? Do you have a
> > link about the "howto"?
> > Thanks! (Though, I appended the output below)
>
> ok ok, googling "troubleshoot bsod" does reveal "some" links... I'll read. Though, if you still have helpful information, I'm
> still
> insterested.
>
>
>
> Armin



.

Loading