re-installation is always an option but a last resort really although it will give a good clean install with no factory bloatware and back to good speeds its just a pain in the ass reinstalling everything its up to you
Looking at the next two dumps you have
0x1E BSOD Index
0xA BSOD Index
if you want to keep going with this as we are getting nothing conclusive from dumps there is a list of things you can run and checks to make to see if it helps
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800032d8e33, 0, 94}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ad )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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: fffff800032d8e33, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000094, Parameter 1 of the exception
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003511100
GetUlongFromAddress: unable to read from fffff800035111c0
0000000000000000 Nonpaged pool
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!memcmp+93
fffff800`032d8e33 483b040a cmp rax,qword ptr [rdx+rcx]
BUGCHECK_STR: 0x1E_c0000005_R
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008db8e10 -- (.trap 0xfffff88008db8e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=44890c54e46eead8 rbx=0000000000000000 rcx=fffff88008db9118
rdx=0000077ff7246f7c rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032d8e33 rsp=fffff88008db8fa8 rbp=0000000000000000
r8=0000000000000010 r9=0000000000000002 r10=00000000000002a0
r11=fffff88008db9250 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!memcmp+0x93:
fffff800`032d8e33 483b040a cmp rax,qword ptr [rdx+rcx] ds:00000000`00000094=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000332ca88 to fffff800032e1fc0
STACK_TEXT:
fffff880`08db8588 fffff800`0332ca88 : 00000000`0000001e ffffffff`c0000005 fffff800`032d8e33 00000000`00000000 : nt!KeBugCheckEx
fffff880`08db8590 fffff800`032e1642 : fffff880`08db8d68 00000000`00000080 fffff880`08db8e10 fffff880`08db9118 : nt! ?? ::FNODOBFM::`string'+0x487ad
fffff880`08db8c30 fffff800`032e01ba : 00000000`00000000 00000000`00000094 00000000`00000000 00000000`00000080 : nt!KiExceptionDispatch+0xc2
fffff880`08db8e10 fffff800`032d8e33 : fffff800`035815dc 00000000`000002a0 00000000`000005d0 00000000`0001baf8 : nt!KiPageFault+0x23a
fffff880`08db8fa8 fffff800`035815dc : 00000000`000002a0 00000000`000005d0 00000000`0001baf8 80010001`00000000 : nt!memcmp+0x93
fffff880`08db8fb0 fffff800`036b3b42 : fffffa80`073a5ba0 00000000`80010001 00000000`00000000 00000000`00000000 : nt!EtwpFindGuidEntryByGuid+0x72
fffff880`08db8fe0 fffff800`036b3dd3 : fffffa80`073a5ba0 00000000`80010001 fffffa80`0b16f930 00000000`00000000 : nt!EtwpRegisterProvider+0x82
fffff880`08db9090 fffff800`036b3f3d : 00000000`00000000 00000000`00000000 00000000`3f800000 00000000`00000000 : nt!EtwRegister+0x23
fffff880`08db90d0 fffff800`036cf60d : fffff8a0`024584a0 fffffa80`0b16f930 fffff880`00000000 00000000`00000000 : nt!DbgkpStartSystemErrorHandler+0x6d
fffff880`08db9140 fffff800`03622941 : 00000000`80010001 fffffa80`073a5ba0 00000000`00000000 00000000`022e6600 : nt!DbgkpSendErrorMessage+0x3d
fffff880`08db9260 fffff800`0332cb6c : fffff880`08db9b78 fffff880`08db98d0 fffff880`08db9c20 00000000`022e6661 : nt! ?? ::NNGAKEGL::`string'+0x35498
fffff880`08db93a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x48891
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+487ad
fffff800`0332ca88 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+487ad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ad
BUCKET_ID: X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ad
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2, 2, 0, fffff8000337f80e}
*** WARNING: Unable to verify timestamp for rtl8192se.sys
*** ERROR: Module load completed but symbols could not be loaded for rtl8192se.sys
Probably caused by : hardware ( rtl8192se+2e70a )
Followup: MachineOwner
---------
2: 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: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000337f80e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003505100
GetUlongFromAddress: unable to read from fffff800035051c0
0000000000000002 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeRemoveByKeyDeviceQueue+7e
fffff800`0337f80e 8b00 mov eax,dword ptr [rax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880033d45b0 -- (.trap 0xfffff880033d45b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8006ae7f50
rdx=fffffa80068e3002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000337f80e rsp=fffff880033d4748 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000500
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeRemoveByKeyDeviceQueue+0x7e:
fffff800`0337f80e 8b00 mov eax,dword ptr [rax] ds:00000000`00000002=????????
Resetting default scope
MISALIGNED_IP:
nt!KeRemoveByKeyDeviceQueue+7e
fffff800`0337f80e 8b00 mov eax,dword ptr [rax]
LAST_CONTROL_TRANSFER: from fffff800032d5569 to fffff800032d5fc0
STACK_TEXT:
fffff880`033d4468 fffff800`032d5569 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033d4470 fffff800`032d41e0 : fffff880`06cc1000 f26106e9`f5630400 ffff0000`06eed6c5 fffffa80`06ae7ea0 : nt!KiBugCheckDispatch+0x69
fffff880`033d45b0 fffff800`0337f80e : fffff800`03212a56 fffff800`03212888 fffffa80`06dd6d10 00000000`00000002 : nt!KiPageFault+0x260
fffff880`033d4748 fffffa80`06ae7e00 : 00000000`00000002 fffffa80`070988a8 fffffa80`06834050 fffffa80`0ac7d990 : nt!KeRemoveByKeyDeviceQueue+0x7e
fffff880`033d4798 00000000`00000002 : fffffa80`070988a8 fffffa80`06834050 fffffa80`0ac7d990 fffff800`0321271f : 0xfffffa80`06ae7e00
fffff880`033d47a0 fffffa80`070988a8 : fffffa80`06834050 fffffa80`0ac7d990 fffff800`0321271f fffffa80`06dd6ce0 : 0x2
fffff880`033d47a8 fffffa80`06834050 : fffffa80`0ac7d990 fffff800`0321271f fffffa80`06dd6ce0 00000000`00000050 : 0xfffffa80`070988a8
fffff880`033d47b0 fffffa80`0ac7d990 : fffff800`0321271f fffffa80`06dd6ce0 00000000`00000050 fffffa80`06ae7ea0 : 0xfffffa80`06834050
fffff880`033d47b8 fffff800`0321271f : fffffa80`06dd6ce0 00000000`00000050 fffffa80`06ae7ea0 fffffa80`0ac7d950 : 0xfffffa80`0ac7d990
fffff880`033d47c0 fffff880`01a51671 : fffffa80`0aed53a0 fffffa80`068d7010 fffff880`000000a0 fffff800`032df099 : hal!HalBuildScatterGatherList+0x2f3
fffff880`033d4830 fffff880`05c5e70a : fffffa80`068341a0 fffff880`01a55d7b fffffa80`070988a8 fffffa80`068d7010 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`033d48d0 fffffa80`068341a0 : fffff880`01a55d7b fffffa80`070988a8 fffffa80`068d7010 fffffa80`06dd6ce0 : rtl8192se+0x2e70a
fffff880`033d48d8 fffff880`01a55d7b : fffffa80`070988a8 fffffa80`068d7010 fffffa80`06dd6ce0 fffff880`000001c0 : 0xfffffa80`068341a0
fffff880`033d48e0 fffff880`05c5e104 : 00000000`00000000 fffffa80`0abbed30 00000000`00000000 fffffa80`068d7010 : ndis!NdisAllocateNetBuffer+0x7b
fffff880`033d4930 00000000`00000000 : fffffa80`0abbed30 00000000`00000000 fffffa80`068d7010 fffffa80`068e3000 : rtl8192se+0x2e104
STACK_COMMAND: kb
FOLLOWUP_IP:
rtl8192se+2e70a
fffff880`05c5e70a ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: rtl8192se+2e70a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
So things you can try
windows disk check Disk Check
bootable disk check Hard Drive Diagnostic Procedure using something like this SeaTools | Seagate
RAM test RAM - Test with Memtest86+
Video stress test Video Card - Stress Test with Furmark
Hardware stress test Hardware - Stress Test With Prime95
Offline virus scan Windows Defender Offline
Rootkit scan http://support.kaspersky.com/5350