[offtopic] submit a bug

NTDEV
1

Hello,

Sorry I’m offtopic, and I want to know how to submit a bug to MS, because there is a bug in Windows OS kernel.

I post a topic recently at the BSOD:
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (Appears to Be On
That Was stack unwound)
Arg2: f0b72adc, IOSB address
Arg3: 00000000, IRP address
Arg4: 00000000

I’m formal, I read the MSDN documentation, it is Windows that is at stake!
I gladly send my file. PDB and the minidump. Dmp to MS;

this bug will never be resolved.

Excuse me for the inconvenience.

2

xxxxx@sivaller.no-ip.org wrote:

Sorry I’m offtopic, and I want to know how to submit a bug to MS, because there is a bug in Windows OS kernel.

I post a topic recently at the BSOD:
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (Appears to Be On
That Was stack unwound)
Arg2: f0b72adc, IOSB address
Arg3: 00000000, IRP address
Arg4: 00000000

I’m formal, I read the MSDN documentation, it is Windows that is at stake!
I gladly send my file. PDB and the minidump. Dmp to MS;

Although it is not impossible, it is extremely unlikely that this is a
kernel bug. The implication here is that you (or someone) called
IoCompleteRequest and passed a NULL pointer for the IRP. Show us the
whole !analyze -v, and the stack trace might prove revealing.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

I would place the probability at 99.9999% that this is your bug not
Windows. This is a classic NULL pointer situation, as this group has
said for the last 4 days.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@sivaller.no-ip.org” wrote in
message news:xxxxx@ntdev:

> Hello,
>
> Sorry I’m offtopic, and I want to know how to submit a bug to MS, because there is a bug in Windows OS kernel.
>
> I post a topic recently at the BSOD:
> DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
> The IO manager has caught a misbehaving driver.
> Arguments:
> Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (Appears to Be On
> That Was stack unwound)
> Arg2: f0b72adc, IOSB address
> Arg3: 00000000, IRP address
> Arg4: 00000000
>
> I’m formal, I read the MSDN documentation, it is Windows that is at stake!
> I gladly send my file. PDB and the minidump. Dmp to MS;
>
> this bug will never be resolved.
>
> Excuse me for the inconvenience.

4

i moved IOCTL IOCTL_DISK_MEDIA_REMOVAL and IOCTL_STORAGE_MEDIA_REMOVAL from thread into
my base function DrvDispatch , it’s OK !
No more BSOD! Driver Verifier OK in Windows XP Os

BY CONS if my driver is attached since Driver Verifier in OS Windows Seven: system freeze when windows access to my virtual RAW disk (ntfs,fat,fat32…)
and I would like to understand why?