By Matt Hartley
No doubt about it, folks, “stop codes” are pain in the butt. Now before
you go postal on the PC throwing these up at you, remember that they are
there to help you troubleshoot issues that your PC is having. When a stop
code appears, this indicates that Windows XP/2000 has actually stopped
loading for some reason and needs your immediate attention. These errors can
be caused for a variety of reasons as we will examine below.
Actual Stop Codes
0×00000009: IRQL_NOT_GREATER_OR_EQUAL
This is one of my favorites. Its Common cause can be from a new driver being
installed that simply did not take. Resolution is to try booting into Safe
Mode and using System Restore (Win XP). On 2000, try “last known good
config.”
0×0000001A: MEMORY_MANAGEMENT
If you are seeing this error, you may be dealing with a memory related
issue. If you are installing the OS for the first time, check to make sure
that you have sufficient RAM installed on that PC. If this just sprang up
out of nowhere, try rebooting and using the “last config known to be good”
option from the boot menu.
0×00000050: PAGE_FAULT_IN_NONPAGED_AREA
See if the memory on the troubled PC has gone bad over time. This can
happen, you know - it is not that unheard of to have a stick of RAM go
“noses up,” although, granted, it is rare. This error can also reflect
issues with the L2 RAM cache and even video RAM from your video card.
Resolutions to this can range from swapping memory to trying another video
card for troubleshooting purposes.
A huge number of stop codes remain, but the previous are without a doubt
the most common and, quite frankly, the most annoying. So when you are
confronted with these blue paged foes, don’t panic. Just boot up your second
PC and head over to Google. With a little time and research, these errors
can be outwitted. As hard as it may be to accept, the idea behind the blue
screen of death is to stop your PC from becoming damaged while providing you
with pertinent troubleshooting information.
0 Responses to “108559084599185562”