STOP Error at 0xA IRQ....

[Guest]

hope im right here, i have a notebook with a problem, it works completly
fine while using it with a electic cable but if i pull it or restart in
Battery Mode i get a bluescreen with the following stop Error:

0x0000000A (0xF884F004, 0x00000007, 0x00000000, 0x805270B4)

Ok, its the irq less or equal error, i got it from the MSDN pages, i tried
also runing the last known good version from the f8 menu, not worked. I found
out that if i deacitivate the ACPI Batterycontrol in the Device Managaer i
can boot in batery mode without problems, of course i dont want to have it
deactivated, so i search for the problem
but what could the problem be? I need to identify the programm or access
that writes at 0xF884F004 and im afraid that im not the best debugger in the
world, precisely i cant access the debugger because the error occurs while
booting, not on the desktop. there are protocol files made if i boot the
notebook with the cable again but is there an analysis tool for them?
I cant identify the programm, and if its a printer driver for example that
causes it, how can i remove the driver? I mean there is no printer programm
when i install it, just sth like a lot of .sys and dll files and reg entrys
scattered in the windows dirs so im unable to locate every possible driver
and delete it to see if the problem is solved.

Hope sb can help me, thx

 

[Ronnie Vernon MVP]

hope im right here, i have a notebook with a problem, it works
completly fine while using it with a electic cable but if i pull it
or restart in Battery Mode i get a bluescreen with the following stop
Error:

0x0000000A (0xF884F004, 0x00000007, 0x00000000, 0x805270B4)

Ok, its the irq less or equal error, i got it from the MSDN pages, i
tried also runing the last known good version from the f8 menu, not
worked. I found out that if i deacitivate the ACPI Batterycontrol in
the Device Managaer i can boot in batery mode without problems, of
course i dont want to have it deactivated, so i search for the problem
but what could the problem be? I need to identify the programm or
access that writes at 0xF884F004 and im afraid that im not the best
debugger in the world, precisely i cant access the debugger because
the error occurs while booting, not on the desktop. there are
protocol files made if i boot the notebook with the cable again but
is there an analysis tool for them?
I cant identify the programm, and if its a printer driver for example
that causes it, how can i remove the driver? I mean there is no
printer programm when i install it, just sth like a lot of .sys and
dll files and reg entrys scattered in the windows dirs so im unable
to locate every possible driver and delete it to see if the problem
is solved.

Hope sb can help me, thx

Check the following article for the resolution.

"STOP 0x0000000A" Error Message When You Change from AC Power to DC Power:
http://support.microsoft.com/kb/316676

If this does not resolve the problem, go to the following website and for the complete list of articles associated with this stop message.

Troubleshooting Windows STOP Messages:
http://www.aumha.org/win5/kbestop.php#0x0a

 

[David Candy]

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

 

[Guest]

Thx ppl, i will check them, but the Stop Error helppages are
a little bit...hm, unhelpful, they say it is fixed it in SP 1 and i work
with SP2, but varifier and Debugging next

I report later

 

[Guest]

Here is an update, that seems to be important.

I set verifier to max, no i have no problems going to DC , there is no
bluescreen.
When i set to max verifier gives me a list of unsigned drivers, i moved them
temporarily into another folder , rebooted and pulled the plug, i got a new
bluescreen, now there is not only the normal stop message but additiionally a
pointer at the usbhub.sys.
Now i installed symbols and debugger, selected symbols and tried to open the
last dump, but i get an error message "File not readable or demaged"
(translated into english from german)
So i cant open the dmps, i tried a lot of them, everything the same, the
last ten dmps are corrupt, i produced a new bluescreen and tried again - no
success.
So if verifier ist at max it works and the debugger cant read it.

I hope sb knows what happend here.

Thx

 

[David Candy]

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

I'll try to read them.

 

[David Candy]

It should be 64 KB in size

 

[Guest]

Ok, i send u one, but even they are set to a small dump (64kb) they are
exactly 88 kb this is wierd.
By the way the dump i send should be a a Stop error conserninng the normal
bug,
But as i mentioned, when i manually delete all unverified drivers manually
and pull the plug, i get the same STOP but with a addendum that usbhub.sys
caused the problem, and that use to happen only then, when the other not
verified drivers are deleted.

And i am not online at the weekend so sorry for no response till sunday
evening.
I appreciate the help.

 

[David Candy]

I haven't recieved a file.

 

[Guest]

But did u get a mail from me?
I checked my sent folder, a mail to <davidc @ mvps.org>
was sent with a minidump file.
But actually my own outlook delete the dmp file of this message
any advice what i could do instead?

 

[David Candy]

No I didn't. Sorry wrong email. it's just david at mvps.org.

 

[Guest]

I did two days ago

 

[David Candy]

I received the file.

 

[David Candy]

What is your memory and disk drive configuration?

 

[Guest]

Im not sure what you mean with that.
Well the notebook has 512 MB RAM
What are those configs? I guess you
dont mean sth like my harddisk is primary master
and so on, or do u?
And what is a memory config?

Thx

 

[David Candy]

Corrupted dmp files are normally related to either memory configuration (running windows in a special memory mode), too much memory (in conjunction with something else), or running windows on RAID and similar high performance hard disks.

 

[Guest]

Well but what does it mean to me?
Its a fresh installed XP ona new Notebook, no RAId
not much RAM and i dunno about any special
memory managment

 

[Guest]

I believe that helping me is getting annoying
but im really not sure, what i could do.
I guess a fresh bought notebook is not
equiped with too much memory or sth else.

What are my possibilities to remove the driver files by hand?
Is there a tool? or should i just remove sys files from the system/driver
folder?