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

Custom PC (Loads of BSOD's) - Gaming


  • Please log in to reply
1 reply to this topic

#1 CyronDnB

CyronDnB

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:33 AM

Posted 20 June 2016 - 12:01 PM

Hello all, hopefully you guys are able to help me with this situation. I mainly play Counter Strike - Global Offensive and ARMA 3, no matter what game I am on I will always get a BSOD error of all different kinds, I have noted most of them down which I will list below if it may help. Appreciate the support in advance.

 

CLOCK_WATCHDOG_TIMEOUT

IRQL_NOT_LESS_OR_EQUAL

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (USBXHCI.SYS)

KERNEL_SECURITY_CHECK_FAILURE

PAGE_FAULT_IN_NONPAGED_AREA

 

I sometimes receive popup errors such as:

 

Whilst Shutting Down:

 

RzStats.Manager.exe - Application Error (Error Window Title) - The instruction at 0x0000000072657a62 referenced memory at 0x000000000000000F. The memory could not be read.

 

RzStats.Manager.exe - Application Error (Error Window Title) - The instruction at 0x0000000000000000 referenced memory at 0x0000000000000000. The memory could not be read.

 

Whilst browsing the servers:

 

Arma 3: arma3.exe - Application Error (Error Window Title) - The instruction at 0x00000000016DF3EA referenced memory at 0x00000000000000EC. The memory could not be read.

 

 

· OS - Windows 8.1, 8, 7, Vista ? - Windows 10
· x86 (32-bit) or x64 ? - 64-bit
· What was original installed OS on system? - N/A
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - OEM (Retailer)
· Age of system (hardware) - Less than 2 months
· Age of OS installation - have you re-installed the OS? - Nope

· CPU - Intel Core i7 6700k (Not Overclocked)
· Video Card - MSI Nvidia GTX 970 Twin Frozr
· MotherBoard - (if NOT a laptop) - Asus z170 Pro Gaming
· Power Supply - brand & wattage (skip if laptop) - Cooler Master v850 (850 Watts) 80 Plus Gold

· System Manufacturer - N/A
· Exact model number (if laptop, check label on bottom) - N/A

· Laptop or Desktop? - Desktop

Attached Files



BC AdBot (Login to Remove)

 


#2 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:10:33 PM

Posted 21 June 2016 - 07:43 AM

Your UEFI/BIOS (version 1204) dates from 2016.  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 recent update.

Only 4 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
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.

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

Your description of multiple different BSOD errors may be suggestive of a hardware problem.
Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

 

Beyond that, I'd suggest updating the older drivers that appear in the memory dumps below.

Pay particular attention to those that date from before the release of the Fall  Update (15 November 2015).

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Mon Jun 20 12:33:24.770 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062016-3765-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:0 days 0:00:30.373
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffd000ee1ed180, 6}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd000ee1ed180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 20 12:32:16.149 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062016-3968-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:0 days 0:00:27.752
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffd0014e2ac180, 7}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0014e2ac180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  NvStreamUserAg
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  1204
  BIOS Release Date             01/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 20 12:28:51.647 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062016-4593-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:0 days 0:00:18.251
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffd0006e3ed180, 6}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0006e3ed180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  1204
  BIOS Release Date             01/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




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:

**************************Mon Jun 20 12:33:24.770 2016 (UTC - 4:00)**************************
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
ASUSFILTER.sys              Tue Sep 20 11:46:33 2011 (4E78B559)
AiChargerPlus.sys           Wed Apr 18 21:17:35 2012 (4F8F67AF)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
IOMap64.sys                 Tue Jul  2 04:27:47 2013 (51D28F03)
I2cHkBurn.sys               Mon Feb 17 20:34:54 2014 (5302B8BE)
gfdriver.sys                Sun Jan  4 10:04:47 2015 (54A9568F)
AndroidAFDx64.sys           Mon Jul  6 04:58:49 2015 (559A4349)
e1d65x64.sys                Thu Aug 13 05:14:29 2015 (55CC5FF5)
rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
nvhda64v.sys                Thu Mar 24 15:26:36 2016 (56F43F6C)
rzendpt.sys                 Tue Apr  5 03:09:18 2016 (5703649E)
rzudd.sys                   Tue Apr  5 03:09:21 2016 (570364A1)
rzvkeyboard.sys             Tue Apr  5 03:09:21 2016 (570364A1)
rzdaendpt.sys               Tue Apr  5 03:09:22 2016 (570364A2)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
NvStreamKms.sys             Sun May  1 17:00:16 2016 (57266E60)
nvlddmkm.sys                Thu Jun  2 23:11:28 2016 (5750F560)


http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=ASUSFILTER.sys
http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
I2cHkBurn.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.
gfdriver.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.
AndroidAFDx64.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=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users