No Idea why I am crashing all of a sudden. Nothing has really changed. I did a restore from a week ago because I screwed something up but I fixed that and now I am getting stopcodes crashes. I updated my audio driver and radeon driver. I am not sure what about a restore could have caused this. Ive done sfc /scannow, chdsk and everything seems fine.
I get "system thread exception not handled" or similar:
On Sun 11/27/2016 11:01:02 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8030CE20B22)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8030CE20B22, 0xFFFFD98137183EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
Also a minidump from the last crash.
MiniDump output
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800f92a3b22, Address of the instruction which caused the bugcheck
Arg3: ffff84800c6feed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_****ysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+12
fffff800`f92a3b22 48890a mov qword ptr [rdx],rcx
CONTEXT: ffff84800c6feed0 -- (.cxr 0xffff84800c6feed0)
rax=0000000000000020 rbx=ffff84800a500180 rcx=ffff84800c6ff9e0
rdx=0800000000000000 rsi=ffffb002ed91b000 rdi=ffff84800c6ff9e0
rip=fffff800f92a3b22 rsp=ffff84800c6ff8e0 rbp=ffffb002ef21be40
r8=ffff84800c6ffa50 r9=0000000000000000 r10=ffffac641f11378e
r11=000000238b9a7000 r12=0000000000000000 r13=000000238bbff050
r14=ffff84800c6ffa60 r15=000000000c6ffa60
iopl=0 nv up di ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010086
nt!KxWaitForLockOwnerShipWithIrql+0x12:
fffff800`f92a3b22 48890a mov qword ptr [rdx],rcx ds:002b:08000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 96da
LAST_CONTROL_TRANSFER: from fffff800f945948f to fffff800f92a3b22
STACK_TEXT:
ffff8480`0c6ff8e0 fffff800`f945948f : ffff8480`0a500180 ffffb002`ed642088 00000000`00000000 00000000`00000010 : nt!KxWaitForLockOwnerShipWithIrql+0x12
ffff8480`0c6ff910 fffff800`f936b0b0 : ffffb002`ef21bde0 ffff8480`0c6ff9d9 ffffb002`ed91b080 ffff8480`0c6ffa60 : nt!KiFastAcquireQueuedSpinLockInstrumented+0x6f
ffff8480`0c6ff960 ffffac64`1e7c91aa : ffffb002`ef21bd02 00000000`00000000 ffffb002`ef21bd02 ffffac64`1e7c73f3 : nt!ExpReleaseResourceForThreadLite+0xb60
ffff8480`0c6ffa40 ffffb002`ef21bd02 : 00000000`00000000 ffffb002`ef21bd02 ffffac64`1e7c73f3 00000000`000072dd : win32kbase+0x391aa
ffff8480`0c6ffa48 00000000`00000000 : ffffb002`ef21bd02 ffffac64`1e7c73f3 00000000`000072dd ffffac64`1e7c8b25 : 0xffffb002`ef21bd02
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xffff84800c6feed0 ; kb
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 38618 instance(s) of page corruption, target is likely to have memory corruption.
I was slightly OC'd so I went ahead and went back to default clock for testing purposes but I have been OC'd for months and months with no issue. Literally nothing has really changed except that I did a a restore from 1 week ago and have update video drivers. Im begginning to think its not even a driver issue and could be something hardware? It confused as nothing seems to make sense based on the crashes.
I get "system thread exception not handled" or similar:
On Sun 11/27/2016 11:01:02 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8030CE20B22)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8030CE20B22, 0xFFFFD98137183EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
Also a minidump from the last crash.
MiniDump output
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800f92a3b22, Address of the instruction which caused the bugcheck
Arg3: ffff84800c6feed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_****ysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+12
fffff800`f92a3b22 48890a mov qword ptr [rdx],rcx
CONTEXT: ffff84800c6feed0 -- (.cxr 0xffff84800c6feed0)
rax=0000000000000020 rbx=ffff84800a500180 rcx=ffff84800c6ff9e0
rdx=0800000000000000 rsi=ffffb002ed91b000 rdi=ffff84800c6ff9e0
rip=fffff800f92a3b22 rsp=ffff84800c6ff8e0 rbp=ffffb002ef21be40
r8=ffff84800c6ffa50 r9=0000000000000000 r10=ffffac641f11378e
r11=000000238b9a7000 r12=0000000000000000 r13=000000238bbff050
r14=ffff84800c6ffa60 r15=000000000c6ffa60
iopl=0 nv up di ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010086
nt!KxWaitForLockOwnerShipWithIrql+0x12:
fffff800`f92a3b22 48890a mov qword ptr [rdx],rcx ds:002b:08000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 96da
LAST_CONTROL_TRANSFER: from fffff800f945948f to fffff800f92a3b22
STACK_TEXT:
ffff8480`0c6ff8e0 fffff800`f945948f : ffff8480`0a500180 ffffb002`ed642088 00000000`00000000 00000000`00000010 : nt!KxWaitForLockOwnerShipWithIrql+0x12
ffff8480`0c6ff910 fffff800`f936b0b0 : ffffb002`ef21bde0 ffff8480`0c6ff9d9 ffffb002`ed91b080 ffff8480`0c6ffa60 : nt!KiFastAcquireQueuedSpinLockInstrumented+0x6f
ffff8480`0c6ff960 ffffac64`1e7c91aa : ffffb002`ef21bd02 00000000`00000000 ffffb002`ef21bd02 ffffac64`1e7c73f3 : nt!ExpReleaseResourceForThreadLite+0xb60
ffff8480`0c6ffa40 ffffb002`ef21bd02 : 00000000`00000000 ffffb002`ef21bd02 ffffac64`1e7c73f3 00000000`000072dd : win32kbase+0x391aa
ffff8480`0c6ffa48 00000000`00000000 : ffffb002`ef21bd02 ffffac64`1e7c73f3 00000000`000072dd ffffac64`1e7c8b25 : 0xffffb002`ef21bd02
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xffff84800c6feed0 ; kb
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 38618 instance(s) of page corruption, target is likely to have memory corruption.
I was slightly OC'd so I went ahead and went back to default clock for testing purposes but I have been OC'd for months and months with no issue. Literally nothing has really changed except that I did a a restore from 1 week ago and have update video drivers. Im begginning to think its not even a driver issue and could be something hardware? It confused as nothing seems to make sense based on the crashes.
Facebook
Twitter
Instagram