BSOD 0x0000000A

  • Thread starter Thread starter Bert Vandenberghe
  • Start date Start date
B

Bert Vandenberghe

Hi,

We have several pc's at customers side which are starting to crash more and
more often. There are about 15 pc's and each week more of these pc's crash
and give the exact same blue screen:
XXX stop:0x0000000A (0xC0000000,0x00000002,0x00000000,0x80438366)
IRQL_NOT_LESS_OR_EQUAL
xxxAdress 80438366 base at 80400000, datestamp 3d366b8b ntoskrnl.exe
Beginning dump of fhysical memory
Click to expand...

The strange thing is that these pc's all give the same BSOD on the same
address (= 0x80438366). But my real problem is to solve this painful problem
asap. If this is caused by some faulty driver, how can I know which one. I
don't come any further with pstat because it's ntoskrnl.exe that crashes.

How can I locate a faulty driver? Or is it bad RAM? How can I retrieve this
information from the minidumps? I tried dumpcheck, but that doesn't help me
much. Any suggestions how to handle this problem?

Thanks,
Bert
 
This may help.

http://msdn.microsoft.com/library/e..._b974c0cb-dd37-4b81-b818-e5ea50cb07a6.xml.asp

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi,
|
| We have several pc's at customers side which are starting to crash more
and
| more often. There are about 15 pc's and each week more of these pc's crash
| and give the exact same blue screen:
|
| > XXX stop:0x0000000A (0xC0000000,0x00000002,0x00000000,0x80438366)
| > IRQL_NOT_LESS_OR_EQUAL
| > xxxAdress 80438366 base at 80400000, datestamp 3d366b8b ntoskrnl.exe
| > Beginning dump of fhysical memory
|
| The strange thing is that these pc's all give the same BSOD on the same
| address (= 0x80438366). But my real problem is to solve this painful
problem
| asap. If this is caused by some faulty driver, how can I know which one. I
| don't come any further with pstat because it's ntoskrnl.exe that crashes.
|
| How can I locate a faulty driver? Or is it bad RAM? How can I retrieve
this
| information from the minidumps? I tried dumpcheck, but that doesn't help
me
| much. Any suggestions how to handle this problem?
|
| Thanks,
| Bert
|
|
|
 
Thanks for the quick response, but the problem is also that the BSOD only
occurs once in a while (about once a week), so it is difficult to debug it.

Can I do anything with the minidump that is valuable? And is there a way to
be sure that this is a driver problem, and not bad RAM?
I assume this BSOD cannot be caused by a software program that is running as
a system service, is that correct?

Thanks,
Bert
 
Here's an article on reading them.

http://support.microsoft.com/default.aspx?kbid=315263

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks for the quick response, but the problem is also that the BSOD only
| occurs once in a while (about once a week), so it is difficult to debug
it.
|
| Can I do anything with the minidump that is valuable? And is there a way
to
| be sure that this is a driver problem, and not bad RAM?
| I assume this BSOD cannot be caused by a software program that is running
as
| a system service, is that correct?
|
| Thanks,
| Bert
|
|
| | > This may help.
| >
| >
|
http://msdn.microsoft.com/library/e..._b974c0cb-dd37-4b81-b818-e5ea50cb07a6.xml.asp
| >
| > --
| > Regards,
| >
| > Dave Patrick ....Please no email replies - reply in newsgroup.
| > Microsoft Certified Professional
| > Microsoft MVP [Windows]
| > http://www.microsoft.com/protect
| >
| > "Bert Vandenberghe" wrote:
| > | Hi,
| > |
| > | We have several pc's at customers side which are starting to crash
more
| > and
| > | more often. There are about 15 pc's and each week more of these pc's
| crash
| > | and give the exact same blue screen:
| > |
| > | > XXX stop:0x0000000A (0xC0000000,0x00000002,0x00000000,0x80438366)
| > | > IRQL_NOT_LESS_OR_EQUAL
| > | > xxxAdress 80438366 base at 80400000, datestamp 3d366b8b ntoskrnl.exe
| > | > Beginning dump of fhysical memory
| > |
| > | The strange thing is that these pc's all give the same BSOD on the
same
| > | address (= 0x80438366). But my real problem is to solve this painful
| > problem
| > | asap. If this is caused by some faulty driver, how can I know which
one.
| I
| > | don't come any further with pstat because it's ntoskrnl.exe that
| crashes.
| > |
| > | How can I locate a faulty driver? Or is it bad RAM? How can I retrieve
| > this
| > | information from the minidumps? I tried dumpcheck, but that doesn't
help
| > me
| > | much. Any suggestions how to handle this problem?
| > |
| > | Thanks,
| > | Bert
| > |
| > |
| > |
| >
| >
| >
|
|
|
 
