Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD problem with new built system


  • Please log in to reply
8 replies to this topic

#1 soulz993

soulz993

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 17 September 2013 - 08:00 PM

Hello, I recent had a new system built and when I'm gaming it randomly BSOD on me.

 

Debugger is says

Microsoft ® Windows Debugger Version 6.3.9431.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02ca56d0
Debug session time: Tue Sep 17 17:29:41.719 2013 (UTC - 7:00)
System Uptime: 0 days 9:33:05.531
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d3b6028, be000000, 800400}

Probably caused by : GenuineIntel

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

7: 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: 0000000000000000, Machine Check Exception
Arg2: fffffa800d3b6028, 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:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre

STACK_TEXT: 
fffff880`0317cb58 fffff800`02a2ba3b : 00000000`00000124 00000000`00000000 fffffa80`0d3b6028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0317cb60 fffff800`02bee453 : 00000000`00000001 fffffa80`0cf84a10 00000000`00000000 fffffa80`0cf84a60 : hal!HalBugCheckSystem+0x1e3
fffff880`0317cba0 fffff800`02a2b700 : 00000000`00000728 fffffa80`0cf84a10 fffff880`0317cf30 fffff880`0317cf00 : nt!WheaReportHwError+0x263
fffff880`0317cc00 fffff800`02a2b052 : fffffa80`0cf84a10 fffff880`0317cf30 fffffa80`0cf84a10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0317cd50 fffff800`02a2af0d : 00000000`00000008 00000000`00000001 fffff880`0317cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0317cd90 fffff800`02a1ee88 : 00000000`00000001 fffff880`03174180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0317cdc0 fffff800`02ad646c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0317cdf0 fffff800`02ad62d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0317cf30 fffff880`05be9c61 : fffff800`02ae0709 00000000`00343edc fffffa80`0c8d2670 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0319cb58 fffff800`02ae0709 : 00000000`00343edc fffffa80`0c8d2670 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19
fffff880`0319cb60 fffff800`02acf85c : fffff880`03174180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!PoIdle+0x52a
fffff880`0319cc40 00000000`00000000 : fffff880`0319d000 fffff880`03197000 fffff880`0319cc00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

Followup: MachineOwner

 

what is causing the problem?

 



BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:46 AM

Posted 18 September 2013 - 04:17 AM

:welcome: to the Bleeping Computer forum.

 

 

Please post a link to the Speccy snapshot of your system by reading instructions from the guide below.

 

 

 

 

Also zip the crash dumps files located inside C:\Windows\Minidump folder and attach with the next reply. 



#3 soulz993

soulz993
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 September 2013 - 05:02 PM

http://speccy.piriform.com/results/YdcGfRyWbYMmE4nFnsdkxWW



#4 soulz993

soulz993
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 September 2013 - 05:10 PM

It is not letting me upload the minidump files. Says Error Not permitted.

I ran memtest for 19hours with 0 errors. Windows Memory Diagnostic ran 5 passes with 0 errors.

Could it be drivers, vid card , or PSU causing BSOD?



#5 soulz993

soulz993
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 September 2013 - 06:41 PM

BluescreenView says these are the 2 responsible for all the BSOD.

 

ntoskrnl.exe    ntoskrnl.exe+18c453    fffff800`02a4a000    fffff800`03030000    0x005e6000    0x51fb06cd    8/1/2013 6:09:33 PM    Microsoft® Windows® Operating System    NT Kernel & System    6.1.7601.18229 (win7sp1_gdr.130801-1533)    Microsoft Corporation    C:\Windows\system32\ntoskrnl.exe    
 

hal.dll    hal.dll+12a3b    fffff800`02a01000    fffff800`02a4a000    0x00049000    0x4ce7c669    11/20/2010 6:00:25 AM    Microsoft® Windows® Operating System    Hardware Abstraction Layer DLL    6.1.7601.17514 (win7sp1_rtm.101119-1850)    Microsoft Corporation    C:\Windows\system32\hal.dll    
 



#6 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:46 AM

Posted 18 September 2013 - 10:47 PM

Hi

 

What you are experiencing is a STOP 0x124 error which is hardware related. In my experience, this particular BSOD is CPU related in most cases. Usually either a overheating CPU, Overclocked CPU , Voltage tweaks etc are the main reasons behind this blue screen error.

 

In you case, both CPU and RAM seems to be running overclocked. CPU stock speed is 3.5 but it seems to be running at 4 Ghz.

Core 0
Core Speed: 4107.0 MHz
Multiplier: x 41.0
Bus Speed: 100.2 MHz
Temperature: 57 °C
Thread 1
APIC ID: 0
Thread 2
APIC ID: 1
Core 1
Core Speed: 4107.0 MHz
Multiplier: x 41.0
Bus Speed: 100.2 MHz
Temperature: 55 °C
Thread 1
APIC ID: 2
Thread 2
APIC ID: 3
Core 2
Core Speed: 4107.0 MHz
Multiplier: x 41.0
Bus Speed: 100.2 MHz
Temperature: 60 °C
Thread 1
APIC ID: 4
Thread 2
APIC ID: 5
Core 3
Core Speed: 4107.0 MHz
Multiplier: x 41.0
Bus Speed: 100.2 MHz
Temperature: 57 °C
Thread 1
APIC ID: 6
Thread 2

Kingston RAM is rated for 1333Mhz . (667 x2 = 1334)

Slot #1
Type: DDR3
Size: 8192 MBytes
Manufacturer: Kingston
Max Bandwidth: PC3-10700 (667 MHz)
Part Number: KHX1600C10D3/8GX
Serial Number: 7817F548
Week/year: 28 / 13
SPD Ext.: EPP
XMP--2

It is now running at 1600 Mhz. ( 801 x 2 = 1602 )

Memory
Type: DDR3
Size: 16384 MBytes
Channels #: Dual
DRAM Frequency: 801.4 MHz
CAS# Latency (CL): 10 clocks
RAS# to CAS# Delay (tRCD): 10 clocks
RAS# Precharge (tRP): 10 clocks
Cycle Time (tRAS): 27 clocks

To overclock or not is your choice but disable all the frequency and voltage turnings and use the recommended stock settings at least as a test. You may need to manually set the memory speed and timing to the optimal values. 

 

 

BTW, if it is a gaming PC, don't bother about overclocking at all. You won't gain a single FPS boost by overclocking the CPU but you can try overclocking graphic card instead.


Edited by Anshad Edavana, 18 September 2013 - 10:51 PM.


#7 soulz993

soulz993
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 September 2013 - 11:44 PM

Thank You. Will try out your suggestion and see if does any more random BSOD.



#8 soulz993

soulz993
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 20 September 2013 - 12:34 AM

Changed the bios settings, no BSOD since!



#9 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:46 AM

Posted 20 September 2013 - 03:44 AM

Glad to be able to help. If you need further assistance, let us know  :thumbup2:






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users