• Now's your chance win big! Join our community and get entered to win a RTX 2060 GPU, plus more! Join here.

    Pi Cast Episode 3 streams live on Tuesday, August 4th at 2:30 pm ET (7:30 PM BST). Watch live right here!

    Catch Scharon on the Tom's Hardware Show live on Thursday, August 6th at 2:00 pm ET (7:00 PM BST). Click here!

Question BSOD Kernel Secuirty Check - BUGCHECK_ERROR 139 parameter 3 from minidump

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
Laptop : Acer aspire E-5 551-G

CPU: Amd a10 with r6 integrated graphics

GPU: Amd r7 dedicated graphics card

1tb hdd

8gb ram


Context: My dedicated graphic card is toast, so i had to disable it from device manager and set group policy settings to never allow its driver installation by using the hardware id. If i allow it windows tries to install drivers on it and it causes bsods 100% of the times

rendering my laptop unusable. Above is the device manager screenshot where video controller is the disabled driverless r7 gpu.


Now doing this fixes the issue as my integrated gpu and cpu are working fine, but after using the laptop for a while i get a bsod (memory minidump details will follow below), im guessing its a driver issue (or a hdd issue,cant think of anything else), how do i solve it and is there any other workaround to isolate the burnt dedicated gpu and use the cpu and integrated gpu for everything. Thanks!


Minidump :
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_44568a8409df1b30, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_44568a84
09df1b30
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80057c00000 PsLoadedModuleList = 0xfffff8005882a2b0
Debug session time: Tue Jul 7 21:21:02.182 2020 (UTC + 5:30)
System Uptime: 0 days 6:54:27.852
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_44568a8409df1b30, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_44568a84
09df1b30
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141

Image path too long, possible corrupt data.
Loading unloaded module list
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
...Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
...Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
....Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.....Image path too long, possible corrupt data.
.
WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000141
CS descriptor lookup failed
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
For analysis of this file, run !analyze -v
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get program counter
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
fffff800
57fdda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0000000000000008=????????????????
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
0: kd> !analyze
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get program counter
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could 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: ffffe003f3a2f5d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffe003f3a2f528, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Page 0 not present in the dump file. Type ".hh dbgerr004" for details
Page 5007400730 too large to be in the dump file.
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 4e5f67db
1f891cd2 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe003f3a2f5d0

BUGCHECK_P3: ffffe003f3a2f528

BUGCHECK_P4: 0

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x139

FAILURE_ID_HASH: {bec1bc00-1c8a-a417-55b2-9f8b67cbb1c5}

Followup: MachineOwner
---------

GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
 

Colif

Win 10 Master
Moderator
all those unknown modules in error don't really help.

Do you happen to know if you have latest BIOS? at least the bios won't try to use the R7, so you can at least get into it.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

Memory dumps can be really large, minidumps max is a few mb, easier for my friend to download.
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
all those unknown modules in error don't really help.

Do you happen to know if you have latest BIOS? at least the bios won't try to use the R7, so you can at least get into it.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

