|
|
 |
|
|
|
|
|
|
Description |
|
|
|
|
|
The IoBuildPartialMdl routine maps a portion of a buffer described by one memory descriptor list (MDL) into another MDL. This error is likely caused by a software bug in the program which used incorrect parameters when calling the IoBuildPartialMdl routine. This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
|
|
|
|
|
|
Sample Screen |
|
|
|
|
|
A problem has been detected and Windows has been shut down to prevent damage to your computer.
IoBuildPartialMdl was called with a virtual address range outside the range of the source MDL. Technical Information:
*** STOP: 0x0000012E
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance. |
|
|
|
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown. |
|
|
|
|
|
Key Facts |
|
|
|
|
|
Full Title |
|
IoBuildPartialMdl was called with a virtual address range outside the range of the source MDL.
|
Stop Code |
|
0x0000012E
|
Type |
|
Fatal
|
|
Windows |
|
7, 8
|
Vendor |
|
Microsoft Corporation |
|
|
|
|
|
|
Solutions and Fixes |
|
|
|
|
|
Uninstall the Last Install |
|
|
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 8+)
- Press the Windows Key and X together, then Control Panel, then Programs and Features.
- Select the software to uninstall and select Uninstall.
For removal of an application (Windows 7 & Vista):
- Click on Start, Control Panel, then Programs and Features.
- Select the software to uninstall and select Uninstall.
For removal of an application (Windows XP):
- Click on Start, Control Panel, then Add or Remove Programs.
- Select the software to uninstall and select Remove.
To disable a driver:
- 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.
- Click on the left side option Advanced system settings (7/Vista only).
- In System Properties, select the Hardware tab, then click on Device Manager button.
- Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
- 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.
- Click OK to exit, then close the Device Manager and other previously opened dialogs.
|
|
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
You may have a defective memory. This is even more likely if it only occurs when the system is cold or hot, but not all the time. Use a memory tester to confirm if it is defective or if you have spare memory, try replacement.
Windows 7 and Vista include a Memory Test program when booting from the Windows Installation DVD. Step-by-step instructions with screen shots are available at Using System Restore on 7/Vista/2008 as part of System Recovery.
Several software products that also provide memory and video diagnostics includes Fix-It Utilities Professional and SystemSuite Professional. Other diagnostic products include Eurosoft's PC Check and Iolo's System Mechanic.
Additional Memory Solutions:
- Confirm all the memory is of the same type and speed. Many motherboards only work correctly when the memory is installed with matched sets and matched speeds.
- If you added or changed your memory just before this problem occurred, try reverting to the prior memory configuration to confirm it's the source of the problem.
- Check that the memory is fully seated in the sockets. Memory sockets often have side latches that need to be upright to indicate the memory is correctly locked in place.
- Confirm the memory resides in the correct slots on the motherboard. You'll need to refer to the motherboard manual to confirm this. There is little consistency, even within a single vendor. Some systems require that memory is installed as matched pairs, but not always adjacent to each other!
- It's also possible the memory problem is on the video card, as they often contain additional memory. The video card should be tested and/or try a different video card to see if the problem goes away.
|
|
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
Also see our list of common Fatal Error Solutions. |
|
|
|
|
|
Forum Help |
|
|
|
|
|
 |
Check out what others say about this issue and review or add your own comments and solutions!
Go to Forums on topic. |
|
|
|
|
|
|
Vendor Summary |
|
|
|
|
|
|
|
|
|
|
|
|
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues. |
|
|
|
|
|
Research this Issue |
|
|
|
|
|
Getting search results...
|
|
|
|
|
|
Notes |
|
|
|
|
|
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it. |
|
|
|
|
|
|
 |
 |
 |
| | |
|
|