BSOD and multiple stop codes

[Brian Scholfield]

Hi All,

I am working on a system that has been having BSOD crashes on a fairly
regular basis. The four stop codes that I have recorded are
0x24 - NTFS.SYS
0XD1- PORTELS.SYS
0X50 - PAGE FAULT IN NONPAGED AREA
0X8E - WIN32K.SYS

I have multiple event codes also:

Application Log:

EVENT ID 4609 - The COM+ Event System detected a bad return code during its
internal processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.

EVENT ID 1009 - Fault bucket 295252419.

EVENT ID 1000 - Faulting application services.exe, version 5.1.2600.2180,
faulting module rpcrt4.dll, version 5.1.2600.2180, fault address 0x0000aa09.

System Log:

EVENT ID 7023 - The IPSEC Services service terminated with the following
error: The attempted operation is not supported for the type of object
referenced.

I have got lots of the 4609 and 7023 events. I am at a loss. I have run
chkdsk /f. I have run Dells memory, hard drive, and processor test
utilities with no failures. I have disabled any unneed startup programs and
un-installed several unused programs.

The first few times that this happened on this system Dell walked my client
through a clean re-install of her system and this did not solve the problem.
For some reason I am now suspecting McAfee, but I can't verify it or say why
I suspect it.

Any help out there on this?

Thank you,
Brian

 

[Chuck]

A first guess is possible hardware failure. I have had very similar symptoms
when:
The processor is running too hot or is overclocked.
The video card is overclocked or has power problems due to a low capability
power supply.
The PC power supply is marginal.

Dell has been known to put low capacity power supplies in low end systems.

 

[John]

Brian Scholfield (removethis) wrote:
The four stop codes that I have recorded are

0x24 - NTFS.SYS
0XD1- PORTELS.SYS
0X50 - PAGE FAULT IN NONPAGED AREA
0X8E - WIN32K.SYS

EVENT ID 4609 - The COM+ Event System detected a bad return code during its
internal processing. HRESULT was C0000005

Put your errors into a search engine.

Examples.

C0000005
http://www.google.com.au/search?hl=en&q=C0000005+&btnG=Google+Search&meta=
EVENT ID 4609
http://www.google.com.au/search?hl=en&q=+EVENT+ID+4609&btnG=Search&meta=

 

[Brian Scholfield]

Thanks Chuck,

I have lately been very unimpressed with Dells low end systems, although
their higher priced offerings still seem to be good. I guess that is the
price of cost cutting.

I will explore the Power Supply issue. I had not thought of that. I do
know that using my tools and Dells tools showed no problems with the hard
drive, possible(?) problems with the RAM (Dells memory test utility showed
no problem and Microsofts memory diagnostic showed one error in 2 of 24
tests).

Well, more exploring to do.

Thank You,
Brian

 

[Brian Scholfield]

Been there, done that.

The 4609 errors relate to applying SP2 to XP Pro that is already joined to a
domain. However this is XP home and not in a domain. Not able to access
the security policy on XP Home, which is the fix spelled out by in the
knowledge base. As a matter of fact, according to M/S this error only
happens on XP Pro machines.

The others have equally useless information for my situation.

Anyway, any help that can be provided that is not in the knowledge base
generally found on the internet would be greatly appreciated.

Thanks,
Brian

 

[Guest]

Been there, done that.

The 4609 errors relate to applying SP2 to XP Pro that is already joined to a
domain. However this is XP home and not in a domain. Not able to access
the security policy on XP Home, which is the fix spelled out by in the
knowledge base. As a matter of fact, according to M/S this error only
happens on XP Pro machines.

The others have equally useless information for my situation.

Anyway, any help that can be provided that is not in the knowledge base
generally found on the internet would be greatly appreciated.

Thanks,

Hi Brian,

Try this and let us know, go to the RUN Command and type the following:
secpol.msc Press OK

In the left Pane [Window] Expand the Plus [+] beside the Local Policies
and click on the * User Rights assignment .
in the Right Pane navigate and Locate *Impersonate a Client after
Authentication* Double click it.
On the Pop-Up new window Click on the Button labled Add User or Group.
Then in the Header above the text Box labled Enter Object names to select
box, Type * service* and Click OK Twice.
Reboot your computer and see if the Error will occur again.
Hope this helps
Please send back your findings
nass

 

[Brian Scholfield]

Thanks nass, but I already tried to do that. secpol.msc is not available on
XP Home. That is part of the frustration that I have been dealing with.
Most of the KB articles relate to things that only exist on XP Pro and do
not give fixes for XP Home. Is there a way to install it on XP Home? I
havn't looked on an XP Pro CD to see if the administrative tools are there
like they were on the 2000 CD, and even if they are will secpol.msc work on
XP Home? I guess there is only one way to find out.

