9800x3d Windows Errors on PRO X870-P

[jatan21]

Hardware (https://ca.pcpartpicker.com/user/jatan21/saved/#view=jPXCrH):
Processor: 9800x3d
Motherboard: MSI PRO X870-P WIFI (BIOS: 7E47v1A31)
GPU: Integrated
MEMORY: TForce Delta RGB 32GB (2 x 16GB) DDR5 6000 CL30
PSU: Corsair RM850e
Cooler: Thermalright Phantom Spirit


Hi All,
I have noticed my system was suddenly unstable recently.

Spotify was not pausing when peeking on Windows taskbar.
Opening Windows Snip caused my system to hang.
When checking my windows event viewer, I can see lots of errors.

When I built my computer, I made sure to do stress tests to ensure everything was running correctly.
I was fully stable for 24 hours each of prime95, ycruncher, and TestMem5 (I did 5 hours of OCCT). I didn’t have windows errors during and after these tests.

Currently, restarting my PC gives me at least 3 windows.

I'm worried about the 9800x3d or motherboard have instability. The Asrock and 9800x3d reddit megathread is what I am referring to (Gamers Nexus did a video on it)

Is there any troubleshooting steps I should take to isolate the issue?

Things tried:
1. Check for System File corruption (sfc /scannow)
2. Reset the Motherboard BIOs. Once done, I used MSI's initial BIOs screen to enable PBO and EXPO1 (6000 CL30).
3. Use M-Flash to reflash the latest BIOs.
4. Repair Windows
5. Clean Install Windows.

 

[zerijelly]

Have you used BIOS default settings (without PBO and EXPO1 options being enabled) to check whether the system could work more stably?

 

[jatan21]

Hi zerijelly,

I just tried to disable PBO and EXPO. The CPU still is clocking up to 5225MHz, but RAM is running stock. The Windows errors are still popping up after each restart.
I repaired Windows after doing so and the issue has not gone away.

I see that John has been posting about moving back to an older BIOs, so I tried to also go back to 7E47v1A3 BIOs and that didn't help.

It seems like I forgot to include some of the error logs that I get:
1. """Device Association Service detected an endpoint discovery failure."""
2. """SCEP Certificate enrollment initialization for WORKGROUP\JATANPC$ via https://amd-keyid-4b7b776d35db9c32bddb98b4dded844a38a66acd.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps

Method: GET(16ms)
Stage: GetCACaps
The server name or address could not be resolved 0x80072ee7 (WinHttp: 12007 ERROR_WINHTTP_NAME_NOT_RESOLVED)"""
3. Printer issues like:
a) """A timeout was reached (45000 milliseconds) while waiting for the Spooler service to connect."""
b) """The Spooler service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."""
c) """PolicyManager: During Inbox found bad enrollment (82965F5A-6C65-4B7A-8075-488FCCE07D4E) during merge. Requesting merge (33AEC352-AA8D-4916-B5AE-00005D9F9BFE). Deleting policies for the enrollment. Enrollment state is (Your file waiting to be printed was deleted.)."""
d) """The Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly."""
e) """Installing printer driver Microsoft Print To PDF failed, error code 0x3, HRESULT 0x80070057. See the event user data for context information."""

 

[jatan21]

Hi All,

Quick update:

I recently installed the latest MSI BIOs 7E47v1A34 and this didn’t fix the issue.

Still getting issues on each boot and weird screen freezes on my web browser once under some load.

I recently heard about the MSI tomahawk with 9800x3d also exploding. Hopefully it’s not the same issue.

 

[Mattech]

I recently heard about the MSI tomahawk with 9800x3d also exploding. Hopefully it’s not the same issue.

There's only one incident regarding that combo (that I'm aware of) from November/December time frame, and the "explosion" was caused by user error. The CPU was installed incorrectly in the socket. You can see the investigation and conclusion here, but this was no fault of the board or the CPU:

 

[jatan21]

There's only one incident regarding that combo (that I'm aware of) from November/December time frame, and the "explosion" was caused by user error. The CPU was installed incorrectly in the socket. You can see the investigation and conclusion here, but this was no fault of the board or the CPU:

Hi Mattech,
I should have made it more clear what incident I was referring to. I watch gamer’s nexus, so I’m aware of the user error situation 4 months ago.

I was referring to issue shown in this Reddit thread 6 days ago.

https://www.reddit.com/r/pcmasterrace/comments/1j98yw0

I am also going off the GN video of the Asrock motherboards which show instability after running fine for a while.

I don’t believe that a CPU would boot up if the CPU is misaligned and shorts pins. I also was careful when installing me and my friend’s 9800x3d due to me hearing about these issues.

Thanks,
jatan21

 

[Mattech]

Hi Mattech,
I should have made it more clear what incident I was referring to. I watch gamer’s nexus, so I’m aware of the user error situation 4 months ago.

I was referring to issue shown in this Reddit thread 6 days ago.

https://www.reddit.com/r/pcmasterrace/comments/1j98yw0

I am also going off the GN video of the Asrock motherboards which show instability after running fine for a while.

I don’t believe that a CPU would boot up if the CPU is misaligned and shorts pins. I also was careful when installing me and my friend’s 9800x3d due to me hearing about these issues.

Thanks,
jatan21

It seems that most people have fixed their issues by setting the VSOC voltage and RAM voltage manually, and also typing in the RAM timings manually. It's almost like most of the current issues are voltage and RAM related, and all of these bad BIOS updates are causing the issues. Manually entering voltages and timings keep bad BIOS updates from running voltages outside of the norm to damage the CPU.