Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC BSOD While Gaming


  • Please log in to reply
12 replies to this topic

#1 steven12

steven12

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 25 January 2018 - 05:03 PM

I need some serious help! So my PC has recently started crashing ONLY while I game. It never has happened while rendering a video (I've had 10 hour renders with no problem at all). It happens randomly too. Sometimes I can start off on PUBG and have no problems for 4-5 games and later on in the day I'd get the problem playing Rainbow Six Siege. Other times it happens after 1-2 games. More recently, I had Overwatch League (a Twitch stream) opened in an internet browser and opened Overwatch to look at the new skins and BOOM it crashed instantly Attached File  crash 1.TXT   6.43KB   1 downloads. Each time I BSOD the PC freezes for a couple of seconds and then the blue screen appears....but it's weird. The screen turns blue but I can also see a portion of my taskbar from my PC at the bottom of the screen and the BSOD's text itself is illegible. A bunch of clumped and jumbled white pixels on the screen. This last, aforementioned crash was strange because I was able to move my mouse while the rest of the PC was frozen before the jumbled up BSOD was shown. HOWEVER, a BSOD did render correctly one time indicating that it was due to a "DPC_WATCHDOG_VIOLATION".

 

I want to say that it's GPU related (drivers or hardware) but I'm not 100% sure. I have posted the crash logs of my last 5 crashes and all of them are showing that "dxgkrnl.sys" is at fault. I've ran chkdsk/f, sfc/scannow, DISM and nothing shows up. I've also ran 2 passes of memtest with no issues at all. Somebody please help!

 

**UPDATE** I now have attached the Speccy files as well as the appropriate .zip required for BSODs

Link- http://speccy.piriform.com/results/saDhWouoKLuqRvrfKkYEsHG

Zip - attached

 

PC Specs:

Windows 8.1

AMD FX 8350

GTX 960

1TB HDD Western Digital

120GB Kingston SSD

4x4GB GSKILL RAM

EVGA 500W PSU Bronze Cert.

Gigabyte GA-970A-UD3P

Cooler Master Hyper 212 Evo

Attached Files


Edited by steven12, 25 January 2018 - 06:03 PM.


BC AdBot (Login to Remove)

 


#2 HyperHenry

HyperHenry

  • Members
  • 775 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Iowa (but travel)
  • Local time:10:37 AM

Posted 25 January 2018 - 05:26 PM

https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



#3 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 25 January 2018 - 05:57 PM

Sorry about that. Thanks for the help! I have attached the .zip file and have posted the Speccy link below.

 

http://speccy.piriform.com/results/saDhWouoKLuqRvrfKkYEsHG

Attached Files


Edited by steven12, 25 January 2018 - 05:57 PM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:37 AM

Posted 26 January 2018 - 08:09 AM

Your UEFI/BIOS (version FB) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
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 the outdated UEFI/BIOS' may be the cause of some compatibility issues).

228 Windows Update hotfixes installed.  Most systems have more than this  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

The older memory dumps don't have a definite blame, while the later one's definitely blame video

 

AMD OverDrive (AODDriver2.sys or AODDriver4.1) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Windows systems.

 

NOTE:  these symptoms were from the previous release of OverDrive.  The new release uses the same driver name, but is dated from 4 November 2013.

 

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLYhttp://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01, etc) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install".  Reboot for changes to take affect.

Sometimes the entry will remain in Device Manager even though you've removed it.  So, open up Device Manager and check for the AODDriver4.2.0 (it may have another number).  Right click on it and select "Uninstall".  If it asks to remove software, put a check in the box.  Then click on OK.

Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

 

Then, if that doesn't fix it, please try a clean install of your video drivers:

 

Please uninstall your video drivers and all the nVidia/AMD/Intel VIDEO (not chipset) software from your system (Settings...Apps - or appwiz.cpl)
- If uninstalling the AMD video drivers, you may also want to run the AMD Clean Uninstall utility (free from here:  http://support.amd.com/en-us/kb-articles/Pages/AMD-Clean-Uninstall-Utility.aspx )
Then use this free tool to remove any traces of the drivers:  http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reboot and check Windows Update (allow it to install video drivers):  https://support.microsoft.com/en-us/help/15054/windows-7-automatically-get-recommended-drivers-updates-hardware

Test to see if this helps and post back with the results.

Then, if that works and you need the nVidia drivers - feel free to download and install the latest, W8 compatible video drivers from http://www.nvidia.com/Download/index.aspx
Then, if that works and you need the AMD drivers - feel free to download and install the latest, W8 compatible video drivers from http://support.amd.com/en-us/download
Then, if that works and you need the Intel drivers - feel free to download and install the latest, W8 compatible video drivers from http://downloadcenter.intel.com (you can also usually download these drivers from the manufacturer's website)

 

If that does not fix it, then please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please start with the video tests (Furmark and all of the Video 2 tests), but complete ALL of the diagnostics and let us know the results

 

Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
Please run ALL of the tests and let us know the results.
FYI - These are the tests and what we usually see for the reports:

 

1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
  - A - simtek.org memtest
  - B - Video memory stress test
  - C - Artifact Locator
  - D - OCCT - 4 built in tests for CPU, GPU, PSU
  - E - Video Memory Stress Test
7 - CPU tests:  run at least one test on your CPU and let us know the result.

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Thu Jan 25 00:35:28.687 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012518-19359-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
System Uptime:0 days 12:31:13.422
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  FB
  BIOS Release Date             06/01/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             970A-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 23 00:28:57.813 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012318-19796-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
System Uptime:0 days 13:06:56.547
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  FB
  BIOS Release Date             06/01/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             970A-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 20 01:31:23.250 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012018-15796-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
System Uptime:0 days 13:27:59.984
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  FB
  BIOS Release Date             06/01/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             970A-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Thu Jan 25 00:35:28.687 2018 (UTC - 5:00)**************************
MpKsl0a573b73.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
AODDriver2.sys              Wed Nov 21 02:44:04 2012 (50AC8644)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
vbaudio_vmvaio64_win7.sys   Mon Apr 21 05:05:09 2014 (5354DF45)
vbaudio_cable64_win7.sys    Thu Aug 14 02:15:25 2014 (53EC53FD)
xhcdrv.sys                  Thu Oct 30 22:43:52 2014 (5452F768)
ViaHub3.sys                 Thu Oct 30 22:43:57 2014 (5452F76D)
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
ElgatoGC656.sys             Thu Nov  5 03:27:04 2015 (563B12D8)
ElgatoVAD.sys               Mon Aug  8 07:32:12 2016 (57A86DBC)
ssdevfactory.sys            Wed Apr  5 12:51:17 2017 (58E52085)
sshid.sys                   Mon May  8 12:03:55 2017 (591096EB)
RTKVHD64.sys                Wed Jun 14 01:58:31 2017 (5940D087)
Rt630x64.sys                Tue Oct  3 04:35:11 2017 (59D34BBF)
nvvad64v.sys                Thu Dec 14 00:40:29 2017 (5A320ECD)
nvhda64v.sys                Fri Dec 15 03:17:43 2017 (5A338527)
nvlddmkm.sys                Wed Jan  3 18:39:48 2018 (5A4D69C4)
nvvadarm.sys                Wed Jan  3 18:56:49 2018 (5A4D6DC1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 23 00:28:57.813 2018 (UTC - 5:00)**************************
MpKsl92401d5a.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
Rt630x64.sys                Tue Jun 17 07:56:46 2014 (53A02CFE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 20 01:31:23.250 2018 (UTC - 5:00)**************************
MpKsl4df62a3e.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
BEDaisy.sys                 Tue Nov  7 21:53:13 2017 (5A027199)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 18 16:18:29.500 2018 (UTC - 5:00)**************************
MpKsl0bfd8eb5.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
voxaldriverx64.sys          Mon Jan 27 22:46:51 2014 (52E7282B)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
nvlddmkm.sys                Fri Dec 15 17:15:18 2017 (5A344976)
nvvadarm.sys                Fri Dec 15 17:34:51 2017 (5A344E0B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 15 23:50:46.969 2018 (UTC - 5:00)**************************
MpKsl44c325e8.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
nvvad64v.sys                Fri Jul  1 09:12:29 2016 (57766C3D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 14 22:46:58.265 2018 (UTC - 5:00)**************************
MpKsl55f16476.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Oct 16 23:00:49.841 2017 (UTC - 5:00)**************************
MpKslf9476303.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
nvhda64v.sys                Tue May 16 09:02:27 2017 (591AF863)
nvvad64v.sys                Sun May 28 19:04:45 2017 (592B578D)
nvlddmkm.sys                Sat Sep 16 13:03:33 2017 (59BD5965)
nvvadarm.sys                Sat Sep 16 13:08:59 2017 (59BD5AAB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 10 01:41:45.659 2017 (UTC - 5:00)**************************
MpKslde530289.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct  8 11:21:10.251 2017 (UTC - 5:00)**************************
MpKsla47a632f.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 25 09:08:03.234 2017 (UTC - 5:00)**************************
nvvad64v.sys                Mon Feb  6 04:37:01 2017 (589843BD)
nvhda64v.sys                Wed Mar 15 08:48:41 2017 (58C93829)
nvlddmkm.sys                Mon May  1 15:58:03 2017 (5907934B)

MpKsl0a573b73.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.
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=amdide64.sys
http://www.carrona.org/drivers/driver.php?id=vbaudio_vmvaio64_win7.sys
http://www.carrona.org/drivers/driver.php?id=vbaudio_cable64_win7.sys
http://www.carrona.org/drivers/driver.php?id=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
ElgatoGC656.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.
ElgatoVAD.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.
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
MpKsl92401d5a.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.
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
MpKsl4df62a3e.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.
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
MpKsl0bfd8eb5.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.
http://www.carrona.org/drivers/driver.php?id=voxaldriverx64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
MpKsl44c325e8.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.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
MpKsl55f16476.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.
MpKslf9476303.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.
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
MpKslde530289.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.
MpKsla47a632f.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.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 


Edited by usasma, 26 January 2018 - 08:13 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 26 January 2018 - 12:08 PM

I really do appreciate the response! Going to do what you suggested and then post back here later when I have the results. 

 

P.S. - My mobo was at fault in those older memory dumps. Had it RMA'd a while back.


Edited by steven12, 26 January 2018 - 01:20 PM.


#6 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 29 January 2018 - 01:45 AM

So after a couple of days of testing my PC I no longer have the issue (well at least as of right now)! So I did everything that you had said in order up until the "clean install of video drivers" part. I figured that I test it at this point but then continue on down the list if I blue screened. Thank you so much usasma!

 

*UPDATE it just crashed again but this time it wasn't during gaming*


Edited by steven12, 29 January 2018 - 02:16 PM.


#7 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 29 January 2018 - 03:45 PM

One more thing that I have noticed during these crashes......each one has happened while I was in a Discord call. It doesn't happen every time I'm in one, but every single crash has happened during one (while playing a game or watching a stream). Don't know if that helps but thought I should just mention it. It's already been re-installed a couple of days ago prior to the recent crash, so I don't think that re-installing it again would fix it. However I have picked up where I left of on the list that was given to me. Going to keep at it and update you with the results.



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:37 AM

Posted 29 January 2018 - 03:56 PM

It's possible that it only crashes when Discord's driver interacts with another driver in a certain way.
Try running Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Once that's started, make several of the Discord calls and try to force a crash.
I'd do it until the system crashes 3 times - that way we're more likely to have good reports.

Good luck!


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 31 January 2018 - 11:54 AM

Alright so I had continued with your first post by uninstalling all of my NVIDIA drivers. I then performed a Windows update and allowed for Windows to install 3 NVIDIA drivers (NVIDIA HD Audio, NVIDIA Graphics, & NVIDIA 3D VISION). Right after that I read your new post and immediately began the Driver Verifier software. It's been running for 34 hours so far out of the suggested 36 hours. As of right now I have only been able to get it to BSOD once while Driver Verifier was active. The BSOD was viewable this time (not scattered like in most of the cases I've experienced with this particular crash) but it gave me the exact same "DPC_WATCHDOG_VIOLATION" BSOD. I'm going to let Driver Verifier run for the additional 2 hours and update you if I was able to get it to crash again. I have attached my latest BSOD crash files below. Was thinking about maybe updating to a fresh install of Windows 10 at some point if the problem is Windows 8.1 related. I'm just frustrated that I can't replicate this BSOD consistently!

 

Speccy - http://speccy.piriform.com/results/chVHCcvsLVNAPVHaHBSaDBh

Sysnative - attached

Attached Files



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:37 AM

Posted 01 February 2018 - 02:09 PM

The uploaded memory dumps were both DPC_WATCHDOG_VIOLATION errors

They were not Driver Verifier memory dumps.

As such, this means the problem is most likely to be hardware related (but compatibility and low-level drivers remain a less-likely possibility).

 

I have seen problems with the VBAudio drivers in the past (just a hunch on my part).

You may want to try uninstalling VB Virtual Audio driver from VB Audio VoiceMeeter and see if that helps.

 

Here's my suggested procedure to fully rule out a hardware problem:

 

My suggested way to diagnose a hardware problem (3 steps):

 

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:

 

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

 

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [ :(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

Edited by usasma, 01 February 2018 - 02:13 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:37 AM

Posted 01 February 2018 - 02:13 PM

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Tue Jan 30 02:37:37.074 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\013018-28671-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18896.amd64fre.winblue_ltsb_escrow.180108-1534
System Uptime:0 days 0:46:21.875
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_VRF_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  FC
  BIOS Release Date             02/26/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             970A-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 29 14:13:06.919 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012918-15031-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18896.amd64fre.winblue_ltsb_escrow.180108-1534
System Uptime:0 days 2:56:04.641
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  FC
  BIOS Release Date             02/26/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             970A-UD3P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Jan 30 02:37:37.074 2018 (UTC - 5:00)**************************
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
vbaudio_vmvaio64_win7.sys   Mon Apr 21 05:05:09 2014 (5354DF45)
vbaudio_cable64_win7.sys    Thu Aug 14 02:15:25 2014 (53EC53FD)
xhcdrv.sys                  Thu Oct 30 22:43:52 2014 (5452F768)
ViaHub3.sys                 Thu Oct 30 22:43:57 2014 (5452F76D)
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
ElgatoGC656.sys             Thu Nov  5 03:27:04 2015 (563B12D8)
ElgatoVAD.sys               Mon Aug  8 07:32:12 2016 (57A86DBC)
ssdevfactory.sys            Wed Apr  5 12:51:17 2017 (58E52085)
RTKVHD64.sys                Wed Jun 14 01:58:31 2017 (5940D087)
sshid.sys                   Mon Aug 14 19:21:50 2017 (5992308E)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
Rt630x64.sys                Tue Oct  3 04:35:11 2017 (59D34BBF)
nvlddmkm.sys                Fri Oct 27 11:43:19 2017 (59F35417)
nvvadarm.sys                Fri Oct 27 11:56:26 2017 (59F3572A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 29 14:13:06.919 2018 (UTC - 5:00)**************************
MpKsl19aa6076.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
xusb22.sys                  Tue Mar 18 04:18:41 2014 (53280161)
nvvad64v.sys                Thu Dec 14 00:40:29 2017 (5A320ECD)
nvhda64v.sys                Fri Dec 15 03:17:43 2017 (5A338527)
nvlddmkm.sys                Wed Jan  3 18:39:48 2018 (5A4D69C4)
nvvadarm.sys                Wed Jan  3 18:56:49 2018 (5A4D6DC1)


http://www.carrona.org/drivers/driver.php?id=amdide64.sys
http://www.carrona.org/drivers/driver.php?id=vbaudio_vmvaio64_win7.sys
http://www.carrona.org/drivers/driver.php?id=vbaudio_cable64_win7.sys
http://www.carrona.org/drivers/driver.php?id=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
ElgatoGC656.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.
ElgatoVAD.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.
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
MpKsl19aa6076.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.
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#12 steven12

steven12
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:10:37 AM

Posted 05 February 2018 - 01:48 PM

Alright so I just finished step #1 with some (hopefully) telling results.

1- Malware scans showed nothing

2- Ran 3 passes of Memtest86 with 0 resulting errors

3- Ran Seagate Seatools for Windows (Long Generic test) for the HDD with no issues. Ran CrystalDiskMark on SSD and the numbers didn't look unusual. Ran CrystalDiskInfo on HDD (Good) and SSD (Good 96%) from Windows and they both looked fine.

4- Ran Furmark twice, once for 15 mins (0 anti-aliasing) and the other for 10 mins (4x). On both runs I waited for the temps on the graph to flatten and it did so at 81C/82C for me. I read that the temps may continue to rise over time though but at a very slow rate. The directions said either to wait for problems or wait for the temps to max out so I think I ran that correctly. No errors at all.

5- Ran Prime95 for 24 hours (max CPU temp of 55C but stayed around 50C for most of it) with no fails. The workers were out of sync but I read that this is normal if you do something else during it (I had a browser open to look at that among other things haha).

6- A- Ran Memtest G80 from simtek on default settings (selected 0 for custom clock speeds [DEFAULT] because I wasn't too sure what it wanted) for 50 iterations and I always get "Random Block" errors. I've read that many people get those though with this software.

    B- VMT showed no errors during the Direct X and CUDA tests

    C- Tried running Artifact Locator. It ran for a little but then it said that the test was incompatible with my PC.

    D- I ran all 4 tests here for 1 hour a piece and got a bunch of graphs that I have no clue what to do with! No issues with the PC while the tests were running though.

    E- Same program as "B" but bootable so I didn't run it.

7- Ran this CPU stability test and it FAILED every single time: http://majorgeeks.com/CPU_Stability_Test_d215.html The fail error looks like this: Attached File  Capture.PNG   44.52KB   0 downloads It's saying that my system is unstable. I tried to find stuff online to make sure that this test ran properly with my FX 8350 but I couldn't find anything. If it isn't the CPU it must be the mobo?

 

All temps looked fine with all of these tests. I want to say that it isn't a GPU issue. Maybe another mobo issue. I don't think it's the PSU but is there a way to officially rule that out? Should I proceed to step #2?



#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:37 AM

Posted 05 February 2018 - 05:46 PM

Step 2 will help to ensure that it's not a software error.

Then Step 3 will let you test the components.

Those components that are left will need testing by replacement (either with a known good component that you borrowed from somewhere, or by purchasing a replacement)

If you do purchase replacements, I suggest doing it from a place that'll let you return it for your money back (if it's not needed).


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users