F5F Stay Refreshed Hardware Desktop The system occasionally allows access to my PC, but often blocks me...

The system occasionally allows access to my PC, but often blocks me...

The system occasionally allows access to my PC, but often blocks me...

S
Stealsz
Member
126
09-10-2016, 07:36 AM
#1
Hi, first time poster on here.
Been racking my brain for the past few days trying to solve a fairly recent BSOD that won't go away. Some background to the issue:
My PC was working perfectly fine with no issues at all until I recently uninstalled Avast and switched to Defender as I felt as if I didn't need Avast anymore (uninstalled Avast through programs and features and didn't realise there was a specific tool you could use for it until after). I let Defender do an intelligence update and then a Windows update shortly followed, this update reversed itself around halfway through (rough estimate as I wasn't really looking), my PC shut down, and since, I've been having a SYSTEM THREAD EXCEPTION NOT HANDLED 0x000007E BSOD plague my startup.
I've done multiple system restores from a restore point that was automatically made when my PC booted after one of the BSOD's took place, tried to diagnose/fix the issue using the usual chkdsk, DISM checks, sfc, Windows Memory Diagnostic etc. to no avail. I checked the crashdump in WhoCrashed and it said that ntoskrnl.exe was causing the issue (which as far as I understand is very generic). The system restore that I had to fall back on has since somehow disappeared. So I'm relying on Windows to boot sometimes (which it still does occasionally) to use my PC. Hoping that someone a bit more versed in diagnosing/fixing these issues can help!
A link to my crashdumps:
https://drive.google.com/drive/u/0/folde...4WSnVrn6kO
Just realised I may have posted this in the wrong section also, apologies if so.
S
Stealsz
09-10-2016, 07:36 AM #1

Hi, first time poster on here.
Been racking my brain for the past few days trying to solve a fairly recent BSOD that won't go away. Some background to the issue:
My PC was working perfectly fine with no issues at all until I recently uninstalled Avast and switched to Defender as I felt as if I didn't need Avast anymore (uninstalled Avast through programs and features and didn't realise there was a specific tool you could use for it until after). I let Defender do an intelligence update and then a Windows update shortly followed, this update reversed itself around halfway through (rough estimate as I wasn't really looking), my PC shut down, and since, I've been having a SYSTEM THREAD EXCEPTION NOT HANDLED 0x000007E BSOD plague my startup.
I've done multiple system restores from a restore point that was automatically made when my PC booted after one of the BSOD's took place, tried to diagnose/fix the issue using the usual chkdsk, DISM checks, sfc, Windows Memory Diagnostic etc. to no avail. I checked the crashdump in WhoCrashed and it said that ntoskrnl.exe was causing the issue (which as far as I understand is very generic). The system restore that I had to fall back on has since somehow disappeared. So I'm relying on Windows to boot sometimes (which it still does occasionally) to use my PC. Hoping that someone a bit more versed in diagnosing/fixing these issues can help!
A link to my crashdumps:
https://drive.google.com/drive/u/0/folde...4WSnVrn6kO
Just realised I may have posted this in the wrong section also, apologies if so.

M
MrCringles
Member
154
09-14-2016, 10:49 PM
#2
Your system specifications are available. Sometimes removing an antivirus might damage a disk or operating system. Have you used the Avast uninstall tool, which can still be effective after the program is removed? If the OS is faulty, it can be restored by reinstalling Windows via a USB installation media and choosing to retain all applications and settings.
M
MrCringles
09-14-2016, 10:49 PM #2

Your system specifications are available. Sometimes removing an antivirus might damage a disk or operating system. Have you used the Avast uninstall tool, which can still be effective after the program is removed? If the OS is faulty, it can be restored by reinstalling Windows via a USB installation media and choosing to retain all applications and settings.

L
Lordyouyou
Member
167
09-21-2016, 09:25 AM
#3
OS Name: Microsoft Windows 10 Home
Version: 10.0.19044 Build 19044
Other OS Description: Not Available
OS Manufacturer: Microsoft Corporation
System Name: DESKTOP-BRFUDNL
System Manufacturer: Dell Inc.
System Model: XPS 8900
System Type: x64-based PC
System SKU: 06B8
Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz, 4008 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date: Dell Inc. 2.0.3, 18/09/2015
SMBIOS Version: 2.8
Embedded Controller Version: 255.255
BIOS Mode: UEFI
BaseBoard Manufacturer: Dell Inc.
BaseBoard Product: 0XJ8C4
BaseBoard Version: A00
Platform Role: Desktop
Secure Boot State: On
PCR7 Configuration: Elevation Required to View
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume3
Locale: United States
Hardware Abstraction Layer: Version = "10.0.19041.2728"
User Name: DESKTOP-BRFUDNL\Grant Hill
Time Zone: GMT Daylight Time
Installed Physical Memory (RAM): 16.0 GB
Total Physical Memory: 15.9 GB
Available Physical Memory: 9.06 GB
Total Virtual Memory: 26.4 GB
Available Virtual Memory: 15.2 GB
Page File Space: 10.5 GB
Page File Path: C:\pagefile.sys
Kernel DMA Protection: Off
Virtualization-based security: Not enabled
Hyper-V - VM Monitor Mode Extensions: Yes
Hyper-V - Second Level Address Translation Extensions: Yes
Hyper-V - Virtualization Enabled in Firmware: Yes
Hyper-V - Data Execution Protection: Yes
The system appears to be from late 2015 or early 2016. I have also tried the Avast Uninstall tool, but it was undone because I needed to restore after another crash.
L
Lordyouyou
09-21-2016, 09:25 AM #3

OS Name: Microsoft Windows 10 Home
Version: 10.0.19044 Build 19044
Other OS Description: Not Available
OS Manufacturer: Microsoft Corporation
System Name: DESKTOP-BRFUDNL
System Manufacturer: Dell Inc.
System Model: XPS 8900
System Type: x64-based PC
System SKU: 06B8
Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz, 4008 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date: Dell Inc. 2.0.3, 18/09/2015
SMBIOS Version: 2.8
Embedded Controller Version: 255.255
BIOS Mode: UEFI
BaseBoard Manufacturer: Dell Inc.
BaseBoard Product: 0XJ8C4
BaseBoard Version: A00
Platform Role: Desktop
Secure Boot State: On
PCR7 Configuration: Elevation Required to View
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume3
Locale: United States
Hardware Abstraction Layer: Version = "10.0.19041.2728"
User Name: DESKTOP-BRFUDNL\Grant Hill
Time Zone: GMT Daylight Time
Installed Physical Memory (RAM): 16.0 GB
Total Physical Memory: 15.9 GB
Available Physical Memory: 9.06 GB
Total Virtual Memory: 26.4 GB
Available Virtual Memory: 15.2 GB
Page File Space: 10.5 GB
Page File Path: C:\pagefile.sys
Kernel DMA Protection: Off
Virtualization-based security: Not enabled
Hyper-V - VM Monitor Mode Extensions: Yes
Hyper-V - Second Level Address Translation Extensions: Yes
Hyper-V - Virtualization Enabled in Firmware: Yes
Hyper-V - Data Execution Protection: Yes
The system appears to be from late 2015 or early 2016. I have also tried the Avast Uninstall tool, but it was undone because I needed to restore after another crash.

F
ForDuckSakes
Member
52
09-21-2016, 09:50 AM
#4
RTX 2060 GPU also.
F
ForDuckSakes
09-21-2016, 09:50 AM #4

RTX 2060 GPU also.

H
Humhumm
Member
137
09-21-2016, 11:17 AM
#5
Your system isn't that outdated, but it requires maintenance to function correctly.
The minidumps lack substantial information; they all reference the same error code 0x1000007E pointing to ntkrnlmp.exe.
However, the root cause remains unclear. This issue might stem from missing drivers or updates, corrupted files, or a failing disk.
Could you ensure your BIOS and Windows 10 are updated to the latest versions, along with your hardware drivers?
Upgrading the hard drive to a SATA SSD would also be wise before it fails.
H
Humhumm
09-21-2016, 11:17 AM #5

Your system isn't that outdated, but it requires maintenance to function correctly.
The minidumps lack substantial information; they all reference the same error code 0x1000007E pointing to ntkrnlmp.exe.
However, the root cause remains unclear. This issue might stem from missing drivers or updates, corrupted files, or a failing disk.
Could you ensure your BIOS and Windows 10 are updated to the latest versions, along with your hardware drivers?
Upgrading the hard drive to a SATA SSD would also be wise before it fails.