[SOLVED] New PC build BSODs

[TomJenkins87]

Hi,

Thank you for taking the time to view my post. I'm new to this forum so I hope this post is alright.

I built a new PC recently and ever since the first time booting it up, the system has suffered from seemingly random bluescreens of many different error codes, seemingly random reboots (no bluescreen) and crashes to desktop within many different games with no errors or warnings. I shall post the specs of the system below, along with some notes about the build.

Specs:
PSU: Seasonic SS-620GM2 M12II-EVO 620W (80+ bronze)
Motherboard: MSI X570-A PRO
CPU: AMD Ryzen 5 3600
RAM: Corsair CMK16GX4M2D3000C16 LPX 16GB (2x 8GB)
GPU: Palit GeForce RTX 2070 Dual 8GB GDDR6
Storage: Samsung 860 EVO 1TB SATA Internal 2.5" SSD
Storage: Kingston SSD A400 M.2 SSD 120GB
OS: Windows 10

Notes - whether they are relevant or not:
The OS is installed onto the kingston M.2 drive.
The RAM is installed into slots 2 and 4.
The motherboard features 12 pins for the CPU power, only 8 of these are currently in use.
At first, the PC was rebooting while idle, but I fixed this by enabling a minimum CPU usage state.
It seems there is a trend between load and frequency of BSODs: when working on the PC there are no issues, when playing old games (Rome:TW) then there are a few BSODs, playing newer games (Mount and Blade 2 - released this week) more frequent BSODs.
If any further details come to mind, I shall add them.

I thank you kindly in advance for any information or assistance on these issues.
Please don't hesitate to ask questions should further details be required for your assistance.

 

[TomJenkins87]

Some info on the most recent bluescreens:

==================================================
Dump File : 021820-14140-01.dmp
Crash Time : 18/02/2020 19:23:18
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 2 : fffff8032d04c8aa Parameter 3 : ffffe10b3388d0c0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c1510
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c1510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021820-14140-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 784,724
Dump File Time : 18/02/2020 19:24:35
==================================================

==================================================
Dump File : 032120-18593-01.dmp
Crash Time : 21/03/2020 21:44:17
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 2 : 0000000000000010 Parameter 3 : ffffdd0c00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032120-18593-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 826,772
Dump File Time : 21/03/2020 21:45:51
==================================================

==================================================
Dump File : 033120-15218-01.dmp
Crash Time : 31/03/2020 10:18:41
Bug Check String :
Bug Check Code : 0x00000139
Parameter 2 : ffffc200cded7ff0 Parameter 3 : ffffc200cded7f48
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\033120-15218-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 757,892
Dump File Time : 31/03/2020 10:23:46
==================================================

==================================================
Dump File : 033120-15140-01.dmp
Crash Time : 31/03/2020 11:14:16
Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code : 0x0000004a
Parameter 2 : 0000000000000002 Parameter 3 : 0000000000000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\033120-15140-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 755,996
Dump File Time : 31/03/2020 11:20:52
==================================================

==================================================
Dump File : 030120-16656-01.dmp
Crash Time : 01/03/2020 01:11:18
Bug Check String :
Bug Check Code : 0x000001c6
Parameter 2 : ffff92370608e290 Parameter 3 : 0000000000000000
Caused By Driver : win32kbase.sys
Caused By Address : win32kbase.sys+34858
File Description : Base Win32k Kernel Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.714 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c1510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030120-16656-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 863,300
Dump File Time : 01/03/2020 01:12:50
==================================================

 

[TomJenkins87]

Reading about on the forum, a lot of BSODs seem to be caused by RAM. I've tried running both sticks then each stick individually and then different slots. No change in errors there unfortunately.

New bluescreens while testing different RAM configs:

==================================================
Dump File : 040120-14031-01.dmp
Crash Time : 01/04/2020 09:56:58
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 2 : fffff806741caf42 Parameter 3 : ffffec875e3a7940
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040120-14031-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 999,252
Dump File Time : 01/04/2020 09:59:09
==================================================

==================================================
Dump File : 040120-14250-01.dmp
Crash Time : 01/04/2020 16:02:21
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 2 : 0000000000000002 Parameter 3 : 0000000000000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040120-14250-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 725,108
Dump File Time : 01/04/2020 16:17:53
==================================================

==================================================
Dump File : 040120-17265-01.dmp
Crash Time : 01/04/2020 20:38:34
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 2 : fffff802669d3873 Parameter 3 : ffffb7000bad8930
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040120-17265-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 733,772
Dump File Time : 01/04/2020 20:42:49
==================================================

==================================================
Dump File : 040220-14968-01.dmp
Crash Time : 02/04/2020 12:46:49
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 2 : fffff8054ffd0071 Parameter 3 : 0000000000000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040220-14968-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 756,828
Dump File Time : 02/04/2020 12:48:38
==================================================

 

