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

New hardware, fresh OS, BSOD and system hangs/freezes until restart


  • Please log in to reply
3 replies to this topic

#1 ludak

ludak

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:46 AM

Posted 03 February 2017 - 06:21 PM

Windows 10 Pro x64

Originally installed an old inactivated version of 10 Pro, which was a free upgrade from 8.1.  I fudged up the license and was unable to activate it so I bought a new retail version of 10 Pro on 2/2/17

Retail

PSU - 2012

SSD Samsung 840 EVO 500GB - 2014

CPU, Mobo, GPU, RAM - 2 weeks old

OS - Installed 2/2/17

 

Intel i7-7700K

ASUS GTX 1080

ASUS Strix z270e

Corsair HX750

Desktop

 

Hello, I've spent the last two days scouring this site and finally decided it was time to post for help.  The first incident was my computer freezing and requiring a restart while playing Overwatch.  It first happened 20 mins into playing, all temps were fine, game froze on screen and audio looped the last ingame sound.  Then it would happen almost immediately when I tried to relaunch the game, still temps were fine.  I played wow for an hour or so after the Overwatch incidents.  I did a clean install of windows that night with the new full retail copy of Windows 10 Pro.  I figured I couldn't activate my OS and it might fix the problems.  I was in the middle of installing mobo drivers when the first crash post-OS install happened.  Then it happened again when I was trying to install battle.net launcher app.  Those were not BSODs though, just system freezes forcing me to restart.  I got the first BSOD which was a dpc_watchdog_violation while installing something, maybe corsair link or gputweakerII.  Next was another dpc_watchdog_violation. After those I got two clock_watchdog_timeout BSODs.  In between the BSODs I had to boot into safe mode or the system would freeze soon after logging into windows.  It seems to happen when I try to install programs, but it also happens when I'm doing nothing.  

 

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:11:46 AM

Posted 06 February 2017 - 05:57 AM

Your UEFI/BIOS (version 0701) 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).
Yet the perfmon report shows problems with the different system components - I have to wonder if there are BIOS tweaks affecting the system.  Please reset the BIOS to default values and remove any tweaks that you may have done.

 

Only 3 Windows Update hotfixes installed.  Most build 14393 (1607) 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.

 

Please uninstall the Corsair Link software, then physically remove any Corsair Link devices from your system.

The Silicon Labs drivers that it uses date from 2010 - and are likely not compatible w/W10.

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

These types of errors are sometimes hardware related.  If the above steps don't stop the BSOD's, please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please run ALL of the tests and 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:
**************************Fri Feb  3 16:59:32.417 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-4343-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:10:59.093
*** 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, ffff80815f008180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff80815f008180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  0222
  BIOS Release Date             10/11/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             STRIX Z270E GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 16:23:16.417 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-4359-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:02:35.094
*** 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, ffff988145608180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff988145608180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  0222
  BIOS Release Date             10/11/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             STRIX Z270E GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 08:59:38.948 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-7062-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:17:30.625
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46470 )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  0222
  BIOS Release Date             10/11/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             STRIX Z270E GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 08:27:39.494 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-8031-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:04:53.172
Probably caused by :CLASSPNP.SYS ( CLASSPNP!ClassIoComplete+63b )
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_CLASSPNP!ClassIoComplete
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  0222
  BIOS Release Date             10/11/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             STRIX Z270E 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:

**************************Fri Feb  3 16:59:32.417 2017 (UTC - 5:00)**************************
SiLib.sys                                  Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                                Thu Jul 15 18:27:13 2010 (4C3F8B41)
AsIO.sys                                   Wed Aug 22 05:54:47 2012 (5034AC67)
dtlitescsibus.sys                          Thu Sep 24 16:17:21 2015 (56045A51)
dtliteusbbus.sys                           Mon Dec 28 08:05:52 2015 (568133B0)
btfilter.sys                               Wed Jun 22 05:21:46 2016 (576A58AA)
Qcamain10x64.sys                           Wed Jun 22 05:26:38 2016 (576A59CE)
intelppm.sys                               Fri Jul 15 22:10:43 2016 (578997A3)
iqvw64e.sys                                Tue Jul 19 10:05:36 2016 (578E33B0)
e1d65x64.sys                               Tue Jul 26 12:48:21 2016 (57979455)
TeeDriverW8x64.sys                         Wed Aug 31 18:45:52 2016 (57C75E20)
RTKVHD64.sys                               Tue Nov 22 05:34:09 2016 (58341F21)
nvvad64v.sys                               Mon Dec 19 00:50:05 2016 (5857750D)
nvvhci.sys                                 Tue Dec 27 20:44:00 2016 (586318E0)
nvlddmkm.sys                               Fri Jan 20 08:29:59 2017 (588210D7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 08:59:38.948 2017 (UTC - 5:00)**************************
690b33e1-0462-4e84-9bea-c7552b45432a.sys   Fri Jan  7 13:07:56 2011 (4D27567C)
cpuz139_x64.sys                            Wed Jan 27 04:18:15 2016 (56A88B57)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 08:27:39.494 2017 (UTC - 5:00)**************************
Qcamain10x64.sys                           Wed Feb 24 03:20:49 2016 (56CD67E1)
nvhda64v.sys                               Tue May 10 04:59:01 2016 (5731A2D5)
intelide.sys                               Fri Jul 15 22:29:13 2016 (57899BF9)
MegaSas2i.sys                              Fri Jul 22 17:36:46 2016 (579291EE)
nvlddmkm.sys                               Fri Sep 16 18:21:27 2016 (57DC7067)


http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
http://www.carrona.org/drivers/driver.php?id=dtliteusbbus.sys
http://www.carrona.org/drivers/driver.php?id=btfilter.sys
http://www.carrona.org/drivers/driver.php?id=Qcamain10x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
nvvhci.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=nvlddmkm.sys
690b33e1-0462-4e84-9bea-c7552b45432a.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=cpuz139_x64.sys
http://www.carrona.org/drivers/driver.php?id=Qcamain10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
MegaSas2i.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=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.

#3 ludak

ludak
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:46 AM

Posted 07 February 2017 - 04:53 PM

I think it's fixed, no BSODs, and all programs are running without issue.  There were no BIOS tweaks, just factory set stuff.  I updated the bios, installed more windows updates, and removed daemon tools.  I didn't uninstall corsair link because I didn't want to remove my corsair H115i as it's the only means of cooling my CPU.  Thank you for all of the help!



#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:46 AM

Posted 10 February 2017 - 07:42 AM

Glad to hear that it's working well for you.
Thanks for letting us know!


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