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

Getting BSOD with CLOCK WATCHDOG TIMEOUT


  • Please log in to reply
11 replies to this topic

#1 soctaviano

soctaviano

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 19 November 2016 - 05:41 PM

Hello Community!

 

My son and I have built a brand new rig and are getting intermittent BSOD's with the CLOCK WATCHDOG TIMEOUT error.  Happens when playing any graphics intensive games or apps, like Space Engine, BeamNG Drive, Fall Out 4 or Gary's Mod with a lot of items loaded. Usually starts out with short screen freezes and/or jitters -- with the sound also getting halted. Eventually the BSOD arrives to our dismay.  We even saw some jittering the other day watching a YouTube video!

 

Here's our component list we used for our build:

- Intel Core i7 6700K 4.00 GHz Unlocked Quad Core Skylake Desktop Processor, Socket LGA 1151 [BX80662I76700K]
- ASUS Z170 PRO GAMING LGA 1151 Intel Z170 HDMI SATA 6Gb/s USB 3.1 USB 3.0 ATX Intel Motherboard
- GIGABYTE GeForce GTX 1060 Windforce OC GV-N1060WF2OC-6GD Video Card
- 1 x G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4 24000) Intel Z170 Desktop Memory 
- EVGA 650 GQ, 80+ GOLD 650W, Semi Modular, EVGA ECO Mode (PSU)
- Boot drive on: Crucial M500 480GB SATA Internal Solid State Drive CT480M500SSD1 -- THIS IS THE ONLY USED COMPONENT TAKEN FROM AN OLD PC (FORMATTED)
- Steam Games installed on new: WD Black 2TB Performance Desktop Hard Disk Drive - 7200 RPM SATA 6Gb/s 64MB Cache 3.5 Inch - WD2003FZEX
- Corsair Hydro Series Cooling H75 Performance Liquid CPU Cooler (plus two other case fans)
- AOC G2260VWQ6 Gaming 21.5'' LCD Monitor (1080p - 60hz)
- NZXT S340 Matte Black/Red Steel ATX Mid Tower Case
- Windows 10 Home Basic 64bit OEM

 

Here are the many steps taken to refresh drivers and perform diagnostics:

- After Win10 install, performed several Windows Updates to be on the latest

- Initially installed all drivers from CD's provided by component manufacturers -- but from what I've read this seemed like a mistake

- Uninstalled several drivers and re-installed by downloading latest drivers from websites manually, also removed ALL dumb extra utilities from ASUS and GIGABYTE

- Nvidia drivers are the latest

- Updated to latest mobo driver using flash install

- Reset BIOS settings to defaults

 

- Ran Win10 MemTest - passed; Downloaded and ran memtest86+ for 2 or 3 passes with no errors

- Downloaded and ran Intel CPU Diagnostic Tool -- passed

- Ran Heaven GPU benchmarking tool on extreme setings, and it plays video, but with a lot of white screen flashing and occasional jittering - not sure if normal, but here is a link to a video showing how the test ran:  https://goo.gl/tPY2RA 

 

Then I stumbled onto this website and community after researching CLOCK WATCHDOG TIMEOUT and saw a means to post my data for analysis and review.

 

