Question Hal.dll and ntoskrnl.exe crashes. (BSOD - Clock Watchdog Timeout)

[Vivek8668]

Just 3 days ago I upgraded from Windows 7 to Windows 10 Pro. Didn't have any major problems at all apart from not having Realtek Audio Manager installed properly but that was fixed with a simple driver install. But yesterday morning I had a BSOD, and then another one in the evening. Checked Bluescreenviewer to see what was causing it but it doesn't tell much apparently (First one marked hal.dll and second one marked both hal.dll and ntoskrnl.exe). Wanna see if you guys could help me out with this one.

https://1drv.ms/u/s!AtNxUqSedeG7bLIwdetG087UhCo?e=C4ITdz (File sharing website: OneDrive) Small memory dump zip of a crash just 20-30 minutes ago while playing a game.
https://pastebin.com/Sw6Cb18k (Dxdiag report. Just in case this can help)

General PC Specs:
Computer Type: PC/Desktop
System Manufacturer/Model Number: ACER
OS: Windows 10 x64
CPU: Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz
Motherboard: Aspire M3985
Memory: 6 GB
Graphics Card: AMD Radeon HD 7700 Series
Sound Card: Realtek HD Audio / AMD High Definition Audio Device
Monitor(s) Displays: Lcd Monitor Acer P207hv
Screen Resolution: 1600x900
Keyboard: Keyboard Multimedia Core Easy Line - USB - Black (Bought this one a few days ago before transitioning to Windows 10)
Mouse: Mouse Logitech M90
PSU: Power Supply 600w Acteck Z600 Es-05003 20+4 Pin Atx 120mm
Hard Drives: 1 TB Hard Drive and 120 GB SSD (It's where my Windows 10 is installed)
Internet Speed: 7.19 MB Down - 1.6 MB UP
Browser: Opera
Antivirus: Windows 10 Defender
Other Info: Purchased 7 years ago PRE BUILT. Only thing that I changed over the years was the GTX 640 it came with with a Radeon HD 7700

If I'm missing something important regarding my pc or if you guys need any additional info that can be useful to you. Please do tell me.

 

[Colif]

I will ask @gardenman to convert dump files into a format I can read.

ntoskrnl - Windows kernel
hal.dll = hardware abstraction Layer - sits between windows and hardware
It was an error called by CPU but not necessarily caused by it, since you updated from 7 to 10 its likely just an old driver.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/INQ6.html

File information:	041319-7890-01.dmp (Apr 13 2019 - 16:14:38)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 33 Min(s), and 28 Sec(s)

Comment: 2 or more types of RAM are installed.

Possible System page: https://www.acer.com/ac/en/AE/content/support-product/4240?b=1
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Vivek8668]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/INQ6.html

File information:	041319-7890-01.dmp (Apr 13 2019 - 16:14:38)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 33 Min(s), and 28 Sec(s)

Comment: 2 or more types of RAM are installed.

Possible System page: https://www.acer.com/ac/en/AE/content/support-product/4240?b=1
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Yeah I forgot to mention that, its a 2GB DDR2 Stick and a 4GB DDR2 stick installed. And as you said, I will wait for additional information before updating BIOS, I have never messed with any updates to the BIOS with my computer before, this seems to be a problem with me upgrading to Windows 10 from 7.

