constant application crashes

By A N D ·
i am running a pc with win xp running on an intel p4(1.6 ghz). recently win xp has become so unstable that almost all applications (including simple ones like notepad) constantly crash within about 3 mins of launching them. most web based apps (firefox 2 & 3, ie7, opera, safari) crash immediately on launching (it took 14 attempts to connect to this site using firefox 2).

does anyone have an idea on what might be the problem? and what should i do to atleast make the system usable?

i have tried formatting my whole hard drive & reinstalling xp but it did not solve anything (so i dont think its a virus, worm, etc).

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Could be several things...... Details needed

by ThumbsUp2 In reply to constant application cras ...

The first thing that comes to mind is bad RAM or overheating. But, without knowing what codes you're getting when things crash, it's pretty tough to diagnose.

Collapse -

probably software problem

by A N D In reply to Could be several things.. ...

how can i tell if its a problem with ram? are there any freeware apps available to know about that?

also i have win 98 also installed. it works fine... so i dont think it has anything to do with hardware. probably some device driver bugs. but my system is pretty old (8 yrs) so there are no updates for the drivers.

how do i get the exact error codes?

Collapse -

2 things

by seanferd In reply to probably software problem

Error codes are given when the system crashes. Write them down. Or, when you reboot, get the reports from the event logs.

How much RAM do you have?

Test memory

Collapse -

error code & ram size

by A N D In reply to 2 things

i have a total of 512 mb sd ram ( 256*2 )
however it is shared with video ram hence 480 mb is available.

the error appears on a blue screen saying
it gives a few mem addresses: 0x00000020, 0xe1b19890,0xe1b19bb8 & 0x0c650074

Collapse -


by ThumbsUp2 In reply to error code & ram size

Usually, the BAD_POOL_HEADER stop error code is 0x00000019 and then lists 4 addresses between parenthesis. If this is what you're getting and didn't tell us correctly, your problem is in your BIOS.

Disable "System BIOS Shadowing" in your BIOS options. It may also be "System BIOS Cacheable" or other similar options.

This can create the exact same problem you're having, although it could very well be something else such as memory. You can test your memory with (Let it run for several hours).

But, it could also be caused by external equipment plugged into the computer and not having the correct drivers installed.

With the system turned off, unplug ALL external devices such as scanners, printers, etc..., then turn the system on and let it boot. If the problem has gone away, suspect the scanner first, then other devices. Using the correct drivers will fix the problem, once you isolate which one it is.

Collapse -

Found some more on BAD_POOL_HEADER

by ThumbsUp2 In reply to re: BAD_POOL_HEADER

From a MS TechNet article:

User Action:

If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows. For information about the hardware, contact the supplier. If you are installing Windows for the first time, check the Windows system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows. If Windows is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

Collapse -

problem with display adapter?

by A N D In reply to Found some more on BAD_PO ...

if hardware compatibility is a problem then i think my display adapter is the culprit. my system has S3 Graphics ProSavageDDR as Display adapter. its very difficult to find proper drivers for it to work in win xp. i think i could check by using a seperate graphics card.

also there may be 2 simultaneous problems on the system. one takes me to the "blue screen of death"(the bad_pool_header error) while the other crashes all applications.

i sincerely thank u for ur help!

Collapse -

when I had this issue

by Slayer_ In reply to constant application cras ...

It was cause my mobo was giving low voltage to my CPU. There was a BIOS update to my mobo for this problem, however we discovered in the shop that... if we tried to apply it, it said that that update was already applied, so when we tried to go back a version, same message... So we tried to simply reflash it with the newest, it wouldn't take the flash... we figured the board was just crap and replaced it. With same CPU but a new board, my system speed almost tripled :).

Collapse -

Download and make a copy of

by OH Smeg Moderator In reply to constant application cras ...

The Ultimate Boot CD available here

Then enter your BIOS and set it to boot off the Optical Drive and insert the Ultimate Boot CD into your optical Drive and boot off it. Then run a full spread of Diagnostics on your Hardware including the HDD Makers Test Utility, CPU and RAM Tests to make sure that you have no Hardware problems. If you have any Hardware problems repair as required to fix the system.


Related Discussions

Related Forums