Member Avatar for NILISHERE

during installation blue screen came up with this message and a stop code
stop: 0x0000000A (0x82563b74, 0x0000001c, 0x00000001,0x804E639B)
please help me........

  • 4 Contributors
  • 5 Replies
  • 245 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by Shadowsedge

Dani AI

Generated

The OP reports a STOP 0x0000000A (IRQL_NOT_LESS_OR_EQUAL). That bugcheck means a kernel-mode component tried to access pageable or invalid memory at too‑high an IRQL — in plain terms, a low‑level driver or kernel code attempted an illegal memory access. This is a hardware/driver symptom, not a generic “Windows bug.” (learn.microsoft.com)

The thread already covers basic hardware/media checks; to move from general to specific, concentrate on mass‑storage and chipset mismatches. On many newer boards Windows XP setup will crash if the SATA controller is in AHCI/RAID mode and XP has no matching driver. Two practical choices are available: change the BIOS SATA mode to IDE/Compatibility (if present) or supply the controller driver during setup using the classic F6 OEM driver method (XP expects a floppy) — or slipstream the driver into the XP install media if no floppy is available. (msi.com)

If changing BIOS isn’t possible, slipstream the vendor’s “F6” driver files (INF, SYS, TXTSETUP.OEM) into an SP3 XP image with a tool like nLite and rebuild the installer; this fixes the majority of installer‑stage crashes tied to storage/chipset drivers. Use the vendor download page for the exact F6 driver package (extract the floppy files rather than running the installer). (terabyteunlimited.com)

If the crash persists after supplying the correct storage/chipset drivers, capture the Windows minidump and analyze it with WinDbg (!analyze -v). The dump/stack will usually point to the offending SYS file or driver call; parameter values in the 0xA message help triage NULL vs. pageable vs. execute/write faults. If analysis names a third‑party driver, update or remove it; otherwise consider a BIOS update or different install media. Microsoft’s debugger docs and the 0xA reference are the authoritative guides for this step. (learn.microsoft.com)

Recommended Answers

All 5 Replies

Member Avatar for Shadowsedge

No clue what that means, your going to have to post more information because that could mean anything.
example:
what were you installing?
Can you restart the machine (laptop or desktop)
anything and everything would help.

Member Avatar for NILISHERE

i was installing windows xp. and even after restarting the comp. the installation comes to certain level and agin goes to blue screen showing the same message.

Member Avatar for Suspishio

What upgrade are you performing (I assume the installation is an upgrade)?

Have you Googled 0x0000000A, because there's a Microsoft KB article on this.

Member Avatar for caperjack

http://support.microsoft.com/?kbid=314063&sd=RMVP

remove all PCI addin cards ,like nic card and modem or sound ,and if you have video card ,and also have onboard video .remove the video card and use the onboard ,and try the install again

Member Avatar for Shadowsedge

Hmm, still can't be sure but follow caperjacks advice and only have the minimal hardware to do a clean install. My guess is it might be
1. A scratch on the CD - find another CD or fix scratch
2. Bad RAM - If you have multiple sticks, try just using one. Memtest would be a good tool to use to check the RAM and see if it bad.
3a. Bad hard drive - Find the maker of the hard drive and get their hard drive tester and test it.
3b. Try using a formatting program like "drive scrubber" to wipe the hard drive completely. 1 pass should be enough.

These are just some suggestions as I really still have no clue as to why it's happening. Still need more information to make a better diagnosis.

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.