Jump to content

Random (& many) BSODs


MtK

Recommended Posts


Well, it *is* a hardware fault, as I said before. Now I have actual data for you:

// The bugcheck is indeed an uncorrectable error bugcheck:
0: kd> .bugcheck
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 8542d3f0, Address of WHEA_ERROR_RECORD structure
Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arg4: 00010014, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error


// So, looking at the error record for more info:
0: kd> !errrec ffffffff8542d3f0
Error Record @ FFFFFFFF8542D3F0 has 3 sections
Severity : Fatal
Validation Bits : 0x00000002 timestamp
Total Length : 0x6C2
Timestamp : 12/30/6174 15:06:41.192
Creator : Windows
Notify Type : Machine Check Exception
Record ID : 0x01C91505E4F7070F
Flags : 0x00000000----------------------------------------------------------
Section 0: Generic Processor Section (Descriptor @ FFFFFFFF8542D470)
Section Offset : 0x158
Section Length : 0xC0
Flags : 0x00000001 primary
FRU ID : n/a
FRU Text : n/a
Severity : 0x1 - Fatal

Generic Processor Error Section Info:
ProcessorType : 0x0 - IA32/X64
Processor ISA : 0x0 - X86
Error Type : 0x2 - TLB Error
Operation : n/a
Flags : 0x00
Level : 0x0
CPU Version : 0x00000000000006E8
CPU Brand String : Genuine Intel(R) CPU T2500 @ 2.00GHz
ProcessorId : 0x0000000000000000
TargetAddress : n/a
RequestorId : n/a
ResponderId : n/a
Instruction Ptr : n/a
----------------------------------------------------------
Section 1: X64 Processor Specific Section (Descriptor @ FFFFFFFF8542D4B8)
Section Offset : 0x218
Section Length : 0x292
Flags : 0x00000000
FRU ID : n/a
FRU Text : n/a
Severity : 0x1 - Fatal

XPF Processor Specific Error Section Info:
Local APIC ID : 0x0000000000000000
CPU ID:
00 08 02 00 A9 C1 00 00 FF FB E9 BF 14 00 01 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

XPF Procinfo : (@ 0xFFFFFFFF8542D648)
Valid Bits : CI tid rid res ip

TLB Check
Target Id : 0x0000000000000000
Requestor Id : 0x0000000000000000
Responder Id : 0x0000000000000000
Instruction Ptr : 0x0000000000000000
----------------------------------------------------------
Section 2: WHEA Packet Section (Descriptor @ FFFFFFFF8542D500)
Section Offset : 0x4AA
Section Length : 0x218
Flags : 0x00000000
FRU ID : n/a
FRU Text : n/a
Severity : 0x1 - Fatal

WHEA Error Packet Info Section (@ FFFFFFFF8542D89A)
Signature : ErPt
Flags : 0x00000000
Size : 0x218
RawDataLength : 0x392
Context : 0x0000000000000000
ErrorType : 0x0 - Processor
ErrorSeverity : 0x1 - Fatal
ErrorSourceId : 0x0
ErrorSourceType : 0x0 - MCE
Version : 00000002
Cpu : 0000000000000000
RawDataFormat : 0x1 - IA32 MCA

Raw Data : Located @ FFFFFFFF8542D9B2

Processor Error: (Bus Interconnect Error)
Processor Number : 0
Bank Number : 2
Status : B200000000010014
Address : 0000000000000000 (I)
Misc : 0000000000000000 (I)

So, it is complaining about your CPU. Either it's damaged from overvoltage or overclocking, or it's overheating, or you're just unlucky and it was a bad part (Status B200000000010014 == damaged or overheating CPU, btw - I'm not guessing). No matter what way you look at it, you aren't going to fix this without going back to the vendor for a replacement.

Link to comment
Share on other sites

I didn't want to say anything but the computer is already at LG's lab since yesterday.

now I can report to them that you found this error so they should check the CPU too :)

(although heating is always one of my complaint when I leave the computer over there)

thanks!

Edited by cluberti
removed quote for brevity for those with slow connections and thread length
Link to comment
Share on other sites

Not a problem. If they weren't able to figure this out themselves from this dump, honestly, I'd not buy a future machine from them. Just my .02¢.

actually, not sure they can see this analysis because the HD is not in the computer :)

but I'll contact them first thing tomorrow to inform them...

btw,

do you still want/need the other 2 DUMPs?

(as far as I can remember they indicated for a different STOP error)

Edited by MtK
Link to comment
Share on other sites

Random BSOD's: 7F, 8e, a, 50:

Been trying to fix my random crashes and sudden reboots for a while now with no big luck, I think I have fixed causes of an USB crash I had and a non random nvidia driver crash (used drive cleaner then reinstalled the driver). I think it started with BSOD's and that made me stop using a chat application that ran many scripts (most of the crash dumps were pointing at it...) but that didn't really fix it. I have also tried many hardware test software such as memtest, burnintest (tested almost everything for long periods) and even formatted my primary hard drive to reinstall windows XP... but after a while the same kind of crashes started happening.

----------------------------------

jacksen

Word Of Mouth

Link to comment
Share on other sites

actually, not sure they can see this analysis because the HD is not in the computer :)
Attaching a null modem cable and a debugger would get them the same data. They should know how to do this.
btw, do you still want/need the other 2 DUMPs? (as far as I can remember they indicated for a different STOP error)
No, once I've got an actual hardware error bugcheck, nothing else matters.
Link to comment
Share on other sites

Random BSOD's: 7F, 8e, a, 50:

Been trying to fix my random crashes and sudden reboots for a while now with no big luck, I think I have fixed causes of an USB crash I had and a non random nvidia driver crash (used drive cleaner then reinstalled the driver). I think it started with BSOD's and that made me stop using a chat application that ran many scripts (most of the crash dumps were pointing at it...) but that didn't really fix it. I have also tried many hardware test software such as memtest, burnintest (tested almost everything for long periods) and even formatted my primary hard drive to reinstall windows XP... but after a while the same kind of crashes started happening.

----------------------------------

jacksen

Word Of Mouth

I'm sorry but you have XP & I have Vista. you have nVidia I have ATI - how is this related?

Link to comment
Share on other sites

What you have is people seeing a bugcheck code and guessing (knowing only some experience with some *other* bugcheck they've had, or someone knows of someone with a similar bugcheck, etc). Since we know what the problem is, I'm closing this thread to avoid any further speculation (not necessary) or embarassment for those just guessing at an answer and grasping at straws.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...