BSOD playing World Of Tanks/Sims 4

O

Omfgorz

New member
Local time
6:08 AM
Messages
14
I think it can be my PSU, because i hear the coil always. While moving my mouse its buzzing... And before BSOD it start BUZZ louder and then BOOM BSOD. Check this out, maybe you can tell me something. Thank you...

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


Code: 
Loading Dump File [C:\Users\Mini\Desktop\111815-12464-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03065000 PsLoadedModuleList = 0xfffff800`032ac730
Debug session time: Wed Nov 18 23:13:09.343 2015 (UTC + 2:00)
System Uptime: 0 days 0:59:43.061
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8013ea8010, 2, 1, fffff80003199626}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f )

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

4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003316100
GetUlongFromAddress: unable to read from fffff800033161c0
 fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

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

4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS:  fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

Followup: MachineOwner
---------
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Code: 
4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS:  fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

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

4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS:  fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

Followup: MachineOwner
---------
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Code: 
4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS:  fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

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

4: 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: fffffa8013ea8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80003199626, address which referenced memory

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


WRITE_ADDRESS:  fffffa8013ea8010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800c066eb0 -- (.trap 0xfffff8800c066eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800fea8010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003199626 rsp=fffff8800c067040 rbp=0000000020000000
 r8=fffff8800c067070  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03199626 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0fea8010=e33007feff3fffbf
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff880`0c066d68 fffff800`030d81e9 : 00000000`0000000a fffffa80`13ea8010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c066d70 fffff800`030d6e60 : fffffa80`11436120 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c066eb0 fffff800`03199626 : fffffa80`1216fc80 00000000`00000000 fffffa80`0f97f850 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c067040 fffff800`03143cd1 : 20000000`00000180 00000000`00000000 20000000`00000180 fffffa80`107bc000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0c0670c0 fffff800`033772af : fffffa80`11ebe990 fffff8a0`033af400 fffffa80`11ebe990 00000000`00180000 : nt! ?? ::FNODOBFM::`string'+0x2ac1d
fffff880`0c067190 fffff800`030e2504 : 00000000`00000000 fffff8a0`033af4b0 fffffa80`0d64f4f0 fffffa80`0d64f4f0 : nt!MiSegmentDelete+0x7b
fffff880`0c0671d0 fffff880`05591327 : fffff8a0`033af4b0 fffff8a0`032d1010 00000000`00000000 fffff8a0`033af4b0 : nt!ObfDereferenceObject+0xd4
fffff880`0c067230 fffff880`055907b8 : fffff8a0`032e00e0 fffff8a0`032e00e0 fffff8a0`034900d0 fffff8a0`0a9ac750 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x2f
fffff880`0c067260 fffff880`055906c6 : fffffa80`00000000 fffffa80`11275b10 fffffa80`1135d340 fffffa80`107b5c20 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`0c067290 fffff880`0557bc93 : fffff880`0c0672b8 fffff8a0`03fd60d0 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0c0672c0 fffff880`05576637 : fffffa80`1216fc80 00000000`00000000 fffff8a0`033af4b0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0c067370 fffff880`0555cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c067440 fffff880`0549dccc : 00000000`00000000 fffff8a0`0a6b4000 fffff8a0`0a6b4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c067470 fffff880`054b08b8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c067560 fffff880`05495815 : 00000000`fffffeda fffff8a0`09d9f960 fffff8a0`0a6b4000 fffffa80`107ae000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0c0675d0 fffff880`054d3fee : 00000000`00000001 fffffa80`107ae000 fffff8a0`09d9f960 fffff8a0`09d9f9e0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0c067600 fffff880`054d3984 : fffff900`c63f1cd0 00000000`00000000 00000000`00000001 fffff900`c63f1cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0c0676b0 fffff960`000f7db4 : 00000000`00001290 fffff900`c63f1cd0 00000000`00000000 fffff900`c63f1cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0c067740 fffff960`000f74a7 : 00000000`00000000 fffff880`0c067ae0 fffffa80`11436060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`0c0677c0 fffff800`033aea97 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`11436000 : win32k!W32pProcessCallout+0x6b
fffff880`0c0677f0 fffff800`03393b5d : 00000000`c000001d 00000000`c0000001 fffffa80`78457300 fffffa80`0f77e060 : nt!PspExitThread+0x4cb
fffff880`0c0678f0 fffff800`030cbf1a : 00000000`00000100 fffffa80`11436120 00000000`00000001 fffff800`030ddcad : nt!PsExitSpecialApc+0x1d
fffff880`0c067920 fffff800`030cc260 : 00000000`00000246 fffff880`0c0679a0 fffff800`03393ad0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c0679a0 fffff800`030d7f77 : fffffa80`11436060 00000000`00000304 00000000`00000000 fffffa80`10858d90 : nt!KiInitiateUserApc+0x70
fffff880`0c067ae0 00000000`74752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`063ff028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74752e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f
fffff880`05591327 eb22            jmp     dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53 (fffff880`0559134b)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+2f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmm_process_heap::freeblock+2f

