I understand, but there's no need to be worried about security. In the meantime, could you please post your entire system spec including PSU make and model, and also what you've changed.Īlso could you post links to the actual dump files, items like WhoCrashed and BlueScreenViewer don't give us the information require in many dump files, so we'd need to manually dig a bit further. So unfortunately, it doesn't actually help in any way, and simply indicates the issue is elsewhere, we just have to figure out where. Reason why you'll see ntoskrnl.exe as a common problem is because when Windows can't find something like that, it will often just blame the kernel driver, even though it won't be the driver that caused the issue. And unfortunately Windows isn't as smart as we'd like it to be, so when an Issue like a non-paged page fault occurs that it can't resolve, quite often the actual driver causing the issue is in hiding or already passed, so Windows then blames the thing that actually crashed, which is your kernel driver, because it can't see anything else. Click to expand.Not so, because ntoskrnl.exe is basically your core OS kernel, not a third party module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |