Windows 10: Random BSODs - can be a few per day, or a few days between BSODs
There is something corrupting the memory - its either the RAM itself or a driver writing bad information to the memory.
As you have already tested the RAM I still think there is a rogue driver somewhere. We can use Driver Verifier to try and flush out the culprit.
Please make a backup of your important files and get your rescue media or create one
Please create a restore point.
Please read and run driver verifier.
If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
I've enabled the driver verifier and now the machine won't boot - it's stuck with a windows logo and a spinning circle. I can't see how to get to any of the options to disable the driver verifier since it hasn't got past this screen. How do I disable the verifier?
I don't know if it's still working and might not be the best approach so wait for more opinions and use this as last resort.
If you reset the PC right after you get the windows loading screen, after 3-5 times you should get the recovery screen.
I don't know why MS got rid of the old F8 option to boot in safe mod..
Use the recovery media which we told you to create and then you can get into recovery mode and follow the instructions in the Driver Verifier tutorial.
Panic over..after a couple of attempts at restarting I did indeed get the option to go into recovery options so was able to do a system restore.
Does this actually tell us anything about the BSOD crashes? Presumably no dump files will have been written?
I am not sure what was happening but something during the boot process was not right. As driver verifier is not going to work for you we will need to try another way. I suggest you perform a clean boot and gradually introduce start-up items back into the process until you find the one which causes problems. Of course if you get a BSOD even with a clean boot there is no point continuing since it is obvious it is not being triggered by any of the software you disabled for the clean boot. This is a bit hit and miss and can be time consuming which is why we do not use this method routinely. Read through the following tutorial:
Clean Boot - Perform in Windows 10 to Troubleshoot Software Conflicts
Hey guys, recently I've been having multiple BSODS of many types. From "IRQL_NOT_LESS_OR_EQUAL" To system service exception and even special pool memory corruption. I uninstalled my GPU driver using DDU and installed the driver needed but I still...
Hello I have been getting random BSODs for the past couple weeks, been trying to figure it out on my own but I feel like it is time to ask for some help.
Recently the BSOD had the error message KERNAL_SECURITY-CHECK-FAILURE. I rebooted with...
Hi hope u guys can help me. would be very thankful :)
Got a new system 1-2 Months old. Fresh installed Windows 10 Pro Build 1511.
But I am getting Bluescreens (not sure what the cause is) random. For example once I plugged in an USB-Stick I got...
Recently i started having random bsods...tried reseting windows and deleting and reinstalling video drivers and still nothing...i attached minidump files...pls help
Hello guys , i have bsods and game crashes of steam .I putted a new ram because the previous ram kit died (faulty rams causing bsods)and also i have a new graphic card r9 280 (because the previous gtx480 died too) . What can i do ? Bumps are not...