Question Please Help: New build, frequent and various BSODs

[JameyF]

Hello folks,

I've recently built a new gaming rig as follows:

MSI mag b650m mortar wifi
Ryzen 5 7600x
Rtx 2060 (bought this a year ago and was using in my old system)
Corsair vengeance ddr5-5200 16g x2 CMK32GX5M2B5200C40 *MSI webpage says CMK32GX5M2B5200C38 is compatible, but not ...40. 8( is this my issue?
Samsung 980 pro 1tb m.2
SilverStone 750W PSU SST-ET750-HG V1.2
Corsair h100i RGB elite

Before installing windows, I updated my BIOS to the latest.

Immediately after installing Windows 11, I began getting BSODs at random intervals and with a wide variety of error codes including, but not limited to:

System service exception : win32kbase.sys
Page fault in non paged area : win32kfull.sys
pfn list corrupt
irql not less or equal : ntoskrnl.exe
unexpected kernal mode trap

I did a clean windows install and have managed to update all the drivers on the Device Manager list that had alerts.

I was worried about the news that the recent Win11 update was causing BSODs but the initial crashes were happening before that update had been applied to my PC. For what it's worth, I have since applied all windows updates, including that one.

As far as diagnostics, so far I have managed to run the windows Memory Diagnostic which, from the start, displayed a message about detecting hardware problems. The results in the event viewer showed two errors. The details are quite lengthy so I'll copy paste them at the end of this.

sfc scannow said that it found problems but could not fix them all
dsim, if i recall, found errors and fixed them? But I'll have to rerun that as I am unsure.
chkdsk, also IIRC, found no problems. chkdsk /f repaired the disk though.

I booted in safe mode and though there were no BSODs, programs would close suddenly, namely chrome, as I was searching for driver updates.
I tried running SFC Scannow again in safe mode with command prompt and got a BSOD though I did not note which of the many error codes that particular instance was. In retrospect, that seems prudent so I reran it just now.
No BSOD on this attempt. But there are still unfixed errors.

On a final note, just now as I was looking for this so called Blue Screen Troubleshooting option a box popped up saying "your computer has a memory problem".

Memory Diagnostic Results:
- System

- Provider

[ Name] Microsoft-Windows-MemoryDiagnostics-Results
[ Guid] {5f92bc59-248f-4111-86a9-e393e12c6139}

EventID 1202

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2023-09-22T00:20:16.0372963Z

EventRecordID 3749

Correlation

- Execution

[ ProcessID] 5704
[ ThreadID] 5764

Channel System

Computer HAL2023

- Security

[ UserID] S-1-5-18


- UserData

- Results

CompletionType Fail

And,

- System

- Provider

[ Name] Microsoft-Windows-MemoryDiagnostics-Results
[ Guid] {5f92bc59-248f-4111-86a9-e393e12c6139}

EventID 1102

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2023-09-22T00:20:16.0372953Z

EventRecordID 3748

Correlation

- Execution

[ ProcessID] 5704
[ ThreadID] 5764

Channel System

Computer HAL2023

- Security

[ UserID] S-1-5-18


- UserData

- Results

LaunchType Manual

CompletionType Fail

MemorySize 31904

TestType 10

TestDuration 1578

TestCount 12

NumPagesTested 8131714

NumPagesUnTested 2323

NumBadPages 77

T1NumBadPages 11

T2NumBadPages 1

T3NumBadPages 5

T4NumBadPages 1

T5NumBadPages 21

T6NumBadPages 0

T7NumBadPages 11

T8NumBadPages 0

T9NumBadPages 0

T10NumBadPages 0

T11NumBadPages 29

T12NumBadPages 1

T13NumBadPages 0

T14NumBadPages 0

T15NumBadPages 0

T16NumBadPages 0

I fear the answer will be "buy new memory that is on MSI's list"...

Thanks for your time.
Cheers,
Jamey

 

[JameyF]

Here's a link to all of the minidump files as well.
Cheers,

HAL Minidumps – Google Drive

drive.google.com

 

[pete_101]

Corsair vengeance ddr5-5200 16g x2 CMK32GX5M2B5200C40 *MSI webpage says CMK32GX5M2B5200C38 is compatible, but not ...40. 8( is this my issue?

Could be, but can't say for certain. What I can tell you is your RAM is Intel XMP 3, so optimized for Intel systems. You have AMD, so you should've looked at EXPO instead...but you probably weren't to know, and I made the same mistake myself.

All I can tell you is my experience with XMP on a 7600X wasn't good, and I ended up selling it after trying EXPO. I had boot issues and unexpected shutdowns, and it all came back to the RAM.

 

[JameyF]

Update:
I've tried, as per some other threads, testing the memory one stick at a time in each slot.
Stick one, resulted in BSOD in either slot, on boot up.
Stick 2 is currently operating for about 10 minutes now. About to run mem diagnostic...

Well, still no BSOD but Memory Diagnostic still says there's a hardware problem and the event viewer still gives me memory errors.

 

[JameyF]

Could be, but can't say for certain. What I can tell you is your RAM is Intel XMP 3, so optimized for Intel systems. You have AMD, so you should've looked at EXPO instead...but you probably weren't to know, and I made the same mistake myself.

All I can tell you is my experience with XMP on a 7600X wasn't good, and I ended up selling it after trying EXPO. I had boot issues and unexpected shutdowns, and it all came back to the RAM.

Well damn. Looks like I failed in my research there. Guess I'll just shelve this rig until I can get some new memory and make sure I get the expo one. Now that I know about it, I see it everywhere...
Fortunately, my old rig works just fine if I pop the old 2060 back in there.
Thanks for the insight.
Cheers,

 

[pete_101]

Well damn. Looks like I failed in my research there. Guess I'll just shelve this rig until I can get some new memory and make sure I get the expo one. Now that I know about it, I see it everywhere...
Fortunately, my old rig works just fine if I pop the old 2060 back in there.
Thanks for the insight.
Cheers,

Make sure you clear the CMOS when you change the memory, otherwise the issues could be carried over....and don't be worried if it takes a minute to post the 1st time, that's just it testing the new timings.

 

[JameyF]

Make sure you clear the CMOS when you change the memory, otherwise the issues could be carried over....and don't be worried if it takes a minute to post the 1st time, that's just it testing the new timings.

Hmm... Should I have cleared the CMOS before testing the individual sticks as well?

 

[pete_101]

Hmm... Should I have cleared the CMOS before testing the individual sticks as well?

Probably. Did you test with XMP enabled, or with it turned off?

 

[kurdtnz]

Ive not long built a 7000 series PC myself and have noticed they are really finicky with RAM. The RAM I bought was on the QVL but I was having issues with the EXPO profiles, it's taken me having to instal the latest BIOS and the 3rd released EXPO profile (EXPO tweaked,) to get my system running as it should.

 

[JameyF]

Probably. Did you test with XMP enabled, or with it turned off?

I believe it was turned off. I left the BIOS setting as it was from first boot and think it was disabled by default. But I'll have another look and then do another round of testing.

 

[JameyF]

Ive not long built a 7000 series PC myself and have noticed they are really finicky with RAM. The RAM I bought was on the QVL but I was having issues with the EXPO profiles, it's taken me having to instal the latest BIOS and the 3rd released EXPO profile (EXPO tweaked,) to get my system running as it should.

Are the expo profiles just for overclocking? You can keep it disabled in BIOS, right?

 

[kurdtnz]

Are the expo profiles just for overclocking? You can keep it disabled in BIOS, right?

Yes, they run at default 4800Hz but with EXPO at 6000Hz, (which AMD said was the 7000 series sweet spot.)

 

[JameyF]

Thanks for all your replies. Sorry for the delay in getting back to you. I was planning to try replacing the memory when I can afford to, which would likely be a couple weeks from now.
However... I was reading up a bit more on the xmp/expo issues and had another question.

I don't see any lists of Ryzen 5 7600x compatible memory, just that it's compatible with ddr5 up to 5200mhz. Higher speeds only being possible if one enables overclocking in the bios.

I know my memory is xmp optimized, but it seems most of the memory on my MSI motherboard's compatibility list is as well. Of course the motherboard is the motherboard and the cpu is the cpu so I guess MSI's list doesn't matter so much if it's an issue of Ryzen not playing well with xmp...

Have I missed something? Is there a list of specifically compatible memory for Ryzen 5 7600x?

Cheers,

 

[JameyF]

Probably. Did you test with XMP enabled, or with it turned off?

Sorry for the lateness of this reply. I was planning to try replacing the memory when I could afford to buy it, w2hich would be a couple weeks from now. However, after reading a bit about xmp/expo and compatible memory, I had some ideas to try out.
I just put the memory in question back in, cleared cmos, then enable the xmp in bios. The speed was then reflected correctly on the bios view (previously it was showing 4800 rather than 5200).
I'm about 25% through a memory diagnostic and one good sign is that the status still says no problems. Previously it said there was a hardware issue from the get go.
Could this one simple setting have been the source of my trouble?

To be fair, I'm also running without my gpu at the moment so assuming the mem tests are successful I reckon that's the next thing to test. Although, the gpu is back in my old rig and working fine there...

Update: Mem Diag came back all clear. PC has been running (without gpu) for a couple hours without BSODs. Out of time today but day after tomorrow I'll pop the gpu back in and see what happens.

There were a few errors in the event viewer about Corsair, svchost, explorer, aggregatorhost, and perfdiag logger... I'll do a bit of googling after dinner ;-)

 

[JameyF]

Though I am still nervous every time I boot up or do anything, it's running fairly smoothly at the moment with the original memory, bios xmp enabled and my old gtx 1660 gpu.
Next step, save up for a new gpu and hope for the best!
Thanks y'all.