"Pat" <pat_whitted@hotmail.com> wrote in message
news:ef70ca17-3337-4e67-8ff8-e9796736446b@j33g2000pri.googlegroups.com...
> So, I've rebuilt the system - AGAIN, and per TVeblen's recommendation,
> I've not installed SP3. It's better than 24 hours since I finished the
> rebuild, and the system has been stable with no errors logged in
> either the System or Applications event log.
<snip>
One other note: I have always had Automatic Updates turned off in XP and I
turn it off for everyone's puter I am asked to look at. IMHO, allowing your
OS to be changed without user input is insane. I manually check the updates,
using the Custom Install feature, and I read the description of every update
they want to install. Most all of the security updates are fine, but there
are some windows updates that don't apply to my hardware/box or my OS setup.
I hide these. Although probably a bit OCD, I only install 3 updates at a
time and then give it a day. If my puter were "hosed" after installing 16
updates, going back would be a real headache. When I was young I installed a
video card driver update from WU (stupid,stupid,stupid). I uninstalled, did
a system restore, and was back and a tiny bit smarter in 15 minutes. You can
also do a web search on any update just by typing in the MS or KB number
under groups. If that update is causing problems you will get some hits. You
might also try a search including your processor model number plus SP3 and
see what comes up. You should also post this problem to one of the microsoft
XP groups.
I'm going to take a look at my updates right now. It's been over a month. I
bet SP3 will be there. Maybe some rainy day I'll install it, providing I've
finished the suduko and clean the toilet.
In article <2oqt345q8pq53hnj7q0r4tb4oblghu3qao@4ax.com>, overload@spam.ftc.gov wrote:
>On Thu, 29 May 2008 05:55:32 -0700 (PDT), Pat
><pat_whitted@hotmail.com> wrote:
>
>>On May 29, 1:42*am, overl...@spam.ftc.gov wrote:
>>> On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat
>>>
>>> <pat_whit...@hotmail.com> wrote:
>>> >Ever since XP SP3 came out, my system has been hosed.
>>>
>>> <snip>
>>>
>>> >AMD Athlon 64 X2 Dual 6000+
>>>
>>> There are known problems with SP3 and AMD processors.
>>> There are known problems with SP3 and Norton Antivirus.
>>>
>>> I don't have either of these, so I wasn't really paying attention, but
>>> you can check at *WindowsSecrets.com. Look for the free edition with
>>> date 5/29/08.
>>>
>>> "The problems with XP SP3 include AMD-based Hewlett-Packard desktop
>>> computers constantly rebooting and Symantec antivirus products
>>> developing strange behaviors."
>>>
>>> There may be other problems as well, but I think this has you covered.
>>>
>>> Jim
>>
>>Thanks for the info Jim, but I'm neither running an HP nor NAV. My
>>system is a beige box, with Windows installed from the original
>>Windoze CD instead of a manufacturer image.
>
>The problem applies to all AMD machines, not just HP. There's some
>file that's used only for intel machines that gets loaded by mistake.
>The details are in the article.
>
>Jim
>
Way to go SP3 beta testers!!!!!!
1. By 6 the morning of the 31st, the system had locekd up with a BSOD:
PAGE_FAULT_IN_NONPAGED_AREA; STOP: 0x00000050 (0x8ACBB778, 0x00000000,
0xBA655721, 0x00000000); NTFS.SYS - Address BA655721 Base at BA635000,
DATESTAMP 45CC56A7.
Believing this could be related to some suspect Kingston memory I
have, I yanked that stick out, leaving me 2-1GB Crucial Ballistix
sticks in place. The system restarted just fine. That was Sunday
night, the 2nd...
2. This morning, I tried to access the system remotely, and it didn't
respond. When I got home tonight, there was a new BSOD: AN ATTEMPT WAS
MADE TO WRITE READ-ONLY MEMORY; STOP: 0x000000BE (0xB7F3C313,
0x0E4FC121, 0xBACDBCE4, 0x0000000B); KS.SYS - Address B7F3C313 base at
B7F2D000, DATESTAMP 41107ef8.
From what I can tell, this suggests an issue with the video driver. I
have the latest driver from NVidia, which is actually MS signed!
BTW - I'm still running at SP2, with autoupdate disabled.
Any suggestions? This has been going on for a couple months now, and
is getting quite tiring!
BTW - Forgot to mention that it seems the system is good for about 36
hours before throwing a BSOD. It doesn't seem to be tied to a time of
day, just duration that the system has been up and running.
"Pat" <pat_whitted@hotmail.com> wrote in message
news:d94ccf88-eddc-4913-8ae4-69b2e6fe6b2d@p39g2000prm.googlegroups.com...
> BTW - Forgot to mention that it seems the system is good for about 36
> hours before throwing a BSOD. It doesn't seem to be tied to a time of
> day, just duration that the system has been up and running.
That is very strange. It seems to me that something is trying to write to
the video memory in both cases, and that is beyond my experience. It could
also mean the video card is going bad and the errors occur when writing
video data to it's memory, but I'm just guessing.
I recall having a BSOD adventure in W98 that would occur like clockwork-
exactly 12 hours, that turned out to be a windows accessory (can't remember
which one - FindFast?) that was scheduled to start every 12 hours. Turned it
off and the problem went away.
Hmmm. Guess I'll try pulling the eVGA card and use the video on the
MoBo to see if that gets me past this 36 hour mark. I'l also see if
the event log shows something consistent before the system locks up.
Thanks TVeblen!
On Jun 4, 4:34*am, "TVeblen" <killtherob...@hal.net> wrote:
> "Pat" <pat_whit...@hotmail.com> wrote in message
>
> news:d94ccf88-eddc-4913-8ae4-69b2e6fe6b2d@p39g2000prm.googlegroups.com...
>
> > BTW - Forgot to mention that it seems the system is good for about 36
> > hours before throwing a BSOD. It doesn't seem to be tied to a time of
> > day, just duration that the system has been up and running.
>
> That is very strange. It seems to me that something is trying to write to
> the video memory in both cases, and that is beyond my experience. It could
> also mean the video card is going bad and the errors occur when writing
> video data to it's memory, but I'm just guessing.
> I recall having a BSOD adventure in W98 that would occur like clockwork-
> exactly 12 hours, that turned out to be a windows accessory (can't remember
> which one - FindFast?) that was scheduled to start every 12 hours. Turned it
> off and the problem went away.
"Pat" <pat_whitted@hotmail.com> wrote in message
news:a6a7897c-855a-4083-9b4b-56bd0e7a4f56@y21g2000hsf.googlegroups.com...
Hmmm. Guess I'll try pulling the eVGA card and use the video on the
MoBo to see if that gets me past this 36 hour mark. I'l also see if
the event log shows something consistent before the system locks up.
Thanks TVeblen!
Whoa! New information.
You've got onboard video and you've installed a video card. I've read of a
few problems that occur with that setup if not done properly. You could have
competing drivers, resource conflicts, or BIOS issues. Any of which would
explain the paging errors. Installing SP3 could have awakened a beast. The
trick, I have read, is to disable the onboard video in BIOS while at the
same time removing it and it's drivers from Windows before installing the
new Video card and it's drivers. My head hurts just thinking about it.
That's providing that this is your problem, which you can't be sure of right
now.
Hopefully someone more experienced than I with that setup will come along
and concur and possibly advise you with a step by step.
> Whoa! New information.
> You've got onboard video and you've installed a video card. I've read of a
> few problems that occur with that setup if not done properly. You could have
> competing drivers, resource conflicts, or BIOS issues. Any of which would
> explain the paging errors. Installing SP3 could have awakened a beast. The
> trick, I have read, is to disable the onboard video in BIOS while at the
> same time removing it and it's drivers from Windows before installing the
> new Video card and it's drivers. My head hurts just thinking about it.
> That's providing that this is your problem, which you can't be sure of right
> now.
> Hopefully someone more experienced than I with that setup will come along
> and concur and possibly advise you with a step by step.
Funny you should mention that! I did have the onboard card disabled in
BIOS. BUT, I HAD installed all the drivers that had come with my MoBo,
which included the ATI drivers. Of course, my vid card is nVidia. SO -
I actually ended up doing what you suggested - removed my nVidia
drivers, removed the ATI drivers, then reinstalled the nVidia drivers.
It's been up since about 10:30 last night. We'll see if I make it past
the magic 36 hour mark!
Well, new info: This afternoon I found a new BSOD: A process or thread
crucial to system operation has unexpectedly exited or been
terminated. STOP: 0x000000F4 (0x00000003, 0x88EA9410, 0x88EA9584,
0x805D11F8)
Now, when I attempt to start this box, I just get non-stop, slow
beeps, not even pixie boot. Methinks I have a dead MoBo, and this was
the issue all along!
Re: XP Pro System is hosed 
Linear Mode
