Start a Conversation

Unsolved

This post is more than 5 years old

41457

June 12th, 2013 22:00

Alienware Area 51, whea_uncorrectable_error

Hi,

First thing first, I have no warranty as it expired >_<

I have been getting this error here and there if not too often after installing Windows 8. I never encountered this problem with Windows 7.

I am not sure if its related to Command Center or hardware issue, if so, I would have experienced it with Windows 7 as well..but didn't.

Hopefully, I can get some sort of solution or else I may go back to Windows 7 to check again as my resort if things doesn't work out.. 

P.S - My CC has been acting up lately too, the fan goes at high speed mode all of sudden even during normal usage.

Which Command Center works well with Windows 8? 

Please help.

Thanks!

3.1K Posts

June 12th, 2013 22:00

Hi MaSx,

I would suggest you to run the Dell Diagnostics to check the hardware functionality. Power off the computer -> restart the computer, press 'F12' key on the Dell logo -> Select ‘Diagnostics’ from the boot menu.

If Diagnostics shows no error, you may provide me the minidump files. Please follow the steps listed to provide the minidump files. We will decode this folder to understand the root cause of the issue that you have been facing:

- Navigate to C:\Windows\Minidump and tap
- Copy all the 'Minidump' folders and paste them to your desktop screen
- Please attach these folders in your next reply.
- Let me check the 'Minidump' folder with a debugging tool to see if we get decisive results

Note: The minidump folders will be .exe folders. You will not be able to attch .exe files on this forum. Right click on each .exe folder and select 'Send to' and then select 'Compressed (Zipped) folder'. A zip file will be created which you can attach here. Below is the screen shot how to attach files:

3276.SS1.JPG


Once you click on the icon, a window will open. Click on 'Browse' to browse the minidump folder. Once the file is uploaded, click on 'Insert':

 

4064.SS2.JPG 

In addition to the minidump files, please provide System Information and the Event Viewer logs using the following steps:

- On the 'Start menu' (Windows), type 'MSINFO32' in the 'Search text box'
- In the 'System Information dialog box', on the File menu, click 'Save'
- In the 'Save As dialog box', make sure that the file type is 'System Information File (*.NFO)'
- Enter a name for the file > Click 'Save' and share the file with me

Event Viewer
- open the Event Viewer by going to start->run->eventvwr

  

  

Please reply if you have any questions.

26 Posts

June 13th, 2013 07:00

I ran the test and everything passed. I also sent you the files you requested. Check your PM.

8 Wizard

 • 

47K Posts

June 13th, 2013 08:00

STOP 0x00000124  whea_uncorrectable_error

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124.

This bug check indicates that a fatal hardware error has occurred.

This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

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*http://msdl.microsoft.com/download/symbols 
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 
.............................................................................. 
******************************************************************************* 
* * 
* 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

26 Posts

June 13th, 2013 10:00

Thanks,..but not sure what all those means..

8 Wizard

 • 

17K Posts

June 13th, 2013 13:00

Which Command Center works well with Windows 8? 

The latest one ... try v2.8.9.0 or higher.

I thought we covered that here:

http://en.community.dell.com/owners-club/alienware/f/3746/p/19475127/20285835.aspx#20285835

Did you turn-off Win8 Fast Boot?

 

26 Posts

June 13th, 2013 13:00

I was using my laptop for quite sometimes and It worked for a short time but started happening again. I am not sure if fastboot is on or off.

June 13th, 2013 14:00

Hi MaSx,

Can you reseat the CPU? I've had some experiences with that same bluescreen and it points towards the CPU.

3.1K Posts

June 15th, 2013 08:00

Hi MaSx,

Thank you for the response. Would like to inform you that this system was not tested with Windows 8. You may refer to the following link on Dell Computer Support for Windows 8 Upgrade http://dell.to/12kQPKY. Hence appropriate drivers are not available and the system may exhibit issues with Windows 8.

I analysed the dump files. As rightly mentioned by SpeedStep, WHEA_UNCORRECTABLE_ERROR points at a possible hardware failure. You may try to update the BIOS version to A10. This version was released on 3/8/2012. Here is the link http://dell.to/147qnVd.

Would also like to know if you tried re-seating the processor as suggested by Alexander.

26 Posts

June 19th, 2013 12:00

Hi MaSx,

 

Can you reseat the CPU? I've had some experiences with that same bluescreen and it points towards the CPU.


 

I reseated the memory, cpu, gpu, reset cmos, used different power cable for GPU and so far it's running good without any BSOD or CC problem.

I have not used the PC for long period of time so can't say for sure that the problem has been resolved but I noticed that the system runs a bit cooler than right before I did all of the above. Let's see what happens from now on.

Thank you!

Hi MaSx,

 

Thank you for the response. Would like to inform you that this system was not tested with Windows 8. You may refer to the following link on Dell Computer Support for Windows 8 Upgrade http://dell.to/12kQPKY. Hence appropriate drivers are not available and the system may exhibit issues with Windows 8.

 

I analysed the dump files. As rightly mentioned by SpeedStep, WHEA_UNCORRECTABLE_ERROR points at a possible hardware failure. You may try to update the BIOS version to A10. This version was released on 3/8/2012. Here is the link http://dell.to/147qnVd.

 

Would also like to know if you tried re-seating the processor as suggested by Alexander.

I think Dell should upgrade the drivers. If you spend so much money on a system you could atleast expect some drivers upgrade and not abandonment.

Currently, I have BIOS A11? I'm not sure if it's updated version one or older version with messed up number? Please advise if I should upgrade to A10 from A11 (it doesn't make sense to me). What driver should I install for Serial ATA Controller? That's the only driver I do not have at this moment.

I have mentioned what I have done above.


Thanks! 

26 Posts

June 19th, 2013 13:00

Hi Maxs,

 

You should have no other problem with that BSOD, as I mentioned, either re-seating or  replacing the CPU fixes the problem. Please keep us posted.

I can reseat it but as for replacing an Intel Core i7 980x would be possible only if Dell would be so kind to do a exchange.

And as I mentioned above, should I flash BIOS A10? I have BIOS A11 and when I run the most current one it says "Current version is newer than new version"

June 19th, 2013 13:00

Hi Maxs,

You should have no other problem with that BSOD, as I mentioned, either re-seating or  replacing the CPU fixes the problem. Please keep us posted.

June 19th, 2013 14:00

Hi Maxs,

If the BSOD continues, and you have an active warranty you can send me a private message.

You should leave the A10 BIOS. BIOS A10's release date is 08/03/2012 and the A11 is 17/10/2011.

No Events found!

Top