Windows 10: Random BSOD different error messages

Recently I have been getting a ton of BSOD errors that I've slowly gotten to happen less frequently but still occuring. Previously the errors were happening during gaming or other serious video/audio usage but I somewhat resolved this issue by resetting my BIOS settings that over the time had been getting wacky. Oddly, sometimes when I bluescreen, the WiFi adapter I use will not work upon bootup, unless I unplug and replug it in. Those BSODs were happening all the time. When the PC would bootup, it would insta-bluescreen again for 4-5 times ina row before it would be allowed to run for 10 minutes to just rinse and repeat.

After all of this, the PC was running good but now the errors happen randomly and the error message is usually different. I have done a Memtest with 4 passes that lasted for 2hours and had 0 errors. This is a complete dumpfile that was analyzed by Windbg so I will include that. Kernal security check failure was the message accompanied with it.

This is the file that was suppose to attached with the post by description of the [how to make bsod posts], I don't think it contains some of the newer error files since I changed how they were suppose to be saved. I think im using big dumpfiles instead of the miniones.
Attachment 137372



Code: Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Full address space is availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 14393 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 14393.1198.amd64fre.rs1_release_sec.170427-1353Machine Name:Kernel base = 0xfffff803`c441a000 PsLoadedModuleList = 0xfffff803`c4719000Debug session time: Tue May 30 12:52:41.315 2017 (UTC - 4:00)System Uptime: 0 days 0:49:45.154Loading Kernel Symbols..................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 139, {3, ffffe480ba13e3d0, ffffe480ba13e328, 0}Probably caused by : Pool_Corruption ( nt!ExFreePool+ce1 )Followup: Pool_corruption---------2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE (139)A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).Arg2: ffffe480ba13e3d0, Address of the trap frame for the exception that caused the bugcheckArg3: ffffe480ba13e328, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------DUMP_CLASS: 1DUMP_QUALIFIER: 402BUILD_VERSION_STRING: 14393.1198.amd64fre.rs1_release_sec.170427-1353SYSTEM_MANUFACTURER: ASUSSYSTEM_PRODUCT_NAME: All SeriesSYSTEM_SKU: AllSYSTEM_VERSION: System VersionBIOS_VENDOR: American Megatrends Inc.BIOS_VERSION: 0310BIOS_DATE: 05/29/2014BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.BASEBOARD_PRODUCT: Z97-PBASEBOARD_VERSION: Rev X.0xDUMP_TYPE: 0BUGCHECK_P1: 3BUGCHECK_P2: ffffe480ba13e3d0BUGCHECK_P3: ffffe480ba13e328BUGCHECK_P4: 0TRAP_FRAME: ffffe480ba13e3d0 -- (.trap 0xffffe480ba13e3d0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff948fa78a3f50 rbx=0000000000000000 rcx=0000000000000003rdx=ffff948fa0d29010 rsi=0000000000000000 rdi=0000000000000000rip=fffff803c4664801 rsp=ffffe480ba13e560 rbp=0000000000000000 r8=ffff948fa78a3e80 r9=ffff948fa12c4e50 r10=0000000000000001r11=ffff948fa7d12e50 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po cynt!ExFreePool+0xce1:fffff803`c4664801 cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffffe480ba13e328 -- (.exr 0xffffe480ba13e328)ExceptionAddress: fffff803c4664801 (nt!ExFreePool+0x0000000000000ce1) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRYCPU_COUNT: 8CPU_MHZ: f9eCPU_VENDOR: GenuineIntelCPU_FAMILY: 6CPU_MODEL: 3cCPU_STEPPING: 3CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)BUGCHECK_STR: 0x139PROCESS_NAME: SystemCURRENT_IRQL: 2ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003DEFAULT_BUCKET_ID: FAIL_FAST_LIST_ENTRY_CORRUPTANALYSIS_SESSION_HOST: ADMINRG-SH5FH9TANALYSIS_SESSION_TIME: 05-30-2017 13:53:00.0033ANALYSIS_VERSION: 10.0.15063.137 amd64freLAST_CONTROL_TRANSFER: from fffff803c4573d29 to fffff803c4568c00STACK_TEXT: ffffe480`ba13e0a8 fffff803`c4573d29 : 00000000`00000139 00000000`00000003 ffffe480`ba13e3d0 ffffe480`ba13e328 : nt!KeBugCheckExffffe480`ba13e0b0 fffff803`c4574090 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffbe69`062a5e48 : nt!KiBugCheckDispatch+0x69ffffe480`ba13e1f0 fffff803`c4573073 : 00000000`00000000 00000000`00000001 00000000`00c54bc8 00000000`00c54bc9 : nt!KiFastFailDispatch+0xd0ffffe480`ba13e3d0 fffff803`c4664801 : ffffd20c`73634946 00000000`000000c0 00000000`00000000 ffff9bbe`00000019 : nt!KiRaiseSecurityCheckFailure+0xf3ffffe480`ba13e560 fffff803`c466286d : ffff948f`a62429d0 fffff803`c474d100 fffff803`c474d100 00000000`00000000 : nt!ExFreePool+0xce1ffffe480`ba13e5e0 fffff80f`cf402212 : ffff948f`a11ef2a0 ffff948f`a3989dc8 00000000`00000000 00000000`0000000c : nt!ExFreePoolWithTag+0x86dffffe480`ba13e6c0 fffff803`c48fbae6 : 00000000`00000000 ffffd20c`530ed570 ffffd20c`530ed830 fffff80f`cfe55961 : FLTMGR!ExFreeToNPagedLookasideList+0x46ffffe480`ba13e6f0 fffff80f`cff04fb0 : ffffd20c`530ed6b0 ffff948f`a11ef2a8 ffffe480`ba13e828 ffff948f`9fc4a180 : nt!FsRtlTeardownPerStreamContexts+0x5affffe480`ba13e740 fffff80f`cff04daf : ffffe400`01010000 00000028`a76c1d00 00000000`00000000 00000000`00000000 : NTFS!NtfsDeleteScb+0x130ffffe480`ba13e7d0 fffff80f`cfe55753 : ffff948f`a0867c90 ffffd20c`530ed6b0 00000000`00000001 00000000`00000000 : NTFS!NtfsRemoveScb+0x5fffffe480`ba13e820 fffff80f`cff04b30 : ffffd20c`530ed570 ffffe480`ba13ea80 ffff948f`a3989dc8 00000000`00000000 : NTFS!NtfsPrepareFcbForRemoval+0x63ffffe480`ba13e860 fffff80f`cfe6edc0 : ffff948f`a3989dc8 ffffe480`ba13e963 ffffd20c`530ed980 ffffd20c`530ed570 : NTFS!NtfsTeardownStructures+0x90ffffe480`ba13e8e0 fffff80f`cff4e6db : ffffe480`ba13eab8 ffffe480`ba13eab8 ffffe480`ba13ea80 ffffd20c`530ed570 : NTFS!NtfsDecrementCloseCounts+0xd0ffffe480`ba13e920 fffff80f`cff58b9e : ffff948f`a3989dc8 ffffd20c`530ed6b0 ffffd20c`530ed570 ffff948f`9fc4a180 : NTFS!NtfsCommonClose+0x40bffffe480`ba13e9f0 fffff803`c447fbd9 : fffff803`c47d0100 ffff948f`a3d6e800 fffff803`00000000 fffff803`c47d0280 : NTFS!NtfsFspCloseInternal+0x1a2ffffe480`ba13eb80 fffff803`c44d0695 : ff174461`ff174561 00000000`00000080 ffff948f`9fcb16c0 ffff948f`a3d6e800 : nt!ExpWorkerThread+0xe9ffffe480`ba13ec10 fffff803`c456e0c6 : fffff803`c4756180 ffff948f`a3d6e800 fffff803`c44d0654 ff1a4864`ff1a4864 : nt!PspSystemThreadStartup+0x41ffffe480`ba13ec60 00000000`00000000 : ffffe480`ba13f000 ffffe480`ba139000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND: kbTHREAD_SHA1_HASH_MOD_FUNC: 4b331e732b05e86a011c410fede1e1e78e4d9336THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3f03ab25c9680130478169ff0553f026bd1e7e88THREAD_SHA1_HASH_MOD: a652ea35d44549839fbcb34b442a701b3bc34d3bFOLLOWUP_IP: nt!ExFreePool+ce1fffff803`c4664801 cd29 int 29hFAULT_INSTR_CODE: 3b929cdSYMBOL_STACK_INDEX: 4SYMBOL_NAME: nt!ExFreePool+ce1FOLLOWUP_NAME: Pool_corruptionIMAGE_NAME: Pool_CorruptionDEBUG_FLR_IMAGE_TIMESTAMP: 0MODULE_NAME: Pool_CorruptionBUCKET_ID_FUNC_OFFSET: ce1FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExFreePoolBUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExFreePoolPRIMARY_PROBLEM_CLASS: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExFreePoolTARGET_TIME: 2017-05-30T16:52:41.000ZOSBUILD: 14393OSSERVICEPACK: 0SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK: 272PRODUCT_TYPE: 1OSPLATFORM_TYPE: x64OSNAME: Windows 10OSEDITION: Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE: USER_LCID: 0OSBUILD_TIMESTAMP: 2017-04-27 19:39:04BUILDDATESTAMP_STR: 170427-1353BUILDLAB_STR: rs1_release_secBUILDOSVER_STR: 10.0.14393.1198.amd64fre.rs1_release_sec.170427-1353ANALYSIS_SESSION_ELAPSED_TIME: 876ANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x139_3_corrupt_list_entry_nt!exfreepoolFAILURE_ID_HASH: {909fba96-793b-fcdd-307f-f96f328d53ad}Followup: Pool_corruption---------2: kd> lmvm Pool_CorruptionBrowse full module liststart end module name[/quote]

:)

 

Constant BSOD - different error messages

Thanks for the reply.

After that last Kernel error the computer won't turn on at all, it's just stuck on the spinning windows icon.

I'll pass this onto my boyfriend but not sure what can actually be done when I can't even get on it anymore

 

Constant BSOD - different error messages

I'll try some of these aswell, thanks. My boyfriend said the CPU in the computer is old and that he might be a new one - could that be a fix? (pretty clueless here)

 

Debugging analysis with Windows Debugger Version 10.0.15063.137 AMD64

BugCheck 1A, {61941, ffffe581ab00a000, 9, ffffe581a6edb1b0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : ntkrnlmp.exe ( nt!KiPageFault+13c )


BugCheck 139, {3, ffffe480ba13e3d0, ffffe480ba13e328, 0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : Pool_Corruption ( nt!ExFreePool+ce1 )







Event[1606]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-05-25T16:58:24.653 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.


Event[1879]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-05-28T20:34:20.189 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.


Event[1940]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-05-28T22:24:05.551 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.


Event[2089]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-05-30T12:50:36.542 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.


Event[49]: Log Name: System Source: Service Control Manager Date: 2017-05-23T17:57:40.112 Event ID: 7023 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-CQB1C7C Description: The IP Helper service terminated with the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.


Event[274]: Log Name: System Source: Service Control Manager Date: 2017-05-23T18:12:24.655 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-SH5FH9T Description: The BCM42RLY service failed to start due to the following error: The system cannot find the file specified.


Event[275]: Log Name: System Source: Service Control Manager Date: 2017-05-23T18:12:24.686 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-SH5FH9T Description: The BCM42RLY service failed to start due to the following error: The system cannot find the file specified.


Event[331]: Log Name: System Source: Service Control Manager Date: 2017-05-23T18:13:01.507 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-SH5FH9T Description: The BCM42RLY service failed to start due to the following error: The system cannot find the file specified.


Event[332]: Log Name: System Source: Service Control Manager Date: 2017-05-23T18:13:01.526 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-SH5FH9T Description: The BCM42RLY service failed to start due to the following error: The system cannot find the file specified.


Event[572]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-23T16:26:50.439 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[662]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T00:06:39.336 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[709]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T00:12:04.477 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[851]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T00:37:17.398 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[983]: Log Name: System Source: volmgr Date: 2017-05-24T00:55:42.245 Event ID: 49 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ADMINRG-SH5FH9T Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.


Event[986]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T00:55:42.351 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1037]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T01:03:23.441 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1158]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T11:52:24.452 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1214]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-24T12:20:53.506 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1696]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-26T11:44:59.373 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1759]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-27T00:36:56.007 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1905]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-28T22:22:38.479 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[1981]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-30T09:57:54.093 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event[2111]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-05-30T13:00:25.111 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ADMINRG-SH5FH9T Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.



5/30/2017 5:52 PM Windows Error Reporting Fault bucket 127882695816, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.14393.1198
P2: 80d02003
P3: 8F0F911A-B310-4CAD-ADBE-D1E163D21B0F
P4: Download
P5: 203
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8047.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.14393.1198_fc3d33b64085e4264f2cf 577c2fa18575492_00000000_07e01812

Analysis symbol:
Rechecking for solution: 0
Report Id: b1e6eba8-4559-11e7-99d3-7824af4648fb
Report Status: 0
Hashed bucket: 1d0aa374bf2eb9044e4110ac022a6949

5/30/2017 5:52 PM Windows Error Reporting Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!ExDeferredFreePool, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 79db3758-c709-4be1-ae96-6ded14f464da

Problem signature:
P1: 139
P2: 3
P3: ffffe480ba13e3d0
P4: ffffe480ba13e328
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\053017-82859-01.dmp
\\?\C:\Windows\Temp\WER-83531-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D02.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_987f81025d197882710ea9d8a1a983f15ebba1 _00000000_cab_07e015ff

Analysis symbol:
Rechecking for solution: 0
Report Id: ba0c875a-5e45-4c64-b96c-594e0dc98d9e
Report Status: 0
Hashed bucket:


5/30/2017 5:01 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffe480ba13e3d0
P4: ffffe480ba13e328
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\053017-82859-01.dmp
\\?\C:\Windows\Temp\WER-83531-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D02.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_987f81025d197882710ea9d8a1a983f15ebba1_0 0000000_cab_02f94d11

Analysis symbol:
Rechecking for solution: 0
Report Id: ba0c875a-5e45-4c64-b96c-594e0dc98d9e
Report Status: 4
Hashed bucket:


5/29/2017 2:24 AM Windows Error Reporting Fault bucket 0x1a_61941_nt!MmCopyToCachedPage, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 51f5a583-1681-45a5-bf83-899589f21c7a

Problem signature:
P1: 1a
P2: 61941
P3: ffffe581ab00a000
P4: 9
P5: ffffe581a6edb1b0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\052817-75671-01.dmp
\\?\C:\Windows\Temp\WER-76234-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30BF.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_d1b58f8e29e3d996fe6fd8dc3a1646ceaa72418 _00000000_cab_13798eae

Analysis symbol:
Rechecking for solution: 0
Report Id: 77cdbb7a-a2f9-43f3-8039-6c0b7fcc164d
Report Status: 0
Hashed bucket:


5/29/2017 2:23 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 61941
P3: ffffe581ab00a000
P4: 9
P5: ffffe581a6edb1b0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\052817-75671-01.dmp
\\?\C:\Windows\Temp\WER-76234-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30BF.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_d1b58f8e29e3d996fe6fd8dc3a1646ceaa72418_0 0000000_cab_02ed30cf

Analysis symbol:
Rechecking for solution: 0
Report Id: 77cdbb7a-a2f9-43f3-8039-6c0b7fcc164d
Report Status: 4
Hashed bucket:


5/27/2017 4:38 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 12b
P2: ffffffffc00002c4
P3: 748
P4: 3a046e40
P5: ffffe58166134000
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\052717-75343-01.dmp
\\?\C:\Windows\Temp\WER-76000-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30DE.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_12b_111cac161568cbb7e6992fbd6eae1f62967cda56 _00000000_cab_033d30ee

Analysis symbol:
Rechecking for solution: 0
Report Id: f82f16de-2ecb-48bf-a2e9-43b4eb508705
Report Status: 4
Hashed bucket:


5/26/2017 3:45 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 41792
P3: ffffa2bffdadc810
P4: 82000000000000
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\Minidump\052617-7453-01.dmp
\\?\C:\Windows\Temp\WER-8390-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2971.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_4d36f043245a394ab6eb0d7123fe5c96be83_0000 0000_cab_02e02981

Analysis symbol:
Rechecking for solution: 0
Report Id: e778df57-62e3-4b9f-8655-4ab8b6b6bbae
Report Status: 4
Hashed bucket:


There were only 2 minidump files. The logs indicated 5 or more bsod. There were many reboots without clean shutdown.


Open administrative command prompt and run:

1) winver (view the pop up and post your windows version and build)
2) sfc /scannow
3) dism /online /cleanup-image /restorehelath
4) chkdsk /scan
Right click on the top of the administrative command prompt box and left click on edit and select all. Then right click again and left click on copy. Then paste into the forum.
5) open control panel > troubleshooting > left pane view all > run windows update troubleshooter.

For the memory test please run memtest64+ so that you will have at least 8 runs. Sometimes it takes more runs to find problems. The minimum numbers of run to be useful is usually > 8 runs.




The event logs have windows update failures.
Per the logs that you sent you are running windows 10.0.1493.
The latest version and build are 10.0.15063.




Attempt windows updates after running the windows update troubleshooter.
If the update fail after running the troubleshooter copy and paste this into notepad and save as a .txt file.
Then rename changing .txt to .bat
Then copy and paste the .bat file into administrative command prompt.

Net stop bits
Net stop wuauserv
Net stop appidsvc
Net stop cryptsvc
Del %ALLUSERSPROFILE%\Microsoft\Network\Downloader\qmgr*.dat /Q
Del "%HOMEDRIVE%\Users\All Users\Microsoft\Network\Downloader\qmgr*.dat" /Q
Del %WINDIR%\SoftwareDistribution\*.* /s /Q
Net start bits
Net start wuauserv
Net start appidsvc
Net start cryptsvc

 

Microsoft Windows
Version 1607 (OS Build 14393.1198)

I ran the update troubleshooter and it corrected like 4-5 things and I ran windows update after and it seems to be downloading version 1703 of Windows 10 I think.

Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.C:\Windows\system32>winverC:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /restorehelathDeployment Image Servicing and Management toolVersion: 10.0.14393.0Image Version: 10.0.14393.0Error: 87The restorehelath option is not recognized in this context.For more information, refer to the help.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 300032 file records processed.File verification completed. 7970 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 390032 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 45001 data files processed.CHKDSK is verifying Usn Journal... 33770800 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 124469247 KB total disk space. 97406452 KB in 224647 files. 157924 KB in 45002 indexes. 0 KB in bad sectors. 404883 KB in use by the system. 65536 KB occupied by the log file. 26499988 KB available on disk. 4096 bytes in each allocation unit. 31117311 total allocation units on disk. 6624997 allocation units available on disk.C:\Windows\system32>

 

There was a typo in the dism command. Sorry that I had not proofread it. Please open administrative command prompt and run:
Dism /online /cleanup-image /restorehealth

After the updates are completed type winver in the left lower corner. In the pop up view the windows version and build and post.

The memtest86+ with 8 or more runs (run overnight will enable you to rule in/out memory ram/dim problems

 

Rule 4
No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.

One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be please to assist - No further assistance will be provided until we are satisfied that the software is genuine.