BSOD

Have an XP machine that blue screens every couple days.  With the following codes:
IRQL_NOT_LESS_OR_EQUAL
STOP: 0x0000000A (0x00000004, 0x0000001C, 0x00000001, 0x804E2058)

Any ideas what could be causing this behavior?
hardwyreAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LeeTutorretiredCommented:
Take a look at the following web page,

http://aumha.org/win5/kbestop.htm

which is presented using frames.  Click on the error code (0A) in the left pane of the page, which is a link to the following quotation:

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Troubleshooting Stop 0x0A Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
Stop 0x0000000A Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Partial List of Driver Error Codes That the Driver Verifier Tool Uses to Report Problems {KB 315252} Win XP
Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
Fatal System Error When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4) error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)

You should go to the actual page in order to read the links given in the quotation above.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WestCoastJohnCommented:
If it is related to a driver, it will usually provide the name of the file that has the problem, at the bottom of the BSOD. Does it do this for you?

John Jennings
MCP,MCDST,MCITP,MCTS
0
JeremySBrownCommented:
Here's a link that explains what can be causing the BSOD.
http://support.microsoft.com/kb/314063

Do you get the the BOSD in Safe Mode?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

optomaCommented:
could you attach some of the recent minidump files and rename them to .txt to upload. located at C:\WINDOWS\Minidump
0
JeremySBrownCommented:
Just realizing that LeeTutor posted a link that explains what might be causing the BOSD...LeeTutor's link provides...I think great information...
0
DatedmanCommented:
Try this: run VERIFIER (built-in program) and take the defaults.  Wait for BSOD, should show more information.  Or you may get some information before BSOD.  

BTW there is some overhead involved so turn it back off after you find the problem.
0
nobusCommented:
can you post the minidump  for more info ? rename it to .txt  
0
LeeTutorretiredCommented:
hardwyre, any feedback?
0
QEMS2Commented:
Do you have an ati graphics card in the machine? This is usually the error that comes up when the card is showing sings of being faulty, my mate had it for months. The only way to correct it was to get a new card, re-install does not correct the issue.
Let me know
0
hardwyreAuthor Commented:
swapped memory, problem not solved
pulled video card, problem not solved
attempted reinstallation of OS on new HD and installation hung on copying files, multiple times.  

machine is possessed..
0
DatedmanCommented:
never tried VERIFIER?

any chance you're overheating?  

Did you check the event log?
0
nobusCommented:
again :  can you post the minidump  for more info ? rename it to .txt  
0
QEMS2Commented:
Do you have any ati drivers installed at all?
0
WestCoastJohnCommented:
If your OS installation is screwing up:
#1 make sure you have third-party drivers ready for any sata/raid controllers.
#2 burn / acquire a new windows installation CD, its possible your disc (or even your CD drive) is going bad, which will cause installation issues.

John Jennings
MCP,MCDST,MCITP,MCTS
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.