BSOD 0x0000000A + 4E Help - Overclock.net

ShadowGun · 09-07-08

I have been having this for about a month trying to fix it it went away for awhile and now it has happened to me 3 times today......

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805226e8, address which referenced memory

Debugging Details:
------------------

WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+66
805226e8 ff08 dec dword ptr [eax]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80522c12 to 805226e8

STACK_TEXT:
bacc37f4 80522c12 0007873e 00000000 00000000 nt!MiRemovePageByColor+0x66
bacc380c 8051cab7 00000000 00008000 00000000 nt!MiRemoveAnyPage+0xbc
bacc3840 80698b94 89e3f680 00000000 00000044 nt!MmZeroPageThread+0x153
bacc3dac 805cff64 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
bacc3ddc 805460de 8069790c 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+66
805226e8 ff08 dec dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageByColor+66

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+66

BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+66

Followup: MachineOwner
---------

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: ffffff7f, new page
Arg3: 00029b3e, old page
Arg4: 00000000, 0

Debugging Details:
------------------

BUGCHECK_STR: 0x4E_8f

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8051cbb4 to 804f9f33

STACK_TEXT:
bacc37f8 8051cbb4 0000004e 0000008f ffffff7f nt!KeBugCheckEx+0x1b
bacc3840 80698b94 89e3f680 00000000 00000044 nt!MmZeroPageThread+0x250
bacc3dac 805cff64 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
bacc3ddc 805460de 8069790c 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmZeroPageThread+250
8051cbb4 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmZeroPageThread+250

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_8f_nt!MmZeroPageThread+250

BUCKET_ID: 0x4E_8f_nt!MmZeroPageThread+250

Followup: MachineOwner
---------

error10 · 09-07-08

Loosen your RAM timings? Increase voltages?

Atomagenesis · 09-07-08

A BSOD could be lots of things and not necessarily your RAM. Although, if it is happening with frequency when you are doing random things then it probably is your RAM.

If you could give a different diagnoses of what you are doing, or any particular action you take that may cause it, and when it occurs, then we could figure out the problem.

Licht · 09-07-08

Quote:

Originally Posted by ShadowGun

I have been having this for about a month trying to fix it it went away for awhile and now it has happened to me 3 times today......

-------------An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.-------------

Take note of my highlighted text. It also claims memory corruption. When i see this and drivers in the same message i think video card drivers. Many of BSOD i saw while on nVidia's GPU.

error10 · 09-07-08

I saw the STOP 0x0000000A just yesterday. It was too tight RAM timing, at least for me.

Licht · 09-07-08

Quote:

Originally Posted by error10

I saw the STOP 0x0000000A just yesterday. It was too tight RAM timing, at least for me.

A stop error doesn't necessarily have to do with RAM. It is a very broad term. (Although i can't say so much for the error names, i don't know them.)

Edit : By the way, a stop error is another name for BSOD.

error10 · 09-07-08

Quote:

Originally Posted by Licht

A stop error doesn't necessarily have to do with RAM. It is a very broad term. (Although i can't say so much for the error names, i don't know them.)

It depends largely on which STOP error it is.

Licht · 09-07-08

Quote:

Originally Posted by error10

It depends largely on which STOP error it is.

Like i said don't have these memorized but it looks familiar strangely...

Licht · 09-07-08

Sorry for report but this deserves it.

Quote:

Troubleshooting a Stop 0x0000000A error in Windows XP

View products that this article applies to.
Article ID:314063Last Review:September 20, 2007Revision:6.3
This article was previously published under Q314063
On This Page

SUMMARY

SYMPTOMS

CAUSE

RESOLUTION

Where to start

Advanced Troubleshooting

If you receive a Stop 0x0A error message during the installation of Windows XP

Verify that your hardware is listed on the Windows XP Hardware Compatibility List

Look for other hardware issues

If you receive a Stop 0x0A error after Windows XP is already installed

Examine third-party software or drivers

Examine newly installed hardware

Additional information

.toc{display: none;}SUMMARY

This article describes several causes and resolutions for a "Stop: 0x0000000A" error message that you may receive in Windows XP.

Back to the top

SYMPTOMS

You may receive the following Stop error message during or after the installation of Windows XP: Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename

