My computer is pissing me off

[AirportFF]

It's constantly locking up with the dreaded "blue screen of death"

I get the following error messages

bad_pool_caller (don't have the error code)

driver_irql_not_less_or_equal (stop 0x000000D1)

page_fault_in_nonpaged_area (stop 0x00000050)

and lastly 0x0000007e with no message


These all seem to happen at random times and when doing different things. I have noticed that if I am selecting multiple files with the CTRL key it seems to happen more often. I also get the IRQL message and the blue screen whenever I try to shut down or re-start my computer. There's also another odd thing, the clock keeps losing time. I don't really know at what rate, but it steadily does. I've reasearched the fuck out of this stuff and found this site

http://aumha.org/win5/kbestop.php

which helps with the identification, but no real solutions. Does anyone know of some good diagnostic software? One site suggested a kernal debugger that uses a stack trace. Whatever the fuck that is. I'm currently running XP home ed., with service pack 2

HELP!!!Or this thing will meet the fate of my desktop (ask Susan about it) :computer:

[Menace]

It's constantly locking up with the dreaded "blue screen of death"

I get the following error messages

bad_pool_caller (don't have the error code)

driver_irql_not_less_or_equal (stop 0x000000D1)

page_fault_in_nonpaged_area (stop 0x00000050)

and lastly 0x0000007e with no message


These all seem to happen at random times and when doing different things. I have noticed that if I am selecting multiple files with the CTRL key it seems to happen more often. I also get the IRQL message and the blue screen whenever I try to shut down or re-start my computer. There's also another odd thing, the clock keeps losing time. I don't really know at what rate, but it steadily does. I've reasearched the fuck out of this stuff and found this site

http://aumha.org/win5/kbestop.php

which helps with the identification, but no real solutions. Does anyone know of some good diagnostic software? One site suggested a kernal debugger that uses a stack trace. Whatever the fuck that is. I'm currently running XP home ed., with service pack 2

HELP!!!Or this thing will meet the fate of my desktop (ask Susan about it) :computer:

I have not seen an IRQ conflict with XP yet. If I had to guess, I would say check the CPU temperature or RAM. Crappy RAM can cause BSOD doing anything. You might want to download the latest drivers for your video/nic/modem/Moterboard etc.... from the manufacturer or the hardware and not Microshaft. And make sure you are virus and spyware free.

[Machinehead]

I have zero experience with xp and not much more with any other os. I can only suggest that you hide the hammer and walk away from it for a while.

I do have xp installed on another pc and used the site below to fine tune it.

http://www.blackviper.com/WinXP/winxp.htm

[Machinehead]

Also....I copied the following from Experts Exchange.



The lesson learned about this is, if you got these several types of errors randomly
or even similar ones,

0x000000C5
0x0000000a
0x00000050
0x0000008E
0x000000D1
0x0000007E

and you have everything up-to-date including the machine BIOS, probably the problem
is a defective RAM or a faulty motherboard.

Just test the memory in EXTENSIVE MODE with "Windows Memory Diagnostic". My experience
told me that other test utilities like MemTest86 or DocMemory wouldn't work properly with
some types of memory.

Of course, you may also have some other faulty hardware. Bad drivers could give one of these
errors, but usually only one.

"Windows Memory Diagnostic" could help you to define if the problem is with RAM memory or
either the motherboard or something connected to it.




ORIGINAL THREAD
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20912978.html

[RustyJake]

Machinehead, could it also be caused by overheating inside a laptop? Just wondering if he's having the problem right away, or does it happen after the computer has been on for a while?
Might be worthwhile to open the box and make sure it's free and clear of dust and that any fans are working correctly and dust free. Even reseating the ram while he's in there. It would be worth a shot.

Thanks for the links you posted Machinehead.....I didn't have them, but do now.

[AirportFF]

Machinehead, could it also be caused by overheating inside a laptop? Just wondering if he's having the problem right away, or does it happen after the computer has been on for a while?
Might be worthwhile to open the box and make sure it's free and clear of dust and that any fans are working correctly and dust free. Even reseating the ram while he's in there. It would be worth a shot.

Thanks for the links you posted Machinehead.....I didn't have them, but do now.

I attempted to open the case to clean out some of the dust bunnies and took out what seemd like a thousand screws, and couldn't get it open. Maybe I'll give it another attempt. But the fan ducts are clear........


And how do I run "windows memory diagnostic"?

[Machinehead]

I am prolly the least knowlegeable person to offer advice. I' ve only 3 years of pc experience, I'm in the construction business and I'm biker trash. :beatnik:

The only hardware probs I've experienced were with a cd-rom drive and a network card. The only real way that I would suspect a hardware problem would be to insert a different HDD and verify that the issue remains then go from there. HDD's are fairly cheap and it can always be re-used as a back-up drive, part of a raid set-up, etc..


Windows diagnostic tool:

http://oca.microsoft.com/en/windiag.asp