Question BSOD issues ?

[Unconformed]

Hi

Built my Son a PC and getting BSOD. I built mine first to make sure things were stable. I have built all my own PCs and things have been fine. Never had this happen, sucks it is happening to my Son, but we are using it as a learning opportunity and he can use his Mum's in the meantime.

I have never taken my PC to a repair store, and I don't want to start now Please help me redeem myself.

Specs
MB: Gigabyte B650 Gaming X mATX
CPU: Ryzen 5 7600X
GPU: 1080TI
RAM: Kingston - KF552C40BBAK2-16
PSU: Cooler Master - MPE-8501-AFAAG-AU
Storage: WD Black SN770 NVMe SSD
OS: Windows 11

Issue
Getting BSOD. It can start occurring randomly, and then it happens constantly. For example, after reinstalling windows, it is fine for a week or two, and then progressively starts crashing.

Things I have done

1. I updated bios to most recent
2. Ran memtest
3. Updated chipset drivers.
4. Reinstalled windows
5. Inspected the mini dump and I am getting this: IRQL_NOT_LESS_OR_EQUAL
6. I started to do the steps here https://www.tomshardware.com/how-to/fix-irql-not-less-or-equal-errors-windows
   1. However, I can't even get into Windows now.
7. Followed this guide
   1. https://www.tomshardware.com/how-to/fix-irql-not-less-or-equal-errors-windows
      1. Ran this command "DISM /Online /Cleanup-Image /CheckHealth" and got more BSOD instantly.

I can't boot in safemode as it says "pin is not set-up" and it gives me no other option to log-in.

I am thinking of taking it apart and making sure everything is set properly.

Minidump

https://www.mediafire.com/file/3sh2su32r1en8az/120224-10484-01.dmp/file

This is older, for some reason. I will try get a newer one.

Question

I have a couple of unused recovery partitions. Could this be causing issues?

https://imgur.com/a/jYaGZLJ

View: https://imgur.com/a/jYaGZLJ


Ty

 

[ubuysa]

Hello and welcome to the forum!

It's always a risk making a diagnosis based on only one dump, more dumps allows for a wider view of what's happening. However, that said, this one dump was caused by a network adapter driver called rtf64x64.sys. You can see it clearly in the failure bucket in the dump....

FAILURE_BUCKET_ID:  AV_rtf64x64!unknown_function

The version of that driver that you have installed is old, dating from Spet 2021...

9: kd> lmvm rtf64x64
Browse full module list
start             end                 module name
fffff806`09060000 fffff806`09071000   rtf64x64 T (no symbols)          
    Loaded symbol image file: rtf64x64.sys
    Image path: rtf64x64.sys
Image name: rtf64x64.sys
    Browse all global symbols  functions  data  Symbol Reload
  Timestamp:        Wed Sep 22 11:40:17 2021 (614AEBF1)
    CheckSum:         000160B6
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

This is a Realtek driver but the network adapter could be from any vendor, most of them use Realtek chipsets. Look on the website for the network adapter that you're using and see whether there is an updated driver.

