BSOD Error on New Build

[Forsy2003]

Hi All,

I've recently built a machine but after a few hours of use i get the BSOD, after this it starts happening more frequently. I thought it may be over heating as it would happen during gaming / video editing so i bought a better CPU cooler but the problem persists. I've ran a stress test since then and cores average around 72 degrees and seems to work fine so any help would be appreciated.

 

[Pauly]

have you actually checked temps ? cpu and gfx
install speccy or something similar and run a stress test on your gfx & cpu while checking temps, the fact it gets more frequent would be likely to be temp related

 

[Forsy2003]

Hi, I've run a stress test on CPU, graphics card and hard drive whilst monitoring the temperature using Speccy. HDD and GC barely changed temp and the CPU averaged around 72 degrees, i left this running for half hour and it seemed fine. This was yesterday after adding a new CPU fan as i thought it might be temperature related (could still be). Hopefully something in the attached zip could help identify the issue.

 

[Pauly]

Well I have been through a few of your dumps and they are all (except 1) reporting 0x124 bug check codes which generally relate to a hardware error.
Every 0x124 is reporting a cache error on Processor 0 Bank 1 - ignore the fact that chrome.exe is mentioned here as this is just the active program at that time its a different process each time through your dump files

Mini Kernel Dump File: Only registers and stack trace are available
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18798.x86fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0x82e12000 PsLoadedModuleList = 0x82f5c5b0
Debug session time: Sat Apr 25 21:50:48.857 2015 (UTC + 1:00)
System Uptime: 0 days 0:04:28.793
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8638e01c, bf800000, 124}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
0: 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, Machine Check Exception
Arg2: 8638e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  1f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
82f37d0c 83235fcd 00000124 00000000 8638e01c nt!KeBugCheckEx+0x1e
82f37d48 82ee3f2c 887d96e9 8638e01c 82e89f10 hal!HalBugCheckSystem+0xab
82f37d78 8323627f 88f61780 83243e40 00000000 nt!WheaReportHwError+0x230
82f37e8c 83236371 88f61780 88f617d0 00000004 hal!HalpMcaReportError+0x3b
82f37eb0 8323648d 00000000 88f617d0 00000000 hal!HalpMceHandler+0x8b
82f37ed0 832365d6 00000000 88f61780 82f37ff0 hal!HalpMceHandlerWithRendezvous+0x4b
82f37ee0 8322c5f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
82f37ff0 83229261 00000000 801de000 00000000 hal!HalpMcaExceptionHandler+0x87
82f37ff0 00000000 00000000 801de000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache
FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
Followup: MachineOwner
---------
0: kd> !errrec [8638e01c]
===============================================================================
Common Platform Error Record @ 8638e01c
-------------------------------------------------------------------------------
Record Id     : 01d07f98e3210163
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/25/2015 20:50:48 (UTC)
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 8638e09c
Section       @ 8638e174
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x86
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000000
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ 8638e0e4
Section       @ 8638e234
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000000
CPU Id        : c3 06 03 00 00 08 10 00 - bf fb fa 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  @ 8638e234
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 8638e12c
Section       @ 8638e2b4
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
[B][U]Error         : DCACHEL0_WR_ERR (Proc 0 Bank 1)[/U][/B]
  Status      : 0xbf80000000000124
  Address     : 0x00000000d95fd440
  Misc.       : 0x0000000000000086

Are you overclocking in any way ? if so revert all bios settings back to defaults and ensure your chipset drivers are up to date and if only for testing I would remove any of your motherboard manufacturers software from your machine to be sure its not interfering with anything

 

[Forsy2003]

Hi Pauly,

Thanks for taking a look at the zip file, much appreciated.

Nothing is being overclocked. All BIOS is set at default. I've just been on the ASUS site and downloaded the latest chipset, i had originally installed everything from the CD that came with the mobo, but whether these are the latest files i don't know.

I've been running the stress test again for an hour and average temp over the 4 cores didn't rise above 59 degrees. I've had not had any BSOD today but i have only been on it to run the stress temp & use the internet.

Edit: Hopefully updating the chipset will resolve this, but either way i will post back later for an update once i've removed the stuff that was bundled with the mobo.

 

[Pauly]

OK, unfortunately with matters mobo and cpu related its very hard to give or be 100% assured with diagnosis all you can do is take all reasonable steps and precautions to eliminate everything you can before considering a replacement cpu but lets hope it doesn't come to that (which is rarely does thankfully) good luck

 

[Forsy2003]

Typically, no BSOD today but based on the information you've given above i've been using google to help identify the issue. It looks like it may be a faulty CPU (based on others in the same boat) so i'll see how it goes over the next few days. It was only purchased 3 weeks ago so i shouldn't have any problems with returning it to Amazon.

Thanks again for your time