I just started using CUV and I am getting the following errors that I
can’t explain. The first one seems to be an internal error within CUV
and the second may also be an internal CUV error.
The first error is when CUV first starts running. As you can see in the
output below, CUV has indicated that it had an internal error.
\Driver\vs03 running with CUV enabled
DO_DEVICE_INITIALIZING flag not cleared on DO 0xffbdaf10
CUV Internal Error – Pool Block not found?
CUV Internal Error – Pool Block not found?
Later when I unload my driver I get a verifier BSOD indicating that
there are 6 non-paged pool blocks still unfreed prior to the driver
unloading. However the tags are not tags from my driver and the callers
address is in pooltrak.cpp @ 368.
PoolAddress SizeInBytes Tag CallersAddress
ffbdadf0 0x00000038 CVPt f8c9921d
ffbbd4b8 0x00000038 CVPt f8c9921d
ffbc36f8 0x00000038 CVPt f8c9921d
ffbc7888 0x00000038 CVPt f8c9921d
ffbd6418 0x00000038 CVPt f8c9921d
819d9248 0x00000038 CVPt f8c9921d
0: kd> u f8c9921d
vso03!DDKExtPoolCreateEntry+0x2a
[d:\srvidx01\sdktools\ddk\ddk_ext\verifier\pooltrak.cpp @ 368]:
f8c9921d 807dff00 cmp byte ptr [ebp-0x1],0x0
f8c99221 8bd8 mov ebx,eax
f8c99223 be4cc8c9f8 mov esi,0xf8c9c84c
f8c99228 756d jnz vs03!DDKExtPoolCreateEntry+0xa4
(f8c99297)
f8c9922a 57 push edi
f8c9922b 56 push esi
f8c9922c e8abf5ffff call vs03!AcquireLListLock (f8c987dc)
f8c99231 8845fb mov [ebp-0x5],al
The operating system that I’m running on is Windows XP SP1. I’m using
Windows Server 2003 SP1 Beta DDK Build 3790.1218. Has anyone else seen
these problems or have any idea on what I can do to prevent them?
Hi,
Are you allocating memory in a driver tracked by CUV that is freed by
another driver (or the O/S) and/or vice-versa? If so, both the “Internal
Error” output and the bugcheck are known bugs in CUV stemming from its
inability to deal with cooperating drivers. I don’t think there’s anything
you can do currently to prevent them, but hopefully these will be fixed in a
future CUV release.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Whitman, Steve” wrote in message news:xxxxx@ntdev…
I just started using CUV and I am getting the following errors that I
can’t explain. The first one seems to be an internal error within CUV
and the second may also be an internal CUV error.
The first error is when CUV first starts running. As you can see in the
output below, CUV has indicated that it had an internal error.
\Driver\vs03 running with CUV enabled
DO_DEVICE_INITIALIZING flag not cleared on DO 0xffbdaf10
CUV Internal Error – Pool Block not found?
CUV Internal Error – Pool Block not found?
Later when I unload my driver I get a verifier BSOD indicating that
there are 6 non-paged pool blocks still unfreed prior to the driver
unloading. However the tags are not tags from my driver and the callers
address is in pooltrak.cpp @ 368.
PoolAddress SizeInBytes Tag CallersAddress
ffbdadf0 0x00000038 CVPt f8c9921d
ffbbd4b8 0x00000038 CVPt f8c9921d
ffbc36f8 0x00000038 CVPt f8c9921d
ffbc7888 0x00000038 CVPt f8c9921d
ffbd6418 0x00000038 CVPt f8c9921d
819d9248 0x00000038 CVPt f8c9921d
0: kd> u f8c9921d
vso03!DDKExtPoolCreateEntry+0x2a
[d:\srvidx01\sdktools\ddk\ddk_ext\verifier\pooltrak.cpp @ 368]:
f8c9921d 807dff00 cmp byte ptr [ebp-0x1],0x0
f8c99221 8bd8 mov ebx,eax
f8c99223 be4cc8c9f8 mov esi,0xf8c9c84c
f8c99228 756d jnz vs03!DDKExtPoolCreateEntry+0xa4
(f8c99297)
f8c9922a 57 push edi
f8c9922b 56 push esi
f8c9922c e8abf5ffff call vs03!AcquireLListLock (f8c987dc)
f8c99231 8845fb mov [ebp-0x5],al
The operating system that I’m running on is Windows XP SP1. I’m using
Windows Server 2003 SP1 Beta DDK Build 3790.1218. Has anyone else seen
these problems or have any idea on what I can do to prevent them?
- Steve -
Hi Scott,
Thanks for this information. The driver does pass memory back to the
O/S so that explains this problem.
It’s too bad that the BSOD occurs because will prevent me from using CUV
for more than an occasional test run since my device is a USB device and
unplugging it which causing the driver to unload is something that
occurs frequently.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Wednesday, October 06, 2004 10:05 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] CUV Problem
Hi,
Are you allocating memory in a driver tracked by CUV that is freed by
another driver (or the O/S) and/or vice-versa? If so, both the "Internal
Error" output and the bugcheck are known bugs in CUV stemming from its
inability to deal with cooperating drivers. I don’t think there’s
anything
you can do currently to prevent them, but hopefully these will be fixed
in a
future CUV release.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Whitman, Steve” wrote in message
news:xxxxx@ntdev…
I just started using CUV and I am getting the following errors that I
can’t explain. The first one seems to be an internal error within CUV
and the second may also be an internal CUV error.
The first error is when CUV first starts running. As you can see in the
output below, CUV has indicated that it had an internal error.
\Driver\vs03 running with CUV enabled
DO_DEVICE_INITIALIZING flag not cleared on DO 0xffbdaf10
CUV Internal Error – Pool Block not found?
CUV Internal Error – Pool Block not found?
Later when I unload my driver I get a verifier BSOD indicating that
there are 6 non-paged pool blocks still unfreed prior to the driver
unloading. However the tags are not tags from my driver and the callers
address is in pooltrak.cpp @ 368.
PoolAddress SizeInBytes Tag CallersAddress
ffbdadf0 0x00000038 CVPt f8c9921d
ffbbd4b8 0x00000038 CVPt f8c9921d
ffbc36f8 0x00000038 CVPt f8c9921d
ffbc7888 0x00000038 CVPt f8c9921d
ffbd6418 0x00000038 CVPt f8c9921d
819d9248 0x00000038 CVPt f8c9921d
0: kd> u f8c9921d
vso03!DDKExtPoolCreateEntry+0x2a
[d:\srvidx01\sdktools\ddk\ddk_ext\verifier\pooltrak.cpp @ 368]:
f8c9921d 807dff00 cmp byte ptr [ebp-0x1],0x0
f8c99221 8bd8 mov ebx,eax
f8c99223 be4cc8c9f8 mov esi,0xf8c9c84c
f8c99228 756d jnz vs03!DDKExtPoolCreateEntry+0xa4
(f8c99297)
f8c9922a 57 push edi
f8c9922b 56 push esi
f8c9922c e8abf5ffff call vs03!AcquireLListLock (f8c987dc)
f8c99231 8845fb mov [ebp-0x5],al
The operating system that I’m running on is Windows XP SP1. I’m using
Windows Server 2003 SP1 Beta DDK Build 3790.1218. Has anyone else seen
these problems or have any idea on what I can do to prevent them?
- Steve -
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cognex.com
To unsubscribe send a blank email to xxxxx@lists.osr.com