Hi Michele,
I have 4 SSDs but I tried disconnecting all the disks, I tried moving them from m.2_1 to m.2_4 slot etc but nothing solved until I reinstalled the old 7950x3d
I tried a different ISO of windows as suggested on Reddit but same problem
Yes using 24h2 but I have older images created with macrium reflect and same problem.
You have already done a lot of testing, I have exhausted my ideas too.
Maybe last thing is switch from AHCI mode to RAID, even though it doesnt make sense if you don't plan to create any array..
Then try to load the raid driver on windows setup. Just out of curiosity.
But 99% will fail, I'm already convinced it's a pcie problem
At this point I think there could be something weird on the pcie lanes of the new cpus
Not sure if hardware or software side (bios/microcode/drivers)
The fact that even on linux you have problems after installing the gpu drivers (gpu is connected to pcie lanes, different from the ones used for storage, but still cpu pcie lanes) is also something that points in the same direction. A coincidence?
Maybe It's just windows that exhibit the problem earlier, in the setup wizard.
What about vsoc? Is 1.3V and below still considered a good one? If I set the memory to 6000mt/s it boots ok but default vsoc is only 1.220V that is pretty low considered the defaults I had with the 7950X3D
Idk how the soc works in the new cpu, but even on 7950x3d 1.3V was already considered pretty high, despite the motherboards pushing very high by default after enabling expo profiles.
6000/6200 typically are ok around 1.2/1.24V with the old cpus, unless you put more stress like using 4 dimms....
You might also want to seek for an updated VBIOS. Most of the problems are on the NV side... Soooo freaking much issues with the 5xxx series I saw only with Fermi....
there are also many problems on 4xxx/3xxx series
mostly caused by recent 572.xx drivers, there's something fishy about nvidia too (and this is also related to pcie, what a coincidence)
For example, lots of people with troubles waking up the monitor from a deep sleep status (monitor sleep, not pc sleep): pc still active and not crashed, but monitor stays black
It also happened to me a couple times: searching in tech forums it's a well know issue of recent drivers, so I disabled monitor sleep in windows and rely on the proximity sensor of my new monitor.... I think it's the best option for me, but not everybody has a proximity sensor available.
Somebody else fixed by forcing the pcie to gen 4 in bios, how curious....
Going back to 566.36 is another way to avoid this weird black screens problem, but I understand maybe it's not a good idea for 5xxx owners. A VBIOS update can mitigate something for sure, but drivers are pretty much broken right now.
Similar black screens events are happening in different situations, on 5xxx series it may happen while gaming too. Very frustrating.
And both in windows and linux environments.
