Newly bought computer BSOD

peccaraze

Honorable
Apr 28, 2013
5
0
10,510
I just got my Alienware M17xR4 Windows 8-64bit and it crashed around 7-8 times the first night. Then I decided to reset and install my window 8 again. After I install drivers the problem came back.

BSOD:whea_uncorrectable_error

Dump from osronline

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
Machine Name:
Kernel base = 0xfffff803`f4a0d000 PsLoadedModuleList = 0xfffff803`f4cd9b00
Debug session time: Sun Apr 28 01:53:42.822 2013 (UTC - 4:00)
System Uptime: 0 days 0:04:29.478
*******************************************************************************
* *
* 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: 0000000000000000, Machine Check Exception
Arg2: fffffa800b7e6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02eae968 fffff803`f518693d : 00000000`00000124 00000000`00000000 fffffa80`0b7e6028 00000000`be000000 : nt!KeBugCheckEx
fffff880`02eae970 fffff803`f4b6d969 : 00000000`00000001 fffffa80`07614ca0 00000000`00000000 fffffa80`0b7e6028 : hal!HalBugCheckSystem+0xf9
fffff880`02eae9b0 fffff803`f51866e3 : 00000000`00000728 00000000`00000007 fffff880`02eaeb10 fffffa80`07614ca0 : nt!WheaReportHwError+0x249
fffff880`02eaea10 fffff803`f518600c : 00000000`00000010 fffffa80`07614ca0 fffff880`02eaebc8 fffffa80`07614ca0 : hal!HalpMcaReportError+0x53
fffff880`02eaeb70 fffff803`f5185f07 : fffffa80`0737b020 00000000`00000001 00000000`00000007 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02eaebc0 fffff803`f5185d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02eaec00 fffff803`f5186edb : fffffa80`0737b020 fffff880`02eaee30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02eaec30 fffff803`f4a6557b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02eaec60 fffff803`f4a6532e : 00000000`00000000 fffff803`f4a652af 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02eaeda0 fffff880`09f60984 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff880`02ece888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)

Thanks for helping
 
Having re-installed drivers, it points to a hardware failure. Rather than waste time analysing, send it back whence it came with the details of the BSOD. Meanwhile you could try a couple of things, like running with a stick of memory removed, and run a HDD test (you may find one in your UEFI)
Some to choose from
http://www.seagate.com/support/downloads/
http://www.seagate.com/support/internal-hard-drives/consumer-electronics/ld25-series/seatools-dos-master/
http://support.wdc.com/product/download.asp?groupid=606&sid=3
Just to satisfy your curiosity..
 

peccaraze

Honorable
Apr 28, 2013
5
0
10,510


I used a program from your link (Data lifeguard Diagnostic for Windows) and it didn't seem to have any problem.
Any thought?
 
HDD should be fine, then. If you don't want to open up the back and remove sticks of RAM try Memtest 86, preferably the bootable version that you burn to a disk, as it will test more RAM (not being used by Windows)
http://www.memtest.org/#downiso
Which drive did you check? Realised you have a combination of SSD and HDD, SSD unlikely to be at fault, depending on where your Games are stored whether the HDD(s) cause problems. For your SSD
http://www.softpedia.com/get/System/Hard-Disk-Utils/SSDlife-Free.shtml
 

peccaraze

Honorable
Apr 28, 2013
5
0
10,510


My laptop just finished 1 pass of memtest and showed no error so far.
Also , I didn't use SSD. My settings is 2 HDD (ST9500423AS) 500gb with RAID0 by intel.
 
When you re-installed Windows, was it from an Installation disk or from a recovery partition?
If the memory testing finds nothing, chances are it's an obscure Hardware fault, probably Motherboard related and difficult to diagnose. Leave it to your supplier to find!
 

peccaraze

Honorable
Apr 28, 2013
5
0
10,510


I install from dell recovery media disk.