Solved BSOD - intermittent . Seems to happen with multiple processes.

[AlertIT]

I have already completely replaced the RAM sticks as well. I ran mem tests on the originals with no errors but thought why not.

This one was code 0x000000C2

Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck C2, {7, 109b, 4050001, fffffa8011e296a0}
 
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+229 )
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000004050001, Memory contents of the pool block
Arg4: fffffa8011e296a0, Address of the block of pool being deallocated
 
Debugging Details:
------------------
 
 
POOL_ADDRESS:  fffffa8011e296a0 Nonpaged pool
 
FREED_POOL_TAG:  Icp 
 
BUGCHECK_STR:  0xc2_7_Icp 
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  chrome.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from fffff80002e02be9 to fffff80002ccb400
 
STACK_TEXT:  
fffff880`0af41878 fffff800`02e02be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`04050001 : nt!KeBugCheckEx
fffff880`0af41880 fffff800`02fb4e79 : 00000000`00000000 fffff800`02fb6301 fffffa80`20706300 fffffa80`0f89d650 : nt!ExFreePool+0xca9
fffff880`0af41930 fffff800`02f86b05 : fffff880`00000000 fffff880`0af41a28 fffff880`0af41a20 fffffa80`0f89d601 : nt!IoRemoveIoCompletion+0x229
fffff880`0af419c0 fffff800`02cca693 : fffffa80`139d0940 00000000`0271eb08 fffff880`0af41a88 00000000`01225364 : nt!NtRemoveIoCompletion+0x145
fffff880`0af41a70 00000000`74bc2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0271eae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bc2e09
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!IoRemoveIoCompletion+229
fffff800`02fb4e79 4c8bac2498000000 mov     r13,qword ptr [rsp+98h]
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  nt!IoRemoveIoCompletion+229
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5708972e
 
FAILURE_BUCKET_ID:  X64_0xc2_7_Icp__nt!IoRemoveIoCompletion+229
 
BUCKET_ID:  X64_0xc2_7_Icp__nt!IoRemoveIoCompletion+229
 
Followup: MachineOwner
---------

 

[AlertIT]

happened again. this one was code 0x0000007E

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 7E, {ffffffffc0000005, fffff80002c9273a, fffff8800805b938, fffff8800805b190}
 
Probably caused by : ntkrnlmp.exe ( nt!KiStartSystemThread+16 )
 
Followup: MachineOwner
---------
 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c9273a, The address that the exception occurred at
Arg3: fffff8800805b938, Exception Record Address
Arg4: fffff8800805b190, Context Record Address
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
 
FAULTING_IP: 
nt!ExpWorkerThread+102
fffff800`02c9273a 498b7c2418      mov     rdi,qword ptr [r12+18h]
 
EXCEPTION_RECORD:  fffff8800805b938 -- (.exr 0xfffff8800805b938)
ExceptionAddress: fffff80002c9273a (nt!ExpWorkerThread+0x0000000000000102)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018
 
CONTEXT:  fffff8800805b190 -- (.cxr 0xfffff8800805b190)
rax=0000000000000001 rbx=fffff880012cd0a0 rcx=0000000000000000
rdx=0000000000000002 rsi=fffffa800fdce680 rdi=0000000000000000
rip=fffff80002c9273a rsp=fffff8800805bb70 rbp=fffff80002e32280
 r8=fffff80002c19000  r9=0000000000000000 r10=fffffffffffffffb
r11=fffff88002f65180 r12=0000000000000000 r13=0000000000000001
r14=fffff8800805bba8 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpWorkerThread+0x102:
fffff800`02c9273a 498b7c2418      mov     rdi,qword ptr [r12+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope
 
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_PARAMETER1:  0000000000000000
 
EXCEPTION_PARAMETER2:  0000000000000018
 
READ_ADDRESS:  0000000000000018 
 
FOLLOWUP_IP: 
nt!KiStartSystemThread+16
fffff800`02c7a6a6 48c7c10e000000  mov     rcx,0Eh
 
BUGCHECK_STR:  0x7E
 
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
 
LAST_CONTROL_TRANSFER:  from fffff80002f20bc6 to fffff80002c9273a
 
STACK_TEXT:  
fffff880`0805bb70 fffff800`02f20bc6 : 00000000`065a0734 fffffa80`0fdce680 00000000`00000080 fffffa80`0c5de430 : nt!ExpWorkerThread+0x102
fffff880`0805bc00 fffff800`02c7a6a6 : fffff880`02f65180 fffffa80`0fdce680 fffffa80`0f73d060 fffffa80`0d54acd0 : nt!PspSystemThreadStartup+0x5a
fffff880`0805bc40 00000000`00000000 : fffff880`0805c000 fffff880`08056000 fffff880`0805b8a0 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  nt!KiStartSystemThread+16
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5708972e
 
STACK_COMMAND:  .cxr 0xfffff8800805b190 ; kb
 
FAILURE_BUCKET_ID:  X64_0x7E_nt!KiStartSystemThread+16
 
BUCKET_ID:  X64_0x7E_nt!KiStartSystemThread+16
 
Followup: MachineOwner
---------

 

[axe0]

BSOD Posting Instructions & How to upload files