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

Windows 10 continued BSOD self build desktop


  • Please log in to reply
2 replies to this topic

#1 scotsman68

scotsman68

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:45 AM

Posted 07 September 2017 - 05:29 PM

Hi, I built a gaming computer along with my son, it did blue screen a few times when first built then worked fine for months now it blue screens all the time, we have run memtest86 and tried serveral other options like running with one memory stick then the other to try and find the problem with no luck, we have restored to previous save points etc.. it now blue screens several time before starting up properly and then may run for one or two nights then back to the bsod routine.

 

We have an old Video card amd radeon hd 6670 (until a new card can be brought) but the computer blue screens with or without the card in.

 

Information Requested

 

operating system : Windows 10 pro ver 1703 build 15063.540

64bit

The original operating system was Windows 10

Full version purchased from retailer

All   under 1 year except Video card

windows was brought to install on this computer (Has not been reinstalled)

 

Desktop

I7 7700k Intel Processor 4.2ghz

AMD Radeon HD 6670

Asus maximus IX Hero motherboard

Corsair 650 Power Supply

 

 

 

 

 

 

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,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:45 AM

Posted 09 September 2017 - 01:51 PM

No Windows Update hotfixes installed.  Most build 15063 (1703) 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.

If that doesn't fix things, then I'd suspect it may be a hardware problem.
Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please start with the video tests (Furmark and Other video), but 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:
**************************Thu Sep  7 17:30:38.810 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090717-27937-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:00:35.443
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffe680803ea180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffe680803ea180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep  7 17:02:56.808 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090717-28921-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:00:23.442
Probably caused by :memory_corruption
BugCheck 101, {18, 0, ffffdb014b040180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffdb014b040180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep  7 16:49:07.807 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090717-18078-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:00:29.447
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffff8000f3380180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8000f3380180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Sep  7 17:30:38.810 2017 (UTC - 4:00)**************************
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
atikmpag.sys                Fri Feb 26 14:58:13 2016 (56D0AE55)
AtihdWT6.sys                Fri Feb 26 15:18:09 2016 (56D0B301)
atikmdag.sys                Fri Feb 26 15:29:22 2016 (56D0B5A2)
TeeDriverW8x64.sys          Wed Aug 31 18:45:52 2016 (57C75E20)
e1d65x64.sys                Wed Oct  5 05:02:43 2016 (57F4C1B3)
intelppm.sys                ***** Invalid 2007 Invalid 2007 Invalid


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=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.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 scotsman68

scotsman68
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:45 AM

Posted 10 September 2017 - 05:38 AM

thank will do updates and run diags






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users