Member Avatar for fitts

Hello everyone,

I've encountered a very nasty problem with my computer and I do not know where else to turn but here, hopefully someone can help me out.

Few weeks ago, I noticed that my computer started taking awfully long to shut down (approx 5 minutes). Since then I scanned my system upside down with NOD32 and Ewido Spyware, everything seemed clean.

However, today I install some new Windows updates and everything went to hell.

Basically, whenever I start up my computer, it shows me the awful blue screen that says the following:

IRQL_NOT_LET_OR_EQUAL

Technical Information:

Stop ***: 0x0000000A (0x0A830017, 0x0000000, 0x00000000, 0x804E87FB)

-----

Does anybody have any idea what it could be? I disabled everything on my start up but it did not do me any good. The only way I can use the computer if I log in via the safe mode.

Thank you very much in advance for your help. I'm looking forward to your replies.

Fitts

  • 3 Contributors
  • 2 Replies
  • 116 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by chunkmartinez

Dani AI

Generated

This looks like a classic IRQL/driver or memory problem where Safe Mode works but normal boot fails. As pointed to Microsoft documentation and as suggested a repair, try targeted diagnostics before doing a repair install — it may save time and your installed programs.

First, collect the crash dumps (C:\Windows\Minidump). Use a dump viewer (BlueScreenView) or WinDbg to map the faulting address to a module; that will tell whether a third‑party driver is at fault. In WinDbg set the symbol path and ask it to list the nearest symbol to the crash address, for example:

.sympath SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
.reload
ln 0x804E87FB

If the address maps to a non-Microsoft driver, uninstall or roll that driver back from Safe Mode.

Also run hardware and file-system checks. Faulty RAM or disk corruption often causes 0x0A errors. Test RAM with memtest86 (run multiple passes) and try booting with one stick at a time. From Safe Mode or Recovery Console run:

chkdsk /r
sfc /scannow

Note: SFC on XP may require the original CD.

For software isolation use msconfig to disable all non-Microsoft services, try “Last Known Good Configuration” at boot, or perform a System Restore to a point before the updates. Uninstall recent drivers or updates from Safe Mode if the dump points to them. Back up important data before doing a repair install or reformat. If these steps don’t show the offending module, post the minidump analysis (module name and version) — that information will pinpoint whether it’s a driver, antivirus filter, or kernel bug and guide the next action.

Recommended Answers

All 2 Replies

Member Avatar for Boldgamer

This is the info that Microsoft gives for that stop message. Look at the section that reads "A Stop 0x0A error after Windows XP is already installed".

Have you recently added new hardware or updated any of your drivers?

Member Avatar for chunkmartinez

ahh yes that crazy blue screen of death hua. well anyway about your problem. I ask, what prevents you from booting up normally, is it the blue screen? You know what, besides fixing, i would suggest to just simply insert your OS RESTO disk, or what ever you have, and siply repair the installation.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.