The crashes you sent are old and I don't remember how many you can do with BlueScreenView, so I would whack the old crash dumps so we only look at the ones that happen now. You could just move the old dumps someplace else, but get rid of the old ones somehow by moving or deleting them.
The folder where the crash dumps are is here:
If you want, just leave the last 2 or 3 most recent. We need ones that happened lately, not last year.
Delete all the .dmp files in that folder, now recreate your situation, then run BlueScreenView again. You can look a the file names and dates and they will tell you the date of the dumps. This is just to avoid confusion.
High pitched noises + games sometimes means heat (too much). Windows has crashed or is about to! Systems that are not specifically designed with games in mind can overheat because of the more intense system demands (especially video).
They were not built with games in mind, but folks put intense games on them sometimes later and expect thing to work.
If it is a particular game, what is the name and we can look it up and compare the minimal requirements against your system specs.
Sometimes there is no BSOD when things get to hot - XP just stops/crashes and you have to reboot and then it might work for a while or sometimes you can let things cool off and it will work again - for a while. If you are not playing games, things are fine - for a while.
Have you started playing any newer game lately since the crashes? Any of that sound familiar? Are games a new thing for you? How are things when your system has been switched ff for a while?
Desktop or laptop (we'll find out shortly). Have you done any dust hygiene on it lately/ever to be sure it is sufficiently ventilated?
Have any hardware oriented changes been made to the system since it worked? RAM, video card, storage (hard disks, USB devices), hardware drivers, device drivers?
Disable Automatic restart on system error to stop the error on your screen so you can see it:
Right click My Computer, Properties, Advanced, Startup and Recovery Settings.
In the System failure section, untick the Automatically restart box, OK, OK.
Here are some BSOD blue screen of death examples showing information you need to provide:http://www.codinghorror.com/blog/images/Windows_XP_BSOD.pnghttp://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg
Send the information pointed to with the red arrows (3-4 lines total). Skip the boring text unless it looks important to you. We know what a BSOD looks like, we need to know the other information that is specific to your BSOD.
Then it would be good to catch a BSOD when it happens and find out the information on the screen, it sill be the same as BSV, but you can learn how to configure your system to do this anyway (what if there was no BSV program!).
Provide system information:
Click Start, Run and in the box enter:
Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste back here.
There would be some personal information (like System Name and User Name) or whatever appears to be only your business that you can delete from the paste.
For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information.
Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD).
Memtest86+ is a more up to date version of the old memtest program and they are not the same.
The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program.
If even a single error is reported that is a failure and should make you suspicious of your RAM.
If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick. Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system.
Sometimes, reseating the RAM in the slots will relieve the error but any failure is still cause for suspicion.
The file and instructions are here:http://www.memtest.org/
If you schedule chkdsk to run on the next reboot you need to be sure it does run properly (not just think
it ran properly), you will not be able to see a log of the results, but the results will be in the Event Log:
When chkdsk runs automatically on a reboot, the results are saved in the Event Viewer Application log.
To see the Event Viewer logs, click Start, Settings, Control Panel, Administrative Tools, Event Viewer.
A shortcut to Event Viewer is to click Start, Run and in the box enter:
Click OK to launch the Event Viewer.
Look in the Application log for an event sourced by Winlogon, something like:
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.
4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.
Windows has finished checking your disk.
Please wait while your computer restarts.