New PC random BSODs

Hi,

I recently bought a new PC (about 3 weeks ago). I've had BSODs since day 1. The PC was put together as a standard package deal from a PC parts retailer.

Most BSODs occur playing Overwatch, however it has crashed without Overwatch running. I've tried to find the problem with WhoCrashed Pro edition (what a waste of money), BlueScreenView and Windbg. I don't have enough knowledge to use Windbg

I reinstalled Windows and have removed or stopped suspected apps (Logitech Gaming for example). I often get a loud buzzing from headphones when the crash occurs - maybe a sound driver problem?

I've run MemTest86 twice for a total of 5 passes, and I've run verifier for all non-MS drivers.

System Manufacturer: NA - package deal from PC parts shop (MSY in Sydney AUS)
Exact model number - components list:

          AMD YD1600BBAEBOX Ryzen 5 1600 3.2Ghz/6 Core/19M/65W AM4 Boxed CPU (With Cooler) 1

- OS: Windows 10 Version 1703 (OS Build 15063.483)
- x64 (64-bit)
- What was original installed OS on system? No, I reinstalled (twice)
- Is the OS an OEM version (came pre-installed on system) or full retail version. Full retail
- Age of the computer: 3 weeks
- Age of OS installation - and whether you have re-installed the OS: Can't remember but about 2 weeks ago was the latest install of OS
- Desktop computer
- CPU: AMD Ryzen 5 1600 Six-Core Processor, 3200 Mhz, 6 Core(s), 12 Logical Processor(s)

- MotherBoard: see components list above
 

I have the OS on the SSD - so C: is SSD, D: is HDD.

Any help would be very very much appreciated.

Let me know if you need any more info.

Most often, these sort of errors are due to hardware problems.
The most common of them are usually video card or motherboard issues.

As such, please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please finish ALL of the tests and let us know the results - we can move on from there.

Here's my analysis of the uploaded reports........................

Your UEFI/BIOS (version 0612) dates from May 2017.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Out of 5 memory dumps there were 4 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results.

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

Please note that all of these drivers date from before the release of Windows 10 (29 July 2015), and may not be compatible with Windows 10.

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:

OpenHardwareMonitorLib.sys   Sat Jul 26 09:29:37 2008 (488B26C1)
 Open Hardware Monitor libraries
OpenHardwareMonitorLib.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67) - you may not be able to update this.  In that case, uninstall PCProbe (or uninstall the AI Suite - which contains PCProbe).
Asus PCProbe Utility http://support.asus.com/download/download.aspx
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
 
CBUFS.sys                    Tue Oct  7 07:04:39 2014 (5433C8C7)
COMODO Safe Backup driver https://support.comodo.com/
http://www.carrona.org/drivers/driver.php?id=CBUFS.sys
 
bdisk.sys                    Tue Oct  7 07:04:50 2014 (5433C8D2)
Comodo raw disk access driver https://support.comodo.com/
http://www.carrona.org/drivers/driver.php?id=bdisk.sys
 
cbvd.sys                     Tue Oct  7 07:05:18 2014 (5433C8EE)
Comodo backup virtual disk driver https://support.comodo.com/
http://www.carrona.org/drivers/driver.php?id=cbvd.sys
 
CBReparse.sys                Tue Oct  7 07:05:26 2014 (5433C8F6)
Comodo backup minifilter driver https://support.comodo.com/
http://www.carrona.org/drivers/driver.php?id=CBReparse.sys
 
vdbus.sys                    Tue Oct  7 07:05:30 2014 (5433C8FA)
Comodo backup virtual disk bus driver https://support.comodo.com/
http://www.carrona.org/drivers/driver.php?id=vdbus.sys
 
