p8ntballsnyper said:
Ok I just got a new computer and I assemblyed it and had to get a new HDD because the other one was bad but yeah anyways here is my problem. I get all the way through the partioning of my SATA HDD and I get to where xp installs devises and blah blue screen of death giving me a IRQL_LESS_THAN_OR_EQUAL error. I have no idea what to do can anyone help with my problem. By the way its windows xp professional OEM.
any advise is helpful.
the error code is 0x0000000A (0x03F00406, 0x00000002, 0x00000000, 0x804f8c38)
I found an article that relates specifically to this...
http://support.microsoft.com/kb/q130802/
General Information on STOP 0x0000000A
View products that this article applies to.
Article ID : 130802
Last Review : November 21, 2003
Revision : 3.0
This article was previously published under Q130802
SUMMARY
One of the more frequent trap codes generated by Windows NT is STOP 0x0000000A. This STOP message can be caused by both hardware and software problems. To determine the specific cause, you must debug the STOP. However, some general information can be learned by examining the parameters of the STOP message and the STOP screen information.
MORE INFORMATION
STOP 0x0000000A indicates a kernel mode process or driver attempted to access a memory address that it did not have permission to access. The most common cause of this error is a bad or corrupt pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has a bad value in it, then the program tries to access memory that it should not. When this occurs in a user mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message.
To determine what process or driver tried to access memory it should not, look at the parameters displayed on the STOP screen information. For example, in the following STOP message
STOP 0x0000000A(0xWWWWWWWW, 0xXXXXXXXX, 0xYYYYYYYY, 0xZZZZZZZZ)
IRQL_NOT_LESS_OR_EQUAL
** Address 0xZZZZZZZZ has base at <address>- <driver>
The four parameters inside the parenthesis have the following meaning:
0xWWWWWWWW Address that was referenced improperly
0xXXXXXXXX IRQL that was required to access the memory
0xYYYYYYYY Type of access, 0=Read, 1=Write
0xZZZZZZZZ Address of instruction which attempted to reference
the memory at 0xWWWWWWWW
If the last parameter (0xZZZZZZZZ) falls within the address range of one of the device drivers loaded on the system, you will know which device driver was running when the memory access occurred. This driver is often identified in the third line of the STOP screen:
**Address 0xZZZZZZZZ has base at <address>- <driver name>
If <driver name> is a specific driver, search in the Microsoft Knowledge Base on the keyword 0x0000000A and the driver name. If you don't find any relevant articles, contact Microsoft Product Support.
apparently
0x03F00406 = 0xWWWWWWWW Address that was referenced improperly
0x00000002 = 0xXXXXXXXX IRQL that was required to access the memory
0x00000000 = 0xYYYYYYYY Type of access, 0=Read, 1=Write
0x804f8c38 = 0xZZZZZZZZ Address of instruction which attempted to reference the memory at 0xWWWWWWWW
What ever it is that is nmessing up is on irq #2 with this address "0x03F00406" If there is a driver involved it will be identified on the third line like this "0xZZZZZZZZ has base at <address>- <driver name>"
Help anyone else?
Remove 1 of the MEMORY DIMMS, and try re-installing XP PRO.