The DMA Subsystem has detected an illegal...

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.

A some of the most popular driver download sites:

• CPU and Chipset Drivers: AMD, Intel, Via
• Video Drivers: ATI, Intel, Nvida
• Computer and other hardware manufacturers

Install the latest Windows software updates. Don't forget to check for non-critical updates too!

To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).

For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.

For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.

If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.

For removal of an application (Windows 7 & Vista):

1. Click on Start, Control Panel, then Programs and Features.
2. Select the software to uninstall and select Uninstall.

For removal of an application (Windows XP):

1. Click on Start, Control Panel, then Add or Remove Programs.
2. Select the software to uninstall and select Remove.

To disable a driver:

1. Bring up the system information dialog:

   On the keyboard, press the Windows key + Pause/Break.

      or

   Select Start, right click Computer and on the drop-down, select Properties.

2. Click on the left side option Advanced system settings (7/Vista only).
3. In System Properties, select the Hardware tab, then click on Device Manager button.
4. Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
5. Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
6. Click OK to exit, then close the Device Manager and other previously opened dialogs.

Check out what others say about this issue and review or add your own comments and solutions!

This covers all Driver Verifier DMA Verification violations when the Driver Verifier is run.

After the Stop code will be a hex values: {Parameter 1}.

Parameter 1 specifies the cause of the issue.

0x00000000	This code can represent two kinds of errors: 1. The driver tried to flush too many bytes to the end of the map register file. The number of bytes permitted and the number of bytes attempted are displayed. 2. Windows has run out of contiguous map registers. The number of map registers needed and the largest block of contiguous map registers is displayed.
0x00000001	The performance counter has decreased. The old and new values of the counter are displayed.
0x00000002	The performance counter has increased too fast. The counter value is displayed in the debugger.
0x00000003	The driver freed too many DMA common buffers. Usually this means it freed the same buffer two times.
0x00000004	The driver freed too many DMA adapter channels. Usually this means it freed the same adapter channel two times.
0x00000005	The driver freed too many DMA map registers. Usually this means it freed the same map register two times. The number of active map registers is displayed.
0x00000006	The driver freed too many DMA scatter/gather lists. Usually this means it freed the same scatter/gather list two times. The number of lists allocated and the number of lists freed is displayed.
0x00000007	The driver tried to release the adapter without first freeing all its common buffers. The adapter address and the number of remaining buffers is displayed.
0x00000008	The driver tried to release the adapter without first freeing all adapter channels, common buffers, or scatter/gather lists. The adapter address and the number of remaining items is displayed.
0x00000009	The driver tried to release the adapter without first freeing all map registers. The adapter address and the number of remaining map registers is displayed.
0x0000000A	The driver tried to release the adapter without first freeing all its scatter/gather lists. The adapter address and the number of remaining scatter/gather lists is displayed.
0x0000000B	HV_TOO_MANY_ADAPTER_CHANNELSThe driver has allocated too many adapter channels at the same time. . (Only one adapter channel is permitted per adapter.)
0x0000000C	The driver tried to allocate too many map registers at the same time. The number requested and the number allowed are displayed.
0x0000000D	The driver did not flush its adapter buffers. The number of bytes that the driver tried to map and the maximum number of bytes allowed are displayed.
0x0000000E	The driver tried a DMA transfer without locking the buffer. The buffer in question was in paged memory. The address of the MDL is displayed.
0x0000000F	The driver or the hardware wrote outside its allocated DMA buffer. The nature of the error (overrun or underrun) is displayed, as well as the relevant addresses.
0x00000010	The driver tried to free its map registers while some were still mapped. The number of map registers still mapped is displayed.
0x00000011	The driver has too many outstanding reference counts for the adapter. The number of reference counts and the adapter address are displayed.
0x00000013	The driver called a DMA routine at an improper IRQL. The required IRQL and the actual IRQL are displayed.
0x00000014	The driver called a DMA routine at an improper IRQL. The required IRQL and the actual IRQL are displayed.
0x00000015	The driver tried to allocate too many map registers. The number requested and the number allowed are displayed.
0x00000016	The driver tried to flush a buffer that is not mapped. The address of the buffer is displayed.
0x00000018	The driver tried a DMA operation by using an adapter that was already released and no longer exists. The adapter address is displayed.
0x00000019	The driver passed a null DMA_ADAPTER value to a HAL routine.
0x0000001B	The driver passed an address and MDL to a HAL routine. However, this address is not within the bounds of this MDL. The address passed and the address of the MDL are displayed.
0x0000001D	The driver tried to map an address range that was already mapped. The address range and the current mapping for that range are displayed.
0x0000001E	The driver called HalGetAdapter. This function is obsolete - you must use IoGetDmaAdapter instead.
0x0000001F	HV_BAD_MDLThe driver referenced an invalid system address - either before the first MDL, or after the end of the first MDL, or by using a transfer length that is longer than the MDL buffer and crosses a page boundary within the MDL. . Either the invalid address and the first MDL address, or the MDL address and the extra transfer length are displayed.
0x00000020	The driver tried to flush a map register that hasn't been mapped. The map register base, flushing address, and MDL are displayed.
0x00000021	The driver tried to map a zero-length buffer for transfer.