![]() |
X870E Taichi 0d debug code |
Post Reply ![]() |
Page 12> |
Author | |
iAmBeatStarr ![]() Newbie ![]() Joined: 02 Jul 2025 Location: UK Status: Offline Points: 15 |
![]() ![]() ![]() ![]() ![]() Posted: 02 Jul 2025 at 6:04pm |
I have the 0d error every time I restarted. I took my PC to back to the shop and they identified that it?™s a conflict with Razer Cortex. Once that is disabled it appears to restart fine and 0d error no longer an issue.
I will keep an eye on it. |
|
![]() |
|
Leon.nl ![]() Newbie ![]() Joined: 22 Jun 2025 Location: The Netherlands Status: Offline Points: 15 |
![]() ![]() ![]() ![]() ![]() |
Hi, have the same problem. How did you solve the problem? Thanks in advance.
|
|
![]() |
|
NDRE28 ![]() Senior Member ![]() ![]() Joined: 08 Sep 2024 Location: Romania Status: Offline Points: 1835 |
![]() ![]() ![]() ![]() ![]() |
Hi!
I'd RMA it. |
|
![]() |
|
Swooop ![]() Newbie ![]() Joined: 11 Apr 2025 Status: Offline Points: 65 |
![]() ![]() ![]() ![]() ![]() |
Well, so much for the problem being solved. Just rolled back my display drivers and during a reboot, system froze with the 0d debug code. Any other ideas? I did eventually get a reply back from someone from ASRock tech support. They want me to RMA the board but I really do not want to go that route. I had a horrible RMA experience with ASUS a few months back where they tried to claim the board I sent them had CID (customer induced damage). They then tried to charge me $70 more for a refurbished board than I had originally paid for a new board. And to make the experience even better, the new replacement I finally managed to get them to send me as a "courtesy", had the same issue. Turns out it was the newer PSU I was using that didnt play nice with the front panel audio. Asus never troubleshooted, just told me to RMA. So im pretty nervous about ASRock just telling me to RMA since I dont have any extra ram to swap out for testing. So I guess im asking, this sound like a hardware defect? Or more like a BIOS issue that can be fixed with an updated BIOS release?
|
|
![]() |
|
Swooop ![]() Newbie ![]() Joined: 11 Apr 2025 Status: Offline Points: 65 |
![]() ![]() ![]() ![]() ![]() |
Well, thanks to everyone's help, I think the problem has been solved. I disabled EXPO as suggested to see if the issue disappeared, It did. So then I re-enabled EXPO and dug around in the BIOS settings looking for the "Memory Context Restore" and "Power Down Enable" settings. I disabled those as suggested and went to see if rebooting would give the 0d error code. It didn't, and hasn't in the handful of times I've rebooted. I then ran Memtest86 overnight, it only ran for four hours with the default test, and it showed no errors.
A couple questions though, 1. With those two BIOS settings disabled, am I losing any performance or ability to do any eventual overclocking with my system if I decided too? 2. Could a new BIOS release from ASRock fix the issue and then allow me to have EXPO, and the two BIOS setting all enabled? 3. After I disabled "Memory Context Restore" in Advanced/AMD CBS/DDR Options/DDR Memory Features, I then saw a "Memory Context Restore" option in the OC Tweaker main BIOS page, and that one is enabled. Should they both be disabled? Or should I just not mess with it since everything seems to be working fine now. Well, other than bootup taking a little longer, but I can live with that. Thanks again to everyone for their help! |
|
![]() |
|
NDRE28 ![]() Senior Member ![]() ![]() Joined: 08 Sep 2024 Location: Romania Status: Offline Points: 1835 |
![]() ![]() ![]() ![]() ![]() |
Yeah.
I agree. I also have almost the same memory kit as the OP, on an X670E Taichi, and a R9 9950X. In my case, everything ran well, however when testing my RAM, extensively, with MemTest86, I got some errors. So, I've reduced the DRAM frequency from DDR5-6000 to DDR5-5800, leaving voltage & timings just as they've been set by the EXPO profile. That solved the errors for me. The system is rock stable: ASRock. Edited by NDRE28 - 18 Apr 2025 at 12:34am |
|
![]() |
|
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 29063 |
![]() ![]() ![]() ![]() ![]() |
Also check this thread:
https://forum.asrock.com/forum_posts.asp?TID=18902&title=error-code-0d Different board but same code, maybe something here will help. |
|
![]() |
|
![]() |
|
M440 ![]() Senior Member ![]() Joined: 12 Jul 2023 Status: Offline Points: 4580 |
![]() ![]() ![]() ![]() ![]() |
i would reseat the cpu in the socket
|
|
asrock b650m-hdv/m.2, ryzen 7700x@85watt, arch/kde
|
|
![]() |
|
Swooop ![]() Newbie ![]() Joined: 11 Apr 2025 Status: Offline Points: 65 |
![]() ![]() ![]() ![]() ![]() |
The manual doesn't mention this specific code. The closest thing I see is 0xD0 DXE_CPU_ERROR. But like I said, the code I'm getting is 0d. I sent an message to ASRock tech support on 4-10-25, but I havent heard back from them yet.
|
|
![]() |
|
M440 ![]() Senior Member ![]() Joined: 12 Jul 2023 Status: Offline Points: 4580 |
![]() ![]() ![]() ![]() ![]() |
what the manual says about this code?
|
|
asrock b650m-hdv/m.2, ryzen 7700x@85watt, arch/kde
|
|
![]() |
Post Reply ![]() |
Page 12> |
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |