Blue Screen of Deaths: Several in the span of hours.

[Inverted_Jesus]

This is a long one, I've been recently been getting blue screens when starting up my computer, I also recently updated my BIOS, I don't know if that has anything to do with it or not but it's happening.

 

I obtained these using WhoCrashed:

 

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 1/22/2020 11:35:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012220-9015-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8066948D829, 0xFFFF96866E7258B8, 0xFFFF96866E725100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 1/22/2020 11:35:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF8066948D829, 0xFFFF96866E7258B8, 0xFFFF96866E725100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sun 1/19/2020 5:06:30 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011920-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x5286CA, 0x2, 0x4300043BFC9)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 1/19/2020 12:16:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011920-10406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xBE (0xFFFFCF090E28EDA8, 0x8A00000004E00121, 0xFFFFA28B50F4D740, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 1/17/2020 11:13:34 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011720-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80413293A3F, 0xFFFFE18E9431D7F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 1/17/2020 10:16:06 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011720-9953-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF805B05817C9)
Bugcheck code: 0xD1 (0x257E31868411, 0xB, 0x0, 0xFFFFF805B05817C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_77e6900053c33f6f\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 441.66
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 441.66
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 441.66 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[ddennis002]

2 minutes ago, Inverted_Jesus said:

This is a long one, I've been recently been getting blue screens when starting up my computer, I also recently updated my BIOS, I don't know if that has anything to do with it or not but it's happening.

 

I obtained these using WhoCrashed:

 

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 1/22/2020 11:35:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012220-9015-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8066948D829, 0xFFFF96866E7258B8, 0xFFFF96866E725100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 1/22/2020 11:35:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF8066948D829, 0xFFFF96866E7258B8, 0xFFFF96866E725100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sun 1/19/2020 5:06:30 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011920-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x5286CA, 0x2, 0x4300043BFC9)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 1/19/2020 12:16:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011920-10406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xBE (0xFFFFCF090E28EDA8, 0x8A00000004E00121, 0xFFFFA28B50F4D740, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 1/17/2020 11:13:34 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011720-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80413293A3F, 0xFFFFE18E9431D7F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 1/17/2020 10:16:06 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011720-9953-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF805B05817C9)
Bugcheck code: 0xD1 (0x257E31868411, 0xB, 0x0, 0xFFFFF805B05817C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_77e6900053c33f6f\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 441.66
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 441.66
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 441.66 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

What are your system specs?

[Inverted_Jesus]

1 minute ago, ddennis002 said:

What are your system specs?

Processor: AMD Ryzen 5 1600X Six Core - 3.60 GHZ

Graphics: EVGA Geforce RTX 2080TI | 11G

RAM: 32GB DDR4-2400 Memory Module - G.SKILL Ripjaws V

Motherboard: GIGABYTE AB350 Gaming 3 -- RGB Fusion, 3x PCIe x16, 2x USB 3.1 Gen2, 4x USB 3.1 Gen1, 1x USB 2.0

Power Supply: Thermaltake Toughpower Grand RGB 650W Gold Full Modular

[boggy77]

2 sticks of ram or 4? if 2, are they in slots 2 and 4? xmp enabled? have you changed anything to  your system that may have caused the bosd's to start? especially related to ram?

[Inverted_Jesus]

4 minutes ago, boggy77 said:

2 sticks of ram or 4? if 2, are they in slots 2 and 4? xmp enabled? have you changed anything to  your system that may have caused the bosd's to start? especially related to ram?

4 8gb sticks, well I've been getting blue screens ever since I've had this. I had this close to 2 and a half years. XMP?

[boggy77]

1 minute ago, Inverted_Jesus said:

4 8gb sticks, well I've been getting blue screens ever since I've had this. I had this close to 2 and a half years. XMP?

go into bios, enable xmp profile, manually set dram voltage to 1.35 and soc voltage to 1.15 and see if it becomes more stable

[Inverted_Jesus]

I used it fine for a few hours and it blue screened again, it entered recovery and I got this.

[Inverted_Jesus]

4 hours ago, boggy77 said:

go into bios, enable xmp profile, manually set dram voltage to 1.35 and soc voltage to 1.15 and see if it becomes more stable

I used it for a few hours just fine but when I restarted it again, it blue screened again, this is what came up.

[Inverted_Jesus]

4 hours ago, boggy77 said:

go into bios, enable xmp profile, manually set dram voltage to 1.35 and soc voltage to 1.15 and see if it becomes more stable

Update, I restarted it from there to see what happened, I also undid what you suggested. Windows, now is completely broken and my os is unusable if anyone has any idea what to do I'll be booting a fresh windows from a USB and reinstalling all of it. That's the only thing I could think of.