Long time listener, first time caller looking for help. It's probably going to be a lot to read.. yea, definitely not for the faint of heart 
I believe the issue now is probably MOBO and/or RAM related. My specs are in my signature.
MOBO: MSI X670E Tomahawk - BIOS: E7E12AMS.1G0
CPU: Ryzen 7 9800 X3D
GPU: ASUS TUF 4080 Super
RAM: 32 GB G SKILL F5-6000J3038F16GX2 FX5
PSU: SuperFlower Leadex VII Pro Platinum 850W ATX 3.0
SSD: 2- WD_Black SN850x M.2 2280 PCIe Gen4 NVME, 1TB and 2TB
DISPLAY: Dell P2419H and LG 27GL850-B
(This is basically a timeline of events and a repost of a post I made on the MSI forums.)
- This is a new build that I was using with basically zero issues (other than some Win11 stuff that I'm adapting to) for ~2 months. My RAM and CPU were recognized with no issues; I ran memtest and Prime95 to ensure the RAM and CPU were in order and it's been smooth sailing. I've been playing quite a bit of Path of Exile 2 and Valheim (again) and just fine tuning my fan curves and making sure temps are ok, which they have been. Really no issues until Cyberpunk, MSI Afterburner and updating to the 576.02 NVIDIA drivers.
I installed Afterburner and Rivatuner because I wanted to mess with the GPU fan curve. In hindsight, probably shouldn't have installed Rivatuner as I won't use it and I didn't realize it was going to download DirectX packages; for some reason I feel like that might be cause. Anyway, I only used Afterburner, I set a fan curve and fired up Cyberpunk for the first time and I was running the benchmark over and over with different settings. No issues, everything was fine and system was running great. So I started a new game, got about 10 minutes in and my computer just shut off/restarted.
When I got back into windows, I had no audio. So I restarted and went into the bios (not sure why) just to check everything looked ok, which it did. Got back into Windows and everything was normal, audio was back and nothing in the event viewer other than an unexpected shutdown, of course. So I'm thinking Cyberpunk was pushing my rig too far, even though all the temps looked great. I start up Valheim with Afterburner running and when it gets to the start screen, my cpu crashes and restarts again. This time, audio is fine, but I restart again anyway.
So now I'm thinking its Afterburner causing the issues and I decided to do a system restore back before I installed it, I don't know if that was the best idea, I never use the system restore but its a new OS, fresh install, I figure why not. The restore goes fine but Afterburner is still on my system, maybe I didn't go far back enough, but I'm pretty sure I did. Anyway, I don't have it set as a startup app, so it shouldn't be running in the background unless I start it. So I try Valheim again, this time without Afterburner running and I crash/restart again at the same spot. But this time the restart just hangs at the black screen and I don't get back into Windows, instead I now have the issue where I cannot get into the bios or windows.
- After the above, I was able to get into the bios (I was just not hitting the F1 key soon enough duh), but W11 would just go to black screen, so I decided to reinstall Windows (I used the same USB I made with Rufus on my first install). During install, everything seems to go ok, until the installation completes and the log in screen is supposed to pop up. At this point, the system crashes/restarts. So it's basically the same as before I reinstalled. I can get into my bios, but I crash at the log in screen. That is, until I swapped monitors to a 24" Dell 1080p. Previously I was using my 27" LG 1440p monitor solely when reinstalling (I use both when I'm not having mysterious issues). When I installed Win11 the first time 2months ago, I was using a 24" monitor then too, no clue if that helped but I found a reddit post that suggested to use a different monitor.
- So now I'm at the point where I have a new W11 install and when W11 update runs, I crash again when it tries to install a 24H2 update. Every single time at about 23%. I had to find the temp download folder for the Windows update and delete that to stop it from installing and crashing.
- Next step, I take out 1 RAM stick so I've just got 1x16GB in there and make a new W11 USB using the Media Creation Tool and the ISO from Microsoft. I go thru the install process with 1 crash, but it seems to work ok. I download the latest AMD chipset drivers (previously I was using the drivers from MSI) and tried to install them. I now crash every time when I try to install the chipset drivers. It unpacks the package, writes all or most of the files to the SSD, then crashes. I also turned off Automatic Restarts in Advanced System Settings to see if I would get BSOD message, but it's the same thing, just a complete shutdown/loss of power with Event ID 41 in event viewer.
So after all this I noticed my RAM is technically not on the MSI RAM compatibility list, but the more I read on that, and posts I see of other people using the same RAM with the board, I don't know.. Also want to add the CPU Soc Voltage in bios is set to 1.2v; I've read that if it's too high it can cause issues.
If you read all this, you're a saint. Any suggestions or advice is appreciated.
I believe the issue now is probably MOBO and/or RAM related. My specs are in my signature.
MOBO: MSI X670E Tomahawk - BIOS: E7E12AMS.1G0
CPU: Ryzen 7 9800 X3D
GPU: ASUS TUF 4080 Super
RAM: 32 GB G SKILL F5-6000J3038F16GX2 FX5
PSU: SuperFlower Leadex VII Pro Platinum 850W ATX 3.0
SSD: 2- WD_Black SN850x M.2 2280 PCIe Gen4 NVME, 1TB and 2TB
DISPLAY: Dell P2419H and LG 27GL850-B
(This is basically a timeline of events and a repost of a post I made on the MSI forums.)
- This is a new build that I was using with basically zero issues (other than some Win11 stuff that I'm adapting to) for ~2 months. My RAM and CPU were recognized with no issues; I ran memtest and Prime95 to ensure the RAM and CPU were in order and it's been smooth sailing. I've been playing quite a bit of Path of Exile 2 and Valheim (again) and just fine tuning my fan curves and making sure temps are ok, which they have been. Really no issues until Cyberpunk, MSI Afterburner and updating to the 576.02 NVIDIA drivers.
I installed Afterburner and Rivatuner because I wanted to mess with the GPU fan curve. In hindsight, probably shouldn't have installed Rivatuner as I won't use it and I didn't realize it was going to download DirectX packages; for some reason I feel like that might be cause. Anyway, I only used Afterburner, I set a fan curve and fired up Cyberpunk for the first time and I was running the benchmark over and over with different settings. No issues, everything was fine and system was running great. So I started a new game, got about 10 minutes in and my computer just shut off/restarted.
When I got back into windows, I had no audio. So I restarted and went into the bios (not sure why) just to check everything looked ok, which it did. Got back into Windows and everything was normal, audio was back and nothing in the event viewer other than an unexpected shutdown, of course. So I'm thinking Cyberpunk was pushing my rig too far, even though all the temps looked great. I start up Valheim with Afterburner running and when it gets to the start screen, my cpu crashes and restarts again. This time, audio is fine, but I restart again anyway.
So now I'm thinking its Afterburner causing the issues and I decided to do a system restore back before I installed it, I don't know if that was the best idea, I never use the system restore but its a new OS, fresh install, I figure why not. The restore goes fine but Afterburner is still on my system, maybe I didn't go far back enough, but I'm pretty sure I did. Anyway, I don't have it set as a startup app, so it shouldn't be running in the background unless I start it. So I try Valheim again, this time without Afterburner running and I crash/restart again at the same spot. But this time the restart just hangs at the black screen and I don't get back into Windows, instead I now have the issue where I cannot get into the bios or windows.
- After the above, I was able to get into the bios (I was just not hitting the F1 key soon enough duh), but W11 would just go to black screen, so I decided to reinstall Windows (I used the same USB I made with Rufus on my first install). During install, everything seems to go ok, until the installation completes and the log in screen is supposed to pop up. At this point, the system crashes/restarts. So it's basically the same as before I reinstalled. I can get into my bios, but I crash at the log in screen. That is, until I swapped monitors to a 24" Dell 1080p. Previously I was using my 27" LG 1440p monitor solely when reinstalling (I use both when I'm not having mysterious issues). When I installed Win11 the first time 2months ago, I was using a 24" monitor then too, no clue if that helped but I found a reddit post that suggested to use a different monitor.
- So now I'm at the point where I have a new W11 install and when W11 update runs, I crash again when it tries to install a 24H2 update. Every single time at about 23%. I had to find the temp download folder for the Windows update and delete that to stop it from installing and crashing.
- Next step, I take out 1 RAM stick so I've just got 1x16GB in there and make a new W11 USB using the Media Creation Tool and the ISO from Microsoft. I go thru the install process with 1 crash, but it seems to work ok. I download the latest AMD chipset drivers (previously I was using the drivers from MSI) and tried to install them. I now crash every time when I try to install the chipset drivers. It unpacks the package, writes all or most of the files to the SSD, then crashes. I also turned off Automatic Restarts in Advanced System Settings to see if I would get BSOD message, but it's the same thing, just a complete shutdown/loss of power with Event ID 41 in event viewer.
So after all this I noticed my RAM is technically not on the MSI RAM compatibility list, but the more I read on that, and posts I see of other people using the same RAM with the board, I don't know.. Also want to add the CPU Soc Voltage in bios is set to 1.2v; I've read that if it's too high it can cause issues.
If you read all this, you're a saint. Any suggestions or advice is appreciated.
Last edited by a moderator:
Facebook
Twitter
Instagram