AMD Motherboards - x670e Taichi can't run stable with ACPI C-States

Print Page | Close Window

x670e Taichi can't run stable with ACPI C-States

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=25386
Printed Date: 07 May 2024 at 8:11am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: x670e Taichi can't run stable with ACPI C-States

Posted By: EEPS
Subject: x670e Taichi can't run stable with ACPI C-States
Date Posted: 21 Jan 2023 at 7:43am

Hello, I have a X670E Taichi with a 7950X. Since I got it, I noticed all sorts of instability, even when running with no OC (reset CMOS). At first I thought is was RAM issue, but now I don't think so. Initially I had 2x16GB Trident neo Z5 6000 RAM. I tried each stick separately in both slot B2 and B1 and still have the same stability issues (crashes in windows, segfaults in linux). Then I bought a second kit of the same type and tried with those, same issue. I am currently on BIOS 1.11.CB08 after downgrading from the now removed 1.14. I have tried every 1.11.XX version though and see the same issue.

The only way I can get my system stable is to go into BIOS and disable any and all settings related to ACPI C-States. There are several places to go, to disable definition of C-States, then I also disable Global C-State Control. With these settings I seem completely stable, however I should not have to resort to this...

Just wondering what else I should try/test/suspect in my setup...

Thanks.

Replies:

Posted By: EEPS
Date Posted: 21 Jan 2023 at 7:50am

Sorry mean memory slots B2 and A2

Posted By: Katana1074
Date Posted: 21 Jan 2023 at 6:43pm

Can you provide windows logs after your board has crashed ?

I have a x670 Taichi and its been rock solid...

Posted By: EEPS
Date Posted: 21 Jan 2023 at 10:10pm

Which logs and how do I get them? I have seen many BSODs, most seem to do with memory access violations. In linux I see segfaults and kernel memory access violation. Right now I have to reinstall windows because it appears to be corrupted after testing and the start menu no longer appe. I will do that and see what logs I can get.

Posted By: Katana1074
Date Posted: 21 Jan 2023 at 10:55pm

Hi there...

In Windows Right Click start menu and select event viewer the select Administrative events look for errors and warnings post back here....

You wouldnt be by chance running the integrated Gpu and another graphics card ie rtx3090 i had no end of bother till i disabled the processor gpu...

Regards

Posted By: EEPS
Date Posted: 21 Jan 2023 at 11:21pm

Thanks, no I have a 7900 XT.

Posted By: EEPS
Date Posted: 22 Jan 2023 at 12:40am

Now I don't know what is going on, I can't even make it through the Windows 11 setup process, it randomly reboots. It installed successfully, but when asking for my info it just reboots. This is in my "stable" config with c-states disabled... so maybe not so stable after all. I do have all 4 sticks of ram in. I may try with just one, then maybe reseat my CPU I guess... not sure what else to try.

Posted By: Katana1074
Date Posted: 22 Jan 2023 at 12:50am

this tells me that its not c-states that is the issue there is something else going on...

Try disabling the igpu and any other controllers you might not need in bios try with only 1 ram stick inserted....

Posted By: Katana1074
Date Posted: 22 Jan 2023 at 12:51am

as an after thought,4 sticks of ram is very hard on the memory controller....

Posted By: EEPS
Date Posted: 22 Jan 2023 at 3:59am

Just reinstalled windows with a single stick of RAM in B2 slot and removed my GFX card and just using the integrated for now and everything seemed fine, but then after installing updates and rebooting I got a BSOD with SYSTEM_SERVICE_EXCEPTION. Then after it restarted I thought I should install amd adrenalin driver in case its a driver issue, but I got an "Oops! Something went wrong" during the install.. so no I don't think it is stable even with one stick ram.

Posted By: EEPS
Date Posted: 22 Jan 2023 at 4:05am

