Bluescreens
From Helpful
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
Contents |
STOP 7E
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
A bluescreen mentioning STOP 0x0000007E, and a driver filename.
what and why
One reason is a driver that was meant for a different platform, or buggy in some way(verify).
In some cases, windows may automatically install the offending driver.
Testing and solutions
Generally, the best way to avoid the error is to uninstall the driver (you may have to do so in safe mode).
You may want to try other drivers.
If windows automatically installs this failing driver, you may want to remove the according hardware to narrow down whether this is whether this is the problem. (You could try to remove the specific driver and its install information.)
STOP 7B
What and why
STOP 0x0000007B means Inaccessible boot device.
As MS puts it, "The "Stop 7B" error occurs when your configuration is missing a component that is required to boot your device. Examples of these components include the PCI bus and the IDE controller." [1]
It seems to occur most often in situations where a motherboard is replaced, since this means replacing the IDE controller with one windows is not yet aware of.
It will give you a 7B bluescreen if this means it can't figure out how to get to the boot device (the one which stores the windows system drive, presumably).
Possible solutions
If all you did to cause this is move your windows drive from one working controller to another, you can likely solve this by booting the old way, changing the controller driver to a generic one for the one boot (I'm not sure, though - I have no idea how the windows boot process works)
Clean reinstall
A full reinstall always works, but backing up data and reinstalling programs obviously takes time.
In-place update (usually simplest)
If you just replaced a faulty motherboard, you likely just want to replace the drive controller drivers.
An in-place update is probably the most generic method. It's fairly simple to do, a sure way to get the basic drivers installed, and doesn't mean reinstalling windows to do so.
You get back the same windows installation after you're done; an in-place update mostly replaces replaces some of the more basic system files in your current installation, and is actually a fairly simple operation (takes perhaps fifteen minutes).
Read Windows in-place update for some more details.
Anticipate
One proposed solution suggest you replace the drivers with generic ones before the change (or just to change the driver to the generic one, for IDE "Standard Dual-Channel PCI IDE Controller"), but that requires a running system, i.e. the original hardware or identical, which is a pretty pointless suggestion if the motherboard is broken and you're not in a big company with identical hardware just lying around.
Unsorted
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
There is also a suggestion that includes not using UDMA (one possible reason is having a controller that has a newer DMA mode that the driver didn't know about, but the BIOS enables/uses because it and the drive can use it) by either forcing PIO mode or using a 40-pin cable. This did not work for me, so it may be random baloney, or maybe it only works for revisions of the same controller chipset.
See also
STOP F4 and 77
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
STOP 0x000000F4 (CRITICAL_OBJECT_TERMINATION) STOP 0x00000077 (KERNEL_STACK_INPAGE_ERROR)
What and why
These seem to usually be caused by failed page file operations, and can be triggered by anything that can stop a page file operation from working, usually some hardware trouble.
These bluescreens often point to one of:
- any reason a hard drive operation can fail or a drive can fail temporarily or under certain conditions, such as a bad cable or badly seated cable, an overheating drive, a marginal power supply, or whatnot.
- a failing hard drive (check SMART info, and do a drive check that tries to locate bad sectors)
- motherboard / hard drive combinations that don't like each other
- bad drivers (upgrading or downgrading may help)
See also
STOP 0A
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
STOP 0x0000000A IRQL Not Less or Equal
What and why
A memory access related driver error, which can be caused by various things, including:
- a specific badly behaving driver (likely if one is mentioned)
- regularly video card drivers (try updating the drivers, or if you have the latest, using a slightly older version)
- Things behaving badly when under strain (CPU, GPU, or memory, particularly when overclocked but not thoroughly strain tested)
- other reasons
Testing and solutions
The time it occurs can give a hint. For example,
If it occurs only while gaming, it's possibly a video driver or, or video card overheating issue. You could run memtest86+[2] or other strain tests to see whether this is reproducable under strain.
If it occured fairly quickly after an update, it's likely a bad driver.
See also
STOP C000021A
| This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine. |
You'll see blue text mode mentioning:
Autochk program not found skipping AUTOCHECK
followed by
STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly
with a status of
0xc000003a (0x00000000 0x00000000).
Apparently related to partition table (changes), seemingly commonly to incorrect changes to the partition type of the windows installation.