I will do some hunting on my own to see if I can find out how to get
secpol.msc on XP Home. Alternately, is there a command line method that
might exist on XP Home?

Thanks,
Brian

Been there, done that.

The 4609 errors relate to applying SP2 to XP Pro that is already joined
to a
domain. However this is XP home and not in a domain. Not able to access
the security policy on XP Home, which is the fix spelled out by in the
knowledge base. As a matter of fact, according to M/S this error only
happens on XP Pro machines.

The others have equally useless information for my situation.

Anyway, any help that can be provided that is not in the knowledge base
generally found on the internet would be greatly appreciated.

Thanks,

Hi Brian,

Try this and let us know, go to the RUN Command and type the following:
secpol.msc Press OK

In the left Pane [Window] Expand the Plus [+] beside the Local Policies
and click on the * User Rights assignment .
in the Right Pane navigate and Locate *Impersonate a Client after
Authentication* Double click it.
On the Pop-Up new window Click on the Button labled Add User or Group.
Then in the Header above the text Box labled Enter Object names to select
box, Type * service* and Click OK Twice.
Reboot your computer and see if the Error will occur again.
Hope this helps
Please send back your findings
nass

 

[Guest]

Thanks nass, but I already tried to do that. secpol.msc is not available on
XP Home. That is part of the frustration that I have been dealing with.
Most of the KB articles relate to things that only exist on XP Pro and do
not give fixes for XP Home. Is there a way to install it on XP Home? I
havn't looked on an XP Pro CD to see if the administrative tools are there
like they were on the 2000 CD, and even if they are will secpol.msc work on
XP Home? I guess there is only one way to find out.

I will do some hunting on my own to see if I can find out how to get
secpol.msc on XP Home. Alternately, is there a command line method that
might exist on XP Home?

Thanks,

Hi Brian,
I did a quick google and I find this:
http://forums.practicallynetworked.com/showthread.php?t=4101&page=4&pp=15
Do you can get or RUN the command: GPEDIT.MSC
Do a Scan for Viruses and be sure your Computer clean.
nass

Been there, done that.

The 4609 errors relate to applying SP2 to XP Pro that is already joined
to a
domain. However this is XP home and not in a domain. Not able to access
the security policy on XP Home, which is the fix spelled out by in the
knowledge base. As a matter of fact, according to M/S this error only
happens on XP Pro machines.

The others have equally useless information for my situation.

Anyway, any help that can be provided that is not in the knowledge base
generally found on the internet would be greatly appreciated.

Thanks,

Hi Brian,

Try this and let us know, go to the RUN Command and type the following:
secpol.msc Press OK

In the left Pane [Window] Expand the Plus [+] beside the Local Policies
and click on the * User Rights assignment .
in the Right Pane navigate and Locate *Impersonate a Client after
Authentication* Double click it.
On the Pop-Up new window Click on the Button labled Add User or Group.
Then in the Header above the text Box labled Enter Object names to select
box, Type * service* and Click OK Twice.
Reboot your computer and see if the Error will occur again.
Hope this helps
Please send back your findings
nass

Brian Scholfield (removethis) wrote:
The four stop codes that I have recorded are
0x24 - NTFS.SYS
0XD1- PORTELS.SYS
0X50 - PAGE FAULT IN NONPAGED AREA
0X8E - WIN32K.SYS

EVENT ID 4609 - The COM+ Event System detected a bad return code
during
its
internal processing. HRESULT was C0000005

Put your errors into a search engine.

Examples.

C0000005
http://www.google.com.au/search?hl=en&q=C0000005+&btnG=Google+Search&meta=
EVENT ID 4609
http://www.google.com.au/search?hl=en&q=+EVENT+ID+4609&btnG=Search&meta=

 

[John]

I will do some hunting on my own to see if I can find out how to get secpol.msc on XP Home.

secpol.msc
http://www.google.com.au/search?hl=en&q=secpol.msc&btnG=Google+Search&meta=
http://www.windowsitpro.com/Windows/Article/ArticleID/38546/38546.html
XP Home Edition doesn't have gpedit.msc or secpol.msc. However, you can
edit the registry to enable the policy in XP Home. Start regedit and
navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Setup\RecoveryConsole
registry subkey. Double-click SetCommand and set the value to 1. Close
the registry editor, then restart the computer.
http://www.ntcompatible.com/Problem_loading_secpol.msc_&_gpedit.msc_need_helpfix.._t24914.html