Now another SYSTEM_SERVICE_EXCEPTION then KMOD_EXCEPTION_NOT_HANDLED so can't even get into windows hardly now without BSOD and eventually will corrupt the drive like last time... So I will try to disable C-State stuff again to see if I can just get in long enough to get logs. Anyway at this point I am contemplating buying the cheapest 7000 processor (7600) and dropping it in just to see if it is the CPU or MoBo.

Posted By: EEPS
Date Posted: 22 Jan 2023 at 4:14am

There are a bunch of errors in the logs, but the two "BugCheck" (BSOD) ones I see are:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          1/21/2023 8:35:21 AM
Event ID:      1001
Task Category: None
Level:        Error
Keywords:
User:          SYSTEM
Computer:      radagast
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffd80a8effd008, 0x0000000000000002, 0xfffff802b0616dbf, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a14e3847-9b4f-4658-8265-d63d50f3c938.
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" rel="nofollow - http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" />
    <EventID>1001</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2023-01-21T16:35:21.9042473Z" />
    <EventRecordID>621</EventRecordID>
    <Correlation />
    <Execution ProcessID="1360" ThreadID="1364" />
    <Channel>System</Channel>
    <Computer>radagast</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="param1">0x00000050 (0xffffd80a8effd008, 0x0000000000000002, 0xfffff802b0616dbf, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">a14e3847-9b4f-4658-8265-d63d50f3c938</Data>
</EventData>
</Event>

and:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          1/21/2023 11:52:52 AM
Event ID:      1001
Task Category: None
Level:        Error
Keywords:
User:          SYSTEM
Computer:      radagast
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8003e2adec6, 0xfffff2048ceb8030, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 630ae38e-a642-4a45-a028-c914cee89460.
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" rel="nofollow - http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" />
    <EventID>1001</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2023-01-21T19:52:52.8359433Z" />
    <EventRecordID>2242</EventRecordID>
    <Correlation />
    <Execution ProcessID="1380" ThreadID="1384" />
    <Channel>System</Channel>
    <Computer>radagast</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff8003e2adec6, 0xfffff2048ceb8030, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">630ae38e-a642-4a45-a028-c914cee89460</Data>
</EventData>
</Event>

Posted By: Katana1074
Date Posted: 22 Jan 2023 at 4:35am

looking at those logs it seems memory related,what is your current memory speed with 1 dimm ?

Posted By: EEPS
Date Posted: 22 Jan 2023 at 4:43am

It defaults to 4800

Posted By: EEPS
Date Posted: 22 Jan 2023 at 4:50am

Reseated and repasted CPU and inspected socket, looks fine. Reboot this time with 2 sticks RAM in A2, B2 and 4800MHz and got immediate BSOD, IRQ_NOT_LESS_OR_EQUAL:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          1/21/2023 12:17:59 PM
Event ID:      1001
Task Category: None
Level:        Error
Keywords:
User:          SYSTEM
Computer:      radagast
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffff957fcd63690f, 0x0000000000000002, 0x0000000000000000, 0xfffff8053b6adcbe). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fbab0e2d-c5b9-4d82-9368-5315bd03ad47.
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" rel="nofollow - http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" />
    <EventID>1001</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2023-01-21T20:17:59.7207409Z" />
    <EventRecordID>2667</EventRecordID>
    <Correlation />
    <Execution ProcessID="1416" ThreadID="1420" />
    <Channel>System</Channel>
    <Computer>radagast</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="param1">0x0000000a (0xffff957fcd63690f, 0x0000000000000002, 0x0000000000000000, 0xfffff8053b6adcbe)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">fbab0e2d-c5b9-4d82-9368-5315bd03ad47</Data>
</EventData>
</Event>

Posted By: Katana1074
Date Posted: 22 Jan 2023 at 4:53am

can you give me the exact make and model of your ram,can you download memtest86 and run on a bootable usb drive and see if it throws any memory errors...

Posted By: EEPS
Date Posted: 22 Jan 2023 at 5:07am

Ram: G.SKILL Trident Z5 Neo F5-6000J3038F16GX2-TZ5N

I checked and it is on the Memory QVL. I did try each stick and I did try memtest86 a while ago but will try again.

