Question My PC gets random BSODs ?

[Vasile01Ro]

My stared getting random BSODs at random times. So far I got: "PAGE_FAULT_IN_NONPAGED_AREA"(i did run a memory test and didn't find any errors), "HYPERVISOR ERROR" and "SYSTEM_THREAD_EXEPTION_NOT_HANDLED" in this order(of course they repeated). All of these BSODs had Ntfs.sys at fault( and when I mean all I mean all of them with no exception). I also have ran tests for the hard drivers and defragment and optimization but there was no problem found.

Another thing that is frustrating is that the BSOD it's self is broken. Instead of automatically restart the PC when it reaches 100% it just gets stuck in there and when I try to find the minidumps with BSOD Viewer there is no dump file at all.

I did a kind of a overclock on my Ryzen 7 5800x but i don't think that is the problem since i have ran Cinebech R23, R24 and Prime95 torture test for more than 2hrs and never got a BSOD or a forced restart from the mobo(it was a PBO overclock so it only reaches 4.850 Ghz in Prime95 on one core at time and for a short period of time, the manual overclock was unstable at +200Mhz so i just gave up with that one an went for small overclock only for about +100Mhz).

I did reinstall win11 but nothing has changed at all ( well it does boot faster to be honest).
The thing is i don't actually know what to do next to repair this. Shall I consider disconnecting one of the drives at a time since the BSODs are pointing to Ntfs.sys?

My config is:
Motherboard: Gigabyte B450 DS3H V2; Bios version:F66
CPU: AMD Ryzen 7 5800X
GPU: Gigabyte GeForce RTX 4060 8GB Windforce Gaming OC
Cooler: Corsair H150i 360MM AIO
RAM: Adata XPG Gammix D10 16GB(2x8GB)
Storage: Samsung 970 EVO Plus 500GB,Seagate Barracuda 7200RPM 2TB HDD and an very old Hitachi 100GB HDD from old dead laptop(language redacted)
PSU:Seasonic S12III 650W 80 Plus Bronze

With all of these and the 8 case fans (including the AIO's fans) the PC should use about 493W of the PSU while at full load on everything.( I'm saying this just to clarify that this PSU is enough)
Sorry for any grammar or spelling mistakes.

 

[Lutfij]

Flash to F67b, then clear the CMOS. The PSU in your is the weakest link(IMHO) in your build. You state reinstalling your OS, did you recreate the installer for said OS to rule out a corruption? To add, did you install the OS in offline mode, to later manually install all relevant drivers with their latest revisions in an elevated command? One other thing is you should disconnect all drives except for the one that you want to install the OS onto prior to the OS install.

You can pass on your .dmp files for us to see and perhaps we can narrow down what is triggering the issue.

+ This is a family friendly site, mind your language

 

[Vasile01Ro]

Flash to F67b, then clear the CMOS. The PSU in your is the weakest link(IMHO) in your build. You state reinstalling your OS, did you recreate the installer for said OS to rule out a corruption? To add, did you install the OS in offline mode, to later manually install all relevant drivers with their latest revisions in an elevated command? One other thing is you should disconnect all drives except for the one that you want to install the OS onto prior to the OS install.

You can pass on your .dmp files for us to see and perhaps we can narrow down what is triggering the issue.

+ This is a family friendly site, mind your language

i did it with a usb flash burned using the media creation tool and all the aditional drivers were downloaded from their official websites since reinstalling windows deletes almost everything on the PC. Talking about the BIOS update i will do it right now (the BIOS update will reset the cmos anyway).

Why are you saying my PSU is the weakest link in my PC? It has 650W, way more than the PC needs to run with the overclock applied (493W).

 

[ubuysa]

I appreciate that there are no dump files, but can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. 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.

The additional data in that output will help us get an insight into what may be going on.

 

[Vasile01Ro]

I appreciate that there are no dump files, but can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. 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.

The additional data in that output will help us get an insight into what may be going on.

Thanks man, i will try as soon as i can

 

[Vasile01Ro]

I appreciate that there are no dump files, but can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. 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.

The additional data in that output will help us get an insight into what may be going on.

Here is the SysnativeBSODCollection app archive. Sorry for being so late I was busy these days.

 

[ubuysa]

I notice in your OP you're talking about CPU overclocks and it seems you might still have the CPU overclocked? If so, please remove all CPU overclocks, they are known to cause BSODs. If you're undervolting the CPU as well please remove that too.

There were three dumps in the upload, although one was corrupted and not readable - that in itself provides information. Although the other two dumps fail with different bugchecks and during different operations there is a common denominator in both dumps, and that's that they both fail with invalid memory accesses. That means we must suspect bad RAM initially.

In addition, there are several application error messages in your Application Log with memory related exceptions. These are not uncommon on normal systems but your log contains more application errors than I would expect. That too points at bad RAM (at least initially).

There are other indicators of things that may be awry in the upload, but all of them could be symptoms of bad RAM, so we have to validate your RAM first....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window.

 

[kerberos_20]

hr=0x80004005 means no file access...either storage has issues or there are file permission issues or corrupted files
seeing as also minidumps not being created would point to drive disconnecting

can you upload eventviewer system logs?
open event viewer, open windows logs, righ click on System and choose save all event as... then post link once you upload that .evtx file

 

[ubuysa]

can you upload eventviewer system logs?
open event viewer, open windows logs, righ click on System and choose save all event as... then post link once you upload that .evtx file

They're in the Sysnative file collection output linked in post #6

 

[Vasile01Ro]

I notice in your OP you're talking about CPU overclocks and it seems you might still have the CPU overclocked? If so, please remove all CPU overclocks, they are known to cause BSODs. If you're undervolting the CPU as well please remove that too.

There were three dumps in the upload, although one was corrupted and not readable - that in itself provides information. Although the other two dumps fail with different bugchecks and during different operations there is a common denominator in both dumps, and that's that they both fail with invalid memory accesses. That means we must suspect bad RAM initially.

In addition, there are several application error messages in your Application Log with memory related exceptions. These are not uncommon on normal systems but your log contains more application errors than I would expect. That too points at bad RAM (at least initially).

There are other indicators of things that may be awry in the upload, but all of them could be symptoms of bad RAM, so we have to validate your RAM first....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small w

I notice in your OP you're talking about CPU overclocks and it seems you might still have the CPU overclocked? If so, please remove all CPU overclocks, they are known to cause BSODs. If you're undervolting the CPU as well please remove that too.

There were three dumps in the upload, although one was corrupted and not readable - that in itself provides information. Although the other two dumps fail with different bugchecks and during different operations there is a common denominator in both dumps, and that's that they both fail with invalid memory accesses. That means we must suspect bad RAM initially.

In addition, there are several application error messages in your Application Log with memory related exceptions. These are not uncommon on normal systems but your log contains more application errors than I would expect. That too points at bad RAM (at least initially).

There are other indicators of things that may be awry in the upload, but all of them could be symptoms of bad RAM, so we have to validate your RAM first....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window.

sorry for being late and thanks for helping, i will run the command in cmd as you said. What i would like to ask you is isn't it strange that all BSODs, no matter the error code, where pointing to Ntfs.sys? Also i had the PAGE_FAULT_IN_NONPAGED_AREA well before the overclock.I will also run the app that you just told me about. Talking about the BSODs dump files even after the win 11 reinstall only the first BSOD was actually
able to auto reboot my PC and after that all the BSODs required manual restart(pressing the reset button on the case) because they were stuck on 100% and that is kinda frustrating

 

[Vasile01Ro]

hr=0x80004005 means no file access...either storage has issues or there are file permission issues or corrupted files
seeing as also minidumps not being created would point to drive disconnecting

can you upload eventviewer system logs?
open event viewer, open windows logs, righ click on System and choose save all event as... then post link once you upload that .evtx file

all my bsods no matter the error code were either not pointing at something at all or they were pointing to Ntfs.exe and nothing else

 

[Vasile01Ro]

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window.

Here is the screenshot, talking about licensing errors I think you might guess why there are so many of them(i don't know if this is the reasson) but my windows is activated using a KMS server(it's not a work PC it's gaming PC so it's my personal PC) and talking about other apps licensing issues i don't know if this is the reason but I'm a little bit afraid to tell you what might be wrong with those apps(talking about games not other types of apps)

 

[Vasile01Ro]

I notice in your OP you're talking about CPU overclocks and it seems you might still have the CPU overclocked? If so, please remove all CPU overclocks, they are known to cause BSODs. If you're undervolting the CPU as well please remove that too.

There were three dumps in the upload, although one was corrupted and not readable - that in itself provides information. Although the other two dumps fail with different bugchecks and during different operations there is a common denominator in both dumps, and that's that they both fail with invalid memory accesses. That means we must suspect bad RAM initially.

In addition, there are several application error messages in your Application Log with memory related exceptions. These are not uncommon on normal systems but your log contains more application errors than I would expect. That too points at bad RAM (at least initially).

There are other indicators of things that may be awry in the upload, but all of them could be symptoms of bad RAM, so we have to validate your RAM first....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window.

Here]https://drive.google.com/file/d/1gnswQExOQPDde6SLus1HuOpm7BZr1aae/view?usp=sharing']Here is the log and html from the Memtest86 app[/URL]

 

