Random freezing followed by driver verifier violation blue screen

Hi i keep getting random freezes on my computer(1-2 times a day), to the point that the computer is completely unresponsive. When it happens the only way to restart it is to disconnect the power and turn it back on. Half the time these freezes are accompanied by a blue screen upon restart, with the DRIVER VERIFIER DETECTED VIOLATION error message, which may or may not be related.

It usually happens when watching videos on YouTube or when playing games.

Here is a link to the minidump files:

https://onedrive.live.com/redir?resid=61A126FB578BD900!1043&authkey=!AMVKtkJrqGv_kpE&ithint=folder%2cdmp

Also, would it help if I upload the much larger MEMORY.DMP  file?

Thanks for any help!

July 16th, 2015 8:26pm

First you can turn verifier off by typing verifier /reset in an elevated command prompt.

The underlying issue is your Avast.  Remove it and use the built in defender in its place

Microsoft (R) Windows Debugger Version 10.0.10166.9 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\zigza\Desktop\New folder\070615-6546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`10202000 PsLoadedModuleList = 0xfffff802`104db850
Debug session time: Mon Jul  6 01:17:24.839 2015 (UTC - 4:00)
System Uptime: 0 days 0:00:02.550
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 0, ffffe001c05fd880, 0}

*** WARNING: Unable to verify timestamp for aswVmm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswVmm.sys
Probably caused by : aswVmm.sys ( aswVmm+9d22 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
	the operating system. The only supported way to extend a kernel
	mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: ffffe001c05fd880
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_P1: 91

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe001c05fd880

BUGCHECK_P4: 0

BUGCHECK_STR:  0xc4_91

CPU_COUNT: 8

CPU_MHZ: f97

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10166.9 amd64fre

EXCEPTION_RECORD:  ffffe001c05fd880 -- (.exr 0xffffe001c05fd880)
ExceptionAddress: ffffe001c05fd888
   ExceptionCode: 00080006
  ExceptionFlags: 00000000
NumberParameters: 0

BAD_STACK_POINTER:  ffffd0010b8aea18

LAST_CONTROL_TRANSFER:  from fffff802102ce552 to fffff80210352ca0

STACK_TEXT:  
ffffd001`0b8aea18 fffff802`102ce552 : 00000000`000000c4 00000000`00000091 00000000`00000000 ffffe001`c05fd880 : nt!KeBugCheckEx
ffffd001`0b8aea20 fffff802`102caf61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpGetStackLimits+0xee
ffffd001`0b8aea60 fffff802`102cf45e : ffffd001`0b8af958 ffffd001`0b8af660 ffffd001`0b8af958 00000000`00000000 : nt!RtlDispatchException+0x61
ffffd001`0b8af130 fffff802`1035e8c2 : ffffe001`c05fd880 ffffd001`0b8af8c0 00000000`00000000 fffff802`102553a7 : nt!KiDispatchException+0x646
ffffd001`0b8af820 fffff802`1035d014 : 00000000`00000000 ffffe001`c29fa630 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd001`0b8afa00 fffff800`ed306d22 : ffffd001`0b8aff78 ffffd001`0b8b5000 00000000`00000000 fffff800`ed303991 : nt!KiPageFault+0x214
ffffd001`0b8afb90 ffffd001`0b8aff78 : ffffd001`0b8b5000 00000000`00000000 fffff800`ed303991 ffffe001`c29fa630 : aswVmm+0x9d22
ffffd001`0b8afb98 ffffd001`0b8b5000 : 00000000`00000000 fffff800`ed303991 ffffe001`c29fa630 ffffe001`c29fa630 : 0xffffd001`0b8aff78
ffffd001`0b8afba0 00000000`00000000 : fffff800`ed303991 ffffe001`c29fa630 ffffe001`c29fa630 00000000`00000004 : 0xffffd001`0b8b5000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswVmm+9d22
fffff800`ed306d22 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  aswVmm+9d22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswVmm

IMAGE_NAME:  aswVmm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55364d7c

BUCKET_ID_FUNC_OFFSET:  9d22

FAILURE_BUCKET_ID:  0xc4_91_STACKPTR_ERROR_aswVmm!Unknown_Function

BUCKET_ID:  0xc4_91_STACKPTR_ERROR_aswVmm!Unknown_Function

PRIMARY_PROBLEM_CLASS:  0xc4_91_STACKPTR_ERROR_aswVmm!Unknown_Function

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc4_91_stackptr_error_aswvmm!unknown_function

FAILURE_ID_HASH:  {27e85b3f-d8d2-7aac-e1af-a8af5f9d79da}

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


Free Windows Admin Tool Kit Click here and download it now
July 19th, 2015 7:34am

Thanks so much for taking the time to look at it. I will remove Avast and run it for a few days with the built in defender enabled. I will update in a few days with the result.

Thanks again

July 19th, 2015 8:54pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics