Blue Screen Nightmare SP2 Prescott CPU Soyo Motherboard

[Guest]

I have updated to SP2 and everyday I get at least one blue screen. In Event
Viewer Log I get a different error message every time, not consistantly the
same error message so it appears to be erroenous. I know about the SP2
Prescot issue and have updated the latest Bio for my Soyo P4I865PE
motherboard but still get the blue screens. I have rebuilt this system at
least 5 times in the last month, each time completly formatting the hard
drive and starting fresh.
I got so frustrated that I decided to just rebuilt it back to SP1a which is
what my XP Home CD is but even with that I still get the blue screen every
once a couple of days. It's like SP2 is still lurking out there somehow. I
did not have any problems with this unit before upgrading to SP2. I did add
a DVD burner but just to rule that out, I pulled it out of the system and
still had the occassional blue screen.
I build about 2 XP systems a month with clients purchasing their own retail
version of MS XP Home and never had any problems like I am having with this
unit.
ANY IDEAS? The Blue Screen seems to come more frequently with MS Office
2003 installed on top of SP2. Only other programs installed is Norton 2003.
Please HELP.
Bill K.

 

[Cari \(MS-MVP\)]

Oh triplicate posting.

Please see my response to you first posting in xp.hardware, not my note in
xp.help_and_support.

 

[Guest]

Cari, I appreciate your help but you act as if you are the only one posting
in this newsgroup. It isn't "triplicate posting" if I am posting on diferent
thread topics when in fact this issue spreads across several topics in this
newsgroup. Not everyone that could be helpful reads all of the SP2 threads
as you appear to do, so that is the reason for the multible posting. This
may not be a SP2 problem. It just appears that way now.
I thank you for your helpful reply that you posted in the XP Hardware
thread, but I am hoping someone over here may have had the same problem I am
having and they only frequent this thread. Sort of like fishing..... if you
don't get a bite in your favorite fishing hole, it might be time to find a
new one. I hope you can understand.
Bill

 

[Tim]

I have no idea what you have tried to date, so I'll start at the beginning.

First thing is to test basic stability of the CPU and RAM. You should also
check the PSU voltages and CPU temp in the BIOS while in there.

What were the various STOP codes that you experienced so far? You should be
able to see them in the System Event Log (under Administrative Tools).

Download memtest86 from memtest86.org and follow the instructions there for
creating a boot floppy or CD. Run the test for quite some time (overnight is
a good idea). If you get 1 error, then no OS will run OK.

If you get errors, then there could be a multitude of reasons. On the
assumption that the RAM is actually OK- it usually is - you will need to
adjust the timings in the bios. Before doing that I would follow the cmos
reset procedure which should be in the manual with your motherboard. Note
the settings in the bios before you do this procedure as it will reset
everything. Then go into the bios and Load Setup Defaults (or whatever they
call it). Re-enter the parameters you noted.

How much memory do you have? If you have more than 1 stick, you may wish to
pull out all but 1 stick leaving the stick that is furthest away from the
CPU in and re-running memtest86. If you have more than 2 sticks, then there
are often special notes in the motherboard manual about what bios settings
to use. EG often it may say to reduce the Command rate from 1T to 2T or the
FSB from 400 to 333. Check the details in the manual.

That's enough for now - if you system passes the memtest86 after a lenthy
run then obviously it may be something else.

When you post back - please let us now full details of how much RAM, what
type, what slots it is in, your PSU rating - check the label on the side and
note the Make and Model, claimed watts then Amps per Volt.

It is a good idea to check the voltages and temparature in the bios - a
struggling PSU is often characterised by low voltage on 1 or more of the PSU
lines. An overtemp CPU can cause all sorts of issues so check and report
back with CPU temp. If the CPU temps seems high (over 70c *is* high with an
ambient of 21c) then try testing the system with the side off the case and
check the temp in the bios then. It is quite common for systems as they get
older for the CPU fan to clagg up and overheat. PSU's fail very often and
often also degrade causing such issues. If you have a spare PSU try it out
if the voltages are not close to specification (5% is the limit).

There is a soyo specific news group in alt.comp.periphs.mainboard.soyo -
sometimes there are bios specific issues so perhaps post over there also and
see what the 'local' experts have to say.

Before you post such a request it is prudent to include the full
specification of your system - PSU, RAM, CPU, Motherboard & Revision etc.
Include the STOP codes as well.

- Tim

 

[Ron Martell]

I have updated to SP2 and everyday I get at least one blue screen. In Event
Viewer Log I get a different error message every time, not consistantly the
same error message so it appears to be erroenous. I know about the SP2
Prescot issue and have updated the latest Bio for my Soyo P4I865PE
motherboard but still get the blue screens. I have rebuilt this system at
least 5 times in the last month, each time completly formatting the hard
drive and starting fresh.
I got so frustrated that I decided to just rebuilt it back to SP1a which is
what my XP Home CD is but even with that I still get the blue screen every
once a couple of days. It's like SP2 is still lurking out there somehow. I
did not have any problems with this unit before upgrading to SP2. I did add
a DVD burner but just to rule that out, I pulled it out of the system and
still had the occassional blue screen.
I build about 2 XP systems a month with clients purchasing their own retail
version of MS XP Home and never had any problems like I am having with this
unit.
ANY IDEAS? The Blue Screen seems to come more frequently with MS Office
2003 installed on top of SP2. Only other programs installed is Norton 2003.
Please HELP.
Bill K.

Random error message patterns most often have a hardware related
cause. Errors caused by software, including the operating system
software, tend to be consistent.

So I would focus on the hardware end initially. Is there any
consistency in the timing of these error message, especially with
regard to the time elapsed between powering up the computer and the
first instance of an error.

And as always the complete *verbatim* text of the error message,
including the STOP code and the 4 parameters that follow it, is
invaluable in terms of pinpointing the underlying cause of an error.
So if you can provide this additional detail it might be helpful.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

 

[Torgeir Bakken \(MVP\)]

Cari, I appreciate your help but you act as if you are the only one posting
in this newsgroup. It isn't "triplicate posting" if I am posting on diferent
thread topics when in fact this issue spreads across several topics in this
newsgroup. Not everyone that could be helpful reads all of the SP2 threads
as you appear to do, so that is the reason for the multible posting. This
may not be a SP2 problem. It just appears that way now.
I thank you for your helpful reply that you posted in the XP Hardware
thread, but I am hoping someone over here may have had the same problem I am
having and they only frequent this thread. Sort of like fishing..... if you
don't get a bite in your favorite fishing hole, it might be time to find a
new one. I hope you can understand.
Bill

Hi,

If you absolutely feel the need to post to several newsgroups, you
should crosspost instead of multiposting as you have done.

More about this here:

What is the accepted way to share a message across multiple newsgroups?
http://smjg.port5.com/faqs/usenet/xpost.html

and

Multiposting vs Crossposting
http://www.blakjak.demon.co.uk/mul_crss.htm

and

Please don't multi-post.
http://www.aspfaq.com/etiquette.asp?id=5003

 

[Guest]

Thanks for the info, will comply.
Bill K.

Hi,

If you absolutely feel the need to post to several newsgroups, you
should crosspost instead of multiposting as you have done.

More about this here:

What is the accepted way to share a message across multiple newsgroups?
http://smjg.port5.com/faqs/usenet/xpost.html

and

Multiposting vs Crossposting
http://www.blakjak.demon.co.uk/mul_crss.htm

and

Please don't multi-post.
http://www.aspfaq.com/etiquette.asp?id=5003



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

 

[Guest]

Here is the latest error code:

BCCode : 1000000a BCP1 : 00010000 BCP2 : 0000001C BCP3 : 00000001

BCP4 : 804E163C OSVer : 5_1_2600 SP : 2_0 Product : 768_1

In Event Viewer I get this errorâ€

Error code 1000000a, parameter1 00010000, parameter2 0000001c, parameter3
00000001, parameter4 804e163c.

Error ID: 1003

Category: (102)

I have 6 minidump files if you would like me to email them to you.
I have updated to latest March 2005 NVIDIA VIDEO driver as well as latest
Intel chipset drivers for the motherboard, and I have ran the Windows Memory
Diagnostic test with no errors.
I'm completely stumped on this. Everything on this Soyo P4I865PE system is
thess than a year old.
Thanks for any help you can give, Bill Kellum

 

[Guest]

Here are the latest error messages:
Error code 1000000a, parameter1 e1507404, parameter2 00000002, parameter3
00000000, parameter4 8056b7fd.

Error code 0000000a, parameter1 8057c682, parameter2 00000002, parameter3
00000000, parameter4 8057c682.

Error code 0000000a, parameter1 8057d3b5, parameter2 00000002, parameter3
00000000, parameter4 8057d3b5.

Error code 1000000a, parameter1 e1544c1c, parameter2 00000002, parameter3
00000000, parameter4 8056b7fd.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a
(0x8057c682, 0x00000002, 0x00000000, 0x8057c682). A dump was saved in:
C:\WINDOWS\MEMORY.DMP.

Error code 1000000a, parameter1 8057d3b5, parameter2 00000002, parameter3
00000000, parameter4 8057d3b5.

It appears to be more consistent now. I turned on VERIFIER and this is what
I got. I had to turn verirfier off in order to boot normally into XP even
when selecting only non-microsoft drivers. I have the latest minidump files
if anyone is interested in looking into this.
Thanks so much.
Bill Kellum

 

[Ron Martell]

Here are the latest error messages:
Error code 1000000a, parameter1 e1507404, parameter2 00000002, parameter3
00000000, parameter4 8056b7fd.

Error code 0000000a, parameter1 8057c682, parameter2 00000002, parameter3
00000000, parameter4 8057c682.

Error code 0000000a, parameter1 8057d3b5, parameter2 00000002, parameter3
00000000, parameter4 8057d3b5.

Error code 1000000a, parameter1 e1544c1c, parameter2 00000002, parameter3
00000000, parameter4 8056b7fd.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a
(0x8057c682, 0x00000002, 0x00000000, 0x8057c682). A dump was saved in:
C:\WINDOWS\MEMORY.DMP.

Error code 1000000a, parameter1 8057d3b5, parameter2 00000002, parameter3
00000000, parameter4 8057d3b5.

It appears to be more consistent now. I turned on VERIFIER and this is what
I got. I had to turn verirfier off in order to boot normally into XP even
when selecting only non-microsoft drivers. I have the latest minidump files
if anyone is interested in looking into this.
Thanks so much.
Bill Kellum

See MVP Jim Eshelman's STOP errors web page at
http://www.aumha.org/win5/kbestop.htm and click on the "0A: IRQL Not
Less/Equal" link in the left side column. That will take you to a
section with links to a number of specific articles regarding this
error.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm