Help! I Recieve a BSOD code 0xC5

[Guest]

Help! I have recieved a BSOD code 0xC5 (Stop error?). Afterwards, my computer
has CONSIDERABLY slowed down, and after a while shows the BSOD again, often
with differing stop codes, like 0xC9. I used System Restore, and that fixed
the problem. However, I recieved a BSOD when shutting down my computer (Might
have been D1, not sure), and today I recieved a 0xC5 again. I decided to go
to Microsoft KB, and search C5. I found an article, but it says it only
applies to NT and 2000. It also said that it causes totally unrelated stop
codes as well, so I didn't bother to look up the other codes. I don't want to
do any of the things the article about C5 recommends, because it says it only
applies to 2000 and NT, and therefore I could damage my Windows XP
Professional computer.

I am using Windows XP Professional, SP2.

I have 2 hard drives, one 8.49 GB large, with 458 MB free, and the other
5.99 GB large, with 2.73 GB free. My computer has 224 MB of RAM, 448 MHz,
Intel Pentium III. I had never recieved any problems before (even though this
computer may be below the minimum requirements)

If you would like any further information, please comment.

Can you tell me how to fix this?

 

[Rich Barry]

Brian, check this site. Scroll down the left and right columns for the
Stop Codes
http://www.aumha.org/win5/kbestop.htm

 

[Guest]

I've tried Driver Verifier, but whenever i click on one of the options and
click next, it immedaitely says something along the lines of "You must reboot
your computer for the settings to take affect". It doesn't show me any info
whatsoever.

And, I can't seem to find anything called gflags on my computer.
Alternatively, I've tried doing the registry war of enabling the Special Pool
Feature. I don't recieve anymore stop codes, but the computer has slwoed down
DRAMATICALLY. Not as much as before, but slow enough that it is impossible to
do anything.

P.S: The computer seems to run fine when in safe mode, so its probably a
driver issue.

Anyway, thanks, and I will instead use sigverif and manually disable
non-signed drivers one by one and see which one is the source of the problem.

Thank you very much!!!!