Memory dumps can be really large, minidumps max is a few mb, easier for my friend to download.
Update:
(memory dump does'nt go through when kernel security check bsod occurs as screen turns off at around 30% so i force shutdown pressing the power button for a couple of seconds, after restarting i get a bsod soon enough with different bugcheck code

(small minidump link below)
https://1drv.ms/u/s!Ahtff0c6L85df9_aDJjSRRMXWE8?e=EKzpzG

(full minidump link below)
https://1drv.ms/u/s!Ahtff0c6L85dflwIMw408YIU3EM?e=cqk6Fs
 
Last edited:

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/mwVL1MTT

File information:071620-42718-01.dmp (Jul 16 2020 - 13:43:03)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 24 Sec(s)

File information:MEMORY.DMP (Jul 16 2020 - 13:43:03)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 24 Sec(s)

Possible system page: https://www.acer.com/ac/en/ID/content/support-product/5403;-;Aspire E5-551G
You have the latest BIOS already installed, version 1.15.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: sariaabdeali

Colif

Win 10 Master
Moderator
Both errors happened in Superfetch

Any old driver could be the cause. You have a few.

May 05 2015 - rt640x64.sys - Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
May 29 2015 - RtsPer.sys - Realtek RTS PCIE Reader driver https://www.realtek.com/en/
Jun 29 2015 - btfilter.sys - Qualcomm Atheros BT Filter driver https://www.qualcomm.com/
Jul 07 2015 - AtihdWT6.sys - AMD High Definition Audio Function driver http://support.amd.com/
Jul 21 2015 - RTKVHD64.sys - Realtek Audio System driver https://www.realtek.com/en/
Jul 29 2015 - SynRMIHID.sys - Synaptics I2C Driver (Synaptics Incorporated) https://www.symantec.com/
Jan 28 2016 - athw8x.sys - Atheros Wireless LAN driver (Qualcomm)


I doubt there is a newer card reader driver

Do you use WIFI or Ethernet?

Ethernet drivers are from 2015
there are newer on here - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

Wifi are from 2016
Up until recently I would have put a killer driver here as a suggestion but Intel bought them and seem to have removed that support... sigh. The WIFI driver on Acer site is older than what is installed.

Should be newer Realtek sound drivers, https://www.tenforums.com/sound-audio/135259-latest-realtek-hd-audio-driver-version-2-a.html

not sure about that AMD sound driver? probably part of the GPU drivers?
Touchpad drivers might be fun to find.
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
Both errors happened in Superfetch

Any old driver could be the cause. You have a few.

May 05 2015 - rt640x64.sys - Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
May 29 2015 - RtsPer.sys - Realtek RTS PCIE Reader driver https://www.realtek.com/en/
Jun 29 2015 - btfilter.sys - Qualcomm Atheros BT Filter driver https://www.qualcomm.com/
Jul 07 2015 - AtihdWT6.sys - AMD High Definition Audio Function driver http://support.amd.com/
Jul 21 2015 - RTKVHD64.sys - Realtek Audio System driver https://www.realtek.com/en/
Jul 29 2015 - SynRMIHID.sys - Synaptics I2C Driver (Synaptics Incorporated) https://www.symantec.com/
Jan 28 2016 - athw8x.sys - Atheros Wireless LAN driver (Qualcomm)


I doubt there is a newer card reader driver

Do you use WIFI or Ethernet?

Ethernet drivers are from 2015
there are newer on here - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

Wifi are from 2016
Up until recently I would have put a killer driver here as a suggestion but Intel bought them and seem to have removed that support... sigh. The WIFI driver on Acer site is older than what is installed.

Should be newer Realtek sound drivers, https://www.tenforums.com/sound-audio/135259-latest-realtek-hd-audio-driver-version-2-a.html

not sure about that AMD sound driver? probably part of the GPU drivers?
Touchpad drivers might be fun to find.
Thanks for replying,i'll try and update the drivers you've listed.
imp INFO : I've noticed this bsod happens mostly when laptop is left idle
 

gardenman

Admirable
Moderator
I ran the minidump file through the debugger and got the following information: https://pastebin.com/hVAGvZgD

File information:071620-42718-01.dmp (Jul 16 2020 - 13:43:03)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 24 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
Try running memtest86 on your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

better safe than sorry. superfetch process mentioned again in stack text, it runs at idle...
SuperFetch simply preloads and makes programs you use more often quick to access. It also enables background programs, defragmenting for example, to run in the background while you do your work.
https://winbuzzer.com/2020/03/14/windows-10-how-to-disable-enable-prefetch-and-superfetch-xcxwbt/

it loads the programs you most often use into ram so that they start up faster. Helpful on PC with hdd. I am not suggesting you disable it yet, just showing what it is.

Maybe try testing the hdd as well as its counted as memory by windows, so perhaps it is cause as well. I don't believe its ram as majority of the time, ram is more random with what it blames, and last 3 have been all SuperFetch.
try this
HD Sentinel - https://www.hdsentinel.com/hard_disk_sentinel_trial.php

knowing what processes it is trying to run would help narrow cause. Did you run that sysnative program as it should have created a zip file. Can you upload that as well? It might give some insight into whats happening on your pc.

it could still be a driver, the lan/wifi drivers could still be cause.

I don't think its related to the GPU problem.
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
Try running memtest86 on your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

better safe than sorry. superfetch process mentioned again in stack text, it runs at idle...


https://winbuzzer.com/2020/03/14/windows-10-how-to-disable-enable-prefetch-and-superfetch-xcxwbt/

it loads the programs you most often use into ram so that they start up faster. Helpful on PC with hdd. I am not suggesting you disable it yet, just showing what it is.

Maybe try testing the hdd as well as its counted as memory by windows, so perhaps it is cause as well. I don't believe its ram as majority of the time, ram is more random with what it blames, and last 3 have been all SuperFetch.
try this
HD Sentinel - https://www.hdsentinel.com/hard_disk_sentinel_trial.php

knowing what processes it is trying to run would help narrow cause. Did you run that sysnative program as it should have created a zip file. Can you upload that as well? It might give some insight into whats happening on your pc.

it could still be a driver, the lan/wifi drivers could still be cause.

I don't think its related to the GPU problem.
Sysnative Zip (One drive link)
https://1drv.ms/u/s!Ahtff0c6L85dgQJrTyhuBDEA3VkN?e=uFuzLq

Thanks for replying!
 

Colif

Win 10 Master
Moderator
One of the errors on 16th says Zero Page Corrupted Image Hardware ram, it happened at startup. You appear to have started PC twice in a row, and then error happened (although order of error reporting could be wrong).

on 18th Windows ram Memory diagnostics and seems to run into a problem.
run memtest
try running this on the hdd - https://support.wdc.com/downloads.aspx?p=3

BSOD in June could point to it being LAN drivers in that case (zip file doesn't include dumps that far back)
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
One of the errors on 16th says Zero Page Corrupted Image Hardware ram, it happened at startup. You appear to have started PC twice in a row, and then error happened (although order of error reporting could be wrong).

on 18th Windows ram Memory diagnostics and seems to run into a problem.
run memtest
try running this on the hdd - https://support.wdc.com/downloads.aspx?p=3

BSOD in June could point to it being LAN drivers in that case (zip file doesn't include dumps that far back)
memtest 4 pass , hw sentinel and wd dlg extended test come clean without errors.
have a few outdated drivers, will update and inform in a couple days if bsod occurs. Thanks for helping.
 
Last edited:

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
One of the errors on 16th says Zero Page Corrupted Image Hardware ram, it happened at startup. You appear to have started PC twice in a row, and then error happened (although order of error reporting could be wrong).

on 18th Windows ram Memory diagnostics and seems to run into a problem.
run memtest
try running this on the hdd - https://support.wdc.com/downloads.aspx?p=3

BSOD in June could point to it being LAN drivers in that case (zip file doesn't include dumps that far back)
1st bsod : intentionally left laptop idle after updating some network drivers, same bsod occurred as expected (only uploading this new bsod because i had turned driver verifier on for better bsod info on which driver is causing it)
https://1drv.ms/u/s!Ahtff0c6L85dgQUOPAzUO-H8_awI?e=RXe7iV

2nd bsod : tried updating r6 drivers, it seems r6 and r7 drivers are bundled together so after installing r6 , it tried installing r7 drivers too, which caused bsod i have blocked that using hw id in group policy and registery.
https://1drv.ms/u/s!Ahtff0c6L85dgQR62K9vgqlHEsu3?e=VmjyvW

touchpad and mice are the only 2 drivers left to be updated.
What do i do next? Thanks!
 

gardenman

Admirable
Moderator
Hi, I ran the dump file(s) through the debugger and got the following information: https://pastebin.com/F2iZN1cY

File information:072320-39203-01.dmp (Jul 23 2020 - 03:15:56)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for atikmpag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 25 Min(s), and 43 Sec(s)

File information:072320-33953-01.dmp (Jul 22 2020 - 09:37:55)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 3 Hour(s), 00 Min(s), and 15 Sec(s)

Comment: New driver I haven't seen before - Jun 09 2020 - amdfendr.sys - AMD Crash Defender Service driver

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: sariaabdeali

Colif

Win 10 Master
Moderator
well, 1st crash was GPU drivers

How new are the drivers?
Aug 16 2019 - atikmdag.sys - ATI Radeon Kernel Mode driver
Aug 16 2019 - atikmpag.sys - ATI video card driver
look old but I suspect
Jun 01 2020 - AtihdWT6.sys - AMD High Definition Audio Function driver http://support.amd.com/
Jun 02 2020 - amdxe.sys - AMD Link Xinput Emulation driver
Jun 09 2020 - amdfendr.sys - AMD Crash Defender Service driver
are also part of the driver package...

try running ddu and install older drivers. How you do that with a disabled GPU is a good question as ddu runs in safe mode and likely try to use broken GPU.

Not sure about 2nd bsod. Not so obvious.
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
well, 1st crash was GPU drivers

How new are the drivers?
Aug 16 2019 - atikmdag.sys - ATI Radeon Kernel Mode driver
Aug 16 2019 - atikmpag.sys - ATI video card driver
look old but I suspect
Jun 01 2020 - AtihdWT6.sys - AMD High Definition Audio Function driver http://support.amd.com/
Jun 02 2020 - amdxe.sys - AMD Link Xinput Emulation driver
Jun 09 2020 - amdfendr.sys - AMD Crash Defender Service driver
are also part of the driver package...

try running ddu and install older drivers. How you do that with a disabled GPU is a good question as ddu runs in safe mode and likely try to use broken GPU.

Not sure about 2nd bsod. Not so obvious.
if hdd and ram are both fine, then why is this happening. Below is the link for the bsod that happened yesterday while i was browsing so the bsod occurred even when laptop was not idle. Please help i have no idea what to next..disable superfetch maybe?
sorry if these daily bsod links are annoying and thanks for helping.
https://1drv.ms/u/s!Ahtff0c6L85dgQazePRXA_GodG3v?e=8lATNE
 

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://pastebin.com/n7irdK9z

File information:072420-48796-01.dmp (Jul 23 2020 - 08:44:37)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 5 Hour(s), 14 Min(s), and 56 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
if hdd and ram are both fine, then why is this happening.
it could be a driver that is just not showing its head in the dumps. Sometimes it just takes time to figure out which driver is to blame as a lot of the time, the error text just mentions windows

Its possible its the GPU driver that crashed on the 23rd, since its still there.

Getting a crash every day is likely more annoying for you than it is me, and maybe one of them might show a driver name.

If you get impatient waiting for it, you could read my 2nd post in this thread but although the process is built into win 10, it can cause boot loops, so its why I have steps in post I suggest you take, and why I don't suggest it right away or without caution - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
it could be a driver that is just not showing its head in the dumps. Sometimes it just takes time to figure out which driver is to blame as a lot of the time, the error text just mentions windows

Its possible its the GPU driver that crashed on the 23rd, since its still there.

Getting a crash every day is likely more annoying for you than it is me, and maybe one of them might show a driver name.

If you get impatient waiting for it, you could read my 2nd post in this thread but although the process is built into win 10, it can cause boot loops, so its why I have steps in post I suggest you take, and why I don't suggest it right away or without caution - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/
  1. ddu worked fine in safe mode, after rebooting i let windows install the driver from device manager. r7 still has no driver and disabled.
  2. I disabled Sysmain service which i am told is the new name for superfetch.
:) now even after superfetch was disabled the same bsod occurred. HELPPPPPPP!!!!
minidump for the same:
https://1drv.ms/u/s!Ahtff0c6L85dgQj46ay9af2FsQW7?e=0q8eMi

additional info (idk if useful) :
  1. since the laptop is 4 and a half year old the battery is very close to death (71% wear acc. to hwmonitor)
  2. I had loose wires in the switch where my adapter was plugged which i used for charging.(so i have been charging my laptop with bad current for too long)
  3. Disassembled the laptop and found the connector from the charging port to the motherboard is burnt (image below).
  4. Orange battery light starts blinking sometimes when charging laptop even now...they stop blinking when i plug adapter to some other switch (doesnt matter which one). So, im thinking of getting a new battery for sure and checking whether the charging port connector needs to be changed and even the adapter.
(i dont know if this info is useful or not but i thought i should just let you know)
image of connector:
https://1drv.ms/u/s!Ahtff0c6L85dgQlICBAHUlcN__M2?e=S8bhZf
Thanks for helping. again.
 
Last edited:

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://pastebin.com/thArCA2r

File information:073120-34015-01.dmp (Jul 30 2020 - 12:50:54)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: csrss.exe)
Uptime:0 Day(s), 2 Hour(s), 23 Min(s), and 42 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: sariaabdeali

sariaabdeali

Prominent
Jan 21, 2019
12
0
510
0
csrss.exe = the client your user runs in. It isn't a great help for isolating the cause.

I wish dump told me more.
new bsod looks same as all bsods
https://1drv.ms/u/s!Ahtff0c6L85dgQqnBHsj9FJsD4aK?e=zfIheq
I think i might have overclocked/turned on amd turbocore on my laptop cpu using AMD Overdrive a long time ago so i have reset that by power plan max processor state to 99% and i have also disabled driver verifier now.
Do tell if you find something from this new bsod minidump . Thanks!
 
Last edited:

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://pastebin.com/PpetJE2y

File information:080620-38343-01.dmp (Aug 6 2020 - 04:31:04)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: firefox.exe)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 34 Sec(s)

Comment: Verifier was still on when this dump was created.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

ASK THE COMMUNITY

TRENDING THREADS