Community
cancel
Showing results for 
Search instead for 
Did you mean: 
KAitk1
Beginner
933 Views

Newly Built PC, BSOD Crashes, I think it may be the CPU

Hi All,

 

First time posting here, been using Intel CPU's for the past 15 years but never had an issue that I thought might be the CPU until now. I'm hoping someone can provide some firm insight as to what my problem might be so I can do the necessary RMA.

 

Built my PC about 10 days ago and have been getting blue screen crashes. Memtest shows no errors, tried each stick individually, including while in safe mode and the crashes still occur while using prime 95. I attempted a stress test - https://www.reddit.com/r/techsupport/wiki/hwinfo_logging

 

This test lasted about 1 minute before crashing.

 

Given that it's crashing while in safe mode I'm assuming this is a hardware issue.

 

I've ensured that all drivers are up to date and that I'm using the most up to date version of my BIOS. All BIOS settings are set to default. I did use the Gigabyte easytune program to bump my clock speeds up to 4.8ghz temporarily but ended up going back to stock and removing all unnecessary software.

 

System specs - http://speccy.piriform.com/results/PvULuupKprLWDp4HXB07HHQ

 

Below is a mini dump from my most recent crash. The WHEA error pointing to Genuine Intel makes me think this is CPU related.

 

Any help would be appreciated.

 

Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Users\Kyle's PC\Desktop\022219-7453-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: srv*

Executable search path is: 

Windows 10 Kernel Version 17763 MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff800`59c03000 PsLoadedModuleList = 0xfffff800`5a01ead0

Debug session time: Fri Feb 22 06:38:41.313 2019 (UTC - 5:00)

System Uptime: 0 days 0:00:03.016

Loading Kernel Symbols

...............................................................

.

Loading User Symbols

Mini Kernel Dump does not contain unloaded driver list

*******************************************************************************

*                                       *

*            Bugcheck Analysis                  *

*                                       *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 124, {7, ffffb281330ea038, 0, 0}

 

Probably caused by : GenuineIntel

 

Followup:   MachineOwner

---------

 

1: 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: 0000000000000007, BOOT Error

Arg2: ffffb281330ea038, Address of the WHEA_ERROR_RECORD structure.

Arg3: 0000000000000000

Arg4: 0000000000000000

 

Debugging Details:

------------------

 

 

KEY_VALUES_STRING: 1

 

 

STACKHASH_ANALYSIS: 1

 

TIMELINE_ANALYSIS: 1

 

 

DUMP_CLASS: 1

 

DUMP_QUALIFIER: 400

 

BUILD_VERSION_STRING: 10.0.17763.316 (WinBuild.160101.0800)

 

DUMP_TYPE: 2

 

BUGCHECK_P1: 7

 

BUGCHECK_P2: ffffb281330ea038

 

BUGCHECK_P3: 0

 

BUGCHECK_P4: 0

 

BUGCHECK_STR: 0x124_GenuineIntel

 

CPU_COUNT: 6

 

CPU_MHZ: e70

 

CPU_VENDOR: GenuineIntel

 

CPU_FAMILY: 6

 

CPU_MODEL: 9e

 

CPU_STEPPING: c

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

 

PROCESS_NAME: System

 

CURRENT_IRQL: 0

 

ANALYSIS_SESSION_HOST: DESKTOP-EKVHL8C

 

ANALYSIS_SESSION_TIME: 02-22-2019 19:46:17.0004

 

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

 

STACK_TEXT:  

fffff68f`15bf84a0 fffff800`5a181a29 : ffffb281`2a151080 ffffb281`330ea010 fffff800`5a00a600 fffff800`00000000 : nt!WheapCreateLiveTriageDump+0x7b

fffff68f`15bf89d0 fffff800`59f21d78 : ffffb281`330ea010 fffff800`59c63811 00000000`00000000 ffffd50c`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d

