I think I did this in the first screen or page of this post. Is that what you want?
Can you enter the specs in the lower left corner of your post, this will make it easier for us to see what components you have without going back through the thread.
Use this link to find your system specs.
Speccy Free System information Utility
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
Please do not zip these and post them, follow the link below so all can easily see the information.
How to Post a Screenshot in Seven Forums
Ok I tried the sfc /scannow 6 time in a row and it allways fails at 71%. I would think it would make some progress from what you told me if I rerun and then reboot but I don't see any progress.
Let's look at some of your hardware first but, when sfc /scannow fails it not only means you have Windows system file problems, it will likely need to be fixed by System restore, a Repair install or a Clean install.
Unless you have Image Backups, if you do let us know when they are from.
Your last dump files posted are still showing 'memory corruption.
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
Cause: Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002a49b50
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a7e1e9 to fffff80002a7ec40
STACK_TEXT:
fffff880`032ffde8 fffff800`02a7e1e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`032ffdf0 fffff800`02a7c6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`032fff30 fffff800`02a49b50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`035542e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteKernelStack+0x28
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80002a49b40-fffff80002a49b78)
fffff80002a49b40 *9d 83 ec 30 41 bf 02 00 *76 00 44 8b ea 48 8b e9 ...0A...v.D..H..
fffff80002a49b50 *c3 84 c7 0f 85 f4 67 09 *2a 41 8b d5 41 8d 75 01 ......g.*A..A.u.
fffff80002a49b60 *27 db fd ff ff 49 8b cd *a7 8b e5 48 f7 d9 48 8b '....I.....H..H.
fffff80002a49b70 *9e 48 8d 6c cd 00 49 8b *41 48 f7 d9 f0 48 0f c1 .H.l..I.AH...H..
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80002bb547e, Address of the instruction which caused the bugcheck
Arg3: fffff88007690cb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!PfpEventHandleFullBuffer+1e
fffff800`02bb547e 44 ???
CONTEXT: fffff88007690cb0 -- (.cxr 0xfffff88007690cb0)
rax=0000000000000001 rbx=fffff80002c5dea0 rcx=fffff80002c5df20
rdx=0000000000000001 rsi=0000000000000028 rdi=0000000000000040
rip=fffff80002bb547e rsp=fffff88007691690 rbp=fffff88007691760
r8=0000000000000000 r9=fffffa800ab65f20 r10=fffff80002c5df20
r11=0000000000000001 r12=0000000014311b58 r13=000000000000000a
r14=0000000000cf4500 r15=0000000000000000
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!PfpEventHandleFullBuffer+0x1e:
fffff800`02bb547e 44 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: BsecAV.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002bb547e
STACK_TEXT:
fffff880`07691690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfpEventHandleFullBuffer+0x1e
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
16 errors : !nt (fffff80002bb5480-fffff80002bb55b8)
fffff80002bb5480 *d6 d8 8b 05 84 2b 15 00 *eb 44 00 04 d1 e8 44 3b .....+...D....D;
fffff80002bb5490 *16 72 11 48 8d 0d 56 87 *73 00 45 33 c0 33 d2 e8 .r.H..V.s.E3.3..
fffff80002bb54a0 *a4 46 f2 ff 48 83 c4 28 *10 90 90 90 90 90 90 90 .F..H..(........
fffff80002bb54b0 *49 89 5c 24 10 57 48 83 *2d 20 48 8b 0d 6f 2b 15 I.\$.WH.- H..o+.
...
fffff80002bb5580 *82 48 8b d7 e8 67 70 f1 *c5 80 bb 88 00 00 00 01 .H...gp.........
fffff80002bb5590 *9c 06 89 83 d8 00 00 00 *83 46 04 89 83 dc 00 00 .........F......
fffff80002bb55a0 *02 8b 46 08 89 83 e0 00 *4c 00 48 8d 87 48 07 00 ..F.....L.H..H..
fffff80002bb55b0 *4d 48 89 83 e8 00 00 00 *9e 8d 87 50 07 00 00 48 MH.........P...H
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: .cxr 0xfffff88007690cb0 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
Have you had any hardware changes?
Re-seat your RAM, take it out and inspect the socket and RAM connectors, clean the connectors with alcohol and a lint free cloth, re-install the RAM cards. Be sure they are firmly inserted.
Check you motherboard for any sign of overheating, bulging compactors, or discoloration on any board components.
Quote