solution request for crash dump

dennisrithcie14 · Dec 21, 2014

View attachment 55508Hi, I need someone to let me know the anlyzed crash dump.

Code:

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: fffffa80059cb028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010019, 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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0148b868 fffff802`31e3e965 : 00000000`00000124 00000000`00000000 fffffa80`059cb028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`0148b870 fffff802`31fddeb3 : 00000000`00000001 fffffa80`042a7850 00000000`00000000 fffffa80`059cb028 : hal!HalBugCheckSystem+0xf9
fffff880`0148b8b0 fffff802`31e3e703 : 00000000`00000728 00000000`00000003 fffff880`0148ba10 fffffa80`042a7850 : nt!WheaReportHwError+0x253
fffff880`0148b910 fffff802`31e3e020 : 00000000`00000010 fffffa80`042a7850 fffff880`0148bac8 fffffa80`042a7850 : hal!HalpMcaReportError+0x53
fffff880`0148ba70 fffff802`31e3df1b : fffffa80`0435fd50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`0148bac0 fffff802`31e3dd78 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`0148bb00 fffff802`31e3ef0f : fffffa80`0435fd50 fffff880`0148bd30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`0148bb30 fffff802`31ed577b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0148bb60 fffff802`31ed552e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`0148bca0 00000000`647109db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0727ede0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x647109db


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_TLB

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_TLB

Followup: MachineOwner

blueelvis · Dec 22, 2014

Hi Naveen & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

3: kd> !errrec fffffa80059cb028
===============================================================================
Common Platform Error Record @ fffffa80059cb028
-------------------------------------------------------------------------------
Record Id     : 01d01b773e84a009
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/21/2014 15:49:22 (UTC)
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80059cb0a8
Section       @ fffffa80059cb180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : TLB error
Flags         : 0x00
Level         : 1
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000003
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80059cb0f0
Section       @ fffffa80059cb240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000003
CPU Id        : a9 06 03 00 00 08 10 03 - bf e3 ba 7f ff fb eb bf
                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
Proc. Info 0  @ fffffa80059cb240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80059cb138
Section       @ fffffa80059cb2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : [U][B]GTLBL1_ERR (Proc 3 Bank 2)[/B][/U]
  Status      : 0xb200000000010019

According to the dump file, there is an error in your Processor's L1 Cache's (Of Processor 3 & Bank 2) Translation LookAside Buffer. This buffer ensures speedy translation between the virtual and physical addresses.
But, since there is only a single dump file (And it is a 0x124 bugcheck) I cannot be sure immediately if it is the Hardware causing the trouble. Let's check the 3rd party drivers present on your system -

Code:

**************************Sun Dec 21 21:19:22.880 2014 (UTC + 5:30)**************************
[B][U]ewusbmdm.sys                Fri Dec 24 09:18:36 2010 (4D141814)
ew_jubusenum.sys            Sun Jan 30 15:49:33 2011 (4D453B35)
CLVirtualDrive.sys          Mon Dec 26 18:56:47 2011 (4EF87617)
[COLOR=#ff0000]SFEP.sys                    Mon Jun 18 13:41:46 2012 (4FDEE2C2)
[/COLOR]IntcDAud.sys                Tue Jun 19 20:10:51 2012 (4FE08F73)
HECIx64.sys                 Tue Jul  3 03:44:58 2012 (4FF21D62)
btwl2cap.sys                Thu Jul 26 20:44:41 2012 (50115EE1)
iaStorA.sys                 Sun Sep  2 06:31:24 2012 (5042AFE4)
dump_iaStorA.sys            Sun Sep  2 06:31:24 2012 (5042AFE4)
bcbtums.sys                 Tue Sep 25 21:39:37 2012 (5061D741)
btwampfl.sys                Sat Oct  6 06:19:51 2012 (506F802F)
intelppm.sys                Tue Nov  6 09:25:02 2012 (50988A16)
btwavdt.sys                 Thu Dec  6 01:35:26 2012 (50BFA906)
btwrchid.sys                Thu Dec  6 01:36:20 2012 (50BFA93C)
btwaudio.sys                Wed Dec 12 22:12:14 2012 (50C8B3E6)
RtsPStor.sys                Mon Dec 24 11:35:36 2012 (50D7F0B0)
Rt630x64.sys                Fri Dec 28 05:34:06 2012 (50DCE1F6)
[/U][/B]igdkmd64.sys                Thu Jan 17 02:00:35 2013 (50F70DEB)
nvlddmkm.sys                Fri Jan 18 18:52:15 2013 (50F94C87)
nvpciflt.sys                Fri Jan 18 18:52:40 2013 (50F94CA0)
bcmwl63a.sys                Thu Feb  7 13:33:12 2013 (51135FC0)
BCM42RLY.sys                Fri Feb  8 14:40:17 2013 (5114C0F9)
RTKVHD64.sys                Mon Mar  4 16:03:04 2013 (51347860)
SynTP.sys                   Tue Mar  5 18:08:40 2013 (5135E750)
Smb_driver_Intel.sys        Tue Mar  5 18:10:24 2013 (5135E7B8)

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
Monitor the CPU temperature and DON'T let it exceed 85ºC. If it does, then you probably have a CPU cooling problem.
- CPU temps exceeding 60ºC can cause errors in Prime95. Fix the cooling solution first, then run Prime95 again.
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
NOTE: Errors should be considered when:
- the system BSOD's during Prime95
- the system freezes during Prime95 (this is different than the extreme slowness caused by the program using all your RAM and CPU)
- the Prime95 program crashes
- the Prime95 program shows errors in it's display
- there are errors in the Prime95 results file
More details on the use of this test: http://www.playtool.com/pages/prime95/prime95.html

Also, see if you are able to find any errors using the Intel Burn test below -
http://www.xtremesystems.org/forums...-IntelBurnTest-The-new-stress-testing-program

Let me know how it goes ^_^

-Pranav

solution request for crash dump

dennisrithcie14

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One