Solved BSOD. WHEA_UNCORRECTABLE_ERROR (124).

[Pedroxabia]

Hi folks. I've been browsing here, and would love some assistance.

I'm running Windows 7 Ultimate 32-bit, and have been getting BSOD problems. I've been seeing elsewhere on these forums. The response seems to be "post your dump logs or debug them yourself". Now my PC don´t start or two minutes after start I have always the same BSOD.

The computer is 5 years old. It has a processor AMD 3500+.

I have been debugging my kernel dump and this is the output:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [F:\Minidump\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
Symbol search path is: SRV*c:\websysmbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Kernel base = 0x83050000 PsLoadedModuleList = 0x8319a850
Debug session time: Wed May 4 16:26:49.895 2011 (GMT+2)
System Uptime: 0 days 0:05:52.004
Loading Kernel Symbols
..............................................................................
Loading User Symbols
 
Loading unloaded module list
.....
 
This is the output after enter !analyze -v command:

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
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: 862cb8fc, Address of WHEA_ERROR_RECORD structure
Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
 
Debugging Details:
------------------
 
 
WHEA_ERROR_RECORD: !errrec ffffffff862cb8fc
 
BUGCHECK_STR: 0x124_AuthenticAMD
 
DEFAULT_BUCKET_ID: CODE_CORRUPTION
 
PROCESS_NAME: System
 
CURRENT_IRQL: 1f
 
STACK_TEXT: 
83175d2c 83027fcd 00000124 00000000 862cb8fc nt!KeBugCheckEx+0x1e
83175d68 83121aec 862a9841 862cb8fc 830c82d0 hal!HalBugCheckSystem+0xab
83175d98 8302827f 861538c0 83035e40 00000000 nt!WheaReportHwError+0x230
83175eac 83028371 861538c0 86153910 00000000 hal!HalpMcaReportError+0x3b
83175ed0 830285dd 00000000 86153910 83175ff0 hal!HalpMceHandler+0x8b
83175ee0 8301e5f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
83175ff0 8301b261 00000002 801df000 00000000 hal!HalpMcaExceptionHandler+0x87
83175ff0 83088f3e 00000002 801df000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
83178ad8 8d7469c6 8d0cd03c 831bb400 86352714 nt!READ_REGISTER_ULONG+0x6
83178af0 8d74e2c8 86352fe0 86352028 863520e0 usbohci!OHCI_CheckController+0x42
83178b04 8d74d56f 863520e0 831b8740 862b1f8c USBPORT!MPf_CheckController+0x55
83178b18 830d14d7 86352028 00000000 83178be8 USBPORT!USBPORT_DM_IoTimerDpc+0x2f
83178b38 830ca039 831b8720 021b86d8 4e543f46 nt!IopTimerDispatch+0x49
83178b7c 830c9fdd 8317bd20 83178ca8 00000003 nt!KiProcessTimerDpcTable+0x50
83178c68 830c9e9a 8317bd20 83178ca8 00000000 nt!KiProcessExpiredTimerList+0x101
83178cdc 830c800e 00005800 86ad9030 83185380 nt!KiTimerExpiration+0x25c
83178d20 830c7e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
83178d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
 
 
STACK_COMMAND: kb
 
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
830c7d6f - nt!KeFlushCurrentTb+1f
[ c3:00 ]
1 error : !nt (830c7d6f)
 
MODULE_NAME: memory_corruption
 
IMAGE_NAME: memory_corruption
 
FOLLOWUP_NAME: memory_corruption
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
MEMORY_CORRUPTOR: ONE_BYTE
 
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
 
BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
 
Followup: memory_corruption
---------
 
 

kd> !errrec ffffffff862cb8fc
Error Record @ FFFFFFFF862CB8FC has 3 sections
Severity : Fatal
Validation Bits : 0x00000002 timestamp
Total Length : 0x3A0
Timestamp : 08/28/6177 20:07:04.130
Creator : Unknown Creator 52455043-0210-FFFF-FFff-030001000000
Notify Type : 00000002-03A0-0000-311a-0E0004050B14
Record ID : 0x01CC0A667D91FA45
Flags : 0x00000000----------------------------------------------------------
Section 0: Generic Processor Section (Descriptor @ FFFFFFFF862CB97C)
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 : n/a
Processor ISA : n/a
Error Type : n/a
Operation : n/a
Flags : n/a
Level : n/a
CPU Version : n/a
CPU Brand String : n/a
ProcessorId : n/a
TargetAddress : n/a
RequestorId : n/a
ResponderId : n/a
Instruction Ptr : n/a
----------------------------------------------------------
Section 1: Generic Processor Section (Descriptor @ FFFFFFFF862CB97C)
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 : n/a
Processor ISA : n/a
Error Type : n/a
Operation : n/a
Flags : n/a
Level : n/a
CPU Version : n/a
CPU Brand String : n/a
ProcessorId : n/a
TargetAddress : n/a
RequestorId : n/a
ResponderId : n/a
Instruction Ptr : n/a
----------------------------------------------------------
Section 2: Generic Processor Section (Descriptor @ FFFFFFFF862CB97C)
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 : n/a
Processor ISA : n/a
Error Type : n/a
Operation : n/a
Flags : n/a
Level : n/a
CPU Version : n/a
CPU Brand String : n/a
ProcessorId : n/a
TargetAddress : n/a
RequestorId : n/a
ResponderId : n/a
Instruction Ptr : n/a

I think it is possible it has a memory problem. But few days ago I runned Memtest86 4.20 and no error was reported. I have other old bank memory and I changed them and the problem don´t change.

I can upload the dump If you think can be helpful.

Can be the problem in the CPU, power supply, motherboard, etc ?

Any suggestions or tips would be helpful.

Thanks and Regards,


Pedro

 

[Jonathan_King]

Hello,

Create an Ubuntu Live CD, and boot up selecting "Try Ubuntu with no changes to my computer". When booted, open up FireFox, and download Prime95. Run all three tests, and let us know the results of each.

Download | Ubuntu

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[Pedroxabia]

Hello,

Create an Ubuntu Live CD, and boot up selecting "Try Ubuntu with no changes to my computer". When booted, open up FireFox, and download Prime95. Run all three tests, and let us know the results of each.

Download | Ubuntu

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Thanks, Jonathan_King.

I will do it this weekend.

Regards,


Pedro

 

[Pedroxabia]

Thank you very much for your help.

I think it's a hardware problem because now it don´t display any BIOS messages. Little by little, the thing has deteriorated. It started happening sporadically. I upgraded from Windows XP SP3 to Windows 7 to check if that solves the problem (including a hard disk formatting). It seemed that everything was fine, but the same thing happen again. It was becoming more frequent, but since last week occurred at 2 minutes of being started (more or less). Now don't display any messages.

I have downloaded Ubuntu, but I can't start the computer.

I have got some old components. I've tried all the slots on the motherboard where memory could be installed. I have replaced the memory, processor, power supply, CPU fan. I have removed those components that were expendable: modem, TV card, etc. The problem don't change, the computer don't start. I think the problem is on the motherboard.

I think I have only two options: Find an old motherboard and replace it or buy a new computer.

What do you think about this problem ?

Thanks. Regards.

 

[Jonathan_King]

Honestly, I think you're right; it really sounds as if the motherboard is the problem.

 

[Pedroxabia]

Honestly, I think you're right; it really sounds as if the motherboard is the problem.

Thanks for your help.

Regards,


Pedro

 

[Pedroxabia]

Hi,

I've changed the motherboard and now it works ok. The motherboard was the problem.

Thanks for your help.


Regards,

 

[Jonathan_King]

Thanks for the update -- glad to hear you've found the problem.

Let us know if you need anything else!