Random BSODs (CRITICAL_PROCESS_DIED, UNEXPECTED_STORE_EXCEPTION) with no minidumps after reinstalling Windows

nephacks

Member
Joined
Jun 27, 2023
Posts
5
Hello everyone,


I reinstalled Windows 2 days ago because I had run Redline Stealer and had some other issues with networking. After reinstalling I have bluescreened a total of 20+ times with various stopcodes like CRITICAL_PROCESS_DIED, UNEXPECTED_STORE_EXCEPTION.

I have taken some steps to try to fix this to no avail. I forced a CRITICAL_PROCESS_DIED crash to test if minidumps even get created which they do, but when it BSODs by itself no minidump gets created.
This happens when I'm doing anything (Gaming, Browsing and watching videos). It does not seem to happen more during intense computation. Sometimes it can crash 20 minutes after boot, sometimes a hour or two.
This doesn't seem to be a hardware issue, because I have checked my drives and RAM. I have updated my BIOS too

Here are my specs from Speccy
http://speccy.piriform.com/results/ecBi0uh33bdo8kLsEcOPKbP
 

Attachments

I wouldn't be so sure it really is fixed, I came across this in your System log (repeatedly)...
Code:
Event[629]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-27T14:00:20.2750000Z
  Event ID: 17
  Task: N/A
  Level: Warning 
  Opcode: Info  g
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: wiretoaster
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Endpoint
Error Source: Advanced Error Reporting (PCI Express)

Primary Bus:Device:Function: 0x2:0x0:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_10EC&DEV_8168&SUBSYS_8767103C&REV_16
Secondary Device Name:
VEN_10EC&DEV_8168 is the code for your RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller. You might have a problem with that card, so suspect that first if you have further problems.

 
I wouldn't be so sure it really is fixed, I came across this in your System log (repeatedly)...
Code:
Event[629]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-27T14:00:20.2750000Z
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info  g
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: wiretoaster
  Description:
A corrected hardware error has occurred.

Component: PCI Express Endpoint
Error Source: Advanced Error Reporting (PCI Express)

Primary Bus:Device:Function: 0x2:0x0:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_10EC&DEV_8168&SUBSYS_8767103C&REV_16
Secondary Device Name:
VEN_10EC&DEV_8168 is the code for your RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller. You might have a problem with that card, so suspect that first if you have further problems.

I'm gonna disable the Ethernet controller again, even though I have tried disabling the Ethernet controller before to no avail, maybe it'll make a difference.
But now that I'm BSODing again after a reinstall of 10, I'm unmarking this thread as solved.
Now I have seen only the stopcode WHEA_UNCORRECTABLE_ERROR. Still no dumps get created but there is a WHEA-Logger event.
I have rerun the BSOD Collection App and attached the ZIP to this reply.
 

Attachments

From your System log I notice a pattern; immediately prior (within the same second) to each of the two WHEA hardware failure message is a message about esif_uf.exe changing a 'policy scheme'...
Code:
Event[104]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-28T10:59:02.1990000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-5JJHRR0
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Event[105]:
  Log Name: System
  Source: Microsoft-Windows-Winlogon
  Date: 2023-06-28T10:59:02.1600000Z
  Event ID: 7001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-5JJHRR0
  Description:
User Logon Notification for Customer Experience Improvement Program

Event[106]:
  Log Name: System
  Source: Microsoft-Windows-UserModePowerService
  Date: 2023-06-28T10:59:02.1450000Z
  Event ID: 12
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-5JJHRR0
  Description:
Process C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_897ea327b3fe52f7\esif_uf.exe (process ID:5088) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}


Event[189]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-28T10:34:44.3990000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-5JJHRR0
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Event[190]:
  Log Name: System
  Source: Microsoft-Windows-UserModePowerService
  Date: 2023-06-28T10:34:44.3400000Z
  Event ID: 12
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-5JJHRR0
  Description:
