Post by tomyn on Nov 28, 2010 19:48:30 GMT
Hello,
I run my software SATlive using the Aplicaton Verifier Tool from microsoft. It reports the following error, which occurs during the start/initialisation of the ASIO driver.
<avrf:logEntry Time="2010-11-28 : 19:00:05" LayerName="InputOutput" StopCode="0x803" Severity="Error">
<avrf:message>An I/O status block is reused while associated I/O request is still pending.</avrf:message>
<avrf:parameter1>90ddbc0 - Address of the I/O status block.</avrf:parameter1>
<avrf:parameter2>d7c - Original thread that issued the I/O.</avrf:parameter2>
<avrf:parameter3>c166f7c - Stack Trace when the I/O was issued.</avrf:parameter3>
<avrf:parameter4>0 - Not Used.</avrf:parameter4>
- <avrf:stackTrace>
<avrf:trace>vfbasics!AVrfpCheckIoStatusBlock+58 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 2579)</avrf:trace>
<avrf:trace>vfbasics!AVrfpPreProcessIoRequest+104 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 1095)</avrf:trace>
<avrf:trace>vfbasics!AVrfpNtDeviceIoControlFile+e7 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 3358)</avrf:trace>
<avrf:trace>KERNEL32!DeviceIoControl+99 ( @ 0)</avrf:trace>
<avrf:trace>asio4all!+90d6903 ( @ 0)</avrf:trace>
</avrf:stackTrace>
</avrf:logEntry>
This is what the helpfile says to this error message:
An I/O status block is reused while associated I/O request is still pending.
Probable Cause
This stop is generated if the application reused an I/O status block while an I/O request using that I/O status block is still pending.
Information Displayed by Application Verifier
Parameter 1 – Address of the I/O status block.
Parameter 2 – Original thread that issued the I/O.
Parameter 3 – Stack Trace when the I/O was issued.
Parameter 4 – Not Used.
Additional Information:
Verifier stop code 803.
To debug this stop:
dps parameter3 to display the stack trace when the original I/O was issued. Parameter1 indicates the address used in the I/O and parameter2 the thread that issued the I/O.
Without the verifier the software seems to work perfect, so I'm not sure if this is a bug which needs fixing.
Tomy
I run my software SATlive using the Aplicaton Verifier Tool from microsoft. It reports the following error, which occurs during the start/initialisation of the ASIO driver.
<avrf:logEntry Time="2010-11-28 : 19:00:05" LayerName="InputOutput" StopCode="0x803" Severity="Error">
<avrf:message>An I/O status block is reused while associated I/O request is still pending.</avrf:message>
<avrf:parameter1>90ddbc0 - Address of the I/O status block.</avrf:parameter1>
<avrf:parameter2>d7c - Original thread that issued the I/O.</avrf:parameter2>
<avrf:parameter3>c166f7c - Stack Trace when the I/O was issued.</avrf:parameter3>
<avrf:parameter4>0 - Not Used.</avrf:parameter4>
- <avrf:stackTrace>
<avrf:trace>vfbasics!AVrfpCheckIoStatusBlock+58 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 2579)</avrf:trace>
<avrf:trace>vfbasics!AVrfpPreProcessIoRequest+104 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 1095)</avrf:trace>
<avrf:trace>vfbasics!AVrfpNtDeviceIoControlFile+e7 (d:\avrf\source\base\avrf\vrfcommon\iocheck.c @ 3358)</avrf:trace>
<avrf:trace>KERNEL32!DeviceIoControl+99 ( @ 0)</avrf:trace>
<avrf:trace>asio4all!+90d6903 ( @ 0)</avrf:trace>
</avrf:stackTrace>
</avrf:logEntry>
This is what the helpfile says to this error message:
An I/O status block is reused while associated I/O request is still pending.
Probable Cause
This stop is generated if the application reused an I/O status block while an I/O request using that I/O status block is still pending.
Information Displayed by Application Verifier
Parameter 1 – Address of the I/O status block.
Parameter 2 – Original thread that issued the I/O.
Parameter 3 – Stack Trace when the I/O was issued.
Parameter 4 – Not Used.
Additional Information:
Verifier stop code 803.
To debug this stop:
dps parameter3 to display the stack trace when the original I/O was issued. Parameter1 indicates the address used in the I/O and parameter2 the thread that issued the I/O.
Without the verifier the software seems to work perfect, so I'm not sure if this is a bug which needs fixing.
Tomy