Question Changing Hardware causes crash

[krisztiantobias]

Hello guys! I upgraded my pc partially

Same:
GIGABYTE GeForce RTX 2070 WINDFORCE 2X 8G
Corsair VS 650W

Old:	New:
MSI Z97-G43	MSI MAG B650 TOMAHAWK WIFI
INTEL I7 4790K	AMD Ryzen 5 7600X
Kingston DDR3 2400 16GB HyperX Savage CL11 KIT (2x8GB)	G.SKILL 32GB KIT DDR5 6000MHz CL36 Trident Z5 NEO RGB AMD EXPO
Win10: Samsung 2.5 870 EVO 500GB SATA3	Win11: ADATA XPG GAMMIX S70 Blade 1TB M.2

If I make any HW changes, the PC crashes even in the bios settings.
For example: The PC worked fine -> STOP -> I connected two ARCTIC P12 to the motherboard, and the next startup crashed on Windows login screen: IRQL_NOT_LESS_OR_EQUAL. I also got MEMORY_MANAGEMENT crash before as well but it's crashing in the bios setup as well. After that, restarting doesn't help either.

I have a 100% working workaround:
If I take out one of the rams it will force the machine to go to bios with f1. After that, the PC works again and I can put in the second ram without any problem.

If the hardware is not changed, then everything is perfect and the stress tests do not yield anything (memtest86 8pass, combustor half an hour, aida64 full 1 hour). Temps are also correct. I'm new to AM5. Is this normal or could be one of the components faulty?

 

[DaleH]

Hello guys! I upgraded my pc partially with MSI MAG B650 TOMAHAWK + 7600X + G.SKILL 32GB 6000MHz CL36 (with my old RTX2070, Corsair VS 650W) and I have a weird problem:

If I make any HW changes, the PC crashes even in the bios settings.
For example: The PC worked fine -> STOP -> I connected two ARCTIC P12 to the motherboard, and the next startup crashed on Windows login screen: IRQL_NOT_LESS_OR_EQUAL. I also got MEMORY_MANAGEMENT crash before as well but it's crashing in the bios setup as well. After that, restarting doesn't help either.

I have a 100% working workaround:
If I take out one of the rams it will force the machine to go to bios with f1. After that, the PC works again and I can put in the second ram without any problem.

If the hardware is not changed, then everything is perfect and the stress tests do not yield anything (memtest86 8pass, combustor half an hour, aida64 full 1 hour). Temps are also correct. I'm new to AM5. Is this normal or could be one of the components faulty?

Seems to me if you replaced the hardware, you need to reinstall Windows.

 

[krisztiantobias]

It happened, I also moved to win11. Based on the MSI forum it could be my PSU or Disable Memory Context Restore in bios, instead of AUTO. I tried the second one and no crash since then, but it was like 10 restarts and HW modifications so not currently it's not 100%

 

[USAFRet]

What specific hardware did you change?

Old:
Full list

New:
Full list



DEtails, please.

 

[krisztiantobias]

Same:
GIGABYTE GeForce RTX 2070 WINDFORCE 2X 8G
Corsair VS 650W

Old:	New:
MSI Z97-G43	MSI MAG B650 TOMAHAWK WIFI
INTEL I7 4790K	AMD Ryzen 5 7600X
Kingston DDR3 2400 16GB HyperX Savage CL11 KIT (2x8GB)	G.SKILL 32GB KIT DDR5 6000MHz CL36 Trident Z5 NEO RGB AMD EXPO
Win10: Samsung 2.5 870 EVO 500GB SATA3	Win11: ADATA XPG GAMMIX S70 Blade 1TB M.2

 

[USAFRet]

Same:
GIGABYTE GeForce RTX 2070 WINDFORCE 2X 8G
Corsair VS 650W

Old:	New:
MSI Z97-G43	MSI MAG B650 TOMAHAWK WIFI
INTEL I7 4790K	AMD Ryzen 5 7600X
Kingston DDR3 2400 16GB HyperX Savage CL11 KIT (2x8GB)	G.SKILL 32GB KIT DDR5 6000MHz CL36 Trident Z5 NEO RGB AMD EXPO
Win10: Samsung 2.5 870 EVO 500GB SATA3	Win11: ADATA XPG GAMMIX S70 Blade 1TB M.2

Option 1 - Full OS wipe and reinstall.
There is no Option 2.

 

[krisztiantobias]

Option 1 - Full OS wipe and reinstall.
There is no Option 2.

I mentioned in the original post that it can crash in the BIOS as well, so before Windows. OS wipe would not really help I guess. Looks like this Memory Context Restore is buggy

 

[USAFRet]

I mentioned in the original post that it can crash in the BIOS as well, so before Windows. OS wipe would not really help I guess. Looks like this Memory Context Restore is buggy

Well, once you get past the BIOS thing, you STILL need to do a full OS install.

 

[krisztiantobias]

The "because" part was left out, i.e. the justification of your advice. If I changed something Hardware related, at the next startup it crashed within 2 minutes. If I was in bios then there, not Windows related. If I fix this issue (and I think fixed it) why would I have to reinstall the system, which is not corrupted and works just fine?

 

[USAFRet]

The "because" part was left out, i.e. the justification of your advice. If I changed something Hardware related, at the next startup it crashed within 2 minutes. If I was in bios then there, not Windows related. If I fix this issue (and I think fixed it) why would I have to reinstall the system, which is not corrupted and works just fine?

The justification is because Windows is NOT as modular as we'd all like.

Changing from old Intel to new Ryzen often/usually fails.


Changing hardware like this has 3 possible outcomes:
1. It works just fine
2. It fails completely.
3. It "works", but you're chasing issues for weeks/months.

I've personally seen all 3.

#3 is the most common.
But, you might luck out and be in the tiny percentage of #1. Maybe.

 

[krisztiantobias]

The justification is because Windows is NOT as modular as we'd all like.

Yeah, I think you missed this:

Win10: Samsung 2.5 870 EVO 500GB SATA3

Win11: ADATA XPG GAMMIX S70 Blade 1TB M.2

So I'm using a fresh win11 on a fresh m.2 SSD, and not the old sata3 with win10.

 

[USAFRet]

Yeah, I think you missed this:

Win10: Samsung 2.5 870 EVO 500GB SATA3

Win11: ADATA XPG GAMMIX S70 Blade 1TB M.2

So I'm using a fresh win11 on a fresh m.2 SSD, and not the old sata3 with win10.

From your previous comments, that was not entirely clear.

 

[krisztiantobias]

From MSI forum:

2 Disable Memory Context Restore in bios, instead of AUTO.

It looks like this one solved the issue, I could not reproduce it anymore.

Maybe this one also fixes the issue, but I did not try it:
"If you enable MemoryContextRestore, you need to enable PowerDownEnable too to prevent BSOD."