Other websites (like Tom's HW) have recommendations of re-installing Win 10 and installing correct drivers 1st before any windows updates, then do win updates and install games and see if still happens. Please let me know if this is the correct course of action next, or if I have a real HW problem.

 

I've attached the requested files ... please let me know if you need anything else.

 

Thank you SO VERY MUCH in advance if you can help us!

 

-Steve

 

#### UPDATE ####

 

1. We got a memory manager BSOD trying the DRIVER VERIFIER process, so we just had to restore from restore point and zipped/attached the latest dump file.

2. We are using an SSD for boot drive so we ran SSDLife tool (trial version) and attached screen shots -- life is very good

3. We plan to run memtest86+ overnight to see if we come up with any RAM errors -- we will post back here if so.

Attached Files


Edited by soctaviano, 19 November 2016 - 06:40 PM.


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:12:46 PM

Posted 20 November 2016 - 06:29 AM

In general, there are only 2 things that can be wrong with your system - hardware or software

We break the software down into 3rd party (non-Windows) and Windows software/drivers (as there are different ways of dealing with each, and that most BSOD issues are due to 3rd party software/drivers) 

 

Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this) (MS says 70% as of mid-2016)
- then I rule out hardware (less than 10% of BSOD's are due to this) (MS says 10% as of mid-2016)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date). (MS says 5% as of mid-2016)
- also, MS says that 15% are due to unknown causes (the crash is too corrupted to tell) as of mid-2016

I usually suggest these steps (but customize them depending on the situation and the evidence in the reports):

 

Beyond this I have these 5 suggestions:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your system from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If ALL of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

On with the analysis..........

 

Your UEFI/BIOS (version 2003) 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 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.

IDSVIA64.sys (a driver for Norton) is blamed for a BSOD in the WER section of MSINFO32.

in order to test, please uninstall Nortan and see if that stops the BSOD's.

Use Windows Defender and Windows firewall for protection while testing.

If you wish to reinstall Norton, please wait until we've finished troubleshooting and then download a fresh copy from the Norton website.

 

If that doesn't solve the BSOD's, then I'd suggest running these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

I would re-run MemTest overnight, and would ensure that you run Prime95's Blend test - as this might be a memory error.

Beyond that, run the rest of the diagnostics as they can also point to memory errors - and please let us know the results.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Nov 19 17:57:18.638 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111916-5765-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:00:11.320
*** WARNING: Unable to verify timestamp for AsIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsIO.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 1A, {1233, bf1c1, 0, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000001233, The subtype of the bugcheck.
Arg2: 00000000000bf1c1
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_1233
PROCESS_NAME:  atkexComSvc.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov 19 16:55:48.126 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111916-6078-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 1:52:54.765
*** 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 101, {18, 0, ffffe08007608180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffe08007608180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  Heaven.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov 19 15:02:21.593 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111916-7796-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 17:54:16.234
*** 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 101, {18, 0, ffff80007c008180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff80007c008180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  RobloxPlayerBeta.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler

[/QUOTE]


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:

**************************Sat Nov 19 17:57:18.638 2016 (UTC - 5:00)**************************
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
ICCWDT.sys                  Tue Apr 21 05:51:44 2015 (55361DB0)
e1d65x64.sys                Thu Aug 13 05:14:29 2015 (55CC5FF5)
iaStorA.sys                 Wed Nov  4 05:27:49 2015 (5639DDA5)
TeeDriverW8x64.sys          Wed Feb  3 17:41:13 2016 (56B28209)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
trufos.sys                  Fri Feb  5 13:10:19 2016 (56B4E58B)
bdfwfpf.sys                 Wed Jun 15 07:17:44 2016 (57613958)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
exfat.SYS                   Fri Jul 15 22:20:44 2016 (578999FC)
RTKVHD64.sys                Wed Aug  3 07:54:55 2016 (57A1DB8F)
avc3.sys                    Thu Sep 15 08:37:35 2016 (57DA960F)
avckf.sys                   Thu Sep 15 08:46:29 2016 (57DA9825)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
gzflt.sys                   Fri Oct 28 05:28:18 2016 (58131A32)
nvlddmkm.sys                Thu Nov 10 17:01:49 2016 (5824EE4D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov 17 11:23:34.579 2016 (UTC - 5:00)**************************
iqvw64e.sys                 Wed Apr 22 07:46:58 2015 (55378A32)


http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.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=trufos.sys
http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=exfat.SYS
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=avckf.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=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.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.

#3 soctaviano

soctaviano
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 22 November 2016 - 09:23 PM

Okay, sorry for the delay in getting back to you, but we have tried MANY things to resolve without success, here's the steps we have taken based on your feedback and analysis:

 

1.  Get ALL available Windows Updates.  It may take several trips to get them all

2.  Get ALL available, compatible updates for your system from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website

 

Regarding these 3 above, we went ahead an reinstalled Windows 10 to rule out any driver issues - wiping clean everything we have done previously.

Before doing this, we downloaded and copied to USB stick the very latest set of recommended drivers from our ASUS motherboard site (FW update, chipset, LAN, USB, etc.), and also downloaded a copy of the very latest Nvidia drivers for our GTX 1060 card.

Then we ran these driver updates, and then ran several passes of Win 10 Updates to make sure it was the latest.

 

We installed Steam and a few games, but started to experience GAME FREEZES (sound track froze also) - requiring reboots. But no BSOD's.

 

So now we felt this could be HW related, but not sure. We felt it may be RAM related ... therefore we started to look into your other recommendations ...

4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If ALL of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

We ran memtest86+ overnight and did see a few errors listed in pass #4 test#7, so we let it run longer but did not see any additional errors accumulate.

 

We decided to purchase new memory sticks and swapped out the originals we felt may have issues because of the memtest results. We ensured the new memory we purchased was listed on the ASUS motherboard approved list. After installing these and removing the others, we went into the BIOS to ensure they were configured properly and chose Default BIOS Settings.

 

We then tested the same set of games (Space Engine, BeamNG.drive, Half-Life2, etc. and experienced the same freezing!

 

Okay, so it was time to run more of these HW Diagnostic tests.

 

We ran extensive tests with Furmark with NO issues at all. We even ran the CPU burner at the same time with the highest Furmark settings with NO problems!

 

We then ran Prime95 blend test.  This ran for a while, with CPU temps reaching up to the low 60's C but then blew up with a BSOD -- we are attaching the SysNativeCollectionApp.zip

 

We also ran (and we are still running) the Driver Verifier as per the detailed instructions. We queried the results after a successful reboot and they seem normal. We will keep this running for 24 hours.

 

Also attached is an html perfmon report.

 

So to recap, we are not seeing BSOD's any longer (except the one created by Prime95) but almost any game we run now freezes.

 

Any ideas?  Thank you soooo much!

 

 

### NEW UPDATE ###

 

We ARE getting BSOD's -- we just had to wait longer. We waited threw several games freezes and eventually received the CLOCK WATCHDOG TIMEOUT

So we updated the zip file uploaded which should have this latest BSOD dump in it.

 

Thanks

Attached Files


Edited by soctaviano, 22 November 2016 - 09:48 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:12:46 PM

Posted 23 November 2016 - 08:34 AM

Lot's of good work here.  Thanks for the detailed report!

 

From what you've done, this seems like a hardware problem.

Try running Prime95 again and see if it forces a BSOD again.
If it's reproducible, then I'd say that we've identified a hardware problem.

 

Prime95 generally tests RAM, CPU cache, and the memory controller (in the CPU in i7 processors)

Next thing to remember is that no test of hardware is 100% certain - so we let them guide us, but the ultimate test is by replacing parts.

 

As you've replaced the RAM, we presume that it is good.

You ran the CPU burner program - so we have to think that the CPU is good (although it would be good to run the Intel Processor Diagnostic tests to verify)

After that, then next most likely problem is the motherboard.  Unfortunately, there are no tests for that.

It would be easier to test another video card (if you have one) in order to rule out the video.  If you don't have one, you may want to purchase one from a shop that will let you return it if it's not needed (for your money back).

 

Finally, beyond the hardware diagnostics, I suggest this procedure to help rule things out:  http://www.carrona.org/strpdown.html

 

I'll be back later on with the memory dumps.

I have to reboot my system (it's having serious lag issues) and I've got to go to the store for groceries.


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 soctaviano

soctaviano
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 23 November 2016 - 03:28 PM

although it would be good to run the Intel Processor Diagnostic tests

We downloaded and ran this test a few times -- all passed

 

It would be easier to test another video card (if you have one)

How about we disable the Nvidia Card Driver and then plug monitor into motherboard to force it to use native Intel Graphics and drivers to see if freezing at least goes away?  We do not think it is the video card due to the very intense Furmark testing which took it way beyond what some of our old games are doing.

 

It almost seems like as soon as we use one of these games, things freeze up - which makes no sense. Like it's maybe trying to use an old or incompatible Open GL driver or something -- I have no idea really.  We do have the latest Nvidia drivers installed so doubt that's a problem.  It almost seems like this rig is too powerful to run older games like Half-Life 2 -- but it should be no issue.

 

I agree, could be motherboard.  In fact, yesterday when I was writing the above response update in Chrome I got a BSOD -- just in the Chrome browser with nothing else running! 

 

Thanks.



#6 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:12:46 PM

Posted 24 November 2016 - 06:09 AM

Sorry for the delay in responding, got hung up on yard work then collapsed after dinner (I've got a cold).

 

I've never tried the video card thing that way (but it's a great idea!).
It sounds reasonable to remove the nVidia card completely and then see if the onboard graphics works w/o problems.

Just disabling the card leaves the card still in the machine - and if it's a hardware problem it may affect the results even though the card isn't being used.

Another option (I just thought of this) is to try another slot for the video card.  It's possible that the slot could be causing problems

 

The Furmark test only tests some of the video card - not all of the components in the card.
I've seen instances where a card has passed all of the video tests that I suggest, yet it still is fixed when replacing the card.

In the interests of keeping expenses down, let's try the other tests (onboard graphics and another slot) before going that route tho'

 

Recently (in the last 6 months or so) I've seen issues with video cards that weren't present in older versions.

I suspect that the advances in video card technology have made cards that can fail with some individual components, yet the card itself keeps operating.

And, we don't have tests that thoroughly test the cards (as is the case with motherboards) - so we're left with replacing parts as our tool of last resort.

 

There are plenty of things running in the background on a Windows PC, so you can't just blame it on Chrome.

Other programs will self-launch, do their business, and then exit without you even seeing them do this.

You can see all the "crap" in the background if you look in the Detailed View of Task Manager.

 

Another ideo is to try a clean boot ( https://support.microsoft.com/en-us/kb/929135 ).

This'll keep most of the extra stuff from starting - and you can run this to see if the BSOD's still occur.

If it stops them, then you can re=enable things one-by-one to see if that helps.

IMO this is a hardware problem - so this shouldn't change things significantly

 

The procedure at http://www.carrona.org/strpdown.html is designed to eliminate as much of the hardware as possible (this includes the standalone video card since you have onboard graphics).

That way you can narrow down the problem part more easily.

 

The memory dumps are suggestive of a hardware problem also

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Nov 22 21:34:24.487 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112216-6359-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:05:48.187
*** 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 101, {18, 0, ffffa5818b228180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa5818b228180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 22 20:31:02.232 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112216-5281-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:12:15.871
Probably caused by :ntkrnlmp.exe ( nt!KiTimerWaitTest+9c )
BugCheck 1E, {ffffffffc0000005, fffff802bd8e389c, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff802bd8e389c, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiTimerWaitTest
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/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:

**************************Tue Nov 22 21:34:24.487 2016 (UTC - 5:00)**************************
e1d65x64.sys                Thu Aug 13 05:14:29 2015 (55CC5FF5)
iaStorA.sys                 Wed Nov  4 05:27:49 2015 (5639DDA5)
TeeDriverW8x64.sys          Wed Feb  3 17:41:13 2016 (56B28209)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
RTKVHD64.sys                Wed Aug  3 07:54:55 2016 (57A1DB8F)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Wed Nov 16 19:26:04 2016 (582CF91C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 22 20:31:02.232 2016 (UTC - 5:00)**************************
cpuz140_x64.sys             Sun Aug 14 15:15:42 2016 (57B0C35E)


http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.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=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.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
cpuz140_x64.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.
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.

#7 soctaviano

soctaviano
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 01 December 2016 - 03:28 PM

Here is the latest actions (somewhat extreme) I have taken and the status:

1. I returned and replaced the mobo with a different brand (MSI Z170A Gaming Pro) to rule that out as an issue.
2. I removed the graphics card to use mobo standard graphics -- to rule out the graphics card as an issue.
3. I re-installed Win10 on new 2TB WD Black HD to rule out my old Crucial SSD which was being used as boot drive -- just in case that had anything to do with the issues.
4. I replaced the RAM (returned those also) with another brand (Corsair Vengeance DDR4 3000Mhz) to rule that out as an issue.

Verdict = Same exact stuff happening. Games freeze (even older ones like Half Life 2). Varied BSOD's after a while, even when simply running a Youtube video.

I even tried changing monitors (one that used HDMI to DVI cables); tried removing speakers to rule out voltage issues; and made sure BIOS is up to date on new mobo and set to standard settings.

MY ONLY FINAL CONCLUSION = that it must be the CPU (which is usually very rare).

I did run the Intel CPU Diagnostic Tool, and yes that passed fine. But when I try to run the Prime95 tool with a blend stress test I get BSOD's pretty quickly. And yes, I verified CPU temps and they never go past 62 degrees C under stress, and I'm using a liquid cooler and NO overclocking.

I doubt this has anything to do with the PSU, especially since the graphics card is removed and that uses the most power. And I doubt it's the actual Computer Case.

So, since I ordered my CPU from Amazon, they are shipping me a replacement to try.

WISH ME LUCK -- unless you have any other ideas.

 

Thanks Again !!!!    I will post new CPU results next week.



#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:12:46 PM

Posted 01 December 2016 - 06:10 PM

Good luck!

Have you had a look at this procedure:  http://www.carrona.org/strpdown.html

I'd try another PSU (but we have spares at work).

You may want to try one from another system, or purchase one from a shop that will let you return it (for your money back) if it's not needed.

 

The blend test in Prime95 primarily tests RAM, but it does have an effect on the CPU cache and the memory controller.

Try running the Small FFT's and Large FFT's tests - they may crash the system more quickly than the Blend test.
If that's the case, then it could be a sign of a bad CPU.


Edited by usasma, 01 December 2016 - 06:11 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.

#9 soctaviano

soctaviano
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 01 December 2016 - 09:30 PM

Try running the Small FFT's and Large FFT's tests - they may crash the system more quickly than the Blend test.

 

Wow - these blew up very quickly with various BSOD's.

 

Strip down procedure is painful -- I feel I have isolated a fair amount and wanna see what happens with the new CPU arriving Monday first.

 

I will keep you posted on the results.

 

​Very much appreciated!


Edited by soctaviano, 01 December 2016 - 09:30 PM.


#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:12:46 PM

Posted 02 December 2016 - 06:21 AM

Since Small and Large FFT's crashed more quickly than the Blend test - the suspicion falls on your CPU.
This isn't a full diagnosis, but it makes it more likely that the CPU was to blame.


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 soctaviano

soctaviano
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:46 AM

Posted 07 December 2016 - 07:17 AM

EUREKA !!!

 

After replacing the Intel CPU, EVERYTHING is working perfectly and as expected.  This was somewhat hard to isolate since the system booted up and ran fine for a while, and the Intel CPU Diagnostic Tool always passed (therefore not a very reliable test).  I suspect the CPU must of had some sort of core timing issue or something like that which eventually caused all these BSOD's.

 

Well, all is well and my son is thrilled ... Thanks for all your help and guidance.  It was very much appreciated!!!

 

-Steve



#12 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:12:46 PM

Posted 07 December 2016 - 05:16 PM

Software tests of hardware parts are, IMO, limited in what they can test.

I'm glad to hear that you've fixed it!

Happy computing!


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