[jdupton]

Since those Blue-Screens are all over the place and seemingly random, I might suspect DRAM first. It could be on the hairy edge of not running.

You can start debugging this by running either MemTest86 or the built in Windows Memory Test (or both if you wish). That should detect whether DRAM corruption is at fault here. Sometimes, these tests will pass even if marginally flaky memory is the cause. In such a case continue with the extra steps below.

Double check your Mother-Board User Manual and the MB online Qualified Vendor List to make sure the DRAM modules you are using are listed.

Also, can you tell us whether you are running default memory speeds or have you enabled the DRAM XMP profile or done any over-clocking? If you have done either, revert to BIOS defaults and run the system for while to see if the problem persists. If that seems to fix it, then you can slowly go back to any over-clock settings a little at a time until the BSODs return and then back off some.

 

[TomJenkins87]

Hi jdupton,

Thank you for your advice.

I have checked the RAM compatibility and (as far as I can tell) CMK16GX4M2D3000C16 is accepted.

I have also loaded the default BIOS settings for the sake of clarity. I had made some changes but only by following methods for fixing issues I had read elsewhere.

I'll run memtest86 overnight for as many passes as it can achieve and let you know the results. (I'll just leave both sticks in).

 

[TomJenkins87]

Since those Blue-Screens are all over the place and seemingly random, I might suspect DRAM first. It could be on the hairy edge of not running.

You can start debugging this by running either MemTest86 or the built in Windows Memory Test (or both if you wish). That should detect whether DRAM corruption is at fault here. Sometimes, these tests will pass even if marginally flaky memory is the cause. In such a case continue with the extra steps below.

Double check your Mother-Board User Manual and the MB online Qualified Vendor List to make sure the DRAM modules you are using are listed.

Also, can you tell us whether you are running default memory speeds or have you enabled the DRAM XMP profile or done any over-clocking? If you have done either, revert to BIOS defaults and run the system for while to see if the problem persists. If that seems to fix it, then you can slowly go back to any over-clock settings a little at a time until the BSODs return and then back off some.

I ran 4 passes (maximum number of passes for free version) with no errors. Report as follows:

 

[jdupton]

Sorry, I am mostly out of ideas. The only things I can think of that are left are the same old suggestions to check drivers and BIOS levels. I don't like messing with those things myself since they can lead to lots of extra work if things go wrong.

You might try first checking you graphics card driver against the latest level shown on the NVIDIA web site. If there is a new level, you can try to more involved method of downloading DDU (Display Driver Uninstaller) and the new driver. Then boot into Windows Safe Mode, run DDU to completely remove all traces of the old driver, and then install the new driver file only (without all the update checker bloatware and such) using the option to do a "Clean Install" (located in the advanced options for the driver installer). Finally, boot back to normal Windows Mode and test.

If that doesn't work and your somewhat brave, you can try updating your BIOS and / or the latest AMD chipset drivers. The latest version of those was just released last month (March 19, 2020. Your current level of BIOS dates back to the summer of 2019 according to MemTest86, so there is likely a more recent version available. See what level is latest and check support forums for any problem reports from users who have recently updated to that level.

 

[TomJenkins87]

Thanks jdupton, you're very helpful. I have updated a few things this morning:

Chipset from the link you provided, 2.03.12.0657. - All went smoothly.
BIOS from msi.com, 7C37vH7 - All went smoothly.
Ryzen Master.
Windows (it wasn't very out of date though, only one update).

GPU - 445,75 from Palit.com (manufacturer). Not so smoothly...
I downloaded the driver update and launched it. I chose custom install and opted for a clean install (with all extras, geforce experience etc.). This turned off the PC early on in the install process (no bluescreen). When the PC booted again, it bluescreened (bluescreen dump below) a few times at various points (early on, sometimes even before i got to desktop). Eventually I was able to sit on the desktop for a while. I then looked in device manager and noticed that I had no display adapter listed (perhaps the install removed my old driver before failing). I relaunced the driver update applcation and did the express install option. All was fine from then.

I'll post again the next time I bluescreen with an update. I'm not optimistic.

Tom.

Bluescreen dump:
==================================================
Dump File : 040320-11890-01.dmp
Crash Time : 03/04/2020 12:09:20
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 2 : 0000000000000002 Parameter 3 : 0000000000000000
Parameter 4 : fffff800`502047db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040320-11890-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 1,148,812
Dump File Time : 03/04/2020 12:12:12
==================================================

 

[TomJenkins87]

More BSODs than ever, seemingly randomly. Dumps below.

I've just gone into BIOS and set A-XMP on, the DRAM speed to 3000MHz and the DRAM voltage to 1.35V.

Again, I'm not optimistic.

==================================================
Dump File : 040320-14984-01.dmp
Crash Time : 03/04/2020 13:22:53
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 2 : fffff802488e6975 Parameter 3 : ffffd809f3cba180
Parameter 4 : 0000000000000000 Caused By Driver : FLTMGR.SYS Caused By Address : FLTMGR.SYS+6975 File Description : Microsoft Filesystem Filter Manager Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.18362.1 (WinBuild.160101.0800) Processor : x64 Crash Address : ntoskrnl.exe+1c2380 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\040320-14984-01.dmp Processors Count : 12 Major Version : 15 Minor Version : 18362 Dump File Size : 1,334,460 Dump File Time : 03/04/2020 13:24:56 ================================================== ================================================== Dump File : 040320-11890-01.dmp Crash Time : 03/04/2020 12:09:20 Bug Check String : IRQL_NOT_LESS_OR_EQUAL Bug Check Code : 0x0000000a Parameter 2 : 0000000000000002
Parameter 3 : 0000000000000000 Parameter 4 : fffff800502047db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040320-11890-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 1,148,812
Dump File Time : 03/04/2020 12:12:12
==================================================

==================================================
Dump File : 040320-13046-01.dmp
Crash Time : 03/04/2020 13:51:39
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 2 : 00000000000000ff Parameter 3 : 000000000000000b
Parameter 4 : fffff8055e0bae50 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+1c2380 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.18362.720 (WinBuild.160101.0800) Processor : x64 Crash Address : ntoskrnl.exe+1c2380 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\040320-13046-01.dmp Processors Count : 12 Major Version : 15 Minor Version : 18362 Dump File Size : 868,668 Dump File Time : 03/04/2020 13:53:24 ================================================== ================================================== Dump File : 040320-14093-01.dmp Crash Time : 03/04/2020 13:54:22 Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA Bug Check Code : 0x00000050 Parameter 2 : 0000000000000000
Parameter 3 : fffffde5e3c2adb8 Parameter 4 : 0000000000000000
Caused By Driver : win32kbase.sys
Caused By Address : win32kbase.sys+38fb5
File Description : Base Win32k Kernel Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.714 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040320-14093-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 1,168,380
Dump File Time : 03/04/2020 14:00:08
==================================================

 

[TomJenkins87]

No good unfortunately. Not only have I had more bluescreens but I've also seen the return of the random rebooting without error which I hadn't seen for a while.

Does anyone have any ideas?

Could there be something wrong with the m.2 drive (which has windows installed on it)?

 

[TomJenkins87]

BSOD dump:

==================================================
Dump File : 040320-13656-01.dmp
Crash Time : 03/04/2020 14:26:23
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 2 : 0000000000000002 Parameter 3 : 0000000000000000
Parameter 4 : fffff802`7c5128f6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.720 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c2380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040320-13656-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 18362
Dump File Size : 1,315,324
Dump File Time : 03/04/2020 14:28:44
==================================================

 

[TomJenkins87]

I reverted to an old BIOS version and set the DRAM voltage to 1.31V.
The random rebooting has stopped however I have seen further blue screens: IRQL NOT LESS OR EQUAL.

Any thoughts would be most appreciated.

 

[jdupton]

The only thing I might have done differently is to load just the NVIDIA device drivers from their site rather than the version from the OEM. In addition, I try to load just the device driver itself and not the whole "Experience" suite of bloated software. (That is just a personal preference for me. I have never really understood why it takes 100 MB to as much as 500 MB of software just to check for new drivers.) Also, the DDU step can be important in some instances since it does more than just remove the device driver. It also scours the Windows registry for all vestiges of stuff associate with the display adapter driver as sometimes that stuff can gunk up the works when a new version is installed.

It still bothers me that all of these BSODs seem to have little in common. The only thing that seems common to a lot of those are CPU and Memory.

I wonder if there are corrupted system files present in your Windows installation. One last gasp effort might be to make sure Windows itself is not messed up somehow. Try the methods from the following link to see if any errors are found, let it fix them, and test some more.

https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker

Other than that, I think I am fresh out of ideas... Sorry.

 

[TomJenkins87]

Thanks.

My BSODs only seem to occur when playing games so I spent some time playing earlier in order to trigger a BSOD. It took me a while as my game CTDd a couple of times without warning. Both times, the event viewer showed an error called "bad_module_info" and one of the times, the error was accompanied by the following error (Bannerlord is the game):

"Application: Bannerlord.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF8DFF92561 (00007FF8DFEF0000) with exit code 80131506."

Whether or not these errors are of use/interest to you I don't know, but I thought I'd better tell you.


I'll try using DDU and then installing video drivers straight from nvidia.

If that fails... then it's clean install of windows time. Possibly without the m.2 in.

 

[jdupton]

This latest error feels rather random to me like the BSODs. I am not seeing anything that points to one specific cause for all this.

After cleaning up the display adapter driver once again, I might suggest the Microsoft system file clean-up first before a wipe and full reinstall. It will be faster and less trouble to try the cleanup than to reinstall Windows completely and have to (potentially) rebuild all the software you have installed.

One other thought might be to do the clean-ups and then try running a system stress program to look for subtle hardware errors. I do not know what others recommend these days. Maybe someone else can chime in here. I have used OCCT and Prime95 on a previous system but they may be outdated now. Normally you would do this sort of testing when you are over-clocking a system. I see no real reason it might not find marginal hardware even running on a default settings for a new system that is acting oddly.

https://www.tomshardware.com/reviews/stress-test-cpu-pc-guide,5461.html

 

[TomJenkins87]

Thanks for your replies so far.

I decided to wipe my hard drives and reinstall windows clean so I could ensure a clean platform to install my display driver.

Unfortunately my PC is frequently BSODing which is preventing installation.

Ive tried with the m.2 card out but still BSODs. My mobo doesnt have onboard graphics so I cant check the gpu using this method.

What can I do?

 

[jdupton]

This new symptom is still pointing to unstable hardware in my opinion. The problem is "which hardware is unstable?"

Are you booting to a USB Windows installation media? Does the boot seem solid or does it never really start due to BSODs? Have you tried unplugging the power supply, removing the CMOS battery on the MB and waiting for 30 minutes (probably much more time than needed), then reinstalling the CMOS Battery, plugging back in to A/C and then booting? Do not change any BIOS settings from default after doing this step.

I am completely out of my realm now but I think it may be possible to build a "portable Linux system" on a USB stick and see if you find some diagnostic software to boot and run against the hardware. Otherwise, you may need to start blindly swapping parts which is a painfully slow an aggravating process when you don't have access to a knowledgeable expert nearby.

 

[TomJenkins87]

I’m sure you’re right that it is hardware. It’s just a matter of narrowing down which hardware it is!

I have finally managed to install windows.

I moved the GPU to the 2nd pci slot, I moved the SSD to a different SATA port and I pushed a few components down to double check they were properly installed. Doing this made the system seem perfect for a good few hours. I was able to install with no troubles and got a few hours gaming in before I got a bluescreen: IQRL NOT LESS OR EQUAL.

That said, I had no other crashes, nostutter or anything bad at all.

All I did after my clean windows install was install google chrome, update my graphics driver straight from Nvidia, install steam and a few games.


If we’re now trying to narrow down which hardware could be at fault, now is the time to try those testing programs you suggest. I’ll have a look tomorrow. If anyone else can suggest some more applications to help narrow down the origins of my hardware failures, that would be great.

 

[TomJenkins87]

I thought it was time for an up-to-date summary:

I've had problems with my PC since I built it. All parts were brand new and should be compatible with each other.

Symptoms

Bluescreens (BSOD). These occur every now and then, more frequently on newer/more demanding games. Most common errors are IRQL_NOT_LESS_OR_EQUAL and SYSTEM_SERVICE_EXCEPTION but I have seen others.

Game crashes (CTD): These never show an error or game has stopped responding etc. These are seemingly random and happen in all games. Event viewer occasionally reports a bad_module_info error, but not always.

Random PC reboots: Sometimes the PC will just reboot itself, no errors or warnings here either. The system is back up and running in no time.

There are also various errors in event viewer, all the time:
application crashes
failed modifying runtime statuses
unable to start, distributedCOM server
windows failed to install a Skype update
critical kernal-power
session perfDiag logger stopped
.NET Runtime error followed by an application error in a game.

What I've tried:

Software

Drivers: I've made several clean installs of windows, being careful to install the correct drivers from the correct places for specific components. My BSOD errors do not indicate specific third-party drivers, only generic Microsoft drivers.

BIOS: The latest BIOS for my motherboard causes frequent random reboots without warning. I have reverted to an old BIOS in which the reboots don't occur. I have not tweaked any OC settings manually.

Hardware

CPU: I ran prime95 small FFT torture tests for a few hours - no errors.

PSU: I swapped my new seasonic 620W for my old Corsair 750W. This made no change. I also ran OCCT power test with no problems.

RAM: I ran memtest86 and memtest64 for several passes each, no errors.

Storage: I performed some quick tests with HDDSentinel. My main SSD had 2 bad sectors but otherwise there were no problems with either drive.

GPU: Ive run OCCTs GPU:3D and GPU:Memtest. Neither gave any errors. I also ran OCCT power test with no problems.

Motherboard: The fact the latest BIOS causes issues worries me. If all of the other components are ok then this suggests a problem with the motherboard I believe. I'm thinking of buying a new one and installing it. Ill be returning the new one if it doesn't fix my problem and Ill RMA/return my current board if it does fix my problem.

Specs (speccy):
https://drive.google.com/file/d/1XtncKULz9e2_uAGna2QBauA5-funs0MV/view?usp=drivesdk