Process C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_897ea327b3fe52f7\esif_uf.exe (process ID:5008) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}
The esif_uf.exe executable is a component of the Intel Dynamic Platform and Thermal Framework, which is used "to resolve fan noise, overheating, and performance-related issues of the system". It would seem from the above that this tool is causing some sort of hardware failure when it makes this policy change. I would suggest at the very least temporarily uninstalling this tool and see whether the problem stops.

We also need to see whether we can get you writing dump files. To write dumps ALL of the following must be true...
  • The page file must be on the same drive as your operating system
  • Set page file to "system managed" on the OS drive
  • Set system crash/recovery options to "Automatic memory dump"
  • Windows Error Reporting (WER) system service should be set to MANUAL
  • User account control must be running
  • Sometimes SSD drives with older firmware do not create dump files (update firmware)
  • Cleaner applications like Ccleaner delete DMP files so don't run them until your issue is fixed.
In addition, you seem to be deliberately clearing your event logs? Either that, or your specified log size is very small. Each log you've uploaded has been only for a day or two. Please stop clearing the event logs, historical messages in there can be extremely valuable and unless you're desperately short of disk space there is no good reason to ever delete them. To increase your System log size, open the Event Viewer via the command eventvwr, expand the Windows Logs in the left-hand pane, right-click on System and select Properties. In there you can set the maxium size of the System log and what happens when it fills. The default size I believe is 20MB, which is way too small for most people. I have mine set to 1GB (1048576KB) and I use the default 'overwrite older events'.
 
I couldn't uninstall the Intel Dynamic Platform and Thermal Framework, not showing up in settings or control panel nor third party uninstallers. I found out that it does run as a service called "Intel(R) Dynamic Tuning service"
I set it to disabled and I see no performance decrease in games or any stability issues after disabiling it. I haven't crashed since 2 hours so I guess it has worked. I will report back in a few hours if I have crashed.

I don't delete Event Logs, like I mentioned I installed Windows 10 instead of 11, thinking it was a OS issue.
I don't run any cleaner applications as for me they are snake oil. WER service is set to manual, page file is on the same drive as the OS and writing debugging infomation is set to "Automatic memory dump".
 
You could ask OP to run this CPU test from Intel just to sleep better!

CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)

Description: A fatal hardware error has occurred.

The message can't get much plainer than that from the dump/file you posted.

We are obviously dealing with a hardware error here along with a 0x124 or perhaps a 0x9c (if still around) bugcheck. The only time that Windows can literally tell you which hardware part has failed is when an NTSTATUS error code is also included that translates to "I/O error". Not much guesswork once that message is found. Then it becomes a hunt to find THE bad drive among the numerous drives installed or just plugged in for a while. Unfortunately, no I/O error code here, so all hardware becomes suspect - even the mobo.

As @x BlueRobot said, Driver Verifier will not help us here. D/V checks kernel mode drivers as well as video and any other drivers that transition between user mode and kernel mode and back again. Outside of kernel mode drivers themselves, very few others do this (like video)/are allowed to transition.

Was OP instructed to reinstall Windows or did OP do it on his own?
- What was the reason?
- Is this the first and only time a reinstall was done?

How old is the system?
When was it purchased (as new)?
Any chance that HP warranty still applies? (1 year unless extended warranty purchased).

Regards. . .

jcgriff2
 
I have already run the Intel Processor Diagnostic Tool and it passed successfully. I haven't had a BSOD so I'm assuming it's all fine now. I have been running intensive games and just even leaving my system on.
All my drives are fine, CrystalDiskInfo shows all health status as good.
The system is from 2021 and was purchased in 2021 from a retailer as new. HP Warranty (Care Pack) still applies for another 6 months, though HP support was not very helpful so I gave up on that.
I reinstalled Windows on my own.
I'm assuming that "Intel Dynamic Platform and Thermal Framework" was probably doing something that made my CPU hang or something and as a result cause a bluescreen and not create dump files
I will be definitely considering donating to support the site. Thank you all.
 
I believe that @jcgriff2 was referring to a different thread. I'm glad your system seems to be okay at the moment and thank you for considering a donation.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top