fffff68f`15bf8a00 fffff800`59f22a8b : fffff800`5a00a5a0 fffff800`5a00a600 ffffb281`2abd8ee8 ffffb281`2a083840 : nt!WheapProcessWorkQueueItem+0x48

fffff68f`15bf8a40 fffff800`59cb71ea : ffffb281`2a0aacf0 ffffb281`2a151080 ffffb281`2abd8e00 ffffb281`00000000 : nt!WheapWorkQueueWorkerRoutine+0x2b

fffff68f`15bf8a70 fffff800`59c89bc5 : ffffb281`2a151080 ffffb281`2a0811c0 ffffb281`2a151080 00000000`00000000 : nt!ExpWorkerThread+0x16a

fffff68f`15bf8b10 fffff800`59dbd89c : ffff9d80`18024180 ffffb281`2a151080 fffff800`59c89b70 00000000`00000000 : nt!PspSystemThreadStartup+0x55

fffff68f`15bf8b60 00000000`00000000 : fffff68f`15bf9000 fffff68f`15bf2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c

 

 

THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2d7687bc4d9a24dd51c507635bc4ce8aa00fde94

 

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: GenuineIntel

 

IMAGE_NAME: GenuineIntel

 

DEBUG_FLR_IMAGE_TIMESTAMP: 0

 

STACK_COMMAND: .thread ; .cxr ; kb

 

FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN_PRV

 

BUCKET_ID: 0x124_GenuineIntel__UNKNOWN_PRV

 

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel__UNKNOWN_PRV

 

TARGET_TIME: 2019-02-22T11:38:41.000Z

 

OSBUILD: 17763

 

OSSERVICEPACK: 316

 

SERVICEPACK_NUMBER: 0

 

OS_REVISION: 0

 

SUITE_MASK: 784

 

PRODUCT_TYPE: 1

 

OSPLATFORM_TYPE: x64

 

OSNAME: Windows 10

 

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

 

OS_LOCALE:  

 

USER_LCID: 0

 

OSBUILD_TIMESTAMP: unknown_date

 

BUILDDATESTAMP_STR: 160101.0800

 

BUILDLAB_STR: WinBuild

 

BUILDOSVER_STR: 10.0.17763.316

 

ANALYSIS_SESSION_ELAPSED_TIME: 3c7

 

ANALYSIS_SOURCE: KM

 

FAILURE_ID_HASH_STRING: km:0x124_genuineintel__unknown_prv

 

FAILURE_ID_HASH: {a7406f97-70d3-5fd4-2647-1fafa47ede59}

 

Followup:   MachineOwner

 

0 Kudos
5 Replies
AlHill
Super User
160 Views

I would try DIFFERENT memory, and a different power supply.

 

Doc

 

KAitk1
Beginner
160 Views

Unfortunately I don't have different memory or a power supply. But the more I think the power supply would make sense. I can use the computer if not stressed without much issue but as soon as it's under load it crashes. It's a semi module power supply, is it possible the PSU is fine but the cables need to be re-attached? Or with something like a bad power supply it's more to do with the internal components?

KAitk1
Beginner
160 Views

Maybe if someone could be so kind to review - https://drive.google.com/file/d/13q0w-SxTDg2G5F0v7zQbccJexC_C7_L4/view

 

Within is a CSV file with the crash details on it. I had someone look that has basic info and they also said the PSU was undervolting and throttling my GPU.

David_V_Intel
Employee
160 Views

Hello KAitk1, Thank you for posting on the Intel ® communities. I am following up with your case and would like to know if you still need help. If you need more assistance do not hesitate to reply. Regards, David V Intel Customer Support Technician Under Contract to Intel Corporation
KAitk1
Beginner
160 Views

Hi David,

 

You can close this thank you.

 

I ended up putting in a RMA request for a new CPU. New CPU's were unavailable so I was asked to mail mine back and a refund would be granted. Still waiting for the refund but have purchased a replacement which has resolved all of my problems.

Reply