Blue Screen Plague

[!TG]

I have an XP Pro machine that is blue screening about once a week, sometimes
more often sometimes less.
I don't know how to evaluate the system to determine what's causing it, the
Microsoft response says "hardware failure is the most likely cause".
Everything on this system is less than 3 weeks old.
I tried to post the minidump file, but it said the article was too large, so
let me know if I need to put it up for download somewhere.
There is also a more recent one 8/10. Let me know if it helps to send it..
Thank you so much for any help you can be, this is very frustrating.
Here are a couple event log entries:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/7/2006
Time: 8:11:23 AM
User: N/A
Computer: ALPHA5
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f
(0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini080706-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/7/2006
Time: 8:12:26 AM
User: N/A
Computer: ALPHA5
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3
00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 64 2c 20 00000d,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

 

[Malke]

I have an XP Pro machine that is blue screening about once a week,
sometimes more often sometimes less.
I don't know how to evaluate the system to determine what's causing it,
the Microsoft response says "hardware failure is the most likely cause".
Everything on this system is less than 3 weeks old.
I tried to post the minidump file, but it said the article was too large,
so let me know if I need to put it up for download somewhere.
There is also a more recent one 8/10. Let me know if it helps to send it..
Thank you so much for any help you can be, this is very frustrating.
Here are a couple event log entries:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/7/2006
Time: 8:11:23 AM
User: N/A
Computer: ALPHA5
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f
(0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini080706-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/7/2006
Time: 8:12:26 AM
User: N/A
Computer: ALPHA5
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3
00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 64 2c 20 00000d,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

I just answered this in your first post. Please keep posts about one subject
in one thread.

Read my previous reply for more details, but briefly you have hardware
issues. If the machine is under warranty, take it back.

Malke