Jump to content

BSODs suddenly

Janne
By Janne
in Troubleshooting
 Share
Posted

These blue screens started to appear 2 days ago and i can't remember any noteworthy changes i made to my computer. I think the only thing i installed was Discord. Happened 4 times so far. Detailed information is inside the spoilers.

Please tell if you need some specific information

 

Spoiler


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


Loading Dump File [A:\Windows\Minidump\061016-38688-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
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.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`03066730
Debug session time: Fri Jun 10 23:35:01.486 2016 (UTC + 3:00)
System Uptime: 0 days 9:30:50.298
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 3B, {c0000005, fffff80002fca617, fffff8800d662d60, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fca617, Address of the instruction which caused the bugcheck
Arg3: fffff8800d662d60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.18939.amd64fre.win7sp1_gdr.150722-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1204

BIOS_DATE:  06/20/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z97-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80002fca617

BUGCHECK_P3: fffff8800d662d60

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`02fca617 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffff8800d662d60 -- (.cxr 0xfffff8800d662d60)
rax=ffeafa850b744807 rbx=fffff800030277e0 rcx=fffffa8006f69dd0
rdx=0000000000000000 rsi=0000000000000013 rdi=0000000000000000
rip=fffff80002fca617 rsp=fffff8800d663740 rbp=0000000000001000
 r8=0000000000000000  r9=fffff800030277e0 r10=fffff80003027588
r11=00000000ff010000 r12=fffff80003027580 r13=0000000000000000
r14=0000000000000000 r15=000000004d52564e
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExAllocatePoolWithTag+0x537:
fffff800`02fca617 48895808        mov     qword ptr [rax+8],rbx ds:002b:ffeafa85`0b74480f=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Overwatch.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  JANNE-PC

ANALYSIS_SESSION_TIME:  06-12-2016 21:56:48.0637

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fca617

STACK_TEXT:  
fffff880`0d663740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537


THREAD_SHA1_HASH_MOD_FUNC:  2d1ce9986fb00d4828089bfd7bd0aeb5d5e49129

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e96ed2d6c441710e376b7c4d60712ad98b63259a

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`02fca617 48895808        mov     qword ptr [rax+8],rbx

FAULT_INSTR_CODE:  8588948

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+537

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55afca65

IMAGE_VERSION:  6.1.7601.18939

STACK_COMMAND:  .cxr 0xfffff8800d662d60 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+537

BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+537

PRIMARY_PROBLEM_CLASS:  X64_0x3B_nt!ExAllocatePoolWithTag+537

TARGET_TIME:  2016-06-10T20:35:01.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-07-22 19:52:53

BUILDDATESTAMP_STR:  150722-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.18939.amd64fre.win7sp1_gdr.150722-0600

ANALYSIS_SESSION_ELAPSED_TIME: 279

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nt!exallocatepoolwithtag+537

FAILURE_ID_HASH:  {f4ecfd04-3da8-a3e2-945f-a8ef896951ac}

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

Spoiler


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


Loading Dump File [A:\Windows\Minidump\061116-31278-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
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.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03093730
Debug session time: Sat Jun 11 19:52:54.682 2016 (UTC + 3:00)
System Uptime: 0 days 4:28:11.494
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 1000007E, {ffffffffc0000005, fffff8800f020e26, fffff88004b88568, fffff88004b87dc0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f020e26, The address that the exception occurred at
Arg3: fffff88004b88568, Exception Record Address
Arg4: fffff88004b87dc0, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.18939.amd64fre.win7sp1_gdr.150722-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1204

BIOS_DATE:  06/20/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z97-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8800f020e26

BUGCHECK_P3: fffff88004b88568

BUGCHECK_P4: fffff88004b87dc0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`0f020e26 488b18          mov     rbx,qword ptr [rax]

EXCEPTION_RECORD:  fffff88004b88568 -- (.exr 0xfffff88004b88568)
ExceptionAddress: fffff8800f020e26 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004b87dc0 -- (.cxr 0xfffff88004b87dc0)
rax=0009f8ac03f5046c rbx=0000000000000000 rcx=fffffa800b363000
rdx=fffffa800be13c30 rsi=fffffa80515ca8d8 rdi=fffffa800b363000
rip=fffff8800f020e26 rsp=fffff88004b887a0 rbp=fffffa80084aba90
 r8=fffffa800c0b4301  r9=0000000000000000 r10=0000000000000000
r11=0000000000000174 r12=0000000000000059 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22:
fffff880`0f020e26 488b18          mov     rbx,qword ptr [rax] ds:002b:0009f8ac`03f5046c=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100
Unable to get MmSystemRangeStart
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`0f020e26 488b18          mov     rbx,qword ptr [rax]

BUGCHECK_STR:  0x7E

ANALYSIS_SESSION_HOST:  JANNE-PC

ANALYSIS_SESSION_TIME:  06-12-2016 21:58:19.0428

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8800f01dff7 to fffff8800f020e26

STACK_TEXT:  
fffff880`04b887a0 fffff880`0f01dff7 : 00000000`00000000 fffffa80`515ca8d8 00000000`00000059 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`04b887d0 fffff880`0f0387d9 : 00000000`00000000 fffff8a0`030d93a0 fffffa80`00000000 fffffa80`0c0b4330 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`04b889a0 fffff880`0f038514 : fffff800`00b94080 fffff880`0f037f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04b88b90 fffff880`0f038012 : 00000000`00000000 fffffa80`07aa0950 00000000`00000080 fffffa80`08b56010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04b88bc0 fffff800`031588e2 : 00000000`015b52ae fffffa80`09aa1610 fffffa80`06cd89c0 fffffa80`09aa1610 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04b88c00 fffff800`02eb0f46 : fffff800`0303fe80 fffffa80`09aa1610 fffff800`0304dcc0 fffffa80`0a72bc10 : nt!PspSystemThreadStartup+0x5a
fffff880`04b88c40 00000000`00000000 : fffff880`04b89000 fffff880`04b83000 fffff880`04b88540 00000000`00000000 : nt!KxStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  feb35ab5dc99a86233227d3cd5946c4850a4d508

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c8f7dc25f8907fb6b1b46ad4ba5ffce855ba3de1

THREAD_SHA1_HASH_MOD:  715ea47f0e0475afca9183e1e7654934d827faef

FAULT_INSTR_CODE:  4c188b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

STACK_COMMAND:  .cxr 0xfffff88004b87dc0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

PRIMARY_PROBLEM_CLASS:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

TARGET_TIME:  2016-06-11T16:52:54.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-07-22 19:52:53

BUILDDATESTAMP_STR:  150722-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.18939.amd64fre.win7sp1_gdr.150722-0600

ANALYSIS_SESSION_ELAPSED_TIME: 276

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_dxgmms1!vidmm_global::referenceallocationforpreparation+22

FAILURE_ID_HASH:  {9c6d3490-4300-aa41-eb60-5cde2841a334}

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

Spoiler


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


Loading Dump File [A:\Windows\Minidump\061216-20217-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
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.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03056730
Debug session time: Sun Jun 12 21:43:44.384 2016 (UTC + 3:00)
System Uptime: 0 days 7:03:59.197
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 3B, {c0000005, fffff80002e6fb7a, fffff8800bbcf000, 0}

Probably caused by : ntkrnlmp.exe ( nt!NtFreeVirtualMemory+765 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e6fb7a, Address of the instruction which caused the bugcheck
Arg3: fffff8800bbcf000, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.18939.amd64fre.win7sp1_gdr.150722-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1204

BIOS_DATE:  06/20/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z97-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80002e6fb7a

BUGCHECK_P3: fffff8800bbcf000

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!NtFreeVirtualMemory+765
fffff800`02e6fb7a 488b4910        mov     rcx,qword ptr [rcx+10h]

CONTEXT:  fffff8800bbcf000 -- (.cxr 0xfffff8800bbcf000)
rax=fffffa80079ebfc0 rbx=fffffa800b0631d0 rcx=fffcfffbfffcfffb
rdx=00000000a7b80000 rsi=00000000a7b80000 rdi=0000000000000000
rip=fffff80002e6fb7a rsp=fffff8800bbcf9e0 rbp=fffff8800bbcfb60
 r8=00000000000a7b88  r9=fffffa800a6f0060 r10=0000000000008000
r11=0000000000008000 r12=fffffa800b0631d0 r13=fffffa800a566b50
r14=00000000a7b7ffff r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!NtFreeVirtualMemory+0x765:
fffff800`02e6fb7a 488b4910        mov     rcx,qword ptr [rcx+10h] ds:002b:fffcfffb`fffd000b=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Overwatch.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  JANNE-PC

ANALYSIS_SESSION_TIME:  06-12-2016 21:59:45.0354

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002e81853 to fffff80002e6fb7a

STACK_TEXT:  
fffff880`0bbcf9e0 fffff800`02e81853 : ffffffff`ffffffff 00000000`0014e808 00000000`0014e800 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x765
fffff880`0bbcfae0 00000000`772ddb9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014e7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772ddb9a


THREAD_SHA1_HASH_MOD_FUNC:  f8740de9ebe76503297ab7484f3ff76764616cce

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  78f6d01d83b397fe009bb0e9d9c06b645dd379e6

THREAD_SHA1_HASH_MOD:  6997106dce080e0f247cffc7d244723501c73d61

FOLLOWUP_IP: 
nt!NtFreeVirtualMemory+765
fffff800`02e6fb7a 488b4910        mov     rcx,qword ptr [rcx+10h]

FAULT_INSTR_CODE:  10498b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!NtFreeVirtualMemory+765

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55afca65

IMAGE_VERSION:  6.1.7601.18939

STACK_COMMAND:  .cxr 0xfffff8800bbcf000 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!NtFreeVirtualMemory+765

BUCKET_ID:  X64_0x3B_nt!NtFreeVirtualMemory+765

PRIMARY_PROBLEM_CLASS:  X64_0x3B_nt!NtFreeVirtualMemory+765

TARGET_TIME:  2016-06-12T18:43:44.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-07-22 19:52:53

BUILDDATESTAMP_STR:  150722-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.18939.amd64fre.win7sp1_gdr.150722-0600

ANALYSIS_SESSION_ELAPSED_TIME: 27e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nt!ntfreevirtualmemory+765

FAILURE_ID_HASH:  {d29382bd-d018-51af-e97e-91965c4c7ea8}

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

Spoiler


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


Loading Dump File [A:\Windows\Minidump\061216-34289-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
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.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03053730
Debug session time: Sun Jun 12 00:50:25.953 2016 (UTC + 3:00)
System Uptime: 0 days 4:56:48.765
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 19, {3, fffff80003014a90, fffff80003014a90, ffd3f7da02d54a6b}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Followup:     Pool_corruption
---------

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff80003014a90, the pool entry being checked.
Arg3: fffff80003014a90, the read back flink freelist value (should be the same as 2).
Arg4: ffd3f7da02d54a6b, the read back blink freelist value (should be the same as 2).

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.18939.amd64fre.win7sp1_gdr.150722-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1204

BIOS_DATE:  06/20/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z97-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: fffff80003014a90

BUGCHECK_P3: fffff80003014a90

BUGCHECK_P4: ffd3f7da02d54a6b

BUGCHECK_STR:  0x19_3

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  opera.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  JANNE-PC

ANALYSIS_SESSION_TIME:  06-12-2016 22:00:43.0457

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

DEVICE_OBJECT: fffffa80538864a8

LAST_CONTROL_TRANSFER:  from fffff80002fb64b3 to fffff80002e7f5c0

STACK_TEXT:  
fffff880`0e3d8658 fffff800`02fb64b3 : 00000000`00000019 00000000`00000003 fffff800`03014a90 fffff800`03014a90 : nt!KeBugCheckEx
fffff880`0e3d8660 fffff800`02e935c6 : 00000000`00000000 00000000`00000108 fffffa80`0a7cf860 00000000`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`0e3d8750 fffff880`0182dd1c : 00000000`00000398 00000000`00000000 fffffa80`53886390 fffff800`03169e6a : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0e3d87a0 fffff880`0183248d : fffff880`0e3d88e0 fffff8a0`0d7fd8c8 00000000`11c83048 00000000`00000001 : Npfs!NpAddDataQueueEntry+0x184
fffff880`0e3d8800 fffff880`01832151 : fffffa80`53886460 00000000`11c83048 00000000`0ec33ce8 fffffa80`0a644060 : Npfs!NpCommonWrite+0x225
fffff880`0e3d8890 fffff800`031886db : 00000000`00000001 fffff800`02e911f1 fffffa80`07a89d00 00000000`00000398 : Npfs!NpFsdWrite+0x5d
fffff880`0e3d8900 fffff800`03194103 : fffffa80`538864a8 00000000`00000000 fffffa80`15fceda0 fffff880`02f65180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0e3d8970 fffff800`02e7e853 : fffffa80`0a644001 00000000`00000000 00000000`00000001 00000000`0ec33d08 : nt!NtWriteFile+0x7e2
fffff880`0e3d8a70 00000000`74bb2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d8efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bb2e09


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  e49412439dd7f5f6061df95f3b2aa644293de419

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a80889a97c58455eb13745dd39bfe888121d5114

THREAD_SHA1_HASH_MOD:  f5d3bc7424056087a7361fd18e1394e7a9bfbc33

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`02fb64b3 cc              int     3

FAULT_INSTR_CODE:  d634ccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18939

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

PRIMARY_PROBLEM_CLASS:  X64_0x19_3_nt!ExDeferredFreePool+a53

TARGET_TIME:  2016-06-11T21:50:25.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-07-22 19:52:53

BUILDDATESTAMP_STR:  150722-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.18939.amd64fre.win7sp1_gdr.150722-0600

ANALYSIS_SESSION_ELAPSED_TIME: 27c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x19_3_nt!exdeferredfreepool+a53

FAILURE_ID_HASH:  {dfbdc8e1-ed53-6f10-9f53-216c75bb0283}

Followup:     Pool_corruption
---------

 

Link to comment
https://linustechtips.com/topic/610245-bsods-suddenly/
Share on other sites
Link to post
Share on other sites
Posted
8 minutes ago, Janne said:

The first thing I'll recommend is open a command prompt as administrator, then type 

sfc /scannow

Press enter and wait for the system file checker to identify any bad system files. If it detected and fixed a file, you're good

We have a NEW and GLORIOUSER-ER-ER PSU Tier List Now. (dammit @LukeSavenije stop coming up with new ones)

You can check out the old one that gave joy to so many across the land here

 

Computer having a hard time powering on? Troubleshoot it with this guide. (Currently looking for suggestions to update it into the context of <current year> and make it its own thread)

Computer Specs:

Spoiler

Mathresolvermajig: Intel Xeon E3 1240 (Sandy Bridge i7 equivalent)

Chillinmachine: Noctua NH-C14S
Framepainting-inator: EVGA GTX 1080 Ti SC2 Hybrid

Attachcorethingy: Gigabyte H61M-S2V-B3

Infoholdstick: Corsair 2x4GB DDR3 1333

Computerarmor: Silverstone RL06 "Lookalike"

Rememberdoogle: 1TB HDD + 120GB TR150 + 240 SSD Plus + 1TB MX500

AdditionalPylons: Phanteks AMP! 550W (based on Seasonic GX-550)

Letterpad: Rosewill Apollo 9100 (Cherry MX Red)

Buttonrodent: Razer Viper Mini + Huion H430P drawing Tablet

Auralnterface: Sennheiser HD 6xx

Liquidrectangles: LG 27UK850-W 4K HDR

 

Link to comment
https://linustechtips.com/topic/610245-bsods-suddenly/#findComment-7892767
Share on other sites
Link to post
Share on other sites
Posted
  • Author
3 minutes ago, Energycore said:

The first thing I'll recommend is open a command prompt as administrator, then type 


sfc /scannow

Press enter and wait for the system file checker to identify any bad system files. If it detected and fixed a file, you're good

Windows Resource Protection did not find any integrity violations. 

:S

 

Could it be hardware related? I have no idea how to read those dump files

Link to comment
https://linustechtips.com/topic/610245-bsods-suddenly/#findComment-7892784
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, Janne said:

Windows Resource Protection did not find any integrity violations. 

:S

 

Could it be hardware related? I have no idea how to read those dump files

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

 

These two are probably useful snippets of info.

 

Google the program name (something like "ntkrnlmp.exe bsod") and see what you can find. Perhaps it's a hardware issue - the exception code reads "the instruction referenced this bit of memory but it wasn't there". Sounds like a RAM issue. Did your BSODs say "MEMORY_MANAGEMENT"?

We have a NEW and GLORIOUSER-ER-ER PSU Tier List Now. (dammit @LukeSavenije stop coming up with new ones)

You can check out the old one that gave joy to so many across the land here

 

Computer having a hard time powering on? Troubleshoot it with this guide. (Currently looking for suggestions to update it into the context of <current year> and make it its own thread)

Computer Specs:

Spoiler

Mathresolvermajig: Intel Xeon E3 1240 (Sandy Bridge i7 equivalent)

Chillinmachine: Noctua NH-C14S
Framepainting-inator: EVGA GTX 1080 Ti SC2 Hybrid

Attachcorethingy: Gigabyte H61M-S2V-B3

Infoholdstick: Corsair 2x4GB DDR3 1333

Computerarmor: Silverstone RL06 "Lookalike"

Rememberdoogle: 1TB HDD + 120GB TR150 + 240 SSD Plus + 1TB MX500

AdditionalPylons: Phanteks AMP! 550W (based on Seasonic GX-550)

Letterpad: Rosewill Apollo 9100 (Cherry MX Red)

Buttonrodent: Razer Viper Mini + Huion H430P drawing Tablet

Auralnterface: Sennheiser HD 6xx

Liquidrectangles: LG 27UK850-W 4K HDR

 

Link to comment
https://linustechtips.com/topic/610245-bsods-suddenly/#findComment-7892794
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, Energycore said:

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

 

These two are probably useful snippets of info.

 

Google the program name (something like "ntkrnlmp.exe bsod") and see what you can find. Perhaps it's a hardware issue - the exception code reads "the instruction referenced this bit of memory but it wasn't there". Sounds like a RAM issue. Did your BSODs say "MEMORY_MANAGEMENT"?

 

5 minutes ago, Janne said:

Windows Resource Protection did not find any integrity violations. 

:S

 

Could it be hardware related? I have no idea how to read those dump files

As a followup, 4 of 5 dumps talk about that bit of memory. It's very likely to be a problem with RAM.

 

Take one stick of RAM out and fire up AIDA64 to stress just the one stick. If it's bad, it will crash before an hour elapses.

We have a NEW and GLORIOUSER-ER-ER PSU Tier List Now. (dammit @LukeSavenije stop coming up with new ones)

You can check out the old one that gave joy to so many across the land here

 

Computer having a hard time powering on? Troubleshoot it with this guide. (Currently looking for suggestions to update it into the context of <current year> and make it its own thread)

Computer Specs:

Spoiler

Mathresolvermajig: Intel Xeon E3 1240 (Sandy Bridge i7 equivalent)

Chillinmachine: Noctua NH-C14S
Framepainting-inator: EVGA GTX 1080 Ti SC2 Hybrid

Attachcorethingy: Gigabyte H61M-S2V-B3

Infoholdstick: Corsair 2x4GB DDR3 1333

Computerarmor: Silverstone RL06 "Lookalike"

Rememberdoogle: 1TB HDD + 120GB TR150 + 240 SSD Plus + 1TB MX500

AdditionalPylons: Phanteks AMP! 550W (based on Seasonic GX-550)

Letterpad: Rosewill Apollo 9100 (Cherry MX Red)

Buttonrodent: Razer Viper Mini + Huion H430P drawing Tablet

Auralnterface: Sennheiser HD 6xx

Liquidrectangles: LG 27UK850-W 4K HDR

 

Link to comment
https://linustechtips.com/topic/610245-bsods-suddenly/#findComment-7892805
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×