Blue Screen - BSOD Windows 10 x64
- Thread starter are
- Start date
The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Check S.M.A.R.T with HD Tune
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.
Test RAM with memtest86+ (Test RAM With Memtest86+)
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.
The CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF. This indicates that a critical system process died.
The FAULTY_HARDWARE_CORRUPTED_PAGE bug check has a value of 0x00000128. This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
Summarizing to check:
RAM memory with memtest 86+ - Test RAM With Memtest86+
S.M.A.R.T with HD Tune - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
And update BIOS to version 02.37 - Komputer HP ProOne 600 G2 21,5" Touch All-in-One - Pobieranie sterowników | Pomoc techniczna HP® dla klientów
Check S.M.A.R.T with HD Tune
Code:
Loading Dump File [F:\022619-21015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff802`54406000 PsLoadedModuleList = 0xfffff802`547525a0
Debug session time: Tue Feb 26 09:48:46.679 2019 (UTC + 1:00)
System Uptime: 0 days 0:21:47.871
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {1, ffffffffc0000005, ffffc200c1208080, ffffd76b800b4000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000001, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000005, error status (normally i/o status code)
Arg3: ffffc200c1208080, current process (virtual address for lock type 3, or PTE)
Arg4: ffffd76b800b4000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP ProOne 600 G2 21.5-in Touch AiO
SYSTEM_SKU: L3N89AV
BIOS_VENDOR: HP
BIOS_VERSION: N12 Ver. 02.15
BIOS_DATE: 11/01/2016
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 805E
BASEBOARD_VERSION: KBC Version 05.22
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: ffffffffc0000005
BUGCHECK_P3: ffffc200c1208080
BUGCHECK_P4: ffffd76b800b4000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x7a_c0000005
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 8A'00000000 (cache) 8A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: ArkSignerGunce
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-09-2019 13:27:45.0571
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff802545a06e9 to fffff80254571f70
STACK_TEXT:
ffff8001`24b1f5a8 fffff802`545a06e9 : 00000000`0000007a 00000000`00000001 ffffffff`c0000005 ffffc200`c1208080 : nt!KeBugCheckEx
ffff8001`24b1f5b0 fffff802`5446f6f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiMakeSystemAddressValid+0x12eab9
ffff8001`24b1f660 fffff802`5446ed8e : 00000000`00000000 00000000`00001000 94000000`00f97005 00000000`00000000 : nt!MiGetNextPageTable+0x314
ffff8001`24b1f720 fffff802`5446eace : 00000000`00000000 fffff802`5486eb00 00007ffd`00000000 ffffc200`c1208580 : nt!MiQueryAddressState+0xce
ffff8001`24b1f7b0 fffff802`5485a04f : ffffc200`00000000 00000000`00000001 00000000`00000000 00000000`80000000 : nt!MiQueryAddressSpan+0x12e
ffff8001`24b1f860 fffff802`548598f1 : 000001e7`6cc03220 fffff802`54857937 ffffc200`c204e080 0000007e`cc37e138 : nt!MmQueryVirtualMemory+0x74f
ffff8001`24b1f9c0 fffff802`5457ce13 : 00000000`00000102 00000000`00000001 00000000`00000001 00000000`00000000 : nt!NtQueryVirtualMemory+0x25
ffff8001`24b1fa10 00007ffd`68c65814 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000007e`cc37e198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`68c65814
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
4 errors : !nt (fffff8025446f773-fffff8025446f7f2)
fffff8025446f770 00 00 80 *94 ff ff 44 8b 71 30 41 8b c6 83 e0 07 ......D.q0A.....
...
fffff8025446f7a0 b8 28 00 00 00 80 *94 ff ff 48 8b 04 07 48 b9 00 .(.......H...H..
...
fffff8025446f7f0 00 *00 *d7 ff ff 48 8b c1 48 c1 e0 19 48 ba 00 f0 .....H..H...H...
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_128
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_128
BUCKET_ID: MEMORY_CORRUPTION_LARGE_128
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE_128
TARGET_TIME: 2019-02-26T08:48:46.000Z
OSBUILD: 15063
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-01 01:44:54
BUILDDATESTAMP_STR: 170317-1834
BUILDLAB_STR: rs2_release
BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
ANALYSIS_SESSION_ELAPSED_TIME: 1db9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large_128
FAILURE_ID_HASH: {cc6a18f2-b8ff-4ab2-2f71-935a687dfb05}
Followup: memory_corruption
---------Test RAM with memtest86+ (Test RAM With Memtest86+)
Code:
Loading Dump File [F:\030619-21562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`80688000 PsLoadedModuleList = 0xfffff803`809d45a0
Debug session time: Wed Mar 6 10:03:15.923 2019 (UTC + 1:00)
System Uptime: 8 days 0:14:04.387
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41792, ffff9e80000308e8, 80000000, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff9e80000308e8
Arg3: 0000000080000000
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP ProOne 600 G2 21.5-in Touch AiO
SYSTEM_SKU: L3N89AV
BIOS_VENDOR: HP
BIOS_VERSION: N12 Ver. 02.15
BIOS_DATE: 11/01/2016
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 805E
BASEBOARD_VERSION: KBC Version 05.22
DUMP_TYPE: 2
BUGCHECK_P1: 41792
BUGCHECK_P2: ffff9e80000308e8
BUGCHECK_P3: 80000000
BUGCHECK_P4: 0
MEMORY_CORRUPTOR: LARGE
BUGCHECK_STR: 0x1a_41792
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 8A'00000000 (cache) 8A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-09-2019 13:30:27.0218
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
ffffb580`a6e23528 fffff803`80820b82 : 00000000`0000001a 00000000`00041792 ffff9e80`000308e8 00000000`80000000 : nt!KeBugCheckEx
ffffb580`a6e23530 fffff803`806e8a4d : ffffcb0b`ef8c5d88 ffffcb0b`f2b74080 ffffcb0b`ef8c5d88 ffffcb0b`ef8c57c0 : nt!MiDeleteVirtualAddresses+0x1333a2
ffffb580`a6e237e0 fffff803`80b032bc : 00000000`06060000 ffffcb0b`eff53d10 00000000`67e954b0 00000000`00000000 : nt!MiDeleteVad+0x3ad
ffffb580`a6e23960 fffff803`80bbaad6 : ffffcb0b`ef8c57c0 00000000`00000008 ffffcb0b`e58b2f20 00000000`06060000 : nt!MiUnmapViewOfSection+0xec
ffffb580`a6e23a30 fffff803`807fee13 : ffffcb0b`f2b74080 00000000`00000000 00000000`00000000 ffffcb0b`ef8c57c0 : nt!NtUnmapViewOfSectionEx+0x86
ffffb580`a6e23a80 00007ffd`110658f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0051e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`110658f4
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80380908374-fffff80380908375 2 bytes - nt!ExFreePoolWithTag+364
[ fb f6:cf 9e ]
2 errors : !nt (fffff80380908374-fffff80380908375)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2019-03-06T09:03:15.000Z
OSBUILD: 15063
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-01 01:44:54
BUILDDATESTAMP_STR: 170317-1834
BUILDLAB_STR: rs2_release
BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
ANALYSIS_SESSION_ELAPSED_TIME: 2765
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
0: kd> !pte ffff9e80000308e8
VA ffff9e80000308e8
PXE at FFFFF6FB7DBED9E8 PPE at FFFFF6FB7DB3D000 PDE at FFFFF6FB67A00000 PTE at FFFFF6CF40000180
Unable to get PXE FFFFF6FB7DBED9E8
Code:
Loading Dump File [F:\030719-19718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`2f27d000 PsLoadedModuleList = 0xfffff803`2f5c95a0
Debug session time: Thu Mar 7 14:12:26.414 2019 (UTC + 1:00)
System Uptime: 1 days 4:08:36.593
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffdb80b4c71130, 0, fffff80f8aaee981, 2}
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffdb80b4c71130, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80f8aaee981, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP ProOne 600 G2 21.5-in Touch AiO
SYSTEM_SKU: L3N89AV
BIOS_VENDOR: HP
BIOS_VERSION: N12 Ver. 02.15
BIOS_DATE: 11/01/2016
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 805E
BASEBOARD_VERSION: KBC Version 05.22
DUMP_TYPE: 2
BUGCHECK_P1: ffffdb80b4c71130
BUGCHECK_P2: 0
BUGCHECK_P3: fffff80f8aaee981
BUGCHECK_P4: 2
READ_ADDRESS: fffff8032f65e358: Unable to get MiVisibleState
ffffdb80b4c71130
FAULTING_IP:
rdbss!_RxAcquireFcb+51
fffff80f`8aaee981 488b8120010000 mov rax,qword ptr [rcx+120h]
MM_INTERNAL_CODE: 2
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 8A'00000000 (cache) 8A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: AV
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-09-2019 13:33:53.0290
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
TRAP_FRAME: ffffa10012617540 -- (.trap 0xffffa10012617540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80f8aad9000 rbx=0000000000000000 rcx=ffffdb80b4c71010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80f8aaee981 rsp=ffffa100126176d0 rbp=0000000000000001
r8=0000000000000001 r9=0000000000000000 r10=0000000000000704
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
rdbss!_RxAcquireFcb+0x51:
fffff80f`8aaee981 488b8120010000 mov rax,qword ptr [rcx+120h] ds:ffffdb80`b4c71130=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8032f417e86 to fffff8032f3e8f70
STACK_TEXT:
ffffa100`126172a8 fffff803`2f417e86 : 00000000`00000050 ffffdb80`b4c71130 00000000`00000000 ffffa100`12617540 : nt!KeBugCheckEx
ffffa100`126172b0 fffff803`2f2eb766 : 00000000`00000000 ffffdb80`b4c71130 ffffa100`12617540 ffff800a`19429680 : nt!MiSystemFault+0x12e8c6
ffffa100`12617350 fffff803`2f3f2772 : fffff80f`87380000 fffff80f`873b8e8b 00000000`00001000 ffffdb80`94b72980 : nt!MmAccessFault+0xae6
ffffa100`12617540 fffff80f`8aaee981 : ffff800a`20d2b300 fffff803`2f7b804f 00000000`00000000 ffffdb80`94c71301 : nt!KiPageFault+0x132
ffffa100`126176d0 fffff80f`8aaecfbd : ffffdb80`b4c71010 00000000`00000000 00000000`00000001 ffffdb80`b4c71010 : rdbss!_RxAcquireFcb+0x51
ffffa100`12617750 fffff80f`8aae96ae : ffffdb80`94c74000 00000000`00000000 00000000`0062f124 00000000`00000000 : rdbss!RxpDereferenceAndFinalizeNetFcb+0x24d
ffffa100`126177f0 fffff80f`8aae8f0c : 00000000`00000000 ffffa100`00000082 ffff800a`20d2b648 fffff803`2f291951 : rdbss!RxScavengeRelatedFobxs+0x33e
ffffa100`126179d0 fffff80f`8aae8db4 : ffff800a`20d2b300 ffff800a`20d2b648 00000000`00000000 ffff800a`1e1e2900 : rdbss!RxScavengerFinalizeEntries+0x8c
ffffa100`12617a40 fffff80f`8aab1b53 : ffff800a`20d2b790 00000000`00000000 ffff800a`1e678a70 ffff800a`1bde5940 : rdbss!RxScavengerTimerRoutine+0x94
ffffa100`12617aa0 fffff803`2f29c1c8 : ffff800a`1e1e27c0 fffff80f`8aab1ac0 ffff800a`20d2b790 fffff803`2f5e8f20 : rdbss!RxpProcessWorkItem+0x93
ffffa100`12617b00 fffff803`2f336a37 : 00000000`00000000 00000000`00000080 ffff800a`19429680 ffff800a`1e1e27c0 : nt!ExpWorkerThread+0xd8
ffffa100`12617b90 fffff803`2f3ee3f6 : ffffa100`0d828180 ffff800a`1e1e27c0 fffff803`2f3369f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffa100`12617be0 00000000`00000000 : ffffa100`12618000 ffffa100`12611000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8032f2eb840 - nt!MmAccessFault+bc0
[ f6:c4 ]
fffff8032f417eab - nt!MiValidFault+12db3b (+0x12c66b)
[ f6:c4 ]
2 errors : !nt (fffff8032f2eb840-fffff8032f417eab)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2019-03-07T13:12:26.000Z
OSBUILD: 15063
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-01 01:44:54
BUILDDATESTAMP_STR: 170317-1834
BUILDLAB_STR: rs2_release
BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
ANALYSIS_SESSION_ELAPSED_TIME: 1ef2
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
2: kd> !pte ffffdb80b4c71130
VA ffffdb80b4c71130
PXE at FFFFF6FB7DBEDDB8 PPE at FFFFF6FB7DBB7010 PDE at FFFFF6FB76E02D30 PTE at FFFFF6EDC05A6388
Unable to get PXE FFFFF6FB7DBEDDB8
2: kd> !pte fffff80f8aaee981
VA fffff80f8aaee981
PXE at FFFFF6FB7DBEDF80 PPE at FFFFF6FB7DBF01F0 PDE at FFFFF6FB7E03E2A8 PTE at FFFFF6FC07C55770
Unable to get PXE FFFFF6FB7DBEDF80
2: kd> r @cr2
cr2=ffffdb80b4c71130
2: kd> kv
# Child-SP RetAddr : Args to Child : Call Site
00 ffffa100`126172a8 fffff803`2f417e86 : 00000000`00000050 ffffdb80`b4c71130 00000000`00000000 ffffa100`12617540 : nt!KeBugCheckEx
01 ffffa100`126172b0 fffff803`2f2eb766 : 00000000`00000000 ffffdb80`b4c71130 ffffa100`12617540 ffff800a`19429680 : nt!MiSystemFault+0x12e8c6
02 ffffa100`12617350 fffff803`2f3f2772 : fffff80f`87380000 fffff80f`873b8e8b 00000000`00001000 ffffdb80`94b72980 : nt!MmAccessFault+0xae6
03 ffffa100`12617540 fffff80f`8aaee981 : ffff800a`20d2b300 fffff803`2f7b804f 00000000`00000000 ffffdb80`94c71301 : nt!KiPageFault+0x132 (TrapFrame @ ffffa100`12617540)
04 ffffa100`126176d0 fffff80f`8aaecfbd : ffffdb80`b4c71010 00000000`00000000 00000000`00000001 ffffdb80`b4c71010 : rdbss!_RxAcquireFcb+0x51
05 ffffa100`12617750 fffff80f`8aae96ae : ffffdb80`94c74000 00000000`00000000 00000000`0062f124 00000000`00000000 : rdbss!RxpDereferenceAndFinalizeNetFcb+0x24d
06 ffffa100`126177f0 fffff80f`8aae8f0c : 00000000`00000000 ffffa100`00000082 ffff800a`20d2b648 fffff803`2f291951 : rdbss!RxScavengeRelatedFobxs+0x33e
07 ffffa100`126179d0 fffff80f`8aae8db4 : ffff800a`20d2b300 ffff800a`20d2b648 00000000`00000000 ffff800a`1e1e2900 : rdbss!RxScavengerFinalizeEntries+0x8c
08 ffffa100`12617a40 fffff80f`8aab1b53 : ffff800a`20d2b790 00000000`00000000 ffff800a`1e678a70 ffff800a`1bde5940 : rdbss!RxScavengerTimerRoutine+0x94
09 ffffa100`12617aa0 fffff803`2f29c1c8 : ffff800a`1e1e27c0 fffff80f`8aab1ac0 ffff800a`20d2b790 fffff803`2f5e8f20 : rdbss!RxpProcessWorkItem+0x93
0a ffffa100`12617b00 fffff803`2f336a37 : 00000000`00000000 00000000`00000080 ffff800a`19429680 ffff800a`1e1e27c0 : nt!ExpWorkerThread+0xd8
0b ffffa100`12617b90 fffff803`2f3ee3f6 : ffffa100`0d828180 ffff800a`1e1e27c0 fffff803`2f3369f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
0c ffffa100`12617be0 00000000`00000000 : ffffa100`12618000 ffffa100`12611000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
2: kd> .trap ffffa100`12617540
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80f8aad9000 rbx=0000000000000000 rcx=ffffdb80b4c71010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80f8aaee981 rsp=ffffa100126176d0 rbp=0000000000000001
r8=0000000000000001 r9=0000000000000000 r10=0000000000000704
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
rdbss!_RxAcquireFcb+0x51:
fffff80f`8aaee981 488b8120010000 mov rax,qword ptr [rcx+120h] ds:ffffdb80`b4c71130=????????????????
Code:
Loading Dump File [F:\030919-20937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`a8808000 PsLoadedModuleList = 0xfffff801`a8b545a0
Debug session time: Sat Mar 9 07:56:48.295 2019 (UTC + 1:00)
System Uptime: 1 days 17:43:55.409
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffff88028de817c0, 0, 0, 0}
ETW minidump data unavailable
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff88028de817c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
ETW minidump data unavailable
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP ProOne 600 G2 21.5-in Touch AiO
SYSTEM_SKU: L3N89AV
BIOS_VENDOR: HP
BIOS_VERSION: N12 Ver. 02.15
BIOS_DATE: 11/01/2016
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 805E
BASEBOARD_VERSION: KBC Version 05.22
DUMP_TYPE: 2
BUGCHECK_P1: ffff88028de817c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: svchost.exe
CRITICAL_PROCESS: svchost.exe
EXCEPTION_CODE: (NTSTATUS) 0x91d3a7c0 - <Unable to get error code text>
ERROR_CODE: (NTSTATUS) 0x91d3a7c0 - <Unable to get error code text>
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 8A'00000000 (cache) 8A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xEF
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-09-2019 13:37:58.0976
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff801a8ee8521 to fffff801a8973f70
STACK_TEXT:
ffffaa01`359e1908 fffff801`a8ee8521 : 00000000`000000ef ffff8802`8de817c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffaa01`359e1910 fffff801`a8e05aa9 : ffff8802`8de817c0 00000000`00000000 ffff8802`8de817c0 00007fff`7a0a00e2 : nt!PspCatchCriticalBreak+0xc9
ffffaa01`359e1960 fffff801`a8c9a666 : ffff8802`00000000 ffff8802`8de817c0 00000000`00000000 ffff8802`8de817c0 : nt!PspTerminateAllThreads+0x16d675
ffffaa01`359e19d0 fffff801`a8c9a75b : ffffffff`ffffffff ffff8802`8de817c0 ffff8802`8f6127c0 ffffab26`d3173201 : nt!PspTerminateProcess+0xde
ffffaa01`359e1a10 fffff801`a897ee13 : ffff8802`8de817c0 ffff8802`91d3a7c0 ffffaa01`359e1b00 00007fff`6fa42148 : nt!NtTerminateProcess+0xa7
ffffaa01`359e1a80 00007fff`7a085934 : 00007fff`76576169 00000000`00000000 00007fff`6fa42148 00000000`000000a4 : nt!KiSystemServiceCopyEnd+0x13
00000066`0c97e5d8 00007fff`76576169 : 00000000`00000000 00007fff`6fa42148 00000000`000000a4 00007fff`6fa42148 : 0x00007fff`7a085934
00000066`0c97e5e0 00000000`00000000 : 00007fff`6fa42148 00000000`000000a4 00007fff`6fa42148 00000000`000000a4 : 0x00007fff`76576169
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
4 errors : !nt (fffff801a8829571-fffff801a8829604)
fffff801a8829570 ff *7f *f5 ff ff 48 3b d0 77 d5 32 c0 eb d3 cc cc .....H;.w.2.....
...
fffff801a8829600 00 00 00 *00 *f5 ff ff 48 8b f3 48 03 e9 48 c1 ee .......H..H..H..
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_STRIDE
TARGET_TIME: 2019-03-09T06:56:48.000Z
OSBUILD: 15063
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-01 01:44:54
BUILDDATESTAMP_STR: 170317-1834
BUILDLAB_STR: rs2_release
BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
ANALYSIS_SESSION_ELAPSED_TIME: 1f31
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_stride
FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}
Followup: memory_corruption
---------
0: kd> !process ffff88028de817c0
PROCESS ffff88028de817c0
SessionId: 0 Cid: 025c Peb: e56bbbf000 ParentCid: 0334
DirBase: 2278f2000 ObjectTable: ffffd48f808d9840 HandleCount: <Data Not Accessible>
Image: svchost.exe
VadRoot ffff88028f587aa0 Vads 87 Clone 0 Private 1489. Modified 6204. Locked 2.
DeviceMap ffffd48f8091e5a0
Token ffffd48f80972060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 138312
QuotaPoolUsage[NonPagedPool] 19112
Working Set Sizes (now,min,max) (0, 0, 0) (0KB, 0KB, 0KB)
PeakWorkingSetSize 0
VirtualSize 2097210 Mb
PeakVirtualSize 2097215 Mb
PageFaultCount 0
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 1705
*** Error in reading nt!_ETHREAD @ ffff88028de827c0
Code:
Loading Dump File [F:\030919-22718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`d7216000 PsLoadedModuleList = 0xfffff800`d75625a0
Debug session time: Sat Mar 9 08:03:36.982 2019 (UTC + 1:00)
System Uptime: 0 days 0:06:16.731
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 12B, {ffffffffc00002c4, 83c, bf0000, ffffdd012b126000}
Probably caused by : ntkrnlmp.exe ( nt!ST_STORE<SM_TRAITS>::StDmPageError+117 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 000000000000083c, physical page number
Arg3: 0000000000bf0000, zero
Arg4: ffffdd012b126000, zero
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP ProOne 600 G2 21.5-in Touch AiO
SYSTEM_SKU: L3N89AV
BIOS_VENDOR: HP
BIOS_VERSION: N12 Ver. 02.15
BIOS_DATE: 11/01/2016
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 805E
BASEBOARD_VERSION: KBC Version 05.22
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc00002c4
BUGCHECK_P2: 83c
BUGCHECK_P3: bf0000
BUGCHECK_P4: ffffdd012b126000
BUGCHECK_STR: 0x12B_c00002c4_StCtDecompressFailed
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 8A'00000000 (cache) 8A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-09-2019 13:40:34.0180
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff800d745e777 to fffff800d7381f70
STACK_TEXT:
ffffdd01`2c3687e8 fffff800`d745e777 : 00000000`0000012b ffffffff`c00002c4 00000000`0000083c 00000000`00bf0000 : nt!KeBugCheckEx
ffffdd01`2c3687f0 fffff800`d73c44b9 : 00000000`00000200 00000000`00000003 00000000`00bf0000 ffffdd01`2b126000 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x117
ffffdd01`2c368840 fffff800`d72cc7bf : 00000000`00000000 ffffdd01`2c368a58 00000000`00000000 00000000`0000005a : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xf7cc5
ffffdd01`2c368920 fffff800`d72cc1ab : 00000000`00000001 00000000`00000000 ffffb50f`00000000 00000000`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b
ffffdd01`2c368970 fffff800`d72cbf7c : ffffdd01`ffffffff ffffb50f`d213c000 ffffdd01`2c368a58 ffffb50f`d4961d80 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x183
ffffdd01`2c368a10 fffff800`d72cdbef : ffffb50f`d4961d80 00000000`00000000 ffffb50f`00000000 ffffb50f`d4961d80 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x98
ffffdd01`2c368ad0 fffff800`d72f40ca : ffffb50f`d26b0000 ffffffff`fffffff8 ffffb50f`d4961d80 ffffb50f`d26b1960 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x6f
ffffdd01`2c368b20 fffff800`d72cfa37 : ffffb50f`d2106080 00000000`00000080 fffff800`d72f3f60 ffffdd01`2bd17218 : nt!SMKM_STORE<SM_TRAITS>::SmStReadThread+0x16a
ffffdd01`2c368b90 fffff800`d73873f6 : ffffdd01`282d4180 ffffb50f`d2106080 fffff800`d72cf9f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffdd01`2c368be0 00000000`00000000 : ffffdd01`2c369000 ffffdd01`2c362000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: ea702371902282a3e09bedf8feed8aed914004b5
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6fdc6c99a139c7f4c7f333afb202480f305e338d
THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406
FOLLOWUP_IP:
nt!ST_STORE<SM_TRAITS>::StDmPageError+117
fffff800`d745e777 cc int 3
FAULT_INSTR_CODE: 448b44cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+117
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 58dee9f6
IMAGE_VERSION: 10.0.15063.138
BUCKET_ID_FUNC_OFFSET: 117
FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
PRIMARY_PROBLEM_CLASS: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
TARGET_TIME: 2019-03-09T07:03:36.000Z
OSBUILD: 15063
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-01 01:44:54
BUILDDATESTAMP_STR: 170317-1834
BUILDLAB_STR: rs2_release
BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
ANALYSIS_SESSION_ELAPSED_TIME: 1bd7
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x12b_c00002c4_stctdecompressfailed_nt!st_store_sm_traits_::stdmpageerror
FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
Followup: MachineOwner
---------RAM memory with memtest 86+ - Test RAM With Memtest86+
S.M.A.R.T with HD Tune - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
And update BIOS to version 02.37 - Komputer HP ProOne 600 G2 21,5" Touch All-in-One - Pobieranie sterowników | Pomoc techniczna HP® dla klientów
Memtest : no error
Hd Tune : clean, no error
But Sfc scannow result:
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Hd Tune : clean, no error
But Sfc scannow result:
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Hi. . .
We need this run before we can continue with anything - Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista
Please attach the output zip file to your next post.
Thank you.
Regards. . .
jcgriff2
p.s. Also - run SeaTools for DOS, LONG test - HDD - SeaTools for DOS, LONG test - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
Did you run memtest86+ one stick at a time; alternate the slots?
One of the dumps - 0x12b -
We need this run before we can continue with anything - Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista
Please attach the output zip file to your next post.
Thank you.
Regards. . .
jcgriff2
p.s. Also - run SeaTools for DOS, LONG test - HDD - SeaTools for DOS, LONG test - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
Did you run memtest86+ one stick at a time; alternate the slots?
One of the dumps - 0x12b -
Last edited:
Hi,
Hi. . .
Thank you for the Sysnative zip file.
For the BSODs, it looks like the hardware tests passed.
That leaves us with the motherboard, PSU, cables, wiring. But one dump said:
Please create a thread in the Windows Update forum to get SFC clean, assuming that you don't BSOD while running their apps to fix the corrupted files.
Then return here and give us the Windows Update thread.
Follow these instructions - Windows Update Forum Posting Instructions
Regards. . .
jcgriff2
Thank you for the Sysnative zip file.
For the BSODs, it looks like the hardware tests passed.
That leaves us with the motherboard, PSU, cables, wiring. But one dump said:
Please create a thread in the Windows Update forum to get SFC clean, assuming that you don't BSOD while running their apps to fix the corrupted files.
Then return here and give us the Windows Update thread.
Follow these instructions - Windows Update Forum Posting Instructions
Regards. . .
jcgriff2
Has Sysnative Forums helped you? Please consider donating to help us support the site!