I already tried dumpcheck, but that is not giving me much more valuable
information...

The crash seems to happen in ntoskrnl.exe, but what is causing this? It is
always happening on the same memory location, how can I further investigate
this?

Thanks for the help,
Bert
 
Well I think I have already given you the tools to find the answer. If it is
happening on identical machines then to me this suggests a driver issue.
Check the hardware manufacturer's web site for the latest Windows 2000
driver for your devices.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I already tried dumpcheck, but that is not giving me much more valuable
| information...
|
| The crash seems to happen in ntoskrnl.exe, but what is causing this? It is
| always happening on the same memory location, how can I further
investigate
| this?
|
| Thanks for the help,
| Bert
 
I installed the debugging tools for Windows, and when I try to open a
minidump with WinDbg, then I always get the following error:

---------------------------
WinDbg:6.3.0017.0
---------------------------
Could not find the C:\Temp\Mini092604-01.dmp Dump File, Win32 error 1392

The file or directory is corrupted and unreadable.
---------------------------
OK
---------------------------

I have tried this with more then 10 minidumps, and it is always the same
problem...
Any suggestions?

Bert
 
Afraid I don't have any mini-dumps to even test this on.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I installed the debugging tools for Windows, and when I try to open a
| minidump with WinDbg, then I always get the following error:
|
| ---------------------------
| WinDbg:6.3.0017.0
| ---------------------------
| Could not find the C:\Temp\Mini092604-01.dmp Dump File, Win32 error 1392
|
| The file or directory is corrupted and unreadable.
| ---------------------------
| OK
| ---------------------------
|
| I have tried this with more then 10 minidumps, and it is always the same
| problem...
| Any suggestions?
|
| Bert
|
|
|
 
I probably wouldn't be able to provide anything in the time frame you
require. It may be easier to check the hardware manufacturer's web site for
the latest drivers for your devices. Failing that you might want to start a
support incident with Microsoft product support services.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I can send you one of my minidumps, if you want...
|
| Regards,
| Bert
 
Bert,

It is very unlikely (almost impossible) that that many machines are
experiencing the same hardware problem at the same time. Way more likely
that some software install or upgrade has been applied to the machines. Try
to find out what common change occurred, then roll one of the machines back
to see if that corrects the problem. If no new installs have been made in
common, I'd first look at frequently updated software such as virus scanners
or windows itself.
Could be that a hotfix simply didn't work with your configuration.


Bert Vandenberghe said:
Thanks for your advice,
Bert

Dave Patrick said:
I probably wouldn't be able to provide anything in the time frame you
require. It may be easier to check the hardware manufacturer's web site for
the latest drivers for your devices. Failing that you might want to
Click to expand...
start
a
support incident with Microsoft product support services.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I can send you one of my minidumps, if you want...
|
| Regards,
| Bert
Click to expand...
Click to expand...
 
Bert Vandenberghe said:
For the record:

I found a Microsoft KB article that might solve the 0x0000000A problem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;867778

We are currently testing this hotfix 867778, and we didn't have a crash
yet
on the pc's that are upgraded. But we need some more time to upgrade all
the
computers, but it looks promising.

Bert
Click to expand...
_______

Hi,

This fix correct one Microsoft bug which can cause a bugcheck 0x0000000A.

Typicaly, this bug check usually occurs after the installation of a faulty
device driver, system service, or BIOS.

This fix does not prevent stop 0x0A to appear, it only correct the bug
describe in the article 867778.
If a faulty third party kernel object is installed on your system this fix
will not correct it so potentialy the stop 0x0A can occur.

Regards

Aurelien Goillot
Microsoft France
 
Back
Top