The parameters refer to the specific issues that are involved: •Parameter 1 - An address that was referenced incorrectly.•Parameter 2 - An IRQL that was required to access the memory.•Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation.•Parameter 4 - The address of the instruction that referenced memory in parameter 1. This article describes how to troubleshoot this Stop error message.

Back to the top

CAUSE

Stop error 0x0000000A (Stop 0x0A) indicates that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.

Back to the top

RESOLUTION

Where to start

When this error occurs, use the Windows Error Reporting tool. With this tool, you can send the error report directly to Microsoft, and then the tool will report back if a fix or a workaround is available. To use this tool, follow these steps:

Click Send Error Report when you are prompted to send the error report to Microsoft.

If a fix or a workaround is available, click More Information after you send the error report to Microsoft. This helps you obtain the fix or information about how to work around the issue.

If a fix or a workaround is not available, you can use the "Advanced Troubleshooting" section to try to resolve this issue. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to contact support, visit the following Microsoft Web site: http://support.microsoft.com/contactus/ (http://support.microsoft.com/contactus/)

Back to the top

Advanced Troubleshooting

If you receive a Stop 0x0A error message during the installation of Windows XP

If you receive a Stop 0x0A error message during the installation of Windows XP, use the following troubleshooting procedures to verify your hardware components. Verify that your hardware is listed on the Windows XP Hardware Compatibility List

If your hardware is not listed on the Windows XP HCL, consider obtaining hardware that is listed on the Hardware Compatibility List (HCL).

To view the latest HCL, visit the following Microsoft Web site: http://winqual.microsoft.com/HCL/Default.aspx?m=x (http://winqual.microsoft.com/HCL/Default.aspx?m=x)
You might also want to read the "Check System Compatibility" topic on the Windows XP CD-ROM to learn about potential software and hardware incompatibility. Look for other hardware issues

The following troubleshooting steps can help you isolate the problem. Use the Windows XP CD-ROM to start the computer, and then follow the on-screen installation instructions. If you continue to receive a Stop 0x0A error during the installation of Windows XP, try the following troubleshooting steps. After each step, try again to install Windows.Warning This article contains steps that may involve changing the BIOS or CMOS settings or that may require that you to make physical changes to your computer hardware. Incorrect changes to the BIOS of your computer can cause serious problems. Microsoft cannot guarantee that problems that are caused by changes to the BIOS can be resolved. Change the BIOS settings at your own risk. If you want help with any of these steps, contact the hardware manufacturer. Making hardware or BIOS changes to your computer may invalidate your warranty. If you do not want to make hardware changes to your computer, take your computer to a repair center.1.During the installation startup, press F5 when the "Setup is inspecting your computer's hardware configuration" message appears. When you are prompted, specify the correct computer type and hardware abstraction layer (HAL). For example, if you have a single processor, specify the "Standard PC" HAL.2.Turn off the following features in the CMOS settings of your computer. See the hardware documentation or manufacturer for instructions.•All caching, including L2, BIOS, internal/external, and writeback caching on disk controllers•All shadowing•Plug and Play•Any BIOS-based virus protection feature3.Remove all adapters and disconnect all hardware devices that are not required to start the computer and install Windows, including the following adapters and devices:•Network adapter•Internal modem•Sound card•Extra hard disks (you have to have at least one to complete the installation)•CD Drive or DVD drive (if you are installing from the local hard disk)4.If you are using a SCSI adapter, use the following methods. See the hardware documentation for information.•Obtain the latest Windows driver from the adapter vendor.•Turn off sync negotiation on the SCSI controller.•Verify that termination and IDs of the SCSI devices are correct.•Remove all SCSI devices from the SCSI chain (except for one hard disk if you are starting from or installing to a drive that is on that disk).5.If you are using IDE devices, use the following methods. See the hardware documentation for more information.•Define the on-board IDE port to Primary only.•Verify that the Master/Slave/Only settings for the IDE devices are correct.•Remove all IDE devices except for the hard disk.6.Check the memory SIMMs (the RAM) in the computer. See the hardware documentation for more information.•Remove any mismatched memory SIMMs so that all the SIMMs operate at the same speed. For example, 60 nanoseconds (ns) or 70 ns.•Run a systems test on the memory, and remove any bad SIMMs.•Test by using different SIMMs if any are available.7.Contact the manufacturer of the computer or the motherboard to see whether there are any known issues about running or installing Windows XP. The manufacturer may be able to help with the following items:•Running a diagnostics program on the computer.•Upgrading the computer BIOS if that is applicable.

