Daily BSOD - - - ntoskrnl.exe (+416980) issue?
Daily BSOD - - - ntoskrnl.exe (+416980) issue?
Using ufile to distribute those small files is possible. Yes, they must be downloaded but it's free.
In the reliability/history viewer didn't locate any shared items.
Pick three random days, and it appears I was operating the PC differently.
Images: https://imgur.com/a/18pNOLN
View: https://imgur.com/a/18pNOLN
This is the most recent dump
https://ufile.io/7fa8eo7i
Tell me if you require additional details.
PS: I'm still using just one drive. Today I simply rebooted the PC, opened Steam to download a game and checked the Reliability/History. It crashed shortly after.
Edit1: Crashed once more when the PC restarted (I forced a restart) due to MEMORY_MANAGEMENT error. New dump
https://ufile.io/tve7atqa
The five uploads you posted recently (dated 5th Dec) clearly focus on memory issues. Four of these are related to memory management problems, but they involve two distinct exceptions: one concerns a page table entry corruption and the other involves an I/O memory space error. The fifth upload checks for a STORE_DATA_STRUCTURE_CORRUPTION bug, with an exception noting that a heap buffer has been damaged—a heap being a type of memory allocation area.
There are no third-party drivers present on the call stack preceding any of these issues, which reduces the likelihood that an external driver is involved. Should poor RAM be the root cause, we should then examine the CPU next. Since you're using an Intel processor, the recommended approach is to use the Intel Processor Diagnostic Tool.
Download it and review its findings.
Additionally, running Prime95 would be beneficial. This stress test can stress both CPU and RAM, helping to uncover instability. It’s important to note that Prime95 may cause your CPU to overheat, so a temperature monitor such as CoreTemP should be used to track temperatures.
Perform all three Prime95 tests—Small FFTs, Large FFTs, and Blend—sequentially for at least one hour per test, extending the duration if possible. If Prime95 reports errors, causes crashes, or triggers BSODs, or if your CPU exceeds its maximum temperature threshold (100°C), cease testing and inform us of the outcome.
This might seem a bit odd, but have you refreshed your bios since this began? I'm asking because you've only talked about drivers. The point is not to highlight exact problems, but to rule out other possibilities and confirm everything is current. I'm bringing this up mainly because I've experienced similar bsods after a big Windows 11 update released last year. Memtests were clean, but the Windows memory diagnostic kept showing errors and logs consistently pointed to RAM issues. Updating the bios helped me, though I'm not guaranteeing it will fix this. I just want to make sure you're not using an outdated bios version that could conflict with Microsoft updates.
So,
I began with the Intel Test. The first and second attempts were successful, but the third attempt caused a crash after opening FF.
Upload files for free - 121123-7140-01.dmp - ufile.io
Download 121123-7140-01.dmp for free from ufile.io instantly, without signup or pop-up ads
ufile.io
I updated the BIOS to the latest version (released just 11 days prior) and repeated the Intel Test three more times, all passing.
Next, I tried Small for about 1 hour and 30 minutes, then Large for nearly 2 hours, followed by Blend for almost 2 hours. No issues occurred during these sessions, even with low temperatures and extended test times.
https://imgur.com/a/dwhVoiP
View: https://imgur.com/a/dwhVoiP
Just experienced another crash while playing a game.
Upload files for free - 121223-6656-01.dmp - ufile.io
Download 121223-6656-01.dmp for free from ufile.io right away, no signup needed and no pop-up ads
ufile.io
I plan to purchase some 100% compatible RAMs (based on motherboard support page).
Another memory management BSOD remains unresolved while my new RAM is installed.
Upload files for free - 121223-8015-01.dmp - ufile.io
Download 121223-8015-01.dmp for free from ufile.io immediately, without signup or pop-ups
ufile.io
Another one
Upload files for free - 121323-7765-01.dmp - ufile.io
Download 121323-7765-01.dmp for free from ufile.io right away, without registration and without pop-up ads
These three error logs still point clearly to a RAM or motherboard RAM slot issue. One of the logs shows a PAGE_FAULT_IN_NONPAGED_AREA warning, which indicates a page fault occurred while handling a non-paged memory area. In the detailed call stack, we observe a memory error in private memory (nt!MiResolvePrivateZeroFault+0x1af) and, after the kernel begins recovery, a page fault appears (nt!KiPageFault+0x369), which triggered the BSOD.
The second log is a MEMORY_MANAGEMENT warning with an exception code pointing to an invalid page table entry (PTE). The stack reveals that the address space ended normally and cleanup was underway for the memory it occupied. The BSOD occurred when the nt!MiDeleteVa+0x2316e2 function was invoked. Although a very large offset (0x2316e2) was recorded, it lies outside the module's range (only 0x104700 bytes), which is why the BSOD happened. The origin of this offset remains unclear, but since all functions are within Windows modules, it's likely not a software issue.
The third log is a KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION warning, suggesting a thread was terminated before all locks were released. The call stack shows the process ended normally with memory cleanup in progress. The BSOD appears during the nt!KeCleanupThreadState+0x246428 function call. Again, a large offset (0x246428) beyond the module's end (0x1047000 bytes) was found, and all functions are in Windows modules, indicating this is not a software fault.
Although Prime95 performed well, it suggests the problem isn't related to CPU performance. However, Prime95 did stress RAM during some tests, which would have been problematic if it failed. It's possible that a faulty third-party driver caused these issues. It could be that such a driver corrupted critical system structures or disrupted queues and lists, only becoming apparent later when a BSOD occurred in a different thread. The faulty driver would have disappeared from the dumps once it was no longer active.
Given this, and before investing further, it's highly advisable to activate Driver Verifier...
Driver Verifier automatically tests selected drivers—especially third-party ones—each time they are invoked. These additional checks aim to detect drivers that behave erratically. If any driver fails its verification, Driver Verifier will trigger a BSOD. The resulting minidump should provide sufficient details to pinpoint the unstable driver. Therefore, it's crucial to retain all minidumps generated while Driver Verifier is active.
To activate Driver Verifier:
1. Create a System Restore point or capture a disk image of your system drive using tools like Acronis or Macrium Reflect. Driver Verifier might cause a BSOD during boot (some drivers load at startup), which could lock you in a boot-BSOD cycle.
2. If you encounter a boot-BSOD, boot from the Windows installation media and restore to the point you saved. This removes Driver Verifier and allows normal booting.
3. Alternatively, use the Acronis or Macrium Reflect boot media to restore your image.
Do not skip this step—it's essential to escape the boot-BSOD trap.
To start Driver Verifier:
1. Save a System Restore point or disk image of your system drive (using Acronis, Macrium Reflect, etc.).
2. During boot, Driver Verifier may cause a BSOD for a driver during installation. If this happens, you'll be stuck in a boot loop.
3. To exit the loop, boot from the Windows media and restore to the saved point, removing Driver Verifier.
4. Alternatively, use the provided boot media to restore your image.
Please note that Driver Verifier will remain active after reboots and shutdowns, and it can only be disabled manually.
Expecting BSODs is part of the process—this is necessary to identify unstable drivers. Ensure all minidumps are preserved while Driver Verifier is running.
To disable Driver Verifier:
- Enter the command `verifier /reset` in the Run command box or command prompt.
- Navigate to the dialog, select options like 'Create custom settings (for code developers)', and click Next.
- In the subsequent checks, ensure you enable all relevant tests (Special Pool, Force IRQL checking, etc.).
- Click Next and confirm the driver list.
- Select drivers from a list (e.g., Wdf01000.sys, ndis.sys, fltMgr.sys, storport.sys).
- Finish and reboot your PC.
Reminder: Disabling Driver Verifier may cause performance drops, as it performs additional checks each time a third-party driver loads. Ensure all drivers are loaded via apps, features, and devices to avoid missing unstable ones.
After reboot, keep all minidumps generated during testing. Upload them to the cloud with a public link if needed.