Windows 10: Windows 10 random restart

i am having stressful random restart with Watchdog Violation. Below is the outcome from WhoCrashed analysis:

System Information (local)
Computer name: DESKTOP-ULD3UHN
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: 80DW, LENOVO, Lancer 4B3
CPU: AuthenticAMD AMD A10-7300 Radeon R6, 10 Compute Cores 4C+6G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 3685339136 bytes total


Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 06/04/2016 08:23:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040616-52265-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x56)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 06/04/2016 08:23:23 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: athw1.sys (athw10x+0xC9E7F)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athw1.sys .
Google query: athw1.sys DPC_WATCHDOG_VIOLATION



On Tue 29/03/2016 08:53:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032916-51687-01.dmp
This was probably caused by the following module: athw1.sys (athw10x+0x9E6A4)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athw1.sys .
Google query: athw1.sys DPC_WATCHDOG_VIOLATION



On Tue 29/03/2016 02:49:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032916-51765-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




Conclusion
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

athw1.sys

:)

 

Windows 10 random restarting

OK - I'm going to get my son to do this when he comes as I haven't a clue Thanks for your help !!

 

Windows 10 random restarting

What is the make and model of your computer?

What have you done so far to troubleshoot the problem?

How long has this been happening?

Have you installed any new software or hardware drivers since you started experience this problem? If so, what are they and are they designed for Windows 10?

Have you checked the manufacturers website or contact support find out about compatibility, updates or support for Windows 10?

Do you have a system restore point created you could go back to?

Does the problem occur in other user accounts on the computer?

Which version of Windows 10 is currently installed: 1507, 1511, 1607, 1703, 1709?

Which version of Windows did you upgrade from?

It could suggest you need to update your chipset drivers and BIOS.

I recommend you update the most critical ones: BIOS, Chipset, Display Driver, Network adapters.

http://answers.microsoft.com/en-us/insider/wiki...

Awaiting your reply.

 

Hi and welcome to the forum *Smile

If i'm not mistaken, a DPC_WATCHDOG_VIOLATION with an errorcode of 0x133 usually means that more than one driver is mostly at fault.
I've noticed that different drivers are mentioned in the different DMP files but the first i would try to target is the following one:

Code: athw10x.sys --> Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter[/quote] At your Lenovo-z40-75 support page you can find the driver for your wireless adapter:

Laptops :: Lenovo Z Series laptops :: Z40-75 Laptop (Lenovo) - Lenovo Support (US)

I would suggest the following:

1) Test if you turn of your WIFI, does this issue still persists?
2) Re-install your network drivers.


EDIT:

Please not that your BIOS could use an update.

Code: BiosReleaseDate = 09/11/2014[/quote] There is an update from september 2015
Laptops :: Lenovo Z Series laptops :: Z40-75 Laptop (Lenovo) - Lenovo Support (US)





Warning
BIOS updates are risky. An improper/partial update will brick the motherboard and thus the laptop.

If you think that you can do it, you have previous experience with BIOS update etc, do it. Otherwise ask a technician to do it for you.

 

hi zztemp,

thanks for your warm welcome, looking over the problems and your suggestion. it is a very prompt one and i truely appreciated that most.

i can't determine if it will happen again if i turn off the wifi because the blue screen occurrence is random, say once every few days. anyhow i did take your suggestion to reinstall network driver, and updated the latest version of BIOS (a4cn40ww). let see if this happen again, i will update again 2-3 weeks from now.

thanks again

 

No problem, hope it works out, i'll keep an eye on this topic.

 

in fact , the day after my last post, my computer had a BSOD seizure again. i updated the network card. it all went good over one week, i thought the problem has gone away, untill yesterday, another BSOD again. Its getting frustrating and especially so when it breaks down at a time when doing something critical n important. appreciated any help at all. here is the whocrashed report:

On Mon 11/04/2016 05:08:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041116-53671-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0xFFFFE001A2825650, 0xFFFFE001A76CA080, 0x1, 0x5A181CD2168731B4)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/04/2016 05:08:49 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0xFFFFE001A2825650, 0xFFFFE001A76CA080, 0x1, 0x5A181CD2168731B4)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 07/04/2016 03:12:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-51406-01.dmp
This was probably caused by the following module: athw1.sys (athw10x+0x9F4DE)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athw1.sys .
Google query: athw1.sys DPC_WATCHDOG_VIOLATION



On Wed 06/04/2016 08:23:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040616-52265-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x56)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

WhoCrashed is very insufficient to provide the necessary data for debugging a BSOD.
We need more information *Arrow BSOD Posting Instructions

 

my apology, kindly find attached

 

What was the previous driver version you installed for the Atheros network adapter? Windows 8.1 or Windows 7?
Code: 0: kd> lmvm athw10x Browse full module list start end module name fffff800`711e0000 fffff800`71617000 athw10x T (no symbols) Loaded symbol image file: athw10x.sys Image path: \SystemRoot\System32\drivers\athw10x.sys Image name: athw10x.sys Browse all global symbols functions data Timestamp: Tue Jun 16 11:29:55 2015 (557FEC93) CheckSum: 00426BB6 ImageSize: 00437000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

hi Axe0, thank you so much for your help.
I have checked my driver version is ar956x 10.0.0.326, and online searched that this supports Windows 10

do u think that this can be the potential cause? is there anything i can do?


Attachment 74530

[/quote]

 

What Windows version was the previous driver created for?