Back to the top
If you receive a Stop 0x0A error after Windows XP is already installed

If you receive the Stop 0x0A error after Windows XP is already installed, use the following troubleshooting methods to verify other components. Examine third-party software or drivers

If you have installed any third-party software or drivers, try removing them or disabling them so that they do not load, and then restart the computer to see whether that software or driver is causing the error. If that software or driver is causing the error, report the problem to the vendor of the software or driver.

If you cannot start Windows XP after you install the software or drivers, use one of the following methods to restore Windows: •Use the Last Known Good configuration.

For more information about using the Last Known Good configuration, click the following article number to view the article in the Microsoft Knowledge Base: 307852 (http://support.microsoft.com/kb/307852/) How to start your computer by using the Last Known Good Configuration feature in Windows XP
•Repair the Windows XP installation. To do this, follow these steps:1.Disable any antivirus program and BIOS-level antivirus protection. For help, see the relevant software manual or online Help.2.Make sure that the CD or DVD drive is the first priority startup device. See your computer documentation for information about how to do this.3.Insert the Windows XP CD into the CD or DVD drive, and then restart your computer.4.When the instruction to "Press any key to boot from CD" appears, press a key. Your computer starts from the Windows XP CD.5.When the computer starts from the CD, the system verifies your hardware, and then prompts you to select one of the following options:•To set up Windows XP now, press ENTER.•To repair a Windows XP installation using Recovery Console, press R.•To quit Setup without installing Windows XP, press F3.6.Press ENTER.7.Press F8 to accept the Licensing Agreement.8.A box lists your current Windows XP installation, and then the computer prompts you to select one of the following options:•To repair the selected Windows XP installation, press R.•To continue installing a fresh copy of Windows XP without repairing, press ESC.9.Press R. After you repair Windows XP, you may have to reactivate Windows XP if you changed some hardware.•Use the Roll Back Driver feature.

For more information about how to use the Roll Back Driver feature, click the following article number to view the article in the Microsoft Knowledge Base: 283657 (http://support.microsoft.com/kb/283657/) How to use the Roll Back Driver feature in Windows XP
•Use the Windows XP System Restore feature.

For more information about how to use the System Restore feature, click the following article number to view the article in the Microsoft Knowledge Base: 306084 (http://support.microsoft.com/kb/306084/) How to restore the operating system to a previous state in Windows XP
•Use Recovery Console.

For additional information about how to use Recovery Console, click the following article number to view the article in the Microsoft Knowledge Base: 307654 (http://support.microsoft.com/kb/307654/) How to install and use the Recovery Console in Windows XP
•If Windows is on a FAT partition, start to MS-DOS, and then rename the problem software or driver.Examine newly installed hardware

If you added any hardware device after Windows was installed, remove the newly added device to see whether the Stop 0x0A error stops occurring. If removing the newly added device resolves the problem, use one or more of the following methods: •Obtain updated drivers for the device if they are available.•Call the vendor of the device to see whether there are any known issues with the device. •Run diagnostics to make sure that the device is working correctly. •Examine the logs in the event viewer to determine whether there is any event information that can help you determine what device or driver is causing the problem.

Back to the top
Additional information

If these steps do not resolve the Stop 0x0A error, and if you are running Windows on HCL-compliant hardware, refer to the following article in the Microsoft Knowledge Base: 314103 (http://support.microsoft.com/kb/314103/) Preparation before you contact Microsoft after you receive a STOP message on a blue screen

Back to the top

Do as it says using error reporting please.

ShadowGun · 09-07-08

Well i have no idea right now what ram timings r and what they should be. Any idea how i can figure out? I ran memtest and got 10 passes i have nvidia lastest official drivers install.

		Overclock.net - Overclocking.net > Software, Programming and Coding > Operating Systems > Windows
BSOD 0x0000000A + 4E Help