lgcoretemp.sys               Tue Jun  9 12:52:10 2015 (557719BA)
Logitech Gaming Software driver http://support.logitech.com/en_gb/software/lgs
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
 
 


Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Fri Jul 14 07:07:36.939 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071417-7156-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 2:53:47.611
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpioclx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 1000007E, {ffffffffc0000005, fffff806077bda54, ffffa580ef7fa9a8, ffffa580ef7fa1f0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff806077bda54, The address that the exception occurred at
Arg3: ffffa580ef7fa9a8, Exception Record Address
Arg4: ffffa580ef7fa1f0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  0612
  BIOS Release Date             05/15/2017
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             PRIME B350M-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 04:13:13.198 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071417-7468-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 9:59:37.869
Probably caused by :memory_corruption
BugCheck 1A, {41792, ffffe28005a82828, 800000000000, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffe28005a82828
Arg3: 0000800000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41792
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  0612
  BIOS Release Date             05/15/2017
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             PRIME B350M-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 13 09:30:34.658 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071317-7609-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 5:21:35.328
Probably caused by :memory_corruption
BugCheck F7, {5d00de04ad50, 7387e6213fc3, ffff8c7819dec03c, 0}
BugCheck Info: DRIVER_OVERRAN_STACK_BUFFER (f7)
Arguments:
Arg1: 00005d00de04ad50, Actual security check cookie from the stack
Arg2: 00007387e6213fc3, Expected security check cookie
Arg3: ffff8c7819dec03c, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
BUGCHECK_STR:  0xF7
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT_LARGE
  BIOS Version                  0612
  BIOS Release Date             05/15/2017
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             PRIME B350M-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

**************************Fri Jul 14 07:07:36.939 2017 (UTC - 4:00)**************************
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)
CBUFS.sys                    Tue Oct  7 07:04:39 2014 (5433C8C7)
bdisk.sys                    Tue Oct  7 07:04:50 2014 (5433C8D2)
cbvd.sys                     Tue Oct  7 07:05:18 2014 (5433C8EE)
CBReparse.sys                Tue Oct  7 07:05:26 2014 (5433C8F6)
vdbus.sys                    Tue Oct  7 07:05:30 2014 (5433C8FA)
MpKsl60f04ab1.sys            Tue May 19 21:50:37 2015 (555BE86D)
MpKslc5e1a823.sys            Tue May 19 21:50:37 2015 (555BE86D)
lgcoretemp.sys               Tue Jun  9 12:52:10 2015 (557719BA)
amdgpio3.sys                 Mon Mar 14 06:19:36 2016 (56E69038)
LGJoyXlCore.sys              Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys                Mon Jun 13 14:47:08 2016 (575EFFAC)
rt640x64.sys                 Thu Jul 14 05:04:28 2016 (5787559C)
amdgpio2.sys                 Tue Aug  9 06:05:07 2016 (57A9AAD3)
asmtxhci.sys                 Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                 Mon Aug 29 04:40:08 2016 (57C3F4E8)
RTKVHD64.sys                 Tue Sep 20 07:47:12 2016 (57E121C0)
amdpsp.sys                   Tue Dec  6 11:53:23 2016 (5846ED03)
nvvhci.sys                   Tue Dec 27 20:44:00 2016 (586318E0)
nvvad64v.sys                 Wed Apr 12 04:06:41 2017 (58EDE011)
nvhda64v.sys                 Tue May 16 09:02:27 2017 (591AF863)
nvlddmkm.sys                 Tue Jun 27 16:02:17 2017 (5952B9C9)
SleepStudyHelper.sys         ***** Invalid 2023 Invalid 2023 Invalid
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 04:13:13.198 2017 (UTC - 4:00)**************************
OpenHardwareMonitorLib.sys   Sat Jul 26 09:29:37 2008 (488B26C1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 13 09:30:34.658 2017 (UTC - 4:00)**************************
MpKsl4d5d4225.sys            Tue May 19 21:50:37 2015 (555BE86D)
nvlddmkm.sys                 Wed Jun  7 19:03:57 2017 (5938865D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 13 03:54:10.288 2017 (UTC - 4:00)**************************
MpKslfaf533b8.sys            Tue May 19 21:50:37 2015 (555BE86D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul  9 08:35:39.839 2017 (UTC - 4:00)**************************
MpKsl3e6c9624.sys            Tue May 19 21:50:37 2015 (555BE86D)

Hi usama,

I've been running the hwdiag tests. Interestingly, after my first post I had another 2 BSODs. Let me know if you want the dump files for those.

So far:

HDD - I tried SeaTools for DOS - could boot and run the app but the tool couldn't see any hard drives - weird. Then tried SeaTools for Windows and ran the long test on both the HDD and SDD - 100% pass. I have screen shots if you'd like to see those.

SDD - used the Transcend Scope tool for the SSD and passed 100%

GPU - Furmark test - ran in window mode for 30 mins - temp maxed at 75C, was generally 73C-74C and was stable. No OpenGL errors and no problems with video. Then ran in full screen mode for 10 minutes and same. Very stable at 74C

CPU - Currently running the Prime75 test (has been running about 3.5 hours now - I'll probably let it run overnight). No errors so far. CPU temp has maxed at 70C but generally sits around the 65C mark.

BIOS:

I've downloaded the latest BIOS but have not flashed it yet. I'll do that tomorrow morning after the Prime75 test runs overnight.

Drivers:

Commodo is backup software. I thought it was a suspect, so uninstalled and still BSODs, so reinstalled again

asio.sys - not sure how that got there. I don't have the PCProbe software installed - I think I may come with one of the setup CDs? and must have uninstalled it. Not sure why the PCProbe directory structure and asio.sys is still hanging around. I can't find a way to uninstall the remnants.

OpenHardwareMonitorLib - is a hardware monitoring tool (voltages temperature etc). BSODs were occurring before installation (actually that's why I installed it - I thought maybe the GPU was overheating). I can uninstall it - I'm using CPUID HWMonitor now to keep an eye on CPU temperature. It seems to be a better tool anyway.

lgcoretemp.sys - I'm not running the Logitech Gaming System at the  moment, and I might uninstall it. I've always been a little distrustful of Logitech software. Hardware is good, software not so much :/  Although if I recall I think I did uninstall it at one stage but BSODs kept occurring.

I'll post again in the morning with the Prime75 results and I'll flash the BIOS and uninstall the Logitech stuff.

The only other thing I can think of is I often but not always get a high volume buzzing in the headphones when the machine BSODs. In Device Manager I have NVIDIA High Definition Audio, NVIDIA Virtual Audio Device (Wave Extensible) (WDM), and Realtek High Definition Audio. I tried disabling the Realtek device but it just stopped the audio I could maybe try disabling the NVIDIA devices?

Appreciate all your help.

Most often when I hear of the buzzing audio, it's a video card issue (either software or hardware)

Even though you're not getting this error, try the steps at this page to see if it helps:  http://www.carrona.org/VideoTDR.html

Sometimes BSOD's are caused by a combination of problems.  When uninstalling suspect software, please leave it uninstalled until the problem is solved (if it's needed, you can always install it, then uninstall it).

I prefer HWMonitor myself - but often recommend SpeedFan because of it's ability to generate logs.

IMO/IME - video cards advancements are in flux right now, with a number of problems being reported that aren't amenable to traditional troubleshooting.

My 2 theories are:
- that the newer video cards incorporate functions that aren't always used and may differ when installed with different OS's and different hardware.  This makes diagnostics difficult - and the trend is towards those we use for SSD's (if it's suspect, try another device to test with).

- that the newer video cards interact with the monitor much more than previous cards did.  And most people only use the built in Windows drivers - not the monitor manufacturer's drivers.  As such, advances with newer video cards may not play well with Windows drivers - and might require more sophisticated drivers from the manufacturer.

Hi usama,

I upgraded the BIOS about 5 days ago, and so far have no BSODs. I think it's fixed (fingers crossed).

Thank you very much for your help!