[SOLVED] Frequent BSODs on New PC Build - Need Help Diagnosing

K

Knufle

Member
Joined
Jun 30, 2024
Posts
7
Hi everyone,

I'm Knufle, and I'm really in need of some help with my new PC build. Since February, I've been experiencing around 2 BSODs per day. My previous 2014 Intel PC never had this issue, so I'm feeling quite frustrated.

PC Configuration

Problem Description:

  • Frequency: 2 BSODs per day
  • Typical Usage: Gaming and watching YouTube
  • Error Messages (one of them): "CRITICAL_STRUCTURE_CORRUPTION tcpip.sys"
Steps Taken:

  1. Formatted PC - problem persisted.
  2. Ran network reset scripts:
    • netsh winsock reset
    • netsh int ip reset These resolved the issue for about 2 weeks.
  3. Ran MemTest - no issues found (at least I think so, please see Logs and Dumps).
  4. Followed instructions from this post: Bleeping Computer BSOD Instructions
Logs and Dumps:

I’m feeling quite lost and would greatly appreciate any insights or advice on what might be causing these issues. These BSODs are driving me crazy, and I don’t know what else to try.

Thank you in advance for your help!
 
Hi,
Your processor only support memory at 5200 GHz, but your ram is at 6000 GHz
Regardless, what your motherboard supports, anything above 5200 GHz will cause
problems on your computer like crashes/bsods.
 
ET_Explorer said:
Hi,
Your processor only support memory at 5200 GHz, but your ram is at 6000 GHz
Regardless, what your motherboard supports, anything above 5200 GHz will cause
problems on your computer like crashes/bsods.
Click to expand...
Hmm, I can definitely try setting it to 5200Mhz or something like that, but I have tried it in the past and the BSODs didn't stop, so I really don't think that's what's causing it...
 
You might not think that running RAM at 6000MT/s is a problem, but AMD didn't spec 5200MT/s as the max for 2x1R DDR5 for the fun of it. You MUST reduce the RAM speed to no more than 5200MT/s. Personally, as a test, I would remove all RAM overclocks and run that RAM at whatever the stock frequency is. RAM is a major cause of BSODs and when you come across something as obvious as excessive overclocking that's clearly the first thing to look at.

In addition, and in support of bad RAM being the most likely cause here, the two dumps are both very similar. Both fail with a 0xC0000096 exception code, that's an attempt to execute a privileged instruction. The stack trace in both dumps looks very much as though garbage addresses are occurring - typical where bad RAM is concerned. In addition, both dumps show an image checksum mismatch error, but for different modules, that too is a big clue that bad RAM is the most likely cause.

As mentioned, I recommend removing all RAM overclocks, and any other hardware overclocks (or undervolts). Everything should be running at stock voltages and frequencies. I would also suggest using OCCT to test the stability of various aspects of your build whilst under stress. I use OCCT to stability test any new build.
 
Hi, thanks for all the help and suggestions, as you might have seen here I have followed your instructions and did two things:
  1. Updated my BIOS to F30 which also reset it.
  2. Disabled Fast Boot and RAM overclock entirely.
For the last 9 days, I had no bsods whatsoever, everything was working flawlessly, I even thought they stopped completely, but I was waiting for a little bit more time before coming back here and giving an update.

Today however, I had a bsod once again, I even managed to be using the PC while it happened, I mentioned "Stop code: SYSTEM_SERVICE_EXCEPTION" and "What failed: Cl.dll" which is different from any bsod I had before, my PC was not under stress at the moment of bsod, I was gonna watch a youtube video and that was it.

I should mention a couple of things, yesterday the power went out in my house for a split second, which did turn my PC off and on again abruptly, I don't know if this might have anything to do with the bsod, and also, it was yesterday, not today.

When I was formatting my PC the last time, I preloaded a network driver that I downloaded from here, more precisely this one (first instance in the list, not the second instance):
Intel - Net - 1.1.4.42Windows 10, version 1809 and later, Servicing Drivers, Windows 10, version 1809 and later, Upgrade & Servicing Drivers

The reason why I didn't use the network driver from the MOBO's website, is because I just wasn't able to preload those during the Windows installation, maybe because of their file type or something. It was the first time I did that while formatting my PC, in previous times I had to mess around to force Windows to let me set up the PC without a network connection.

I will be reinstalling the LAN driver using GIGABYTE's link, should I do something else to clean the old driver I've been using though? Not sure.

Also here are the updated minidumps and MEMORY.DMP, I think they might look different now since the error message was different?
 
Last edited:
I waited a month to come back here and thank everybody for the help, I isolated the possible fixes and apparently, what did the most difference was to disable Windows Fast Startup, ever since I disabled it I've got no BSODs whatsoever, I researched about Windows Fast Startup and apparently a lot of people have BSOD issues because of it, I even got my RAM back to EXPO 1 at 6000MHz also without BSODs again, so yeah, from my understanding the main issue was Windows Fast Startup, thanks again everybody!
 
Thanks for getting back and I'm glad it's sorted.

FWIW. What Fast Startup in Windows does is to hibernate the Windows kernel when you shutdown, when you then do a cold boot the kernel is resumed from hibernation. Fast Startup was really designed for those using an HDD as their system drive, hibernating/resuming the kernel made for faster boot times. The problem with it is that some third-party drivers don't play well when they are resumed in this way, that's probably what caused your problems if disabling Fast Startup has cured them. In any case, if you have an SSD as your system drive (and you do) then Fast Startup bring no real benefit at all.

Also, the issue regarding the maximum memory speed specified in CPU documentation is something I've been researching of late because I wasn't certain what it actually meant. What it does mean is that the speed specified in the CPU documentation is the fastest RAM speed that the CPU is guaranteed to be stable with - it's the warranty speed, the maximum RAM speed at which the CPU vendor will consider a warranty claim. Most CPUs will happily accept RAM speeds much higher than this, as you are finding, but if you ever suspect RAM as a possible cause of problems (BSODs/crashes/freezes) then it's important not to exceed the CPU specified maximum RAM speed.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top