If that adapter is WiFi, and there is no updated driver (or it doesn't help) then try (temporarily) connecting via Ethernet direct to the router to prove whether it's the WiFi adapter itself at fault.

If it does BSOD again please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

 

[Unconformed]

Hello and welcome to the forum!

It's always a risk making a diagnosis based on only one dump, more dumps allows for a wider view of what's happening. However, that said, this one dump was caused by a network adapter driver called rtf64x64.sys. You can see it clearly in the failure bucket in the dump....

FAILURE_BUCKET_ID:  AV_rtf64x64!unknown_function

The version of that driver that you have installed is old, dating from Spet 2021...

9: kd> lmvm rtf64x64
Browse full module list
start             end                 module name
fffff806`09060000 fffff806`09071000   rtf64x64 T (no symbols)         
    Loaded symbol image file: rtf64x64.sys
    Image path: rtf64x64.sys
Image name: rtf64x64.sys
    Browse all global symbols  functions  data  Symbol Reload
  Timestamp:        Wed Sep 22 11:40:17 2021 (614AEBF1)
    CheckSum:         000160B6
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

This is a Realtek driver but the network adapter could be from any vendor, most of them use Realtek chipsets. Look on the website for the network adapter that you're using and see whether there is an updated driver.

If that adapter is WiFi, and there is no updated driver (or it doesn't help) then try (temporarily) connecting via Ethernet direct to the router to prove whether it's the WiFi adapter itself at fault.

If it does BSOD again please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Hi

Ty, I failed to add that I looked that up, and based on instructions here, I disabled

https://www.reddit.com/r/WindowsHelp/comments/1e0xycv/windows_11_24h2_bsod_related_to_rtf64x64sys_driver/

I disabled Realtek LightWeigh Filter(NDIS6.40) in wifi and ethernet adapters. wifi was disabled anyway.

I think you are right, I will check MB site for updated drivers. It could be that simple.

Tho it won't load at all ATM, and I can;t get into safemode as it it says, you will need to rest pin. Before not allowing me to do that.

I might just reset windows and update drivers.

 

[Unconformed]

Hello and welcome to the forum!

It's always a risk making a diagnosis based on only one dump, more dumps allows for a wider view of what's happening. However, that said, this one dump was caused by a network adapter driver called rtf64x64.sys. You can see it clearly in the failure bucket in the dump....

FAILURE_BUCKET_ID:  AV_rtf64x64!unknown_function

The version of that driver that you have installed is old, dating from Spet 2021...

9: kd> lmvm rtf64x64
Browse full module list
start             end                 module name
fffff806`09060000 fffff806`09071000   rtf64x64 T (no symbols)        
    Loaded symbol image file: rtf64x64.sys
    Image path: rtf64x64.sys
Image name: rtf64x64.sys
    Browse all global symbols  functions  data  Symbol Reload
  Timestamp:        Wed Sep 22 11:40:17 2021 (614AEBF1)
    CheckSum:         000160B6
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

This is a Realtek driver but the network adapter could be from any vendor, most of them use Realtek chipsets. Look on the website for the network adapter that you're using and see whether there is an updated driver.

If that adapter is WiFi, and there is no updated driver (or it doesn't help) then try (temporarily) connecting via Ethernet direct to the router to prove whether it's the WiFi adapter itself at fault.

If it does BSOD again please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Hi,

Also, do you have any thoughts on the drivers here? Are there any recovery partitions I can rid of? I just went into windows repair and went to command prompt and it put me in x drive. I changed Dir to C:, but thought it was odd that it placed me in X drive. I also can;t restore windows (I'll do a clean install, concerned I will create another recovery partition.

https://imgur.com/a/jYaGZLJ

View: https://imgur.com/a/jYaGZLJ

 

[ubuysa]

The Recovery Partition is used only when you do a Windows Reset. Having two isn't ideal but I doubt that's the cause of your problems.

I really don't like the disabling you've done, that's never a wise thing to try. I was also a tad incorrect when I said it was a wireless driver, it's actually a packet filter driver and thus could be called using a LAN adapter too (which you are doing).

I note that there is a LAN driver for that board dated 10th Dec 2024, that's more recent than the 26th Aug 2024 version you have installed.

There is also a BIOS update (FB3g) that is more recent than the FB3e version you have installed. THe later version contains AGESA code updates and you always want to get the latest AGESA updates.

From where did you source all the drivers when you installed Windows?

If you do a clean install then delete all UEFI partitions (to remove the extra Recovery Partition), also only install Windows, the drivers from the motherboard vendor's site, and all Windows updates, but don't install anything else. Then see how stable it is.

 

[Unconformed]

Hi

Have done as you suggested, will get my Son to play some games on it as it was gaming that initially triggered it. right now it seems fine.

I would normally get drivers form MB site. I was promoted to DL Gigabyte Control center. I can only hope they would auto detect the relevant drivers for their own MB. I installed them form there. PLs let me know if this is an issue with the Gigabyte Control center tool.

I'll update Bios again, good pick-up, ty.

TYSM for your help!

 

[ubuysa]

I prefer to do things manually but the Gigabyte tool should (of course) find the right drivers.

 

[Unconformed]

Cheers, you would think so.

I might make him update bios

 

[Unconformed]

Hello and welcome to the forum!

It's always a risk making a diagnosis based on only one dump, more dumps allows for a wider view of what's happening. However, that said, this one dump was caused by a network adapter driver called rtf64x64.sys. You can see it clearly in the failure bucket in the dump....

FAILURE_BUCKET_ID:  AV_rtf64x64!unknown_function

The version of that driver that you have installed is old, dating from Spet 2021...

9: kd> lmvm rtf64x64
Browse full module list
start             end                 module name
fffff806`09060000 fffff806`09071000   rtf64x64 T (no symbols)         
    Loaded symbol image file: rtf64x64.sys
    Image path: rtf64x64.sys
Image name: rtf64x64.sys
    Browse all global symbols  functions  data  Symbol Reload
  Timestamp:        Wed Sep 22 11:40:17 2021 (614AEBF1)
    CheckSum:         000160B6
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

This is a Realtek driver but the network adapter could be from any vendor, most of them use Realtek chipsets. Look on the website for the network adapter that you're using and see whether there is an updated driver.

If that adapter is WiFi, and there is no updated driver (or it doesn't help) then try (temporarily) connecting via Ethernet direct to the router to prove whether it's the WiFi adapter itself at fault.

If it does BSOD again please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

I just got BSOD again.

There is no dump file, IO I have not changed default setting. Minidump explorer can't see anything.

I went to install SysnativeBSODCollectionApp, but windows came up saying that it is a potential threat. I can see you are a respected member here and I will choose to trust your judgment.

Am yet to update bios too.

 

[Unconformed]

Here is the upload.

https://file.io/c7ZQ6dZ0iiun

Will update bios now.

Have been reading other threads where you helped too. Will try make things easy for you.

TY

 

[ubuysa]

Thanks for the upload.

First things first. I can see that you're using two WD Black SN770 SSDs and that you're running Windows 11 24H2 (build 26100). There is a known issue with some WD SSDs and 24H2 which requires a drive firmware update to fix. Download the WD Dashboard and use that to update the firmware for both drives.

If there is a firmware update available that may well solve your problems.

If it doesn't then we need to get you writing dumps and to do that ALL of the following must be true...

• The page file must be on the same drive as your operating system
• Set page file size to "system managed"
• Set system crash/recovery options to "Automatic memory dump"
• The "Overwrite any existing file" box must be checked
• The "Write an event to the system log" should be checked
• The dump file location must be %SystemRoot%\MEMORY.DMP
• Windows Error Reporting (WER) system service should be set to MANUAL
• User account control must be running

In addition, the following can also prevent you seeing dumps...

• SSD drives with older firmware may not create dumps (update the drive firmware - which you should have now done)
• Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
• Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

I am seeing volume manager errors each time you get a crash with a 0x00040049 exception code, that can be caused by a flaky system drive (where the pagefile is located), this may well be firmware related.

Unfortunately the msinfo32.nfo file in your upload is corrupted and that's often a very useful source of information. Please enter the Run command msinfo32. When the System Information window appears click File > Save and choose a location to save the msinfo32.nfo file. Then upload that file to the cloud with a link to it here.

Also, navigate to the folder C:\Windows\LiveKernelReports. Under there you may find many sub-folders, look through all of them and upload an dump files you find in there.

I suspect the WD firmware update will solve your issues but please upload the other data asked for.

 

[Unconformed]

Thanks for the upload.

First things first. I can see that you're using two WD Black SN770 SSDs and that you're running Windows 11 24H2 (build 26100). There is a known issue with some WD SSDs and 24H2 which requires a drive firmware update to fix. Download the WD Dashboard and use that to update the firmware for both drives.

If there is a firmware update available that may well solve your problems.

If it doesn't then we need to get you writing dumps and to do that ALL of the following must be true...

• The page file must be on the same drive as your operating system
• Set page file size to "system managed"
• Set system crash/recovery options to "Automatic memory dump"
• The "Overwrite any existing file" box must be checked
• The "Write an event to the system log" should be checked
• The dump file location must be %SystemRoot%\MEMORY.DMP
• Windows Error Reporting (WER) system service should be set to MANUAL
• User account control must be running

In addition, the following can also prevent you seeing dumps...

• SSD drives with older firmware may not create dumps (update the drive firmware - which you should have now done)
• Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
• Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

I am seeing volume manager errors each time you get a crash with a 0x00040049 exception code, that can be caused by a flaky system drive (where the pagefile is located), this may well be firmware related.

Unfortunately the msinfo32.nfo file in your upload is corrupted and that's often a very useful source of information. Please enter the Run command msinfo32. When the System Information window appears click File > Save and choose a location to save the msinfo32.nfo file. Then upload that file to the cloud with a link to it here.

Also, navigate to the folder C:\Windows\LiveKernelReports. Under there you may find many sub-folders, look through all of them and upload an dump files you find in there.

I suspect the WD firmware update will solve your issues but please upload the other data asked for.

Hi

Ty. Bios and firmware now updates.

Will see how it goes and upload the requested files at a later time.

Will also take other steps mentioned if issue persists.

Appreciate your assistance. I think the best thing is I am my son are learning.

 

[ubuysa]

We're all learning. Always.

 

[Unconformed]

Fingers crossed, but no crashes. I think you nailed it.

I do recall reading about an issue with these drives when building mine a while ago. I had forgotten completely. I also did not know you could update the firmware.

Thanks for being a kind person and helping me redeem myself in my Son's eyes.