[Vasile01Ro]

I notice in your OP you're talking about CPU overclocks and it seems you might still have the CPU overclocked? If so, please remove all CPU overclocks, they are known to cause BSODs. If you're undervolting the CPU as well please remove that too.

There were three dumps in the upload, although one was corrupted and not readable - that in itself provides information. Although the other two dumps fail with different bugchecks and during different operations there is a common denominator in both dumps, and that's that they both fail with invalid memory accesses. That means we must suspect bad RAM initially.

In addition, there are several application error messages in your Application Log with memory related exceptions. These are not uncommon on normal systems but your log contains more application errors than I would expect. That too points at bad RAM (at least initially).

There are other indicators of things that may be awry in the upload, but all of them could be symptoms of bad RAM, so we have to validate your RAM first....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

BTW. There are massive numbers of repeating licensing error messages in your Application Log...

Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          12/08/2024 12:07:28
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-52CH1KV
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x80004005
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window.

The html file here

 

[ubuysa]

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window. I want to be sure your copy of Windows is licensed.

 

[Vasile01Ro]

Can you please open a command prompt and enter the command slmgr /dlv. A small windows will open, please post a screenshot of that small window. I want to be sure your copy of Windows is licensed.

https://drive.google.com/file/d/1rPNORNOsWy2NYagNCg0L1yUHtu7dfC0j/view?usp=sharing

 

[ubuysa]

If this is a home PC, which I'm pretty sure it is, then it's not licensed properly. Home PCs cannot use the VOLUME_KMS channel, it's reserved for corporations that license many PCs. This is commonly seen with cheap licenses from the Internet where they illegally resell volume license keys. That's why you're seeing all those licensing errors in the logs.

I'm not sure what the forum policy is, but I won't help with Windows systems that are not properly licensed. Sorry.

 

[Vasile01Ro]

If this is a home PC, which I'm pretty sure it is, then it's not licensed properly. Home PCs cannot use the VOLUME_KMS channel, it's reserved for corporations that license many PCs. This is commonly seen with cheap licenses from the Internet where they illegally resell volume license keys. That's why you're seeing all those licensing errors in the logs.

I'm not sure what the forum policy is, but I won't help with Windows systems that are not properly licensed. Sorry.

Bro this KMS wasn't cheap.... it was free 😁, like the old KMSPico app wasn't working anymore so i went on GitHub and found a list of free KMS servers to use a set up manually in order to activate windows. Thanks for help any way. By the way those licensing errors, didn't even know they existed.

 

[Vasile01Ro]

If this is a home PC, which I'm pretty sure it is, then it's not licensed properly. Home PCs cannot use the VOLUME_KMS channel, it's reserved for corporations that license many PCs. This is commonly seen with cheap licenses from the Internet where they illegally resell volume license keys. That's why you're seeing all those licensing errors in the logs.

I'm not sure what the forum policy is, but I won't help with Windows systems that are not properly licensed. Sorry.

is it possible those were the BSODs reason? I mean i've done that on my dads laptop and on my laptop and they work without any BSOD exept that PC which is currently running fine(i don't exactly know why) but i'm concerned that it won't last for long until it does that thing again. Anyway I appreciate your time trying to help me. Hope it's just a faulty hard drive since i have an very rusty old one installed just for fun and since those bsods are pointing to Ntfs.exe.