F5F Stay Refreshed Hardware Desktop Extreme BSOD issues affecting a modern high-performance computer.

Extreme BSOD issues affecting a modern high-performance computer.

Extreme BSOD issues affecting a modern high-performance computer.

Pages (3): 1 2 3 Next
R
RulwenJr
Posting Freak
786
06-11-2022, 08:23 AM
#1
Hey there, this is my debut here, so please be gentle if I’m off track! Last year I made a small investment to upgrade my old setup. I went for a premium gaming PC to replace my worn-out 9900k/RTX2080 rig. My choices were: a 9800x3D Gigabyte X870 Wi-Fi 6, Noctua NHD15 Gen2 64GB (two 32GB), Corsair DDR5-6000 DIMM CL 38-44-44-96 Dual Kit, Lexar 2TB PCIe Gen4 SSD, PNY RTX 4090, Verto 2x1TB Crucial SATA SSD (from my previous build), and a 12TB Seagate Ironwolf HDD. I also used a Corsair RM1000e PSU and an Fractal POP Silent XL case.

The graphics card came later, since I originally wanted a GTX 5090 but couldn’t find one initially. Once I got the 4090, it cost about €1,800 and still has its full warranty.

The main issue started right away: BSODs popped up immediately after startup. They were linked to the amdi2c.sys driver and the error code “ATTEMPTED_WRITE_TO_READONLY_MEMORY.” The machine wouldn’t power off by itself and needed a hard reset. I’ll share some screenshots of the BSOD logs on my Google Drive. Other BSODs were less frequent, appearing after about half an hour or so and showing “DRIVER_POWER_STATE_FAILURE.”

The third problem was that Windows would block login after entering the PIN. I’ve recorded these moments—will link to the dumps. Once the system boots, crashes are rare, but problems mostly happen at startup. The easiest way to trigger the error is by shutting down and restarting multiple times.

So far I’ve done: updated BIOS, ran CPU and GPU temperatures for hours (no crash), reset BIOS to defaults, swapped RAM (started with G.Skill, then Corsair QVL certified), replaced CPU with a friend’s unit for a week, re-seated all parts, reinstalled Windows several times, got drivers from the maker, unplugged USB except mouse/keyboard, removed SATA drives, tried different NVMe SSDs, swapped GPU, put it in an RMA, and used a thermal AM5 contact frame. I’m pretty sure I’ve tried many things but still stuck.

I might need to replace the mainboard now. Any suggestions? Thanks for your help!

Best,
Edited May 2, 2025 – Ed
R
RulwenJr
06-11-2022, 08:23 AM #1

Hey there, this is my debut here, so please be gentle if I’m off track! Last year I made a small investment to upgrade my old setup. I went for a premium gaming PC to replace my worn-out 9900k/RTX2080 rig. My choices were: a 9800x3D Gigabyte X870 Wi-Fi 6, Noctua NHD15 Gen2 64GB (two 32GB), Corsair DDR5-6000 DIMM CL 38-44-44-96 Dual Kit, Lexar 2TB PCIe Gen4 SSD, PNY RTX 4090, Verto 2x1TB Crucial SATA SSD (from my previous build), and a 12TB Seagate Ironwolf HDD. I also used a Corsair RM1000e PSU and an Fractal POP Silent XL case.

The graphics card came later, since I originally wanted a GTX 5090 but couldn’t find one initially. Once I got the 4090, it cost about €1,800 and still has its full warranty.

The main issue started right away: BSODs popped up immediately after startup. They were linked to the amdi2c.sys driver and the error code “ATTEMPTED_WRITE_TO_READONLY_MEMORY.” The machine wouldn’t power off by itself and needed a hard reset. I’ll share some screenshots of the BSOD logs on my Google Drive. Other BSODs were less frequent, appearing after about half an hour or so and showing “DRIVER_POWER_STATE_FAILURE.”

The third problem was that Windows would block login after entering the PIN. I’ve recorded these moments—will link to the dumps. Once the system boots, crashes are rare, but problems mostly happen at startup. The easiest way to trigger the error is by shutting down and restarting multiple times.

So far I’ve done: updated BIOS, ran CPU and GPU temperatures for hours (no crash), reset BIOS to defaults, swapped RAM (started with G.Skill, then Corsair QVL certified), replaced CPU with a friend’s unit for a week, re-seated all parts, reinstalled Windows several times, got drivers from the maker, unplugged USB except mouse/keyboard, removed SATA drives, tried different NVMe SSDs, swapped GPU, put it in an RMA, and used a thermal AM5 contact frame. I’m pretty sure I’ve tried many things but still stuck.

I might need to replace the mainboard now. Any suggestions? Thanks for your help!

Best,
Edited May 2, 2025 – Ed

S
smider3
Member
107
06-12-2022, 10:05 AM
#2
Attempted disabling docp as well. Check gigabyte’s advice: install memory modules in slots DDR5_A2 and DDR5_B2 for optimal compatibility and speed. Experienced issues when modules were placed in A1 and B1, so switching to A2 and B2 resolved the problem at 4600 MHz on DDR4. You might also review the crash log to identify the issue.
S
smider3
06-12-2022, 10:05 AM #2

