Please register or login. There are 0 registered and 752 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s September 23 - 10:40am EDT 
Hardware Analysis
Forums Product Prices

  Latest Topics 

More >>


  You Are Here: 
/ Forums / Problem Products /

  BSOD - Stop 0x0000000A error 
 Date Written 
Jason Bokenkamp Apr 15, 2004, 02:55am EDT Report Abuse

I am constantly getting the following error message which is causing windows xp home to fail to start:

"A problem has been detected and windows has been shut down to prevent damage to your computer.


If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press f8 to select Advanced Startup options, and then select safe Mode.

Technical information:

*** STOP: 0x0000000A (0x0A1F0008, 0x00000002, 0x00000000, 0x804E524D) "

I have disabled all BIOS cacheing and shadowing, have disabled almost everything that I can, yet I cannot get to the logon screen. As far as I know the disk is ok, as xp checks it for errors every time I restart it. I have researched the problem thoroughly, and believe it is a hardware device driver that is causing the problem, but I can't even get to xp via all safe mode options or the last known good configuration. The PC is an Acer Aspire, out of the box for a week and all I'm getting is BSOD, BSOD, BSOD. I am using AVG Antivirus 6 (free), and my hardware setup is as follows:

I have 512MB of dram
The Bios is Phoenix award bios - dated jan 14 2004
I have a realtek audio card
I have a radeon graphics card and an ati lcd monitor (works fine)
realtek internal modem

I have read the following help message that looked like it could help me rectify the problem, but it introduces a problem all of it's own:

"Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted 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. This Stop message is typically due to faulty or incompatible hardware or software.

Interpreting the Message
This Stop message has four parameters:

1.Memory address that was improperly referenced.

2.IRQL that was required to access the memory.

3.Type of access (0x00000000 = read operation, 0x00000001 = write operation).

4.Address of the instruction that attempted to reference memory specified in parameter 1.

If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:

**Address 0xZZZZZZZZ has base at <address>- <driver name>"

The thing is that with every error message that I get the memory address that is being referenced improperly keeps changing. The 2nd, 3rd and 4th paremeters remain the same. And I don't get the
"**Address 0xZZZZZZZZ has base at <address>- <driver name>" message at all.

I need to discover what is at address 0x804E524D and then I need to either knock the driver out of service while I find out what the problem is, or remove the faulty hardware. Thing is, I can't get to it any way that I can think of. Is there some prog that I can fit onto a floppy which will allow me to discover these things?

Thanks, and sorry for the length and the lack of knowledge.

Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
Chris McNally Apr 15, 2004, 03:15am EDT Report Abuse
>> Re: BSOD - Stop 0x0000000A error
Sounds like a memory issue. You running an nforce2 chipset in dual channel mode? If so remove one of the dimms and see how you go. If not, post your full system specs.


Chris McNally

Moderator - Hardware Analysis
james chen Apr 13, 2015, 08:50pm EDT Report Abuse
>> Re: BSOD - Stop 0x0000000A error



  Topic Tools 
RSS UpdatesRSS Updates

  Related Articles 

A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.