Question BSOD - Please help.

Toggle sidebar Toggle sidebar
M

Mcfckyle91

Prominent
Dec 30, 2021
79
8
565
Gigabyte Z87D3HP MBoard with latest bios
i7 4790k CPU @ Default settings, runs at 4.4Ghz on High Performance
16GB Corsair Vengeance LP 1600 XMP Enabled (runs at 1333 otherwise)
Corsair RM1000X PSU
Gigabyte SC 11GB 1080TI
Dark Rock Pro Cooler
120GB Samsung SSD
250GB PNY SSD
2TB Seagate Barracuda HDD

***
  • *
  • 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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9c0cb9d0a028, Address of the nt!_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:
------------------

*


    • *

    • *

    • Either you specified an unqualified symbol, or your debugger *

    • doesn't have full symbol information. Unqualified symbol *

    • resolution is turned off by default. Please either specify a *

    • fully qualified symbol module!symbolname, or enable resolution *

    • of unqualified symbols by typing ".symopt- 100". Note that *

    • enabling unqualified symbol resolution with network symbol *

    • server shares in the symbol path may cause the debugger to *

    • appear to hang for long periods of time when an incorrect *

    • symbol name is typed or the network symbol server is down. *

    • *

    • For some commands to work properly, your symbol path *

    • must point to .pdb files that have full type information. *

    • *

    • Certain .pdb files (such as the public OS symbols) do not *

    • contain the required information. Contact the group that *

    • provided you with these symbols if you need this command to *

    • work. *

    • *

    • Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *

    • *
*
*


    • *

    • *

    • Either you specified an unqualified symbol, or your debugger *

    • doesn't have full symbol information. Unqualified symbol *

    • resolution is turned off by default. Please either specify a *

    • fully qualified symbol module!symbolname, or enable resolution *

    • of unqualified symbols by typing ".symopt- 100". Note that *

    • enabling unqualified symbol resolution with network symbol *

    • server shares in the symbol path may cause the debugger to *

    • appear to hang for long periods of time when an incorrect *

    • symbol name is typed or the network symbol server is down. *

    • *

    • For some commands to work properly, your symbol path *

    • must point to .pdb files that have full type information. *

    • *

    • Certain .pdb files (such as the public OS symbols) do not *

    • contain the required information. Contact the group that *

    • provided you with these symbols if you need this command to *

    • work. *

    • *

    • Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *

    • *
*

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4866

Key : Analysis.Init.CPU.mSec
Value: 296

Key : Analysis.Init.Elapsed.mSec
Value: 7467

Key : Analysis.Memory.CommitPeak.Mb
Value: 79

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 123021-11781-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9c0cb9d0a028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: HuntGame.exe

STACK_TEXT:
fffff8072f69b8e8 fffff8072a8b433a : 0000000000000124 0000000000000000 ffff9c0cb9d0a028 00000000be000000 : nt!KeBugCheckEx
fffff8072f69b8f0 fffff807284015b0 : 0000000000000000 ffff9c0cb9d0a028 ffff9c0caeb12390 ffff9c0cb9d0a028 : nt!HalBugCheckSystem+0xca
fffff8072f69b930 fffff8072a9b5fde : 0000000000000000 fffff8072f69b9d9 ffff9c0cb9d0a028 ffff9c0caeb12390 : PSHED!PshedBugCheckSystem+0x10
fffff8072f69b960 fffff8072a8b5c61 : ffff9c0cb9d09070 ffff9c0cb9d09070 ffff9c0caeb123e0 ffff9c0caeb12390 : nt!WheaReportHwError+0x46e
fffff8072f69ba40 fffff8072a8b5fd3 : 0000000000000000 ffff9c0caeb123e0 ffff9c0caeb12390 0000000000000000 : nt!HalpMcaReportError+0xb1
fffff8072f69bbb0 fffff8072a8b5eb0 : ffff9c0cadccbbe0 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0xef
fffff8072f69bc00 fffff8072a8b6101 : 0000000000000008 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
fffff8072f69bc40 fffff8072a8b536b : 0000000000000000 0000000000000000 fffff8072f69bed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff8072f69bc70 fffff8072a8b7bb5 : ffff9c0cadccbbe0 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
fffff8072f69bca0 fffff8072a90d2c9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
fffff8072f69bcd0 fffff8072a8061fa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
fffff8072f69bd00 fffff8072a805eb7 : 0000023d00000000 fffff8072a805dec 0000023d34f1e030 0000000000000000 : nt!KxMcheckAbort+0x7a
fffff8072f69be40 fffff8072ae12e16 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000000000000000 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiKernelSysretExit+0x56


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner

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

In addition to this I was having a HID Compliant Headset issue where a driver kept uninstalling I have since disabled this driver and thought that was the issue, still getting the BSOD though. Headset is a Hyper Cloud II.

Let me know if I am missing any information.

Thanks!

Temperatures are all absolutely fine, have even tried rebuilding the pc fully doing a complete clean down and reapplying paste.

PShed.dll + 15b0 and ntoskrnl.exe + 3f70d0 show as crash addresses.
 
Last edited:
Sort by date Sort by votes
Seems to me that you might need to reinstall your OS, might want to do so by recreating your bootable USB installer using Windows Media Creation Tools to rule out a corrupt installer. I'm saying a corrupt OS since you've spoken of having issues with your audio, given how the Hyper X Cloud II is an USB driven headset, the chipset drivers might be a problem. How old is the PSU in your build? 1KW is a little too much for a system of that caliber. As for your motherboard's BIOS, a version number would help us two fold.

Lastly, when installing all drivers for your platform, make sure you manually install them in an elevated command, i.e, after you source the latest from Gigabyte's support site, Right click installer>Run as Administrator. The OS tends to install drivers it thinks is right for your platform which often times isn't.

You sure the GPU is by gigabyte and not EVGA? EVGA make an SC(superclocked version of cards) Gigabyte have the OC(overclocked) version of cards.
 
Upvote 0 Downvote
Lutfij said:
Seems to me that you might need to reinstall your OS, might want to do so by recreating your bootable USB installer using Windows Media Creation Tools to rule out a corrupt installer. I'm saying a corrupt OS since you've spoken of having issues with your audio, given how the Hyper X Cloud II is an USB driven headset, the chipset drivers might be a problem. How old is the PSU in your build? 1KW is a little too much for a system of that caliber. As for your motherboard's BIOS, a version number would help us two fold.

Lastly, when installing all drivers for your platform, make sure you manually install them in an elevated command, i.e, after you source the latest from Gigabyte's support site, Right click installer>Run as Administrator. The OS tends to install drivers it thinks is right for your platform which often times isn't.

You sure the GPU is by gigabyte and not EVGA? EVGA make an SC(superclocked version of cards) Gigabyte have the OC(overclocked) version of cards.
Click to expand...
Hi,

Appreciate the response, I manged to (fix) patch/work around? the issue. I would be typing a lot if I went through everything however in short when I removed my i5 4670k and installed the i7 4790k in my z87 even with bios updates the CPU was overheating like mad! The video linked in here explains the exact process I used to fix the issue a few months ago however, after clearing CMOS the overheating stopped. I since removed an rx480 and installed a Gigabyte 11GB 1080ti Gaming OC Model. Had 1 or 2 crashes in Tarkov and thought nothing of it until I purchased Hunt: Showdown and the crashes were constant, making it look like it was the GPU.

View: https://www.youtube.com/watch?v=AxuNUIqeml4


I have had no more issues with the HID Compliant Headset uninstalling anymore as disabling it has done to trick in regards to making me think it was that. It seems that something might be going wrong under load with the CPU and my motherboard? I couldn't recreate the issue when stress testing only in certain games. Temps were also more than acceptable throughout. The crash would case the game the freeze completely then BSOD after a few seconds with successful reporting had DUMP files to go at etc.

The 'fix' I have to open Intel Xtreme Tuning Utility and ensure the profile is running from the video. No more BSOD no more crashes no more errors. The CPU shows as Current Limit Throttling sometimes within the XTU facility and I noticed now even in high performance I don't see the CPU sat at 4.4 Ghz constantly it is fluctuating between 4.0 and 4.4? Perhaps before all 4 cores were running at 4.4 and this would count as an OC on cores #2 and #3? even though in BIOS the settings are defined as 44 44 43 42 with base set to 4.0?

If you need more info or I think of something to add I will post back.

Thanks.

Ps. If it wasn't for finding the fix months ago for the overheating issue I might not have figured out a work around for this, last ditch attempt I thought maybe that old fix will work and it did.

Trying to reinstall windows was also a nightmare kept corrupting and crashing then going into boot loops. I realised this was happening due to the IGPU installing on Windows Updates and hanging the system, once restarted I ended up in a boot loop. Had to disable the IGPU and reinstall windows to get back on without not being able to turn back on after restart.

In regards to PSU my TX750M conked out a while ago I RMA'd it but impatient so grabbed the RM1000X off some bloke on Facebook MP. Seemed genuine and at least I don't think its broken. Could be wrong though.

Latest BIOS F7 don't believe there is anymore on the website.
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom