[SOLVED] Random CPU BSODs (PSHED.dll - ntoskrnl.exe) ?

[thevoidblade]

Hey,

I keep getting a bunch of bluescreen errors that are related to the CPU as it always lists intelgenuine.sys as the problem. I've never had these issues before and was wondering what the cause might be? My PC is quite old so maybe the processor is just failing. Having said that, it is also an unsupported processor, but I have never had this issue before either. I am suspecting I might need to rollback to Windows 10, but then I have been on Windows 11 for over a year now and never had issues. Just curious to know if anyone can see anything that suggests what the issue is. If you need dump files I can provide no problem.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidumps\032223-5296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8042dc00000 PsLoadedModuleList = 0xfffff8042e813430
Debug session time: Wed Mar 22 00:51:47.116 2023 (UTC + 0:00)
System Uptime: 0 days 15:37:10.250
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8042e029400 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8880f95fc910=0000000000000124
3: 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
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: ffffc40b7fc16028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, 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: 1171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3459

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 032223-5296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc40b7fc16028

BUGCHECK_P3: bf800000

BUGCHECK_P4: 124

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Mullvad VPN.ex

STACK_TEXT:
ffff8880f95fc908 fffff8042e0f403b : 0000000000000124 0000000000000000 ffffc40b7fc16028 00000000bf800000 : nt!KeBugCheckEx
ffff8880f95fc910 fffff804304010c0 : 0000000000000000 ffff8880f95fc9e9 ffffc40b7fc16028 ffffc40b7d529090 : nt!HalBugCheckSystem+0xeb
ffff8880f95fc950 fffff8042e1fe20f : 0000000000000000 ffff8880f95fc9e9 ffffc40b7fc16028 ccccccc35d50c483 : PSHED!PshedBugCheckSystem+0x10
ffff8880f95fc980 fffff8042e0f5a6a : ffffc40b7fc89bc0 ffffc40b7fc89bc0 ffffc40b7d5290e0 fffff8042dfbfe3a : nt!WheaReportHwError+0x38f
ffff8880f95fca50 fffff8042e0f5eb5 : 0000000000000003 ffffc40b00000003 fffffa8965327000 fffffa896532d000 : nt!HalpMcaReportError+0xb2
ffff8880f95fcbc0 fffff8042e0f5d54 : ffffc40b7d526790 8b48d23300000001 0000000000000000 00b8248400000000 : nt!HalpMceHandlerCore+0x12d
ffff8880f95fcc20 fffff8042e0f5ffd : 0000000000000004 0000000000000001 0000000000000000 5718708948106889 : nt!HalpMceHandler+0xe0
ffff8880f95fcc60 fffff8042e0f51b2 : 0000000000000000 0000000000000000 ffff8880f95fcef0 8b20245c8b48ffff : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8880f95fcc90 fffff8042e0f797b : ffffc40b7d526790 8b48000166dae808 17bf0775c08548f0 438b4427ebc00000 : nt!HalpHandleMachineCheck+0x62
ffff8880f95fccc0 fffff8042e15a729 : 894108438b068949 bf05eb0075894807 74db8548c0430001 01686be8cb8b4808 : nt!HalHandleMcheck+0x3b
ffff8880f95fccf0 fffff8042e03b23e : 5f4130c483486024 ccccccccc35f5e41 74894808245c8948 8b48564157551024 : nt!KiHandleMcheck+0x9
ffff8880f95fcd20 fffff8042e03ae53 : 0000000000000010 0000000000000000 ffffc40b934c6720 ffff8880f95fcef0 : nt!KxMcheckAbort+0x7e
ffff8880f95fce60 fffff8042df4d315 : fffff8043d9f1c08 ffffc40b7fb6aa90 0000000000000004 fffff8042de9c7c3 : nt!KiMcheckAbort+0x2d3
fffffa896532b780 fffff8043db07329 : ffffc40b7ded0060 0000000000000000 ffffc40b883ae000 0000000000000004 : nt!ExTryAcquirePushLockSharedEx+0x105
fffffa896532b7d0 fffff8043db02857 : ffffd406653f3688 ffffffffffffffff fffffa896532bb00 ffffc40b883ae000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0xa9
fffffa896532b9e0 fffff8043db02445 : 000000e2f05ff200 ffffc40b88a03cd0 0000000000000000 0000000010000000 : dxgkrnl!DxgkWaitForVerticalBlankEventInternal+0x3d7
fffffa896532ca60 fffff8042e03e1e5 : ffffc40b934c6080 fffffffffff3cb00 0000000000000000 ffffc40b00000000 : dxgkrnl!DxgkWaitForVerticalBlankEvent+0xe5
fffffa896532cae0 00007ffd4d076194 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000e2f05ff1c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`4d076194


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------

​

 

[Fix_that_Glitch]

What is your pc build?

 

[thevoidblade]

What is your pc build?

I5 4690K (overclocked to 4.3 ghz)
GTX 970
16gb Ram

Thus why I say it is an unsupported build for Windows 11. I suspect that might be the issue actually, but strangely the dump shows the issue as coming from a third party program and not an OS program.

 

[Fix_that_Glitch]

I5 4690K (overclocked to 4.3 ghz)
GTX 970
16gb Ram

Thus why I say it is an unsupported build for Windows 11. I suspect that might be the issue actually, but strangely the dump shows the issue as coming from a third party program and not an OS program.

I am not familiar with mullvad vpn. Have you tried disabling it to see if the crashes stop? What motherboard are you using? Is the chipset driver, if there is one , up to date along with the bios?

 

[thevoidblade]

I am not familiar with mullvad vpn. Have you tried disabling it to see if the crashes stop? What motherboard are you using? Is the chipset driver, if there is one , up to date along with the bios?

Interestingly, it has been triggered by a bunch of different programs. Not just Mullvad. So, to list them:

1. OverwolfHelper
2. svchost
3. Overwatch
4. Battle.net
5. Mullvad

Motherboard is a MSI Z87 GD65. All drivers are up to date. Same for Bios. Nothing out of the ordinary.

 

[Fix_that_Glitch]

Try resetting your bios to optimal setting. I would also try one memory stick at a time to rule those out.

 

[thevoidblade]

Try resetting your bios to optimal setting. I would also try one memory stick at a time to rule those out.

Yeah. I was thinking to undo the overclock and test the ram next. I'll give a try and see how I get on. Sadly, this glitch tends to only kick in once every few days. Makes testing it a bit of a challenge. Thanks for the advice though! I'll leave thread for now and keep it updated.

 

[johnbl]

you might put the actual memory dump on a server, share it for public access and post a link.
I can dump the !errrec structure and look for common driver issues

 

[thevoidblade]

you might put the actual memory dump on a server, share it for public access and post a link.
I can dump the !errrec structure and look for common driver issues

Sure! I can place the actual minidump up on Google drive easily enough. Link is below for the most recent one. I have 4 others with the same error. Let me know if you want or need to take a look at those. I really appreciate the help!

BSOD Dump

 

[johnbl]

cpu called the shutdown. The system had been running for 15 hours.
the returned error code indicated that basically it failed for a unknown reason. most often for a old machine like this I would be looking for a overheating problem. Maybe a overheated gpu, or cpu. I would look for fans that are not spinning. ie blow out the dust from the gpu and cpu and maybe the psu. check psu voltages.

since the stack had a call to the gpu you might remove your overclock software RTCore64.sys from 2020
you can use microsoft autoruns, to find the driver and prevent it from loading.


note: bunches of old drivers installed, network issues
BIOS Release Date 05/19/2015
Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Product Z87-GD65 GAMING (MS-7845)

 

[thevoidblade]

cpu called the shutdown. The system had been running for 15 hours.
the returned error code indicated that basically it failed for a unknown reason. most often for a old machine like this I would be looking for a overheating problem. Maybe a overheated gpu, or cpu. I would look for fans that are not spinning. ie blow out the dust from the gpu and cpu and maybe the psu. check psu voltages.

since the stack had a call to the gpu you might remove your overclock software RTCore64.sys from 2020
you can use microsoft autoruns, to find the driver and prevent it from loading.


note: bunches of old drivers installed, network issues
BIOS Release Date 05/19/2015
Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Product Z87-GD65 GAMING (MS-7845)

Very interesting. I've been watching for overheats. Given the PC a clean and all fans are working so no overheating that I have seen so far, but might have been at the time. I've undone any and all overclocks too cause I figured they might be related. Having said that, under a stress test I was getting a max of 77c on overclock so I don't think that was the issue honestly.

You mention bunches of old drivers. I assume you mean for things like the chipset and so on. They are old sadly as they are the newest versions available as it stands. I can probably uninstall RTCore too. I know that's MSI Afterburner.

You mention network issues. I've not had any that I've noticed beyond the odd DNS error from my VPN. What else are you seeing?

Another point is that the PC seems to always fail on boot because fast start up seemed to keep failing.

Windows failed fast startup with error status 0xC00000D4.

Got a couple of these as above. I've since disabled it. Maybe that is contributing.

 

[johnbl]

remove this:
Intel(R) Extreme Tuning Utility Device Driver
XtuAcpiDriver.sys Wed Apr 12 01:58:50 2017
use microsoft autoruns and reboot
(it is the only driver that would be a likely cause of this bugcheck)

remove:
ISCTD64.sys Tue Nov 27 11:52:34 2012 (very old intel driver)
intel (R) Smart Connect software (dead product, you should remove the driver)

TeeDriverW8x64.sys Mon Oct 2 23:21:38 2017 (old version for windows 8, hope intel driver update tool will update it.)
Intel® Driver & Support Assistant

e2xw10x64.sys Wed Sep 14 13:52:26 2016
(old Killer E2400/2500 Gigabit Ethernet driver)
(i think intel bought the company, maybe they make a driver update)



EPMVolFl.sys Wed Oct 17 19:40:11 2018 (old disk performance driver?)
from EaseUS Partition Master Free Edition
(also two other drivers)


ignis.sys Wed Sep 30 02:19:49 2020 (part of Bitdefender?)
trufos.sys Wed Nov 30 14:23:47 2022 (guess it is part of bitdefender antivirus)

seems to be various files for vpn installed.
droidcamvide driver (name truncated)

pwdrvio.sys Mon Jun 15 18:43:45 2009
(old partition wizard driver)

 

[thevoidblade]

remove this:
Intel(R) Extreme Tuning Utility Device Driver
XtuAcpiDriver.sys Wed Apr 12 01:58:50 2017
use microsoft autoruns and reboot
(it is the only driver that would be a likely cause of this bugcheck)

remove:
ISCTD64.sys Tue Nov 27 11:52:34 2012 (very old intel driver)
intel (R) Smart Connect software (dead product, you should remove the driver)

TeeDriverW8x64.sys Mon Oct 2 23:21:38 2017 (old version for windows 8, hope intel driver update tool will update it.)
Intel® Driver & Support Assistant

e2xw10x64.sys Wed Sep 14 13:52:26 2016
(old Killer E2400/2500 Gigabit Ethernet driver)
(i think intel bought the company, maybe they make a driver update)



EPMVolFl.sys Wed Oct 17 19:40:11 2018 (old disk performance driver?)
from EaseUS Partition Master Free Edition
(also two other drivers)


ignis.sys Wed Sep 30 02:19:49 2020 (part of Bitdefender?)
trufos.sys Wed Nov 30 14:23:47 2022 (guess it is part of bitdefender antivirus)

seems to be various files for vpn installed.
droidcamvide driver (name truncated)

pwdrvio.sys Mon Jun 15 18:43:45 2009
(old partition wizard driver)

Removed. Seems pretty stable since I disabled fast startup interestingly. No updates for any of the drivers you listed sadly. But I expected that. Thanks again for the advice and suggestions. I might try placing back my overclock at some point and see how I get on. But for now at least no more BSODs. Fingers crossed it stays that way.