Re: Why !deadlock command is not functional ?
- From: "Dan Mihai [MSFT]" <dmihai@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 13 May 2006 08:48:35 -0700
What is the output of "version" and "lml"?
Thanks,
Dan
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:23AEF333-A93C-4575-86BA-836A0274A961@xxxxxxxxxxxxxxxx
I have this bug:
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
...
Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a '!deadlock' KD command to get more information.
Arguments:
Arg1: 00001001, subclass of driver violation.
Arg2: 864fedd8
Arg3: 84fdacf0
Arg4: 00000000
But when I am trying:
0: kd> !deadlock
issue: 00001001 00000000 864FEDD8 FFFFFFFF
No deadlock detected
-----
What can be reason that in my debugger is not functional this command ?
Peter
.
- Follow-Ups:
- Re: Why !deadlock command is not functional ?
- From: Peter
- Re: Why !deadlock command is not functional ?
- Prev by Date: Re: your help urgently required..........
- Next by Date: Any news on USB autorun (xp)?
- Previous by thread: Drivers for Toshiba Satellite Pro 6100
- Next by thread: Re: Why !deadlock command is not functional ?
- Index(es):
Relevant Pages
|