Attempted disabling docp as well. Check gigabyte’s advice: install memory modules in slots DDR5_A2 and DDR5_B2 for optimal compatibility and speed. Experienced issues when modules were placed in A1 and B1, so switching to A2 and B2 resolved the problem at 4600 MHz on DDR4. You might also review the crash log to identify the issue.

K
Killa_Dx
Senior Member
645
06-12-2022, 11:53 AM
#3
The bios has been fully reinitialized (no docp or xmp files) and the RAM modules are set to A2 and B2.
K
Killa_Dx
06-12-2022, 11:53 AM #3

The bios has been fully reinitialized (no docp or xmp files) and the RAM modules are set to A2 and B2.

A
aikorner
Junior Member
43
06-18-2022, 06:54 PM
#4
Open the device manager and turn off the iGPU for your 9800X3D. Run your usual tests that trigger the BSOD and check if the problem persists. There’s been a long-standing issue where Nvidia GPUs paired with 7000 series or newer AMD X3D CPUs with built-in graphics can cause driver BSODs. If the problem remains, I’d like more details but I’ve encountered this before and it’s resolved on the systems I’ve seen. If disabling the iGPU in the BIOS helps, you’re good to go. Since you already use a dGPU, it’s not needed.
A
aikorner
06-18-2022, 06:54 PM #4

Open the device manager and turn off the iGPU for your 9800X3D. Run your usual tests that trigger the BSOD and check if the problem persists. There’s been a long-standing issue where Nvidia GPUs paired with 7000 series or newer AMD X3D CPUs with built-in graphics can cause driver BSODs. If the problem remains, I’d like more details but I’ve encountered this before and it’s resolved on the systems I’ve seen. If disabling the iGPU in the BIOS helps, you’re good to go. Since you already use a dGPU, it’s not needed.

A
Avatar__Kyoshi
Junior Member
47
06-18-2022, 07:23 PM
#5
I realized I missed something in my post, so I tried anyway. Unfortunately, it didn’t work. I recall reinstalling Windows, leaving out the AMD GPU drivers, and then turning off the GPU in the BIOS.
A
Avatar__Kyoshi
06-18-2022, 07:23 PM #5

I realized I missed something in my post, so I tried anyway. Unfortunately, it didn’t work. I recall reinstalling Windows, leaving out the AMD GPU drivers, and then turning off the GPU in the BIOS.

B
byGifti
Junior Member
13
06-27-2022, 07:55 PM
#6
I’d start by using tools like WinDbg or BlueScreenView to get a clearer look at the bluescreen issues. Usually they help identify the specific driver or hardware causing the problem. After pinpointing it, we can explore better solutions together.
B
byGifti
06-27-2022, 07:55 PM #6

I’d start by using tools like WinDbg or BlueScreenView to get a clearer look at the bluescreen issues. Usually they help identify the specific driver or hardware causing the problem. After pinpointing it, we can explore better solutions together.

S
SkyMaster280
Member
214
07-04-2022, 06:43 PM
#7
i'll take a look in bluescreenview, here is also a LINK to a microsoft forum post i made a few months ago. i think the support technician took a look at the logs aswell but couldnt find any clear indicators. where in the bluescreenview can you see what causes the crash?
S
SkyMaster280
07-04-2022, 06:43 PM #7

i'll take a look in bluescreenview, here is also a LINK to a microsoft forum post i made a few months ago. i think the support technician took a look at the logs aswell but couldnt find any clear indicators. where in the bluescreenview can you see what causes the crash?

L
LunaDoll
Member
193
07-08-2022, 12:21 PM
#8
Execute the program and it will display a list of all detected BSOD crashes, ordered by date. Clicking on any entry reveals a section to scroll through, helping you identify the driver or process responsible. Highlighted items in red indicate consistency across crashes, signaling areas for further investigation.
L
LunaDoll
07-08-2022, 12:21 PM #8

Execute the program and it will display a list of all detected BSOD crashes, ordered by date. Clicking on any entry reveals a section to scroll through, helping you identify the driver or process responsible. Highlighted items in red indicate consistency across crashes, signaling areas for further investigation.

C
Chester007
Senior Member
528
07-13-2022, 10:54 AM
#9
here are some of the newer files if you're interested in checking them out. i searched and came across a reddit thread. though it didn't seem very useful at first, i thought it might help. the links i found were: 042125-24218-01.dmp, 042825-22109-01.dmp, 042925-17625-01.dmp, and 043025-21828-01.dmp.
C
Chester007
07-13-2022, 10:54 AM #9

here are some of the newer files if you're interested in checking them out. i searched and came across a reddit thread. though it didn't seem very useful at first, i thought it might help. the links i found were: 042125-24218-01.dmp, 042825-22109-01.dmp, 042925-17625-01.dmp, and 043025-21828-01.dmp.

E
elliottrg
Member
70
07-13-2022, 05:27 PM
#10
ntoskrnl.exe was mentioned by the Microsoft technician as not very useful, and I think it’s more likely a general type error. Edit: This suggests there might be an unusual hardware problem that occasionally happens.
E
elliottrg
07-13-2022, 05:27 PM #10

ntoskrnl.exe was mentioned by the Microsoft technician as not very useful, and I think it’s more likely a general type error. Edit: This suggests there might be an unusual hardware problem that occasionally happens.

Pages (3): 1 2 3 Next