Windows Xp crash

Have you tried running a RAM test? That would be my first port of call for something like that: http://www.memtest86.com/

Aha! I remember i got this issue with my desktop two years ago. You memory is going bad. That is what is meant by the "memory changed" error. I am not sure what the other error means for certain. I might be that either you processor or motherboard is going also.

BTW, did you do anything to it lately?

I have installed temperature monitoring software, but it worked on it before, there is also a UPS connected

Hi Acollyer, will this mem test do?

http://hcidesign.com/memtest/download.html

I'd be more inclined to use memtest86 from my link above, as it's a free bootable CD you can run outside of XP.

The memtest app at the link you posted is for windows only, so it's probably not the best choice in this case as you're just interested in testing your physical hardware/RAM - not Windows itself.

ok i have made a boot disk, i will run it tomorrow  morning and let you know how it goes, thanks for the help.

Hi doing mem test that will help u
one thing is system virus free sometimes bcoz of virus also the system restarts
even i had same problem
if that is the case use disk manager and delete all partitions.
then create new partitions
if u just format u r drives it wont work
bocz some virus gets stored in boot sectors which will trouble u

Hi, I am running the memtest86 as we speak, it is very slow though, its been going for over an hour, no errors so far. Has anyone been able to take a look at the minidump folder I attached? I am not sure how to analyze it myself so was hoping mabey someone could?

Thanks

The memory tested without errors, I am also getting an error on boot up saying domething like "the following VDs are not configured 00,01,02"
Has anyone been able to take a look at the minidump folder I attached?

Thanks

I've attached an analysis of the minidump you posted. Maybe this section of it may throw some light on the problem:


FAULTING_THREAD:  88e953f8

FAULTING_IP:
b5mp2fhd+c20
bfddac20 ??              ???

IMAGE_NAME:  b5mp2fhd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  43a1fe68

MODULE_NAME: b5mp2fhd

FAULTING_MODULE: bfdda000 b5mp2fhd

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  BarcoPnPSetup.e



A few things to see here - "graphics_driver_fault", and the process "BarcoPnPSetup.exe". There is also a warning at the beginning of the analysis:
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.



I would therefore first boot into Safe Mode and uninstall the device from Device Manager, reboot and install the latest driver from your graphics card manufacturer (Barco?). If that doesn't work, I would attempt using a program like Autoruns (from Microsoft/Sysinternals) to stop BarcoPnPSetup from running. Finally, I'd recommend trying a different graphics card in your PC as your current one my be failing (although I suspect it is actually just a driver issue.)
xpcrash.txt

ok, thats not a problem if i just need to reinstall the video card, though is this definetly why I am getting the error messages, is it possible it crahed once becasue of this (i.e. CUSTOMER_CRASH_COUNT:  1) and the reason it keeps restartring with the error message I described is because of something else?

Thanks for the analysis!!

I'd say the minidump analysis is a strong indication of what the problem is, although I don't think it explains the "amount of RAM has changed" problem... Perhaps your CMOS battery needs replacing? This wouldn't cause your computer to restart, however.

I'm not sure, but I think CUSTOMER_CRASH_COUNT is used when you get many BSODs in succession of the same type/cause, so instead of creating another minidump, Windows just increments that counter. So if you have a BSOD of a different nature in between, the counter is reset and stored in a new minidump file.

Looking good so far with the new drivers, no crash in the last hour, I have set up an alert to let me know if it crashes over night, so i will monitor it before closing this off. Looks like it may work tho, thanks for all the help!

No crash yet and no more error messages so far so I will close the case for now, hopefully that will see this issue resolved. Thanks for all the help, would never have guessed the video card without your help!
Thanks again!