Bugcheck: Apple iSight 1394a camera, 1394bus.sys

J

James

Hi all,

I've tried plugging an Apple iSight 1394a camera (webcam)
into a couple of Windows 2000 Pro machines and all of them
bugcheck instantly. It appears to be a problem in
1394bus.sys

Windows XP SP1 does not crash. Anyone else notice this
problem?


Windows 2000 Pro SP4
Intel Pentium III 800Mhz, 256MB RAM, 1394a OHCI card

----------------- WinDebug info -----------------

BugCheck C2, {7, b8a, 81529c20, 81529c28}

*81529c20 size: 80 previous size: 20 Probably caused
by : 1394BUS.SYS ( 1394BUS!
Bus1394GetConfigurationInformation+905 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
804aab44 cc int 3


kd> !analyze -v

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.
Typically this is at a bad IRQL level or double freeing
the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already
freed
Arg2: 00000b8a, (reserved)
Arg3: 81529c20, Memory contents of the pool block
Arg4: 81529c28, Pointer to pool header

Debugging Details:
------------------

*81529c20 size: 80 previous size: 20
FREED_POOL_TAG: Mdl

BUGCHECK_STR: 0xc2_7_Mdl

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80439257 to 804aab44

STACK_TEXT:
f403f6d0 80439257 00000003 f403f718 00000007 nt!
RtlpBreakWithStatusInstruction
f403f700 8043984a 00000003 81529c20 804d5de0 nt!
KiBugCheckDebugBreak+0x31
f403fa8c 804c769c 000000c2 00000007 00000b8a nt!
KeBugCheckEx+0x390
f403fad0 804c7353 81529c28 00000000 f403fb34 nt!
ExFreePoolWithTag+0x243
f403fae0 f3c2d0b3 81529c28 8153f3d4 8153f3c4 nt!
ExFreePool+0xd
f403fb34 f3c24583 81524750 81578008 815410e8 1394BUS!
Bus1394GetConfigurationInformation+0x905
f403fb74 f3c2c1c0 81541030 81578008 81541030 1394BUS!
Bus1394HandleDeviceRelations+0x6bf
f403fbf8 80424f7c 81541030 81578008 81541030 1394BUS!
Bus1394PnP+0x1048
f403fc10 8054a60a 00000000 8184d9a8 804d8864 nt!
IopfCallDriver+0x4f
f403fc3c 80434511 81541030 f403fc5c f403fcd0 nt!
IopSynchronousCall+0x101
f403fc84 8053f7a2 00000000 81850418 00000000 nt!
IopQueryDeviceRelations+0x14f
f403fcd4 8053edf7 81850418 f403fcf0 00000000 nt!
IopEnumerateDevice+0x198
f403fcfc 8043067c 81850400 00000001 00000000 nt!
IopBusCheck+0x87
f403fd40 8041c794 00000000 00000000 00000000 nt!
IopDeviceActionWorker+0x469
f403fda8 804aa09a 00000001 00000000 00000000 nt!
ExpWorkerThread+0x106
f403fddc 804c526a 8041c68e 00000001 00000000 nt!
PspSystemThreadStartup+0x54
00000000 00000000 00000000 00000000 00000000 nt!
KiThreadStartup+0x16


FOLLOWUP_IP:
1394BUS!Bus1394GetConfigurationInformation+905
f3c2d0b3 53 push ebx

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: 1394BUS!
Bus1394GetConfigurationInformation+905

MODULE_NAME: 1394BUS

IMAGE_NAME: 1394BUS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3e9264ab

STACK_COMMAND: kb

BUCKET_ID: 0xc2_7_Mdl _1394BUS!
Bus1394GetConfigurationInformation+905

Followup: MachineOwner
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top