![]() That's why it's important to follow a process like the one I did. It could be something other than your graphics driver. ![]() If you experience a Kernel Security Check Failure BSOD, the cause of your problem may not be the same as mine. Note that the driver that GeForce Experience reinstalled was the same exact version (December 8th) that I had before. I have no idea how my graphics driver became corrupted, but this reinstall seems to have fixed it. Since doing the reinstall, I haven't experienced a single BSOD (and no wavy lines either). In my case, I found that using DDU to uninstall my graphics driver and then using Nvidia GeForce experience to install it fresh was the solution to my problems. From there, you can download and reinstall the drivers. Your computer will then complete the uninstall process and restart. Then select GPU from the Device type menu and click Clean and restart. However, in short, what you need to do is download DDU, install it and launch it. We have a complete guide to uninstalling graphics drivers using DDU elsewhere. Simply using Windows' built-in uninstall tools will leave remnants of the driver behind which could remain in place even after you reinstall. To uninstall a graphics driver properly, you need to completely remove it using a free tool called DDU (Display Driver Uninstaller). The idea of the problem being graphics related made sense to me, because the crashes occurred when I had started watching videos and, right before the first BSOD, weird wavy pink and gray lines were appearing on every web page I visited in Chrome browser. Perhaps something had caused the driver to be corrupted recently. Uninstall and Reinstall Graphics Driver (in my case)ĭespite the fact that the graphics driver had been working successfully in my system for about a month, I decided to try completely removing and reinstalling it. Its driver date was December 8, 2023, which was more than a month before my BSOD, which made it seem like the driver could not be the issue. I decided that the problem was likely related to my graphics card, an Nvidia RTX 3090 Ti I have used without issue for a long time. Dxgkrnl.sys is related to the graphics card - the dxg stands for DirectX graphics - so it suggests a problem with the GPU. Ntoskrnl, is a big part of the OS but apparently it fails when there are memory issues, which could be due to a driver or due to a physical fault in memory. SFC /scannow did claim to fix some corrupted files, but it does that almost every time I run it, even if I haven't had a BSOD. I launched an elevated command prompt (running CMD as Administrator) and ran the following commands. So it's good practice to do these scans, but if they find and fix errors, this is not necessarily the end of your woes. On the other hand, if your computer just had a BSOD, some files could register as corrupted as a result of the BSOD crash rather than the cause of it. ![]() If your computer has corrupted files that could be causing a BSOD. This is low-hanging fruit that may or may not solve your problem. Scan for Disk Corruption and Corrupt Files So I determined that malware was not the cause of my Kernel Security Check Failure BSOD. ![]() ![]() I ran a Malware Bytes scan and it didn't find anything significant (a couple of older files in my downloads folder were flagged, but these were data files and nothing I had edited or installed). I find that Malware Bytes can pick up some malware which is not technically viruses that Windows Security misses. I also downloaded and installed a trial version of Malware Bytes, which is also available in a free version. I use Microsoft's built-in Windows Security application as my anti-virus app, and I used it to do a quick scan, but it didn't find anything. Because the word "security" is in the BSOD, Kernel Security Check Failure, the first thing I tried was scanning for malware. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |