D
DHG Affinity
Starting two nights ago, I have been getting consistent blue screen's at random intervals while using my computer. And the most confusing part is that there's been a variety of different stop codes. And to top it off, some other miscellaneous issues have occurred, such as: programs are sometimes randomly crashing, windows update refuses to run, windows defender does not work in safe mode, wifi does not work in safe mode, google chrome pages are often crashing, larger downloads are becoming corrupted, and more. I'm kind of at the end of my rope here so I'm looking for any help. I'm able to use my computer for a little while before it crashes so I can still do some things, but anything requiring a large download won't work while that problem persists. I tried a system restore in safe mode and got a BSOD during it. I've tried running Windows Memory Diagnostic, it found no errors. RogueKiller was able to successfully scan in Safe Mode and found some threats but after removal nothings changed (as a side note Safe Mode seems more stable but I can't use the internet while in it). I uninstalled my nvidia display driver but it didn't seem to do anything and I can't update it now because the download has corrupted 6/6 times. My hard drive seems okay judging by CrystalDiskInfo, and my temperatures seem to be normal judging by Core Temp.
Here's the WhoCrashed report if it helps:
On Sun 3/24/2019 7:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-35109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x19 (0xE, 0xFFFF868750712A10, 0xE32089485476234D, 0xE32089685476234D)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 7:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ExFreePoolWithTag+0xCAB)
Bugcheck code: 0x19 (0xE, 0xFFFF868750712A10, 0xE32089485476234D, 0xE32089685476234D)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 7:20:42 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-42234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x19 (0xD, 0xFFFFBC0691BFBBB0, 0x46EC304AEFF5BBFB, 0x46EC305AEFF5BBFB)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 12:27:34 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-40453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xEF (0xFFFFBF0A16990080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 11:26:21 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-42031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x50 (0xFFFF97AE838A4080, 0x0, 0xFFFFF803EE188516, 0xC)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 11:11:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-95062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x1A (0x404, 0xFFFF865C071BD718, 0x8A0000018E4DD863, 0xFFFF864C071BD718)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 10:17:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-43406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xEF (0xFFFF868156CE3080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 9:02:23 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-39906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x139 (0x2, 0xFFFF8703BA18D950, 0xFFFF8703BA18D8A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...
Here's the WhoCrashed report if it helps:
On Sun 3/24/2019 7:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-35109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x19 (0xE, 0xFFFF868750712A10, 0xE32089485476234D, 0xE32089685476234D)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 7:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ExFreePoolWithTag+0xCAB)
Bugcheck code: 0x19 (0xE, 0xFFFF868750712A10, 0xE32089485476234D, 0xE32089685476234D)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 7:20:42 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-42234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x19 (0xD, 0xFFFFBC0691BFBBB0, 0x46EC304AEFF5BBFB, 0x46EC305AEFF5BBFB)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/24/2019 12:27:34 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032419-40453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xEF (0xFFFFBF0A16990080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 11:26:21 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-42031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x50 (0xFFFF97AE838A4080, 0x0, 0xFFFFF803EE188516, 0xC)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 11:11:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-95062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x1A (0x404, 0xFFFF865C071BD718, 0x8A0000018E4DD863, 0xFFFF864C071BD718)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 10:17:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-43406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xEF (0xFFFF868156CE3080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/23/2019 9:02:23 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032319-39906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x139 (0x2, 0xFFFF8703BA18D950, 0xFFFF8703BA18D8A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...