The Unknown P

[Guest]

Unknown,

I did as you suggested and went to the application log. Apparently the crash
is so sudden the event did not register in the app log.

I have tried running both Norton virus scan and the SP 2 install in the safe
mode and I still get a crash.

I have reformatted my disk and reloaded only basic programs and still get a
crash.

I am at a loss.

I believe that XP Pro is like NT and is graphically challenged. Any
prolonged graphic crashes the system.

I am ordering 256 MB of additional memory. Hopefully that will help. I will
also go to Cnet and try and find SpeedXP.

Any other ideas for me?

Thanks,

leeb40

 

[Malke]

Unknown,

I did as you suggested and went to the application log. Apparently the
crash is so sudden the event did not register in the app log.

I have tried running both Norton virus scan and the SP 2 install in
the safe mode and I still get a crash.

I have reformatted my disk and reloaded only basic programs and still
get a crash.

I am at a loss.

I believe that XP Pro is like NT and is graphically challenged. Any
prolonged graphic crashes the system.

I am ordering 256 MB of additional memory. Hopefully that will help. I
will also go to Cnet and try and find SpeedXP.

Any other ideas for me?

Thanks,

leeb40

Since you did not post back to the original thread or include any
references, it is hard to comment. However, from your description above
(particularly since you say you've done a clean install) I would guess
you have hardware problems. I wouldn't bother with buying more RAM
until you know your hardware is good. Also, I wouldn't bother with
something like SpeedXP. Programs like that are not needed on a healthy,
stable system. Also, installing software on bad hardware will simply
not help. Here are some hardware troubleshooting steps:

1) open the computer and run it open, cleaning out all dust bunnies and
observing all fans (overheating will cause system freezing); 2) test
the RAM - I like Memtest86 from www.memtest86.com - let the test run
for an extended (like overnight) period of time - unless errors are
seen immediately; 3) test the hard drive with a diagnostic utility from
the mftr.; 4) the power supply may be going bad or be inadequate for
the devices you have in the system; 5) test the motherboard with
something like TuffTest from www.tufftest.com. Testing hardware
failures often involves swapping out suspected parts with known-good
parts. If you can't do the testing yourself and/or are uncomfortable
opening your computer, take the machine to a good local computer repair
shop (not a CompUSA or Best Buy type of store).

Malke

 

[Alex Nichol]

I did as you suggested and went to the application log. Apparently the crash
is so sudden the event did not register in the app log.

Posting a message out of nowhere, unconnected to your previous one, so
there is no context, is going to be incomprehensible, even to the person
you had previously had a message from. Post as a 'reply to group' (not
to author) to his message to you so it has context