Windows 10: KERNEL_SECURITY_CHECK_FAILURE after USB short

Hard drives do not get corrupted with the BSODs.
@Ztruker, what software that is installed does it belong to? I did not find any program from Diskeeper.

 

I disabled the diskeeper service, it was not running when the latest bsod occured.

 

What was the error code displayed?

Unfortunately the dump is useless because of
Code: Event[7817]: Log Name: System Source: volmgr Date: 2016-06-24T01:08:47.483 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Jarvis-5 Description: Crash dump initialization failed![/quote] Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Please (re)move some files to increase the free space to at least 15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background, 15% is to be on the safe side.


Warning Less free space could cause BSODs or other problems, because Windows cannot perform the tasks it needs to do in the background!


Now that I am checking it, the driver of which I posted about in the first post is a USB driver that is provided by ASUS. Where did you get those drivers from? Checking ASUS the newest drivers are from 2012 Windows 7.

 

It was a page fault in non paged area BSOD with some sys file listed.

Also I have 639 GB free. I think I have enough disk space. *Smile

 

Your E partition does not have enough free space.

 

ExpressCache is in services.txt post #12

 

The E drive is an external drive with more free space than currently used on my primary drive. Do I really have to shuffle disk space around because of BSODs?

Waiting for a few more BSODs before I give up and reinstall the OS. I do not like giving up without a fight, however. I really don't understand how a short caused all this.

 

Service yes, but software?

Code: Drive Eescription Local Fixed Disk Compressed No File System NTFS Size 3.64 TB (4,000,751,546,368 bytes) Free Space 292.59 GB (314,161,111,040 bytes) Volume Name My Book Volume Serial Number 9AB1D2CE[/quote]

 

[/quote] I don't know what you're trying to say as my statement remains valid. Yes I only have 292GB free on the E drive but I only have 267GB used on my C drive. I find it absurd Windows needs that much space free but if it will help with the BSODs somehow, which it didn't have a problem with before mind you, I will clear some space.

Latest BSOD while I was asleep attached.

 

There are lots of services that you won't find backing software for. I expect this is one associated with a driver perhaps? I don't know but disabling the Service should take care of it.

From what I can find it belongs to Diskkeeper.

 

The free space is not only meant for the main drive, but for ALL connected partitions as mentioned. Your statement is valid, but it is not enough as your other partition(s) do not have enough free space.

 

Free space hasn't been made because I'm not moving my backups to the C drive, which seems unstable, at the moment. I may have to buy another hard drive for specifically backups now.

Latest BSOD included. This time it was some IRQL error.

 

Lets rule out the memory, if the memory test returns zero errors then continue with driver verifier.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

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 when you have a bluescreen, whatever 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 in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note 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.

 

Oh boy, here we go with the frustrating memory tests again, jeeze. They take longer than reinstalling the OS, lol.

Anyway, last night's dump while I was asleep. Will do Memtest tonight.

 

That is certainly true, it can be a real pain, for 12GB it could take up to a day with bad luck, but once it is done many find out the memory is the cause and are living happy afterwards.

Real quick I could not find anything interesting in the dump that would cause me to give another suggestion.