Blue Screen when playing videos and games

Hi, this is my first time to post a question so please let me know if there is a format that I need to follow or information I need to add.

As the title says, I am experiencing annoying BSOD everytime I play videos in YT or playing games(low graphics games).  I tried to research and used WinDbg to read the minidump.  Can you please help me?  This drives me crazy.

Let me know if I need to provide my PC specs

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffd000206f8242, 2, 0, fffff800552a6028}

Probably caused by : win32k.sys ( win32k!EnterCritAvoidingDitHitTestHazard+13 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffd000206f8242, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800552a6028, address which referenced memory

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


READ_ADDRESS: fffff800554b3340: Unable to get special pool info
fffff800554b3340: Unable to get special pool info
GetUlongFromAddress: unable to read from fffff8005554e208
 ffffd000206f8242 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSearchForNewThread+178
fffff800`552a6028 f6410204        test    byte ptr [rcx+2],4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  ffffd00023eda5a0 -- (.trap 0xffffd00023eda5a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=ffffd000206f8240
rdx=fffff800554a0100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800552a6028 rsp=ffffd00023eda730 rbp=ffffd00023eda780
 r8=0000000000007a5d  r9=0000000000000091 r10=fffff80055201000
r11=fffff780000003b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiSearchForNewThread+0x178:
fffff800`552a6028 f6410204        test    byte ptr [rcx+2],4 ds:ffffd000`206f8242=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8005535a7e9 to fffff8005534eca0

STACK_TEXT:  
ffffd000`23eda458 fffff800`5535a7e9 : 00000000`0000000a ffffd000`206f8242 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23eda460 fffff800`5535903a : 00000000`00000000 ffffd000`206ac180 ffffe000`0569c000 ffffd000`23eda5a0 : nt!KiBugCheckDispatch+0x69
ffffd000`23eda5a0 fffff800`552a6028 : 00000001`00000005 ffffe000`000000fe ffffcbc0`b244ee65 001f0003`00000000 : nt!KiPageFault+0x23a
ffffd000`23eda730 fffff800`552a5892 : ffffd000`206ac180 ffffe000`04e09340 fffff800`fffffffe 00000000`fffffffe : nt!KiSearchForNewThread+0x178
ffffd000`23eda7c0 fffff800`552a53a7 : ffffe000`04e09340 ffffe000`014ce3f0 ffffd000`201e0180 00000000`00000000 : nt!KiSwapThread+0xd2
ffffd000`23eda860 fffff800`552a2af2 : ffffe000`02fe6b60 00000000`00000001 00000000`00000091 00000000`00000000 : nt!KiCommitThreadWait+0x127
ffffd000`23eda8c0 fffff800`5527399d : ffffe000`0277ec30 ffffe000`027859f0 00000000`7759c000 00000000`00000002 : nt!ExpWaitForResource+0x282
ffffd000`23eda980 fffff960`001b9443 : ffffe000`04e09302 ffffe000`04e09340 ffffd000`23edab00 00000000`7759c000 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x1ad
ffffd000`23edaa10 fffff960`000f3a89 : 00000000`0000002e 00000000`0000000a 00000000`00b90894 fffff800`55353e45 : win32k!EnterCritAvoidingDitHitTestHazard+0x13
ffffd000`23edaa50 fffff800`5535a4b3 : ffffe000`04e09340 00000000`000012f4 00000000`7759a130 00000000`00cfee20 : win32k!NtUserCallNoParam+0x11
ffffd000`23edaa80 00000000`775a5a1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bfdeb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775a5a1a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EnterCritAvoidingDitHitTestHazard+13
fffff960`001b9443 488bd8          mov     rbx,rax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  win32k!EnterCritAvoidingDitHitTestHazard+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f9930a

BUCKET_ID_FUNC_OFFSET:  13

FAILURE_BUCKET_ID:  AV_win32k!EnterCritAvoidingDitHitTestHazard

BUCKET_ID:  AV_win32k!EnterCritAvoidingDitHitTestHazard

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

August 12th, 2015 11:42pm

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 12:04am

Hi,  I tried Driver verifier and encountered BSOD during startup.  Can you please explain this dump?:

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff802`1160a000 PsLoadedModuleList = 0xfffff802`118d42d0
Debug session time: Thu Aug 13 12:37:29.643 2015 (UTC - 7:00)
System Uptime: 0 days 0:00:39.413
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {122, 2, ffffe000ddabb060, ffffd000227a73f8}

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

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

1: 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: 0000000000000122, Waiting at DISPATCH_LEVEL, with a timeout different than zero.
Arg2: 0000000000000002, IRQL value.
Arg3: ffffe000ddabb060, Object to wait on.
Arg4: ffffd000227a73f8, Address of the time out value.

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


BUGCHECK_STR:  0xc4_122

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80211c7f6b0 to fffff8021175dfa0

STACK_TEXT:  
ffffd000`227a72f8 fffff802`11c7f6b0 : 00000000`000000c4 00000000`00000122 00000000`00000002 ffffe000`ddabb060 : nt!KeBugCheckEx
ffffd000`227a7300 fffff802`11c86e79 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`227a7340 fffff801`122e3f8f : ffffe000`ddabb060 fffff801`00000000 ffffcf81`9b286fb0 00000000`00000008 : nt!VerifierKeWaitForSingleObject+0xa5
ffffd000`227a73c0 ffffe000`ddabb060 : fffff801`00000000 ffffcf81`9b286fb0 00000000`00000008 ffffd000`227a73f8 : athuwbx+0x1f8f
ffffd000`227a73c8 fffff801`00000000 : ffffcf81`9b286fb0 00000000`00000008 ffffd000`227a73f8 00000000`00000000 : 0xffffe000`ddabb060
ffffd000`227a73d0 ffffcf81`9b286fb0 : 00000000`00000008 ffffd000`227a73f8 00000000`00000000 00000000`00000000 : 0xfffff801`00000000
ffffd000`227a73d8 00000000`00000008 : ffffd000`227a73f8 00000000`00000000 00000000`00000000 ffffffff`fd050f80 : 0xffffcf81`9b286fb0
ffffd000`227a73e0 ffffd000`227a73f8 : 00000000`00000000 00000000`00000000 ffffffff`fd050f80 00000000`00000000 : 0x8
ffffd000`227a73e8 00000000`00000000 : 00000000`00000000 ffffffff`fd050f80 00000000`00000000 fffff801`122e7603 : 0xffffd000`227a73f8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athuwbx+1f8f
fffff801`122e3f8f ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athuwbx+1f8f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athuwbx

IMAGE_NAME:  athuwbx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  528c2ff5

FAILURE_BUCKET_ID:  0xc4_122_VRF_athuwbx+1f8f

BUCKET_ID:  0xc4_122_VRF_athuwbx+1f8f

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


August 13th, 2015 1:00am

1. I would start here
https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

2. For analysis there is nice blog (older but useful)
http://blogs.technet.com/b/marcelofartura/archive/2008/06/25/kernel-mode.aspx

3. Sometimes "history" may give some useful data. Have you used drivers from computer vendor (chipset, other device drivers,...). I does not hurt to address vendor support/forum (chances are that there is typical error for particular model)

4. In addition to minidump analysis look into Event Logs and Device Manager.

Regards
Milos

Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 1:31am

The above crash was related to your athuwbx.sys driver.  This is your Atheros lan driver.

Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

August 13th, 2015 7:19am

Reinstalled the athuwbx.sys and re-ran the Verifier.  Is this something related to bios?  I think I have the updated bios:

Use !analyze -v to get detailed debugging information.

BugCheck C4, {122, 2, ffffe001c857b060, ffffd00064da73e8}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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: 0000000000000122, Waiting at DISPATCH_LEVEL, with a timeout different than zero.
Arg2: 0000000000000002, IRQL value.
Arg3: ffffe001c857b060, Object to wait on.
Arg4: ffffd00064da73e8, Address of the time out value.

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


BUGCHECK_STR:  0xc4_122

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff803e570b6b0 to fffff803e51d99a0

STACK_TEXT:  
ffffd000`64da72e8 fffff803`e570b6b0 : 00000000`000000c4 00000000`00000122 00000000`00000002 ffffe001`c857b060 : nt!KeBugCheckEx
ffffd000`64da72f0 fffff803`e5712e79 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`64da7330 fffff801`b02ccf8f : ffffe001`c857b060 fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 : nt!VerifierKeWaitForSingleObject+0xa5
ffffd000`64da73b0 ffffe001`c857b060 : fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 : 0xfffff801`b02ccf8f
ffffd000`64da73b8 fffff801`00000000 : ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 00000000`00000000 : 0xffffe001`c857b060
ffffd000`64da73c0 ffffcf80`4bb3afb0 : 00000000`00000008 ffffd000`64da73e8 00000000`00000000 00000000`00000000 : 0xfffff801`00000000
ffffd000`64da73c8 00000000`00000008 : ffffd000`64da73e8 00000000`00000000 00000000`00000000 ffffffff`fd050f80 : 0xffffcf80`4bb3afb0
ffffd000`64da73d0 ffffd000`64da73e8 : 00000000`00000000 00000000`00000000 ffffffff`fd050f80 00000000`00000000 : 0x8
ffffd000`64da73d8 00000000`00000000 : 00000000`00000000 ffffffff`fd050f80 00000000`00000000 fffff801`b02d0603 : 0xffffd000`64da73e8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff803`e570b6b0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55a68c66

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

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



  • Edited by OlieAbe 5 hours 30 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 9:54pm

watched YT today and got another BSOD:

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

Followup: MachineOwner

August 13th, 2015 11:22pm

Reinstalled the athuwbx.sys and re-ran the Verifier.  Is this something related to bios?  I think I have the updated bios:

Use !analyze -v to get detailed debugging information.

BugCheck C4, {122, 2, ffffe001c857b060, ffffd00064da73e8}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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: 0000000000000122, Waiting at DISPATCH_LEVEL, with a timeout different than zero.
Arg2: 0000000000000002, IRQL value.
Arg3: ffffe001c857b060, Object to wait on.
Arg4: ffffd00064da73e8, Address of the time out value.

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


BUGCHECK_STR:  0xc4_122

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff803e570b6b0 to fffff803e51d99a0

STACK_TEXT:  
ffffd000`64da72e8 fffff803`e570b6b0 : 00000000`000000c4 00000000`00000122 00000000`00000002 ffffe001`c857b060 : nt!KeBugCheckEx
ffffd000`64da72f0 fffff803`e5712e79 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`64da7330 fffff801`b02ccf8f : ffffe001`c857b060 fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 : nt!VerifierKeWaitForSingleObject+0xa5
ffffd000`64da73b0 ffffe001`c857b060 : fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 : 0xfffff801`b02ccf8f
ffffd000`64da73b8 fffff801`00000000 : ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 00000000`00000000 : 0xffffe001`c857b060
ffffd000`64da73c0 ffffcf80`4bb3afb0 : 00000000`00000008 ffffd000`64da73e8 00000000`00000000 00000000`00000000 : 0xfffff801`00000000
ffffd000`64da73c8 00000000`00000008 : ffffd000`64da73e8 00000000`00000000 00000000`00000000 ffffffff`fd050f80 : 0xffffcf80`4bb3afb0
ffffd000`64da73d0 ffffd000`64da73e8 : 00000000`00000000 00000000`00000000 ffffffff`fd050f80 00000000`00000000 : 0x8
ffffd000`64da73d8 00000000`00000000 : 00000000`00000000 ffffffff`fd050f80 00000000`00000000 fffff801`b02d0603 : 0xffffd000`64da73e8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff803`e570b6b0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55a68c66

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

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



  • Edited by OlieAbe Friday, August 14, 2015 1:53 AM
Free Windows Admin Tool Kit Click here and download it now
August 14th, 2015 1:52am

Reinstalled the athuwbx.sys and re-ran the Verifier.  Is this something related to bios?  I think I have the updated bios:

Use !analyze -v to get detailed debugging information.

BugCheck C4, {122, 2, ffffe001c857b060, ffffd00064da73e8}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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: 0000000000000122, Waiting at DISPATCH_LEVEL, with a timeout different than zero.
Arg2: 0000000000000002, IRQL value.
Arg3: ffffe001c857b060, Object to wait on.
Arg4: ffffd00064da73e8, Address of the time out value.

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


BUGCHECK_STR:  0xc4_122

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff803e570b6b0 to fffff803e51d99a0

STACK_TEXT:  
ffffd000`64da72e8 fffff803`e570b6b0 : 00000000`000000c4 00000000`00000122 00000000`00000002 ffffe001`c857b060 : nt!KeBugCheckEx
ffffd000`64da72f0 fffff803`e5712e79 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`64da7330 fffff801`b02ccf8f : ffffe001`c857b060 fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 : nt!VerifierKeWaitForSingleObject+0xa5
ffffd000`64da73b0 ffffe001`c857b060 : fffff801`00000000 ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 : 0xfffff801`b02ccf8f
ffffd000`64da73b8 fffff801`00000000 : ffffcf80`4bb3afb0 00000000`00000008 ffffd000`64da73e8 00000000`00000000 : 0xffffe001`c857b060
ffffd000`64da73c0 ffffcf80`4bb3afb0 : 00000000`00000008 ffffd000`64da73e8 00000000`00000000 00000000`00000000 : 0xfffff801`00000000
ffffd000`64da73c8 00000000`00000008 : ffffd000`64da73e8 00000000`00000000 00000000`00000000 ffffffff`fd050f80 : 0xffffcf80`4bb3afb0
ffffd000`64da73d0 ffffd000`64da73e8 : 00000000`00000000 00000000`00000000 ffffffff`fd050f80 00000000`00000000 : 0x8
ffffd000`64da73d8 00000000`00000000 : 00000000`00000000 ffffffff`fd050f80 00000000`00000000 fffff801`b02d0603 : 0xffffd000`64da73e8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff803`e570b6b0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55a68c66

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

BUCKET_ID:  0xc4_122_VRF_nt!VerifierBugCheckIfAppropriate

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



  • Edited by OlieAbe Friday, August 14, 2015 1:53 AM
August 14th, 2015 1:52am

In the verified DMP it cannot be ntkrnlmp.exe so it is a false positive.  In the above it pointed to the video driver.  I would remove completely the current video driver and install the newest available driver..  Given the differing apparent causes I would also run a malwarebytes scan just to eliminate the possibility and run a system file check

Please download the free version of Malwarebytes. Update it immediately.
Do a full system scan
Let us know the results at the end.

http://www.malwarebytes.org/products


Please run a system file check (SFC) & DISM (if necessary) if you are on win 8 or higher
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

Free Windows Admin Tool Kit Click here and download it now
August 14th, 2015 7:17am

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

Other recent topics Other recent topics