Another thing, in linux with C-States enabled it crashes reliable on boot every time. Here is the kernel crash when I just tried:

Jan 21 00:06:37 radagast kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 6
Jan 21 00:06:37 radagast kernel: Modules linked in: video wmi fjes(-) rfkill gpio_amdpt pcc_cpufreq(-) gpio_generic acpi_cpufreq mac_hid drm backlight fuse efi_pstore i2c_core configfs efivarfs ipv6 crc_ccitt autofs4 nvme crc32_pclmul aesni_intel r8169 nvme_core xhci_pci realtek xhci_pci_renesas crypto_simd mdio_devres cryptd t10_pi xhci_hcd ahci crc64_rocksoft libphy crc64 libahci btrfs xor raid6_pq libcrc32c crc32c_intel
Jan 21 00:06:37 radagast kernel: CPU: 6 PID: 1407 Comm: systemd-udevd Tainted: G D 6.2.0-rc4-x86_64 #1
Jan 21 00:06:37 radagast kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 1.11.CB08 01/19/2023
Jan 21 00:06:37 radagast kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x78/0x2d0
Jan 21 00:06:37 radagast kernel: Code: 92 c2 8b 45 00 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 f0 01 00 00 85 c0 74 10 8b 45 00 84 c0 74 09 f3 90 8b 45 00 <84> c0 75 f7 b8 01 00 00 00 66 89 45 00 5b 5d 41 5c 41 5d c3 cc cc
Jan 21 00:06:37 radagast kernel: RSP: 0018:ffffb03082193dc0 EFLAGS: 00000002
Jan 21 00:06:37 radagast kernel: RAX: 0000000000000101 RBX: ffff95527d96218c RCX: 0000000000000004
Jan 21 00:06:37 radagast kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff95527d96218c
Jan 21 00:06:37 radagast kernel: RBP: ffff95527d96218c R08: ffffffffa662b2c0 R09: 0000000000000000
Jan 21 00:06:37 radagast kernel: R10: 0000000000000006 R11: 0000000000000000 R12: ffff95527d96218c
Jan 21 00:06:37 radagast kernel: R13: ffff95527d962128 R14: 0000000000000004 R15: ffff9552115455e0
Jan 21 00:06:37 radagast kernel: FS: 00007f12ce500800(0000) GS:ffff955957780000(0000) knlGS:0000000000000000
Jan 21 00:06:37 radagast kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 00:06:37 radagast kernel: CR2: 0000562a8b43f010 CR3: 00000001106fe000 CR4: 0000000000750ee0
Jan 21 00:06:37 radagast kernel: PKRU: 55555554
Jan 21 00:06:37 radagast kernel: Call Trace:
Jan 21 00:06:37 radagast kernel: <TASK>
Jan 21 00:06:37 radagast kernel: _raw_spin_lock_irq+0x3a/0x50
Jan 21 00:06:37 radagast kernel: pm_runtime_allow+0x20/0x100
Jan 21 00:06:37 radagast kernel: control_store+0x45/0x90
Jan 21 00:06:37 radagast kernel: kernfs_fop_write_iter+0x12f/0x1c0
Jan 21 00:06:37 radagast kernel: vfs_write+0x2c5/0x3d0
Jan 21 00:06:37 radagast kernel: ksys_write+0x63/0xe0
Jan 21 00:06:37 radagast kernel: do_syscall_64+0x3f/0x90
Jan 21 00:06:37 radagast kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jan 21 00:06:37 radagast kernel: RIP: 0033:0x7f12ce0c46a0
Jan 21 00:06:37 radagast kernel: Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb af 66 2e 0f 1f 84 00 00 00 00 00 90 80 3d 41 ff 0d 00 00 74 17 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 48 89
Jan 21 00:06:37 radagast kernel: RSP: 002b:00007ffdcc064998 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jan 21 00:06:37 radagast kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f12ce0c46a0
Jan 21 00:06:37 radagast kernel: RDX: 0000000000000004 RSI: 00007ffdcc064c70 RDI: 0000000000000006
Jan 21 00:06:37 radagast kernel: RBP: 00007ffdcc064c70 R08: 00007f12ce1990c0 R09: 00007ffdcc064a40
Jan 21 00:06:37 radagast kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004
Jan 21 00:06:37 radagast kernel: R13: 0000562a8b517930 R14: 0000000000000004 R15: 00007f12ce198a00
Jan 21 00:06:37 radagast kernel: </TASK>
Jan 21 00:06:37 radagast kernel: watchdog: BUG: soft lockup - CPU#20 stuck for 27s! [modprobe:1384]
Jan 21 00:06:37 radagast kernel: Modules linked in: video wmi fjes(-) rfkill gpio_amdpt pcc_cpufreq(-) gpio_generic acpi_cpufreq mac_hid drm backlight fuse efi_pstore i2c_core configfs efivarfs ipv6 crc_ccitt autofs4 nvme crc32_pclmul aesni_intel r8169 nvme_core xhci_pci realtek xhci_pci_renesas crypto_simd mdio_devres cryptd t10_pi xhci_hcd ahci crc64_rocksoft libphy crc64 libahci btrfs xor raid6_pq libcrc32c crc32c_intel
Jan 21 00:06:37 radagast kernel: CPU: 20 PID: 1384 Comm: modprobe Tainted: G D 6.2.0-rc4-x86_64 #1
Jan 21 00:06:37 radagast kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 1.11.CB08 01/19/2023
Jan 21 00:06:37 radagast kernel: RIP: 0010:smp_call_function_many_cond+0xeb/0x300
Jan 21 00:06:37 radagast kernel: Code: 63 d0 e8 e8 32 3f 00 39 05 32 06 52 01 76 25 48 63 d0 49 8b 36 48 03 34 d5 c0 1a 31 a6 8b 56 08 83 e2 01 74 0a f3 90 8b 4e 08 <83> e1 01 75 f6 83 c0 01 eb c1 48 83 c4 30 5b 5d 41 5c 41 5d 41 5e
Jan 21 00:06:37 radagast kernel: RSP: 0018:ffffb03081f8fb18 EFLAGS: 00000202
Jan 21 00:06:37 radagast kernel: RAX: 0000000000000006 RBX: 0000000000000246 RCX: 0000000000000011
Jan 21 00:06:37 radagast kernel: RDX: 0000000000000001 RSI: ffff9559577b9f20 RDI: ffff9552002586b0
Jan 21 00:06:37 radagast kernel: RBP: 0000000000000000 R08: 0000000000000006 R09: ffff955200258660
Jan 21 00:06:37 radagast kernel: R10: 0000000000000104 R11: 0000000000000000 R12: 0000000000039f20
Jan 21 00:06:37 radagast kernel: R13: 0000000000000001 R14: ffff955957b33340 R15: ffff955957b33340
Jan 21 00:06:37 radagast kernel: FS: 00007f10d8bc8040(0000) GS:ffff955957b00000(0000) knlGS:0000000000000000
Jan 21 00:06:37 radagast kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 00:06:37 radagast kernel: CR2: 00007f12cc9fe000 CR3: 000000017bcae000 CR4: 0000000000750ee0
Jan 21 00:06:37 radagast kernel: PKRU: 55555554
Jan 21 00:06:37 radagast kernel: Call Trace:
Jan 21 00:06:37 radagast kernel: <TASK>
Jan 21 00:06:37 radagast kernel: ? __pfx_do_flush_tlb_all+0x10/0x10
Jan 21 00:06:37 radagast kernel: ? __pfx_do_flush_tlb_all+0x10/0x10
Jan 21 00:06:37 radagast kernel: on_each_cpu_cond_mask+0x40/0x80
Jan 21 00:06:37 radagast kernel: __purge_vmap_area_lazy+0xd8/0x780
Jan 21 00:06:37 radagast kernel: ? __pfx_orc_sort_swap+0x10/0x10
Jan 21 00:06:37 radagast kernel: _vm_unmap_aliases.part.0+0xf4/0x130
Jan 21 00:06:37 radagast kernel: change_page_attr_set_clr+0xb9/0x1b0
Jan 21 00:06:37 radagast kernel: set_memory_ro+0x2a/0x40
Jan 21 00:06:37 radagast kernel: module_enable_ro+0x6b/0x100
Jan 21 00:06:37 radagast kernel: load_module+0x1be9/0x2090
Jan 21 00:06:37 radagast kernel: ? __do_sys_finit_module+0xb4/0x130
Jan 21 00:06:37 radagast kernel: __do_sys_finit_module+0xb4/0x130
Jan 21 00:06:37 radagast kernel: do_syscall_64+0x3f/0x90
Jan 21 00:06:37 radagast kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jan 21 00:06:37 radagast kernel: RIP: 0033:0x7f10d8cc4e99
Jan 21 00:06:37 radagast kernel: Code: 08 44 89 e0 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 57 df 0c 00 f7 d8 64 89 01 48
Jan 21 00:06:37 radagast kernel: RSP: 002b:00007ffcb17fc588 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Jan 21 00:06:37 radagast kernel: RAX: ffffffffffffffda RBX: 000055c0c223c150 RCX: 00007f10d8cc4e99
Jan 21 00:06:37 radagast kernel: RDX: 0000000000000000 RSI: 000055c0c0269500 RDI: 0000000000000001
Jan 21 00:06:37 radagast kernel: RBP: 0000000000040000 R08: 0000000000000000 R09: 000055c0c223ea20
Jan 21 00:06:37 radagast kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 000055c0c0269500
Jan 21 00:06:37 radagast kernel: R13: 0000000000000000 R14: 000055c0c223bf90 R15: 000055c0c223c150
Jan 21 00:06:37 radagast kernel: </TASK>

