microsoftne
In Runtime
- Messages
- 469
Parameter Validation
All spin lock, IRQL, and pool allocation calls the driver makes receive automatic parameter validation. This means that checks are made to ensure the following things:
A raised IRQL really is a raised IRQL (the current IRQL is less than the target IRQL).
A lower IRQL really is a lower IRQL.
Double release of a spin lock.
Spin lock acquisitions/releases are made at the proper IRQL.
Paged pool allocations/frees are made at the correct IRQL (APC_LEVEL or below).
Non-paged pool allocations/frees are made at the correct IRQL (DISPATCH_LEVEL or below).
No random (uninitialized) values are specified to these application programming interfaces (APIs).
Pool Allocation Injection Failures
Pool allocations that are not marked MUST_SUCCEED by the driver can be randomly failed to ensure the driver can correctly handle a low memory situation.
Pool Being Freed
All pool being freed is examined to ensure no pending timers are inside the pool allocation as these cases would cause extremely hard to track down system crashes.
Pool Leakage Detection
All of the driver's pool allocations are automatically tracked. At driver unload time, a bug check occurs if any of the allocations are not freed. You can then use the !verifier 3 kernel-debugger command to show all the allocations that are not freed. You can also use this command before unloading to view the outstanding allocations the driver has at any point in time.
Driver Unload Checking
Driver unload checking is performed to catch drivers that unload and do not clean up resources used (which increases the possibility of a system bug check shortly after the driver unloads). Resources that the driver may not delete include look-aside lists, pending deferred procedure calls (DPCs), worker threads, queues, timers, and other resources.
I/O Verifier
If you turn on the I/O Verifier flag using the Verifier tool or the VerifyDriverLevel registry key (for more information, refer to the "Enabling Driver Verification" section of this article), some I/O Manager verifications are turned on. This includes:
All IRPS allocated through IoAllocateIrp are allocated from special pool.
Checks are made in IoCallDriver, IoCompleteRequest, and IoFreeIrp to catch driver error messages.
All I/O Verifier failures bug check with the code DRIVER_VERIFIER_IOMANAGER_VIOLATION (0xC9).
All this means is either a bad Video Card/or bad video card driver............try unistalling and reinstalling the drivers if that doesn't work it is the video card.....
All spin lock, IRQL, and pool allocation calls the driver makes receive automatic parameter validation. This means that checks are made to ensure the following things:
A raised IRQL really is a raised IRQL (the current IRQL is less than the target IRQL).
A lower IRQL really is a lower IRQL.
Double release of a spin lock.
Spin lock acquisitions/releases are made at the proper IRQL.
Paged pool allocations/frees are made at the correct IRQL (APC_LEVEL or below).
Non-paged pool allocations/frees are made at the correct IRQL (DISPATCH_LEVEL or below).
No random (uninitialized) values are specified to these application programming interfaces (APIs).
Pool Allocation Injection Failures
Pool allocations that are not marked MUST_SUCCEED by the driver can be randomly failed to ensure the driver can correctly handle a low memory situation.
Pool Being Freed
All pool being freed is examined to ensure no pending timers are inside the pool allocation as these cases would cause extremely hard to track down system crashes.
Pool Leakage Detection
All of the driver's pool allocations are automatically tracked. At driver unload time, a bug check occurs if any of the allocations are not freed. You can then use the !verifier 3 kernel-debugger command to show all the allocations that are not freed. You can also use this command before unloading to view the outstanding allocations the driver has at any point in time.
Driver Unload Checking
Driver unload checking is performed to catch drivers that unload and do not clean up resources used (which increases the possibility of a system bug check shortly after the driver unloads). Resources that the driver may not delete include look-aside lists, pending deferred procedure calls (DPCs), worker threads, queues, timers, and other resources.
I/O Verifier
If you turn on the I/O Verifier flag using the Verifier tool or the VerifyDriverLevel registry key (for more information, refer to the "Enabling Driver Verification" section of this article), some I/O Manager verifications are turned on. This includes:
All IRPS allocated through IoAllocateIrp are allocated from special pool.
Checks are made in IoCallDriver, IoCompleteRequest, and IoFreeIrp to catch driver error messages.
All I/O Verifier failures bug check with the code DRIVER_VERIFIER_IOMANAGER_VIOLATION (0xC9).
All this means is either a bad Video Card/or bad video card driver............try unistalling and reinstalling the drivers if that doesn't work it is the video card.....