Also, I don't know if this can help but this clock watchdog timeout thing only happens when I play heavy CPU stress inducing games. Hasn't happened while using the browser but when I play games like Smite (A MOBA with heavy graphics and effects I can only last about 10-15 minutes before crashing but I can play less graphic-intensive games all day.

 

[Colif]

This might be cause only as its oldest driver and anything prior to June 2015 isn't a win 10 driver -

Aug 28 2012

dfx12x64.sys

Explore Systems Virtual Audio Device (Power Technology)

Given only drivers on web site for device are Win 7 drivers mainly, it could be any of them

See this post in regard to upgrading bios - https://community.acer.com/en/discussion/480197/acer-aspire-m3985-bios-upgrade - I would only do it if you sure.

Comment: 2 or more types of RAM are installed.

only difference is size of ram sticks, 1 is the 2gb stick and other is 4gb, code differences account for different sizes. All Acer ram, expect its from factory.

Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[Vivek8668]

This might be cause only as its oldest driver and anything prior to June 2015 isn't a win 10 driver -

Aug 28 2012

dfx12x64.sys

Explore Systems Virtual Audio Device (Power Technology)

Given only drivers on web site for device are Win 7 drivers mainly, it could be any of them

See this post in regard to upgrading bios - https://community.acer.com/en/discussion/480197/acer-aspire-m3985-bios-upgrade - I would only do it if you sure.



only difference is size of ram sticks, 1 is the 2gb stick and other is 4gb, code differences account for different sizes. All Acer ram, expect its from factory.

Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

That dfx12x64.sys is from DFX Audio Enchancer. Something I used on Windows 7 to increase the audio since it was low for me. I uninstalled it. I will hold on from updating BIOS just as a last resort I guess. Also I ran the Intel Processor Diagnostic Tool and I got a clock watchdog timeout again during it's test and when I booted the PC and logged in with my Windows Credentials I got a Machine check exception BSOD which was new.

 

[Colif]

Hmmm... Machine Check Exception (Otherwise known as WHEA errors) and Clock Watchdog Timeout errors are both hardware, both called by CPU. Not necessarily caused by them, but still. 2 hardware errors in a row...

Try making this on another PC - http://www.tcsscreening.com/files/users/IPDT_UEFI/ (its the Intel test but in a bootable form so no need for windows, it might get further or not)

 

[Vivek8668]

Try making this on another PC - http://www.tcsscreening.com/files/users/IPDT_UEFI/ (its the Intel test but in a bootable form so no need for windows, it might get further or not)

I'm sorry I don't quite understand, what do you mean make it in another PC? I don't really have another one.

 

[Colif]

ok, then make it on yours. just thought it be better to make it on a pc that works

 

[Vivek8668]

ok, then make it on yours. just thought it be better to make it on a pc that works

Ran the program and passed all tests without issues this time. Before I ran it while using browser and watching streams so maybe that was too much and crashed but now I ran it without anything open and it passed.

 

[Colif]

that is good, don't really want it to be cpu

Lets see if its software:

Before running this,

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

 

[Vivek8668]

that is good, don't really want it to be cpu

Lets see if its software:

Before running this,

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

I ran the driver verifier and crashed 2 times on boot with the DRIVER_VERIFIED_DETECTED_VIOLATION message (although it didn't specify which driver it was) before sending Recovery message on 3rd boot about using installer to boot properly. It didn't create a minidump for both of these crashes, only for one.

https://1drv.ms/u/s!AtNxUqSedeG7bmKiqoMLeXfMF4Y?e=DcjVWN One drive link for zip file containing minidump file.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/UGVp.html

File information:	041319-5734-01.dmp (Apr 14 2019 - 02:55:16)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Probably caused by:	netr28ux.sys (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 09 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Ralink RT2870 series USB802.11n Wireless Adapter Driver

RT2870
Broadband Wi-Fi Legacy Product
Please contact your device manufacturer website for product driver downloads. The driver downloads offered below for the RT2870 are designated for business partner use.

By downloading MediaTek product drivers you acknowledge they are provided without warranty and MediaTek does not provide direct support to end-users.

https://www.mediatek.com/products/broadbandWifi/rt2870

its your wifi which isn't surprising, it is a win 8 May 2015 driver on system and newest on Acer web site from 2012. There are drivers at link above, but not sure they will work on your PC.

there are 3rd party sites that claim to have newer drivers but often they just relabelled Win 8 or lower drivers. You might need to get a new wifi card and disable the onboard in laptop

 

[Vivek8668]

Ralink RT2870 series USB802.11n Wireless Adapter Driver



https://www.mediatek.com/products/broadbandWifi/rt2870

its your wifi which isn't surprising, it is a win 8 May 2015 driver on system and newest on Acer web site from 2012. There are drivers at link above, but not sure they will work on your PC.

there are 3rd party sites that claim to have newer drivers but often they just relabelled Win 8 or lower drivers. You might need to get a new wifi card and disable the onboard in laptop

Searched around the web and found this link which points to an update from 07/15/2016 for my RT2870. Installed it and seems legit. (Past update which seemed to be the issue of the BSOD was Driver Version: 5.1.25 and from 2015 and this ones from 5.1.28 and from 2016).

Gonna play around my pc for a while and see if the BSOD clock watchdog thing persists. Thank you for your help Colif and gardenman for helping me along. Will update with more minidump files if the issue persists.

 

[Colif]

i could have linked a site that purported to have the drivers but I don't like recommending 3rd party sites when the makers themselves stop supporting hardware. I can't stop you though

Cheaper than buying a new one

 

[AnpheniX]

Ralink RT2870 series USB802.11n Wireless Adapter Driver



https://www.mediatek.com/products/broadbandWifi/rt2870

its your wifi which isn't surprising, it is a win 8 May 2015 driver on system and newest on Acer web site from 2012. There are drivers at link above, but not sure they will work on your PC.

there are 3rd party sites that claim to have newer drivers but often they just relabelled Win 8 or lower drivers. You might need to get a new wifi card and disable the onboard in laptop

Ok, I was able to use the PC and play around for like an hour before I got the first BSOD, again a clock watchdog timeout. After that I couldnt use the pc for more than 5 minutes before getting another one. In total I tried using the PC 4 times after the first one. In total I got 4 clock watchdog timeout and 1 machine check exception before stopping using the PC.

RAR File (On OneDrive) Contains the 5 small memory dumps.

If it's still the driver from my wifi adapter card then I will get rid of it. I just want to know if thats still the issue since I updated the old driver to a Windows 10 driver.

 

[Colif]

guess I will have to wait for gardenman to read dumps and see.

Curious if those drivers are win 10 or not...

they not on here: https://www.catalog.update.microsoft.com/Search.aspx?q=ralink wireless g pci

drivers appear to be made by Airties Wireless networks, or at least thats who make the devices the drivers are for.

Always suspect of drivers that claim they work in XP all the way to win 10, its highly unlikely and more likely win 7 drivers. I stop speculating as bsod might be something else.

 

[Vivek8668]

guess I will have to wait for gardenman to read dumps and see.

Curious if those drivers are win 10 or not...

they not on here: https://www.catalog.update.microsoft.com/Search.aspx?q=ralink wireless g pci

drivers appear to be made by Airties Wireless networks, or at least thats who make the devices the drivers are for.

Always suspect of drivers that claim they work in XP all the way to win 10, its highly unlikely and more likely win 7 drivers. I stop speculating as bsod might be something else.

I see some ''Windows 10'' drivers from May 2015, I thought you said anything prior to June 2015 cant be a windows 10 driver, should I try installing one of these and check it out or just wait for gardenman to help you read the dumps and continue. What do you think?

 

[Colif]

Yes, june is cut off for most drivers, it doesn't mean there aren't exceptions. Its possible those are relabelled win 8 drivers that work just as well in 10 as 8, as there isn't that great a difference between 2. If they forwarded copies to MIcrosoft to be signed, that would explain why they still work with Win 10

The main reason many old drivers don't work on win 10 is digital signing. If the driver itself has not been supplied to MIcrosoft to be digitally signed to work with Windows 10, the operating system will refuse to run them, or let you install them. If companies do supply a copy to MIcrosoft, then it will run. This explains why files from 2012 and earlier can keep working on windows 10. Your PC isn't a good example but many AMD PC still have files form 2009 on them that work because AMD sent copies to MS for signing.

MS signing drivers means they should work, but many times its not that simple and newer drivers may not be sent for approval, rather company just uses signatures earned from other drivers. I don['t think Nvidia give MS a copy of every new driver, which explains why WIndows update still supplies a Driver from Sept 2017

Don't install older drivers yet. See what dumps show before attempting to fix something that might be fine

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/a1ce.html

Spoiler

File information:	041619-8328-01.dmp (Apr 16 2019 - 05:20:29)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 45 Min(s), and 36 Sec(s)

File information:	041619-6703-01.dmp (Apr 16 2019 - 05:31:52)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: MsMpEng.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 41 Sec(s)

File information:	041619-6265-01.dmp (Apr 16 2019 - 05:30:04)
Bugcheck:	MACHINE_CHECK_EXCEPTION (9C)
Probably caused by:	ntkrnlmp.exe (Process: PathOfExile_x6)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 13 Sec(s)

File information:	041619-6140-01.dmp (Apr 16 2019 - 05:24:54)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 59 Sec(s)

File information:	041619-5875-01.dmp (Apr 16 2019 - 05:32:42)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 18 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

MsMpEng = Windows Defender
POE = Online game

I interpret that as being the LAN drivers still. It doesn't help that 4 of them say unknown image where driver name should be.

I am helping someone else here with the same model PC, I just realised looking at the bios page... small world, he is getting the same error codes... coincidence?

you both have same bios version, only way i can tell 2 dumps apart is number of errors and yours shows how much ram is installed.

I think you need a new wifi card.