Posted By: EEPS
Date Posted: 22 Jan 2023 at 9:04am

I tested each ram stick again and they all crash in linux. With only one stick in I booted memtest86 and it passed. It took hours, so I only tested the one stick, but not sure it matters since they all behave the same. I have to conclude it is not a problem with the memory sticks themselves. I went ahead and ordered a 7600X since I could get it tomorrow. Hopefully that will settle once and for all if it is the CPU or MoBo... I will report back tomorrow.

Posted By: Katana1074
Date Posted: 22 Jan 2023 at 5:34pm

EEPS wrote:

I tested each ram stick again and they all crash in linux. With only one stick in I booted memtest86 and it passed. It took hours, so I only tested the one stick, but not sure it matters since they all behave the same. I have to conclude it is not a problem with the memory sticks themselves. I went ahead and ordered a 7600X since I could get it tomorrow. Hopefully that will settle once and for all if it is the CPU or MoBo... I will report back tomorrow.

Well looks like the memory is ok, only other thing i can think of is the cpu mount,i had loads of issues with my ek magnitude waterblock (sporadic reboots),memory speed not setting correctly in bios etc, turned out to be to much downward pressure on the cpu- sorted with a few washers.....

another cpu will rule out a lot of issues...

Posted By: EEPS
Date Posted: 23 Jan 2023 at 12:17am

Got the 7600X this morning, put it in and... It's completely stable. Put all 4 RAM sticks in, running at 6000 MHz, C-States enabled of course and no issues at all in windows or Linux. So I guess I got to RMA the CPU :(

Posted By: Katana1074
Date Posted: 23 Jan 2023 at 3:04am

Hi there

Well least ya know it was the cpu,I`m glad you got it sorted

Rma should be easily done with AMD

Thanks for posting back here and enjoy your stable system :)

Posted By: EEPS
Date Posted: 07 Feb 2023 at 6:58am

Just wanted to update, I got my replacement 7950x today and so far its working great, so seems like that was definitely my problem the whole time!

Posted By: Katana1074
Date Posted: 07 Feb 2023 at 5:27pm

Thanks for posting back....

Enjoy your system.....