Re: DeviceIoControl causes crash on XP machine

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

nospam_at_cristalink.com
Date: 10/03/04 

Date: Mon, 4 Oct 2004 09:30:50 +1300

> size. But I'm a newbie when it comes to device
> drivers and I'm not sure what the problem is or
> how to debug it.

Then it's a good idea to hire an expert.

Usually, you run the WinDbg kernel debugger on a crash dump (Ctrl+D), type
"!analyze -v" and see the source line of your driver which caused the crash,
provided you have the driver's .pdb file.

"RickL" <zlingle@nospam.com> wrote in message
news:%ZY7d.2812$z04.1083@twister.socal.rr.com...
> Problem:
> Call to DeviceIoControl causes system reboot on an
> XP machine. The error indicated before XP tells me
> to shutdown is DEVICE_IRQL_NOT_LESS_OR_EQUAL.
>
> Details:
> I have an application that communicates with an
> 8-bit monochrome camera through a 3rd-party DLL
> and 1394 device driver. The camera is DCAM
> compliant and provides 2 modes of operation,
> Format 0 (640x480) and Format 7 ( variable
> height). The application and camera work
> correctly in all cases except one as desribed
> below.
>
> In Format 7 mode, the user can adjust the the
> number of vertical lines in increments of 6 lines
> up to the maximum height of 480 lines. (Note: the
> camera sends image data in chunks that are 6 lines
> by 640 pixels = 3840 bytes). For example, the
> user could configure the camera to start at line 1
> with an image height of 48 lines. In this case,
> the size of the image would be 640x48 = 30720
> bytes. Likewise, if the height was set to 12
> lines, the image size would be 7680 bytes. Both of
> these cases work fine.
>
> The problem occurs when I set the height to 6
> lines. Now the image size is 640x6 = 3840 bytes.
> As it turns out, this size is equal to the
> camera's bytes-per-packet size which is also 3840
> bytes. I have the source code for the DLL and
> device driver and found by stepping, that the
> crash occurs in the call to DeviceIoControl. My
> guess is that the problem is caused by the
> bytes-per-packet size being equal to the image
> size. But I'm a newbie when it comes to device
> drivers and I'm not sure what the problem is or
> how to debug it.
>
> Thanks for any suggestions?
>
> RickL
>
>
>
>
>
>
>

Relevant Pages

  • Installing drivers for Red Hat 9 using 2.4 kernal
    ... Hey can anyone here help me install these drivers I have for this ... An USB camera with ST Microelectronics bridge chip and either VV6410, ... 0x0870 or the camera definitely is not supported by this driver. ... kernel source directory, but some distributions might ...
    (comp.os.linux.setup)
  • [PATCH 5/5] Add the viafb video capture driver
    ... Add a driver for the video capture port on VIA integrated chipsets. ... CMOS camera controller. ... * Some simple register accessors; they assume that the lock is held. ... * Find the next videobuf buffer which has somebody waiting on it. ...
    (Linux-Kernel)
  • RE: Webcam installation problem
    ... is in themissing driver. ... them sepcs of your camera and they will send you the driver, ... Explanation of error codes generated by Device Manager in Microsoft Windows ... install the driver as some anti-virus famous of killing drivers sometimes. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: setting a spca5xx webcam under sarge?
    ... the camera causes the whole system to freeze. ... a gcc version problem between the kernel gcc and the driver gcc. ... but how are you accessing the camera? ... Cat'ing /dev/video1 (video0 is a bttv card) froze the ...
    (Debian-User)
  • RE: Webcam installation problem
    ... The driver is available on their website. ... them sepcs of your camera and they will send you the driver, ... Explanation of error codes generated by Device Manager in Microsoft Windows ... install the driver as some anti-virus famous of killing drivers sometimes. ...
    (microsoft.public.windowsxp.help_and_support)