FAILURE_ID_HASH:  {74216d2d-b1af-0739-0f35-d93dfb479770}

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


ANYONE CAN TELL ME WHAT IS WITH MY COMPUTER???? PSU OR DDR4 ??? OR DRIVERS?? PLEASE
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Please someone :(
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Please someon tell me, Completely reinstalled graphic card drivers , restored default bios, all drivers up to dave. What's the problem... Tell me someon who's PRO at this issues....
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
I got new BSOD... Please someon tell me any options..



MEMTEST PASSED 2 HOUR EASY.

MEMTEST2_H.jpg
[/url]
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
Ooh I get it, thank you very much. I don't have experience in this forum sorry !.
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Axe0 ????????? PLEASE HELP lol 4 days no one ... wth is this forum FOR ? :)
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
I can't help while asleep.

This is an open forum, keep in mind that we are in different time zones!
 
Last edited:

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
Daemon tools uses drivers that are known for causing bluescreen in Windows 7.
I recommend to remove Daemon tools to improve system stability.

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.



Diagnostic test

 GPU TEST


arrow.png
Run Furmark to test your GPU. Furmark tutorial

   Note
Run Furmark for around 30 minutes


   Warning
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high


Code: 
BugCheck 1A, {41284, fffff8800a797001, f76, fffff78000001000}

Probably caused by : [COLOR="Red"]dxgmms1[/COLOR].sys ( dxgmms1![COLOR="red"]VIDMM_GLOBAL[/COLOR]::DestroyOneAllocation+156 )
 

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
axe0 said:
i can't help while asleep.

This is an open forum, keep in kind that we are in different time zones!
Click to expand...

ok trying :d
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
OK so I did what you told me to do. Test passed, driver didn't crashed, pc was stable all the time. Any other options ?
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Make sure the gpu is properly seated and no dust is anywhere in the case.
If you're overclocking your gpu, revert back to stock!
 

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
Its stock. GPU is seated propertly. Gona play the game and wait for the BSOD appear. Maybe its repaired... Cuz ram is good,GPU is good, everything is up to date.. Well going to test it now on the game, be right back :D
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Heey Im back :D Got 2 BSOD's after all tests and drivers reinstalls... lol check this out :
1st :
2nd: (after 15-20minutes of playing The Sims4):

Attaching Both DMP's and PC info... Please help someon I don't know what to do...
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
If you're overclocking anything, revert back to stock while troubleshooting.
Code: 
CPUID:        "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: [COLOR="Red"]4008[/COLOR]

Unfortunately the dump isn't loading properly and I do not have the time for a standard procedure that might resolve the loading problem for the dump, it is the reason why my suggestion is based on usual causes for the crash 0x1E(KMODE_EXCEPTION_NOT_HANDLED) and a little debugging experience with this crash.



Diagnostic Test

 RAM TEST


arrow.png
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note
picture.php


MemTest86+ needs to be run for at least 8 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.
 

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
All 4 ram stick passed 8/8 but when I tested ram one by one and find out that one ram stick was faulty. SO If you get this error and none help = RAM FAULT 100%
 

My Computer My Computer

At a glance

Windows 7 Professional x64Intel i7 6700kCorsair Vengeance DDR4 DRAM 2133MHz C13 CMK16...MSI GTX 970 GAMING 4G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Professional x64
CPU
Intel i7 6700k
Motherboard
MSI B150 GAMING M3
Memory
Corsair Vengeance DDR4 DRAM 2133MHz C13 CMK16GX4M4A2133C13B
Graphics Card(s)
MSI GTX 970 GAMING 4G
Monitor(s) Displays
1
Screen Resolution
1920x1080
Hard Drives
Samsung SSD 850 EVO 120GB
PSU
Corsair CX 750W
Internet Speed
100Mbps
Antivirus
Norton Antivirus
Browser
Google Chrome
Omfgorz said:
All 4 ram stick passed 8/8 but when I tested ram one by one and find out that one ram stick was faulty. SO If you get this error and none help = RAM FAULT 100%
Click to expand...

There are with this crash more things to consider as a possible cause then just the memory.

Hope you don't get anymore crashes :)
 

My Computer My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
You must log in or register to reply here.

Similar threads

BSOD playing World of Warcraft
Replies
2
Views
1K
axe0
A
BSOD playing World of Warcarft, error 0x00000116
Replies
2
Views
965
axe0
A
Solved BSOD Playing Paladins, World of Tanks, error 0x000000d1
Replies
4
Views
2K
torchwood
torchwood
BSoD playing world of warcraft, error 0x000000EA
Replies
1
Views
2K
axe0
A
BSOD When Playing Game (World Of Tanks)
Replies
1
Views
1K
axe0
A
Back
Top