question

DzmitryHorski-2292 avatar image
0 Votes"
DzmitryHorski-2292 asked vigneshsampath-9987 answered

(Win10) Random BSOD - WHEA_UNCORRECTABLE_ERROR (ntoskrnl.exe, PSHED.dll)

Hello guys,

I bought a PC in August and I've been catching BSODs randomly since then.
BSOD happens at random periods of time, no pattern to reproducve was found. Usually, PC crashes once a day every day.
The errors that appear during BSOD were mostly WHEA_UNCORRECTABLE_ERROR.
BlueScreenView showed that drivers / apps causing the crash include ntoskrnl.exe and PSHED.dll.
I went with this problem to the service guys at the place where I bought the PC.
First time, they re-installed Windows and updated BIOS (currently, it's said to be the latest version).
Second time, they replaced RAM, but it didn't help.
Also, I ran Intel Diagnostic Tool tests yesterday - all passed.

here's the archive with some minidump files - https://drive.google.com/file/d/1K-wBof4AWwz7lbZ1Bv_RGenCREl7KfWE/view?usp=sharing

My specs:

CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
Motherboard: MSI B460M-A PRO (MS-7C88)
RAM: AMD Radeon R7 Performance 16GB DDR4 PC4-21300 R7416G2606U2S (2x16Gb)
GPU: GeForce RTX 2070 SUPER 8Gb
SSD: Hynix BC501 512GB M.2 2242 PCIe HFM512GDHTNG-8310A
HDD: TOSHIBA HDWD110 1Tb
CPU cooler: DeepCool GAMMAXX 400 v2
PSU: Zalman ZM700-LXII

OS: Windows 10 Pro 10.0.19041

Here's what WinDBG showed me for MEMORY.dmp file:



  •                      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: ffffa50be4d02028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, 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


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 19041.1.amd64fre.vb_release.191206-1406

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7C88

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.40

BIOS_DATE: 08/21/2020

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: B460M-A PRO (MS-7C88)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa50be4d02028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 14

CPU_MHZ: e70

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: a5

CPU_STEPPING: 5

CPU_MICROCODE: 6,a5,5,0 (F,M,S,R) SIG: CA'00000000 (cache) CA'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: SearchApp.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-IS5C9EB

ANALYSIS_SESSION_TIME: 10-12-2020 12:41:55.0517

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

STACK_TEXT:
ffffc901`05660908 fffff802`15ab323a : 00000000`00000124 00000000`00000000 ffffa50b`e4d02028 00000000`b2000000 : nt!KeBugCheckEx
ffffc901`05660910 fffff802`120815b0 : 00000000`00000000 ffffa50b`e4d02028 ffffa50b`dd0dbe80 ffffa50b`e4d02028 : nt!HalBugCheckSystem+0xca
ffffc901`05660950 fffff802`15bb4d3e : 00000000`00000000 ffffc901`056609f9 ffffa50b`e4d02028 ffffa50b`dd0dbe80 : PSHED!PshedBugCheckSystem+0x10
ffffc901`05660980 fffff802`15ab4b61 : ffffa50b`e4d3b540 ffffa50b`e4d3b540 ffffa50b`dd0dbed0 ffffa50b`dd0dbe80 : nt!WheaReportHwError+0x46e
ffffc901`05660a60 fffff802`15ab4ed3 : 00000000`0000000b ffffa50b`dd0dbed0 ffffa50b`dd0dbe80 00000000`0000000b : nt!HalpMcaReportError+0xb1
ffffc901`05660bd0 fffff802`15ab4db0 : ffffa50b`dcebe0e8 01d5ad0b`00000001 00000000`00000000 00000000`00000a00 : nt!HalpMceHandlerCore+0xef
ffffc901`05660c20 fffff802`15ab5001 : 00000000`00000014 00000000`00000001 00000000`00000000 01d5ad0b`6773435e : nt!HalpMceHandler+0xe0
ffffc901`05660c60 fffff802`15ab426b : 00000000`00000000 00000000`00000000 ffffc901`05660ef0 00000000`00000020 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffc901`05660c90 fffff802`15ab6ab5 : ffffa50b`dcebe0e8 00690075`006d002e 00020000`00054b36 00000000`00620078 : nt!HalpHandleMachineCheck+0x5f
ffffc901`05660cc0 fffff802`15b0c1b9 : 01d5ad0b`60797def 01d6998c`9bc7396e 01d5ad0b`60797def 00000000`00001000 : nt!HalHandleMcheck+0x35
ffffc901`05660cf0 fffff802`15a035fa : 0073006f`00680010 006d0061`006e0074 00780065`002e0065 0075006d`002e0065 : nt!KiHandleMcheck+0x9
ffffc901`05660d20 fffff802`15a032b7 : 00000000`00000000 00000000`00000000 000001ac`55ade18b 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffc901`05660e60 00007ffc`eb5e8340 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000053`37dfd008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`eb5e8340


THREAD_SHA1_HASH_MOD_FUNC: 5c91c3d76fc9f150adf6d77dbfe8ac022a356ed3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 17b3c337f93b19cf93c0b6cfb3a177ab9a84c74f

THREAD_SHA1_HASH_MOD: 75ec0b4d7f9e15e8f6f461f510dc6054820a8f0e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR__UNKNOWN

TARGET_TIME: 2020-10-11T20:27:26.000Z

OSBUILD: 19041

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1994-09-07 22:05:02

BUILDDATESTAMP_STR: 191206-1406

BUILDLAB_STR: vb_release

BUILDOSVER_STR: 10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME: b4e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor__unknown

FAILURE_ID_HASH: {86f02343-3a24-6d22-b341-ad6c04114faf}

Followup: MachineOwner




two questions I have:

  1. there is this line - PROCESS_NAME: SearchApp.exe. Can it be that Cortana is messing with my system somehow?

  2. this line - FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN. Does it mean my CPU is behind the crashes? Also, in BlueScreenView I saw the mention of mcupdate_GenuineIntel.dll. Can it be related somehow?

Please help!

windows-10-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Dzmitry, did you ever find a solution to your issue?

I am having the exact same problem as you. ntoskrnl.exe, and PSHED.dll are causing BSOD. It's been happening since I was forced to update Windows to 20H2. The only piece of hardware that is common across our systems is the GeForce RTX 2070 SUPER 8Gb. Last time it crashed was while playing Doom Eternal but I usually get a BSOD right after the computer wakes from sleep.

0 Votes 0 ·
CarlFan-5627 avatar image
0 Votes"
CarlFan-5627 answered DzmitryHorski-2292 commented

Hi,
Based on the dumps you provided, it includes some process names.
EpicGamesLauncher.exe
atmgr.exe
ModernWarfare.exe
It means that the process crashed when BSOD. These process could point related application.
But we need to know what causes these process crashes.
0x124 always points to a hardware error. According to the dump, I found the stack information below:
nvlddmkm+0x11d1ef
So update and reinstall your video card driver, motherboard driver firstly to check.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

hey thanks for your answer

my gpu driver was reinstalled last weekend, and now I have the latest version
they said I have latest BIOS too
and I think all of the drivers are okay at this point

here is another portion of crash dumps, maybe it will help? - https://drive.google.com/file/d/172eq-tLA9pDkJ-F4Zgm9HOGAyearg6V6/view?usp=sharing

thank you in advance

0 Votes 0 ·
PrabodhaKumarSarangi-9891 avatar image
0 Votes"
PrabodhaKumarSarangi-9891 answered

Hi, I had experienced such BSOD in few systems in past with windows 10, and I ended up finding with bad HDD. Most probably the hard disk not working perfectly. Even I purchased a new Dell laptop, and after few months such BSOD appear, but system check all OK. I directly replace the hard disk with a new one, and since then no issue. Even that old hard disk is working OK inside a small casing with USB connect (like an external storage). It surprise me!

You can try replacing another hard disk (temporary) and install windows 10 again and check if still you have issue.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

victorlucena-0392 avatar image
0 Votes"
victorlucena-0392 answered

I have the same problem, solved this uninstaling the realtek audio driver and disabling hdmi nvidia audio in nvidia control pannel, Seems that is a conflict between realtek and nvidia.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

vigneshsampath-9987 avatar image
0 Votes"
vigneshsampath-9987 answered

i had the same problem after disabling global c-state in bios it works fine for me no bsod error

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.