New Posts  All Forums:Forum Nav:

New Build BSOD

post #1 of 9
Thread Starter 
http://speedy.sh/XkaCT/Files.zip

· OS - Vista/ Windows 7 ? Windows 7
· x86 (32-bit) or x64 ? 64 bit
· What was original installed OS on system? None
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? No
· Age of system (hardware): New
· Age of OS installation - have you re-installed the OS?: New

· CPU - 4670k
· Video Card - EVGA 770 Superclocked
· MotherBoard - MSI Z87-G45
· Power Supply - Rosewill 650w

Thanks for all the help its greatly appreciated
post #2 of 9
Among the attached DMP files we have many WHEA_UNCORRECTABLE_ERROR (124) bugchecks.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:
Quote:
===============================================================================
Section 2 : x86/x64 MCA
Descriptor @ fffffa800e1bf138
Section @ fffffa800e1bf2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : GCACHEL2_ERR_ERR (Proc 1 Bank 7)
Status : 0xbe0000000100110a
Address : 0x000000034791f540
Misc. : 0x0000005086000086

GCACHEL2_ERR_ERR = L2 Cache Error. The Processor and Cache Bank seem to change throughout the different dumps.

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

^^ Implies that this was NOT caused by any sort of software complication (drivers, etc) but hardware... processor cache also furthers our diagnosis in the CPU itself (L2 Cache) possibly being faulty.

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
post #3 of 9
Thread Starter 
Before I send it in can you check if my cpu settings are normal?

http://valid.canardpc.com/k22l09
post #4 of 9
Hi,

From that, it's running at 3.8, which AFAIK is max turbo frequency in regards to that chip, and its stock clock spec is 3.4. Do you have SpeedStep disabled, have you cleared the CMOS to return to stock settings as I advised?

Regards,

Patrick
post #5 of 9
Thread Starter 
@pjBSOD
I'm not sure how to do those things can you please direct me to how to disable them?

Thanks
post #6 of 9
Hi,

If you've never made adjustments in the BIOS in regards to your CPU, you have nothing to worry about and or change. If you did however, clear the CMOS - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

If you didn't change anything in the BIOS in regards to CPU settings, your CPU is more than likely faulty as I stated earlier and will need to be replaced.

Regards,

Patrick
post #7 of 9
I don't know anything about his/her BSOD, unfortunately, but CPU-Z on my i5-4670K reports the full Turbo frequency even when it is not running at that frequency; see here:



T-Monitor reports the real CPU multiplier at that time.
The 2013 Build
(14 items)
 
  
CPUMotherboardGraphicsRAM
--- SOLD --- --- SOLD ---  --- SOLD --- --- SOLD --- 
Hard DriveOptical DriveCoolingOS
Samsung 850 EVO 500GB ASUS DRW-24B3ST (24X DVD burner) Noctua NH-U14S w/ NH-T1 TIM Windows 10 Pro (x64) 
MonitorKeyboardPowerCase
ASUS VG248QE w/ Lightboost @ 120Hz Ducky Shine III (MX Brown w/ Red backlights) Kingwin LZP-1000 (1000W) PSU Corsair Carbide Air 540 
Mouse Pad
Razer Goliathus (Precision Control model) - Sta... 
  hide details  
Reply
The 2013 Build
(14 items)
 
  
CPUMotherboardGraphicsRAM
--- SOLD --- --- SOLD ---  --- SOLD --- --- SOLD --- 
Hard DriveOptical DriveCoolingOS
Samsung 850 EVO 500GB ASUS DRW-24B3ST (24X DVD burner) Noctua NH-U14S w/ NH-T1 TIM Windows 10 Pro (x64) 
MonitorKeyboardPowerCase
ASUS VG248QE w/ Lightboost @ 120Hz Ducky Shine III (MX Brown w/ Red backlights) Kingwin LZP-1000 (1000W) PSU Corsair Carbide Air 540 
Mouse Pad
Razer Goliathus (Precision Control model) - Sta... 
  hide details  
Reply
post #8 of 9
Thread Starter 
Everything on my BIOS is on default. Even when my ram out of box 1600mhz it is running 1333mhz on the mobo but I'm not sure if thats the problem
post #9 of 9
Hi,
Quote:
Originally Posted by edamons View Post

Everything on my BIOS is on default. Even when my ram out of box 1600mhz it is running 1333mhz on the mobo but I'm not sure if thats the problem

Your RAM is running at 1333 because that's the default frequency on Auto. If your BIOS is up to date and the system still crashes at all stock settings, then your CPU is the issue and needs to be replaced as I have said.

Regards,

Patrick
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging