Does my computer experience random BSODs?
Does my computer experience random BSODs?
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.
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 completed the task using a USB flash burned with the media creation tool, and all necessary drivers were downloaded from their official sites after reinstalling Windows, which wipes almost everything on the PC. Regarding the BIOS update, I plan to do it immediately—it will reset the CMOS anyway.
Why are you implying my PSU is the weakest part of my PC? It has 650W, significantly more than what the PC requires, especially with the overclock applied (493W).
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.
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....
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.
Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
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...
Code:
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.
hr=0x80004005 indicates no file access. Possible reasons include storage problems, permission issues, or corrupted files. Since minidumps aren't being created, the drive might be disconnecting. You can upload the eventviewer system logs by opening the event viewer, navigating to windows logs, right-clicking on System, and selecting save all event as... then share the .evtx file once uploaded.
The information is included in the Sysnative file collection output referenced in post #6.
Sorry for the delay, thank you for your assistance. I plan to execute the command in CMD as you suggested. My main question is whether it's unusual for all BSODs, regardless of the error code, to point to Ntfs.sys. Also, I noticed the PAGE_FAULT_IN_NONPAGED_AREA setting was changed before the overclocking. I will also test the app you mentioned. Regarding the BSOD dump files, even after reinstalling Windows 11, only the first one could auto-reboot my PC, and afterward all BSODs required a manual restart by pressing the reset button on the case since they were stuck at 100%. This is quite frustrating.