BSOD - Page Fault - ntoskrnl.exe+efde7

[johndossier]

OS: Win7
Mobo: Asus Maximus IV Hero
CPU: i5 4670K
GPU: GTX 970 MSI Gaming 4G
RAM: 8GB Corsair Vengeance CAS 9
HDs: 250GB Kingston SSD, 1TB WD HDD, 300GB Hitachi HDD

DMP File

http://s000.tinyupload.com/index.php?file_id=98252543666263440824

Hi all.
System has been stable for a couple years without having to see the dreaded blue.

Notable changes today were a handful of Windows Updates

and a new HDD install, the WD terrabyte drive (not using for OS, just storage).

I used Acronis True Image to clone a single partition 160GB drive that I was replacing. Seemed to go fine but data and disk issues are definitely my expertise bottleneck. One thing I did notice was that I inadvertently ended up with a 100GB EFI partition on the disk that I didn't intend for. I formatted as GPT not MBR, maybe that was a mistake? Not sure if that BSOD is related to the HD anyway.

After the HD install I used the system for about an hour, almost everything I ran was from C: (my SSD) then after the windows updates I rebooted and went to run a game on my E: drive (300GB HItachi) and the BSOD happened. Did a memtest, everything fine, then tried the same game again after reboot and it ran fine.

Hopefully I've provided all of the useful information here. If I've missed anything please let me know.

Thanks.

 

[okcnaline]

It's the RAM; a RAM read error. How many times have you gotten the BSOD?

 

[johndossier]

It's the RAM; a RAM read error. How many times have you gotten the BSOD?

Yeah I was worried about that, hence the memtest right away.
I've only gotten it once, about 2 hours ago.

EDIT: Should probably mention I have 2 dimms of 4GB in Dual Channel mode in slots 1 and 3.
1st dimm is very snug (ram heatsink, not module itself) against one of my 120mm CPU fans (push/pull) but slid into place easily.

 

[okcnaline]

Hm... Alright, there shouldn't be problems. Tell us if you get any further BSODs.

 

[johndossier]

If I get another BSOD I will be back on here right away. So far nothing. Any thights about that EFI partition? Probably unrelated?

 

[Paul NZ]

I would uninstall Kaspersky. Looks like this can also cause this stop error. Then use their removal tool

It looks like Zonealarm is also on this system. vsdatant.sys is on this pc. This belongs to ZA. Looks like ZA can also cause this stop error

You should only have one firewall installed. Otherwise they'll conflict

 

[okcnaline]

Pah... Pathetic and unacknowledged and common anti-antivirus guys.

Don't listen to him. RAM read-writes got no relations to problems with antivirus causing IRQL_NO_MORE/LESS_OR_EQUAL errors, and you'd at least have to give more credit to modern security softwares to be more reliable than that.

And the EFI partition is completely unrelated. It's only the bootcodes that allow booting into Windows, Mac, or Linux from UEFI firmwares, not related to when booted into Windows.

 

[Paul NZ]

Modern security doesnt = Kaspersky. Its crap. Or ZA.

These 2 should go in the bin next to Nortons, AVG and Mcafee, and Bitdefender. Theyre all useless

The only thing theyre good at is crashing systems. Or screwing something up. Avast isnt far behind

 

[okcnaline]

Lel...

Stop making comments about bad security for a moment. The security software's system files crashing the system is IRQL_NO_LESS/MORE_OR_EQUAL, and is not equal to PAGE_FAULT_IN_NON_PAGED_AREA, or whichever the RAM error is. Fundamentally different issues.

The IRQL_NO_LESS/MORE_OR_EQUAL means that there are some problems reading a .sys or .dll files. It's usually data corruption, or maybe a bad install. Also, it could be bad hardware indexing (corrupt component), or bad job reading drivers. It's purely software errors, with very low occurrences that I try to help fix that is hardware-related.

Whilst the PAGE_FAULT_IN_NON_PAGE_AREA is a immediate problem with a mistaken byte while reading the RAM, or maybe a bad RAM module transferring very erroneous bytes. It's hardware problems, or maybe the software with that 1/x amount of lucky combinations that causes the error.

It's not about whether Kaspersky, ZoneAlarm, or for that matter, any anti-virus, is crappy or not. That's not even the problem. Antiviruses doesn't have the ability to control the RAM parts of the system. So explain how an antivirus can cause a RAM problem without even being able to communicate directly with it.
Oh, and it's also ntoskrnl.exe having trouble, not any other executables.

 

[begedis]

I am IT administrator (lazy one to dig much for you), and I guess it is coming with Windows updates. We see it being present a lot when users log off on different stations - they are trapped into BSOD instead. It definitely started being registered about 2015-06-12, up to several cases at stations every day. Exactly the same +efde7 offset in ntoskrnl.exe, as you cite here. My bet for cure so far is the same, it must have came with: patching actively, I have fished several patches from Microsoft Update right upon automatic check now.