Blue Screen Nightmare SP2 Prescott CPU Soyo Motherboard

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.
I now have problems everyonce in a while in Win Update site... while checking
for updates I will get an error message and IE will close. If I open IE
again and go to WU, everything is fine and it lets me know if there are any
updates available. Go figure??
Please HELP.
Bill K.

Hi Bill,

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights

"BILL KELLUM" <> wrote in message
news295AF7E-3690-47E9-AD23-...
>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.
> I now have problems everyonce in a while in Win Update site... while
> checking
> for updates I will get an error message and IE will close. If I open IE
> again and go to WU, everything is fine and it lets me know if there are
> any
> updates available. Go figure??
> Please HELP.
> Bill K.
>

"BILL KELLUM",

Without going into a big, long, laborious explanation you may not care about --
blue screens happen when memory has been "trampled on" that should not have been
changed by anything else. This is done, eventually, at the Kernel level in the
NT/Windows 2000/XP/2003 architecture. That being said, very little code runs at
the kernel level except drivers. Applications that run at the OS level are in
their own protected memory space and CANNOT write over each other. They can,
however, call kernel level code erroneously or improperly and cause the faults
of which you speak.

Verify that all drivers you are running are digitally signed by Microsoft, and
you should dramatically lower the number of "blue screen" scenarios you are
encountering.

Sincerely,

Pat Walters [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights. Use
of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

"BILL KELLUM" <> wrote in message
news295AF7E-3690-47E9-AD23-...
>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.
> I now have problems everyonce in a while in Win Update site... while checking
> for updates I will get an error message and IE will close. If I open IE
> again and go to WU, everything is fine and it lets me know if there are any
> updates available. Go figure??
> Please HELP.
> Bill K.
>

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

"Pat Walters [MSFT]" wrote:

> "BILL KELLUM",
>
> Without going into a big, long, laborious explanation you may not care about --
> blue screens happen when memory has been "trampled on" that should not have been
> changed by anything else. This is done, eventually, at the Kernel level in the
> NT/Windows 2000/XP/2003 architecture. That being said, very little code runs at
> the kernel level except drivers. Applications that run at the OS level are in
> their own protected memory space and CANNOT write over each other. They can,
> however, call kernel level code erroneously or improperly and cause the faults
> of which you speak.
>
> Verify that all drivers you are running are digitally signed by Microsoft, and
> you should dramatically lower the number of "blue screen" scenarios you are
> encountering.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights. Use
> of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm"
>
> "BILL KELLUM" <> wrote in message
> news295AF7E-3690-47E9-AD23-...
> >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.
> > I now have problems everyonce in a while in Win Update site... while checking
> > for updates I will get an error message and IE will close. If I open IE
> > again and go to WU, everything is fine and it lets me know if there are any
> > updates available. Go figure??
> > Please HELP.
> > Bill K.
> >
>
>
>

"BILL KELLUM" <> wrote in message
news:20C0BF53-49FE-4103-8B12-
....
> Here are the latest error messages:
> Error code 1000000a, parameter1 e1507404, parameter2 00000002, parameter3
> 00000000, parameter4 8056b7fd.

> I have the latest minidump files if anyone is interested in looking into this.

Did you see Joshua's offer to you?

FWIW I would guess that parameter 4 is an address inside
a driver. FYI you can use the pstat -s command line tool
to get a list of drivers and their load addresses. You may find
that the 8056... addresses give you a clue using that display.

Also you can get a summary of the contents of a minidump
by using the dumpchk command line tool. Again, I suspect
the most useful thing that you might get from it is a better
association of one of those parameter addresses with a module
name, which in turn should give you a driver and device to focus
your attention on.

Here is a reference for you about the suggested techniques:

<title>KB314084 - How to gather information after a memory dump in Windows XP</title>

(TechNet search for
pstat dumpchk kbwinxp*
)


HTH

Robert Aldwinckle
---

Yes, we have been corresponding through email. We are still investigating
it, but it seems to be ZoneAlarm that is causing his BSOD. We are going to
see if there is any updates and try an uninstall/reinstall since there are
some users that report that fixing them.

Joshua Smith
OpenGL Test Lab
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights


"Robert Aldwinckle" <> wrote in message
news:...
> "BILL KELLUM" <> wrote in message
> news:20C0BF53-49FE-4103-8B12-
> ...
>> Here are the latest error messages:
>> Error code 1000000a, parameter1 e1507404, parameter2 00000002, parameter3
>> 00000000, parameter4 8056b7fd.
>
>> I have the latest minidump files if anyone is interested in looking into
>> this.
>
> Did you see Joshua's offer to you?
>
> FWIW I would guess that parameter 4 is an address inside
> a driver. FYI you can use the pstat -s command line tool
> to get a list of drivers and their load addresses. You may find
> that the 8056... addresses give you a clue using that display.
>
> Also you can get a summary of the contents of a minidump
> by using the dumpchk command line tool. Again, I suspect
> the most useful thing that you might get from it is a better
> association of one of those parameter addresses with a module
> name, which in turn should give you a driver and device to focus
> your attention on.
>
> Here is a reference for you about the suggested techniques:
>
> <title>KB314084 - How to gather information after a memory dump in Windows
> XP</title>
>
> (TechNet search for
> pstat dumpchk kbwinxp*
> )
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>