Random BSODs, memory access violations and more

[estXcrew]

Hello!

My computer has a history of BSODs. I've re-installed my windows 4 times in the hope of finding the solution. The current version I'm running is downloaded from MSDN with Service Pack 1 pre-installed on it, of course installed all the updates. This install of windows is I'd say like a month old, and the copy of my windows is OEM.

I've ran verifier, no unsigned drivers are found. I have all my drivers up to date as far as I know.

The BSOD happens to be somewhat random. There really isn't a rule, but it often occurs while gaming, but that might just be coincidence because gaming is the thing I do most at this PC. I talked with a guy about this issue and he helped me to find out that most of my BSODs are memory access violations..

My computer is old, so I'm thinking its hardware but if so where is it and if it's not hardware then I'd like to find the solution. I have ran memtest for one night and it concluded my memory is fine, but maybe I'll have to leave it running longer to find out. I've included the zip file below.

Hope you can help me based on the information I've provided

 

[Arc]

Hi estXcrew.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________

BugCheck D1, {2f444640, 2, 0, fffffa80053d36aa}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_TxSetState+1d )

Followup: MachineOwner
---------

BugCheck 3B, {c0000005, fffff96000184be8, fffff88008851ef0, 0}

Probably caused by : win32k.sys ( win32k!AllocateObject+34 )

Followup: MachineOwner
---------

BugCheck 1000007E, {ffffffffc0000005, fffff88012390c57, fffff88005874758, fffff88005873fb0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[estXcrew]

This is new (copied from WhoCrashed)

This was probably caused by the following module: win32k.sys (win32k+0xB4BE8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000124BE8, 0xFFFFF8800B2C96C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver

Occurred about 10 minutes after i started up my computer.

Also yesterday my OpenGL driver stopped responding, started with my computer deep-freezing for 10 minutes or so, resulting in my monitors blacking out the following message (and Minecraft being closed)
(Yes I know it looks like windows 8, its a theme and I'm actually using windows 7)

I've included the dump file for the previous bsod.

Also followed all your steps, nothing changed. Had verifier enabled even before I came posting here.

I'm going to run memtest agian tonight but I have ran it multiple times before with no errors overnight.

 

[Golden]

fffff880`0b2c8ef8  fffff880`032da45fUnable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for[COLOR="Red"] klif.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
 klif+0x1c45f

http://carrona.org/drivers/search.php?id=klif.sys
Lets test something...uninstall Kaspersky completely and replace it with MSE.

 

[estXcrew]

But I have licensed KIS.. meh.. okay.. I'll do that but I really need to get it back up and running, don't want to waste the money I've put into the year license

 

[Golden]

I understand. The choice is yours. All I am pointing out is that Kaspersky is objectively identified as a problem

Its not at all uncommon, I have seen many BSOD's here caused by every single anti-virus provider....the only exception being MSE.

 

[estXcrew]

Can I fix it? I've installed MSE but I want the bsod to be solved for KIS.. any suggestions?

 

[Golden]

Just so you understand, WinDBG has identified that Kaspersky is interacting in a way that causes Windows to crash. In other words Kaspersky is the cause of the BSOD.

If you uninstall Kaspersky and you get no BSOD, then the fix for the BSOD was uninstalling Kaspersky. There is no fixing the BSOD for Kaspersky.

 

[Arc]

The third party antivirus programs often cause BSODs. Unfortunately there is no way to fix the BSOD keeping the program installed. So either you have to accept the BSODs or you have to remove the program.

We suggest MSE because it never causes a BSOD.

 

[estXcrew]

Okay, thanks. I am now going to use MSE for a week or until the next bsod, then I'm going to reinstall KIS... I'm also going to report it on the KIS forums or support or whatever they have. Thank you

 

[Arc]

Its OK mate.

Hope those annoying BSODs dont get back to you.

 

[Golden]

 

[estXcrew]

Guess what! :C

(WhoCrashed)

On Wed 30.04.2014 14:46:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\043014-19203-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x68C1C)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88011D73C1C, 0xFFFFF88007AEAB80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel

dump file linked.

Occurred while Chrome, skype, and Brackets(Adobe product) were open. Luckily all my coding is stored straight on Google drive.

No KIS installed at this moment; using MSE.

 

[Arc]

Can you try to roll back the display driver to the earlier version? As a test?

Device Manager - Roll Back Driver
_____________________

fffff880`07aea6b8  fffff880`1119b847*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xe8847

 

[estXcrew]

Is it inevitable? Because I have no "old" drivers, meaning it will go back to the default "driver", what disables my secondary monitor, displays everything at a stone-age resolution, and messes up all my graphics in general.

And Maybe it will take weeks till another BSOD happens, so I'm not very keen to do that

 

[Arc]

That means you did a clean install on the display driver earlier.

Install the NVIDIA DRIVERS 314.22WHQL only, as another test.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  • GeForce Experience
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Observe if it BSODs with that old version too.

Suggesting such an old version, because that one is the last released driver from nvidia that did not ever fail on itself.

 

[estXcrew]

sorry for the long delay, I've been busy/lazy. I've now reverted to the 314.22 version with your recommended settings. I hope the bsods are solved finally =)

Marked as solved for now

 

[Arc]

Its ok mate.

Let us know if the issue bounces back.

 

[estXcrew]

occurred while browser, windows media player and Skype were open.


Whocrashed:

This was probably caused by the following module: dxgkrnl.sys (0xFFFFF88002C6EC56)
Bugcheck code: 0x50 (0xFFFFFFFF848B6A78, 0x0, 0xFFFFF88002C6EC56, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that invalid system memory has been referenced.

file linked as usual

 

[Arc]

Have you done the memtest as suggested in post #2?