Solved Random BSOD multiple times in a row

Recently my PC has been having random BSODs from time to time, and each time I'm doing something different.

Each time the BSODs happen multiple times in a row, and BSOD -> Restart -> BSOD -> Restart will return to normal after repeated multiple times.

At first I used sfc /SCANNOW and Dism to check the system files, and detected corruption, so I suspected that there was a problem with the hard drive, so I replaced the system disk with a new KOXIA SE10 SSD, but the problem still exists, so the system file corruption should be cause by the BSOD.

Then I ran MemTest86 and it passed 4 rounds without error, and it also passed 4 rounds when I assembled the system (3/‎18/‎2024).

All the hardware is under warranty, except for the RAM which is Corsair RAM from an old machine, so it should also have a permanent warranty.
I use an AIO cooler and opened the side panel of the case, so heat dissipation should not be an issue
So this should not be a hardware problem.

I now suspect the software Netlimter 5 and Clash Verge Rev,
Clash Verge Rev is my must-have software, I can't live without it, and I didn't find any BSOD reports on Github and it doesn't install drivers, so it shouldn't be caused by it?

I also briefly checked the dump and used windbg to run !program and found that it was caused by a different program each time, so I think it is not very accurate. My shallow knowledge can't support me to continue debugging. I have adjusted the dump type to automatic memory dump, but the dump file size it generates is still 2MB. I hope it will not affect the diagnosis.

I have set the system language to English for several days, but the logs collected by the v2 log collector are still partially in Chinese. I can't do anything about it, sorry.

Please help me, thank you very much!

log collector by V2 log collector: 16.96 MB folder on MEGA

Inory said:

I also briefly checked the dump and used windbg to run !program and found that it was caused by a different program each time, so I think it is not very accurate.

Click to expand...

Do you mean !process? Yes, it will potentially be different each time since it simply returns the last process context, it doesn't indicate what caused the crash, despite what many tutorials or videos might suggest.

It seems that the crashes are being caused by NetLimiter. I would suggest that you remove the program completely and then ensure that the nldrv.sys isn't being loaded afterwards by using the following command from command prompt:


It should either not exist or have a value of 0x4.

x BlueRobot said:

Do you mean !process? Yes, it will potentially be different each time since it simply returns the last process context, it doesn't indicate what caused the crash, despite what many tutorials or videos might suggest.

It seems that the crashes are being caused by NetLimiter. I would suggest that you remove the program completely and then ensure that the nldrv.sys isn't being loaded afterwards by using the following command from command prompt:

Code:

reg query HKLM\SYSTEM\CurrentControlSet\Services\nldrv /v Start

It should either not exist or have a value of 0x4.

Click to expand...

Thanks for your help, I made a typo, it was !process.

It seems that NetLimiter is causing the blue screen, and it seems that the driver works even when I don't have NetLimiter running.
I actually want to continue using NetLimiter, anyway I will report the error to them.

Thanks again.

Inory said:

It seems that NetLimiter is causing the blue screen, and it seems that the driver works even when I don't have NetLimiter running.

Click to expand...

It will do since drivers will be implemented as their own service in most cases which is why I mentioned about checking wherever the driver is disabled or not.

Inory said:

I actually want to continue using NetLimiter, anyway I will report the error to them.

Click to expand...

Okay good, they're the ones who will be able to actually resolve the issue with that driver. Please make sure that you provide them with the dump files as well. In the meantime, you could disable the Netlimiter driver using the following from command prompt:


You'll need to reboot the machine for the changes to take effect.