I would REALLY like to see MS make it so I can tell what components are responsible for some random crashes. Granted, crash frequency is infrequent, but diagnosing the cause (Memory, video card mem, other hardware, etc) is still near impossible for some those odd crashes that leave absolutely nothing in the event logs or information that is otherwise useless for me the "user". I can't help but wonder if memory is getting a bad rap here. Its would seem much more likely the more complex components would be more prone to failure than the (relatively) simple memory sticks. (History of failures seem to point to this, too as, generally speaking, complexity fails and simplicity succeeds)
(just a scan through my event log pulled these 2 prime examples)
Event Type: Error
Event Source:
Event Category: None
Event ID: 0
Date: 11/1/2005
Time: 6:27:03 PM
User: N/A
Computer: G
Description:
The description for Event ID ( 0 ) in Source ( ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 6.
Data:
0000: 3f 3f d1 2a e3 ee 92 2d ??Ñ*ãî-
0008: ae 39 d9 22 ee e9 9a e5 ®9Ù"îéå
0010: 2e 2f c1 3a f3 f1 82 3d ./Á:óñ=
0018: e9 22 8d 32 f9 f9 8a 35 é"?2ùù5
0020: 1f 1f f1 0a af bf f6 0a ..ñ.¯¿ö.
0028: 82 e0 eb 02 d7 c9 ba 05 àë.×ɺ.
0030: 6a 22 b8 f7 63 26 b0 1d j"¸÷c&°.
0038: 06 07 e9 12 cb f4 f3 f8 ..é.Ëôóø
0040: 41 7f 90 6a a3 a1 d2 6d A?j£¡Òm
0048: 76 77 99 62 ab a9 da 65 vwb«©Úe
0050: 6e 6f 81 7a b3 b1 c2 7d no?z³±Â}
0058: 66 67 89 72 bb b9 ca 75 fgr»¹Êu
Ohhhhhh here's another one of my favorites...
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2/5/2006
Time: 12:44:38 PM
User: N/A
Computer: G
Description:
Error code 1000007f, parameter1 00000008, parameter2 f788ed70, 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 38 2c 20 000008,
0038: 66 37 38 38 65 64 37 30 f788ed70
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
Gotta love this:
http://www.anetforums.com/posts.aspx?ThreadIndex=29710
So I should replace my memory AND my video card and if that doesn't fix it AND my sound card and if that doesn't fix it AND my motherboard... jeeze. gimme a break. I prefer MS helping me determine what part is failing. Increase my ability to make educated CHOICES as opposed to baby proofing (aka nerfing) my system.
side note: memtest86 had seven flawless passes (non ECC) and i'm not about to go about buying random parts to replace what may or may not be failing... see my point?