Windows 10: Frequent BSODs even after clean install

Hey everyone,


Posting here looking for some help, now I'm a pretty tech savvy guy, have been building/ fixing computers for over 8 years, however lately my computer has been giving me nothing but trouble.


Basically I am getting random BSODs, several unique ones, also random freezing. Rebooting the computer fixes this, however it tends to happen at least once a day, today was 3 times.


I have done a clean install of windows a few weeks ago to try to resolve these issues, installing the latest drivers from manufacturer's website, latest bios and all and if anything it seems to be getting worse.


I ran DDU Uninstaller for my GPU drivers and reinstalled a couple weeks ago as well.


I have still yet to do a memory test on my RAM, i ran intel's diagnostic tool for my CPU which passed.


My last BSODs:


On Sat 5/23/2020 6:43:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052320-7625-01.dmp
This was probably caused by the following module: usbxhci.sys 0xFFFFF80028D28DF8
Bugcheck code: 0xD1 0x0, 0x2, 0x1, 0xFFFFF80028D28DF8
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
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.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 5/23/2020 6:43:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: usbxhci.sys 0xFFFFF80028D28DF8
Bugcheck code: 0xD1 0x0, 0x2, 0x1, 0xFFFFF80028D28DF8
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
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.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 5/23/2020 3:29:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052320-8046-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x139 0x3, 0xFFFFAC050A036850, 0xFFFFAC050A0367A8, 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.



On Sun 5/10/2020 6:18:49 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051020-7718-01.dmp
This was probably caused by the following module: tcpip.sys 0xFFFFF807093BA320
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF807093BA320, 0x0, 0xFFFFFFFFFFFFFFFF
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 5/5/2020 6:26:36 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050520-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x139 0x3, 0xFFFFF8000F82A2B0, 0xFFFFF8000F82A208, 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.



On Tue 4/28/2020 8:17:57 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-7906-01.dmp
This was probably caused by the following module: nvlddmkm.sys 0xFFFFF80729E70705
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF80729E70705, 0x0, 0xFFFFFFFFFFFFFFFF
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95bdb3a23d6478de\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 445.87
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 445.87
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
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 445.87 , NVIDIA Corporation.
Google query: nvlddmkm.sys NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED


Note that when the system freezes, no dump file is created.



Specs:


i7-4770k

16GB DDR3 1600Mhz RAM

Samsung Evo 960 500GB, a samsung Evo 850, and a couple HDDs

RTX 2080

1000w Antec psu

MSI Z97s SLI Krait Edition Mobo.



Any help would be greatly appreciated

:)

 

Clean Install Workaround for Vista

You may remember this news story on techPowerUp! a couple of days ago relating to the lack of clean installs when using the Upgrade Editions of Vista, which required an old OS to be installed. However, Paul Thurrott has managed to find a workaround for this issue, which ironically lets users do a clean install Vista without any previous version of Windows, albeit a little tedious. Here are the steps:

• Boot from the Windows Vista Upgrade DVD as normal
• When prompted for a product code, leave this blank
• Select the version of Vista you have purchased and let Vista install
• When you boot to your desktop for the first time, run the Vista setup from Windows
• This time enter your product key
• When asked whether you want to do an Upgrade of Custom install, select custom and choose a clean install
• Windows will now install for a second time and you should be able to activate it

Remember, these steps are only advised for use in order to achieve a clean install of Vista, it is only legal to use the upgrade editions if you have previously purchased the appropriate version of Windows.

Source: DailyTech

 

7 different BSoD

First off this is what I went through once I installed them 11.1 drivers . BSOD till I had to reinstall the OS .
It seems that some maybe missing the point here this STARTED for you after you installed the 11.1 drivers and then as it would seem you are getting them after a clean install of the old drivers . Correct ? If so have you wiped the HDD and did a clean install of the OS ?
If not then I would do this before thinking your cards are going out .

 

Windows 10 infinite restart black screen


The tutorials provided are just a list of troubleshooting steps. Use only the steps which apply to you.

Since none of the troubleshooting steps here worked, I'd suggest you do a Clean install.

John