BSOD - ntoskrnl.exe/hal.dll

dantas17 · 10 Jun 2020

Hello all,

Lately I've been having some problems with my computer since it has been freezing for a while then BSOD.
The warning that appears on the BSOD is " DPC Watiching Violation".
What appears on BlueScreenView is that is caused by hal.dll and ntoskrnl.exe.

I've updated all my drivers, updated the windows, cleaned what I could, bought an extra fan because I thought it could be temperatures but it didn't help and I ran out of options.

It usually happens mostly when I'm playing any game, outside gaming the computers sometimes freezes for a couple of seconds then comes back.

Here is the Dxdiag, in case it helps:
------------------ System Information ------------------ Time of this r - Pastebin.com

And in att the log collector.
Hope that someone can help me out

Thank you very much

zbook · 10 Jun 2020

Hi dantas17,

Welcome to the BSOD forum.

The logs were in a foreign language and could not be scanned.
Please use English as the default language so the logs can be scanned and read:

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

For all steps please make sure images are posted into the thread:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

There was only one mini dump file.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com

13) The logs displayed overclocking with Intel(R) Core(TM) i7-8700K tested RAM speeds up to 2666.
The current speed is 3000.
The maximum tested speed is 2666.

14) Make sure that there is no over clocking while troubleshooting

15) Sometimes there are problems in the bios that produce BSOD

16) The BIOS: Data/versão de BIOS American Megatrends Inc. 2.60, 05/07/2018
Upgrade the BIOS: 2.6 > 2B
Support For Z370-A PRO | Motherboard - The world leader in motherboard design | MSI Global

17) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

18) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

19) Uninstall Driver Booster

20) Identify any drivers installed by Driver Booster and install new drivers from the MSI website or the component manufacturer website

21) Identify software with driver replacement for:
nvrtxvad64v.sys
NVIDIA RTX Voice
NVIDIA RTX Voice: Setup Guide

22) Give feedback to Nvidia and open a support ticket:
NVIDIA RTX Voice Feedback Form

23) Uninstall NVIDIA RTX Voice during the troubleshooting.
Only if necessary reinstall the application with its driver nvrtxvad64v.sys

https://answers.microsoft.com/en-us/...0-8d22254aa1c1

24) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Code:

Nome	NVIDIA RTX Voice
Fabricante	NVIDIA
Estado	OK
ID de dispositivo PNP	ROOT\UNNAMED_DEVICE\0002
Controlador	C:\WINDOWS\SYSTEM32\DRIVERS\NVRTXVAD64V.SYS (1.0.0.0, 53,23 KB (54*504 bytes), 28/04/2020 18:46)

Code:

nvrtxvad_waveextensible	NVIDIA RTX Voice	c:\windows\system32\drivers\nvrtxvad64v.sys	Kernel Driver	Não	Manual	Stopped	OK	Normal	Não	Não

Code:

nvrtxvad64v.sys Thu Mar 12 02:52:51 2020 (5E6A0673)

dantas17 · 11 Jun 2020

Hello Zbook,

Thank you very much for your answer.
I've tried to follow your steps as strictly as I could, if I did something wrong I'm really sorry.

The cmd part (1-11):

Code:

Microsoft Windows [Version 10.0.18363.900]
(c) 2019 Microsoft Corporation. All rights reserved.
 
C:\WINDOWS\system32>sfc /scannow
 
Beginning system scan.  This process will take some time.
 
Beginning verification phase of system scan.
Verification 100% complete.
 
Windows Resource Protection did not find any integrity violations.
 
C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
 
Deployment Image Servicing and Management tool
Version: 10.0.18362.900
 
Image Version: 10.0.18363.900
 
[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
 
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
 
Deployment Image Servicing and Management tool
Version: 10.0.18362.900
 
Image Version: 10.0.18363.900
 
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 
C:\WINDOWS\system32>
C:\WINDOWS\system32>sfc /scannow
 
Beginning system scan.  This process will take some time.
 
Beginning verification phase of system scan.
Verification 100% complete.
 
Windows Resource Protection did not find any integrity violations.
 
C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ...
  791808 file records processed.
File verification completed.
  28423 large file records processed.
  0 bad file records processed.
 
Stage 2: Examining file name linkage ...
  1865 reparse records processed.
  1095210 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  1865 reparse records processed.
 
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  151702 data files processed.
CHKDSK is verifying Usn Journal...
  41910616 USN bytes processed.
Usn Journal verification completed.
 
Windows has scanned the file system and found no problems.
No further action is required.
 
 468220927 KB total disk space.
 272074736 KB in 600093 files.
    390608 KB in 151703 indexes.
         0 KB in bad sectors.
    923411 KB in use by the system.
     65536 KB occupied by the log file.
 194832172 KB available on disk.
 
      4096 bytes in each allocation unit.
 117055231 total allocation units on disk.
  48708043 allocation units available on disk.
 
C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-5SJBMKO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
 
C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-5SJBMKO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
 
C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE
 
 
C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7
 
 
C:\WINDOWS\system32>bcdedit /enum {badmemory}
 
RAM Defects
-----------
identifier              {badmemory}
 
C:\WINDOWS\system32>

13 - I've never overclocked neither I know how to do it, my pc was built on a local store and came to me fresh, they didnt't installed windows. So if it's overclocked I don't know if it is by default or they changed somehow while building it.

16 - Updated

17 - Screenshot by Lightshot
Screenshot by Lightshot

18 - Screenshot by Lightshot

19 - Done

20 - I unistalled first so I couldn't check the history of updates, either way I didn't used it for major ones. If I recall was just a couple for realtek I believe.

21-23 - I've unistalled for now to check if it solves anything, anyway the drivers from Nvidia are always updated through Nvidia GeForce.

24 - Below new log collector and memory zip link: Dropbox - MEMORY.rar - Simplify your life

Hope that this helps.

Thank you very much

zbook · 11 Jun 2020

For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files

Please make sure feedback is sent to Nvidia for the RTX Voice BSOD (driver nvrtxvad64v.sys).

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

dantas17 · 11 Jun 2020

Zbook,

So you think is RTX Voice that is causing it?
I've sent them a feedback about it.

Anything else you need for me or I should do?

Thanks

zbook · 11 Jun 2020

Did you uninstall or uninstall and reinstall the software?

Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10