Re: ZwCreateFile BSOD


"John" <jvasquez@xxxxxxx> wrote in message
news:mb9ah35e4jb9dgcupsn7iqhe95ek4gkjcc@xxxxxxxxxx
On Tue, 16 Oct 2007 10:56:55 -0400, "Don Burn"
<burn@xxxxxxxxxxxxxxxxxxxx> wrote:

No, it does not say you have a pointer problem. All it says is you have a
problem. Drop SoftIce since it is worthless and unsupported. Take the
dump
and then do a !analyze with WinDbg and submit that to the group.

Ok, Its not always a pointer problem. However, with my experience 90%
of the time it was.

Softice is great. I know it no longer supported in Vista but for XP it
works perfectly. WinDbg is ok but it requires two computer, which
sometimes I don't have.

I have used WinDbg and I wasn't too thrilled about it. It took awhile
for me to get debug statements to be transmitted over the serial port.
And then when I made a change to the driver, it appeared that I had to
reboot the target machine. In SoftIce when I make a change to the
driver, I just have to unload and then reload the driver for the
changes to take place. But I am a newbie to Windbg and probably not
using it correctly. Also because of the serial inteface, debugging was
very slow compared to Sotfice. It took what appears to be seconds
for a breakpoint to be hit. Whereas, the same break point was
instantanious.

The only way to find crashes well is !analyze. I gave up on SoftIce years
ago after discovering that SoftIce created bugs because they have
replacement of kernel functions that they implemented incorrectly.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply


.

Relevant Pages

  • Re: ZwCreateFile BSOD
    ... Drop SoftIce since it is worthless and unsupported. ... and then do a!analyze with WinDbg and submit that to the group. ... for me to get debug statements to be transmitted over the serial port. ... The only way to find crashes well is!analyze. ...
    (microsoft.public.development.device.drivers)
  • Re: Driver Expert
    ... > SoftICE and Visual SoftICE ... > Bounds Checker ... understand WDM and your own driver model very very well. ... WinDBG. ...
    (microsoft.public.development.device.drivers)
  • Re: question about oneys samples
    ... I have stated this on a number of forums, SoftIce has problems: ... debug your driver on the latest version you are SOL ... system reboots and have WinDBG load it for you. ... By using Microsoft's> central symbol server and a 1394 cable, WinDBG is just a "no brainer" for> me. ...
    (microsoft.public.development.device.drivers)
  • RE: Windbg or SoftIce?
    ... it is very handy to be able to debug on a single machine. ... SoftICE to run at all. ... I have been using WinDbg to read crash dumps for a couple of years ... driver game as they used to be. ...
    (microsoft.public.development.device.drivers)
  • Re: Build device driver using Microsoft Visual C++ 2005
    ... I have never tried the WinDbg 2 machine thing ... ... For me Softice is ... I was wrong for jumping to conclusions about 2 machine debugging ... development environment with the driver, this latter is critical if you work ...
    (microsoft.public.development.device.drivers)