T
TurrbanatoR
Guest
Hi,
Here is the google drive link to the zip file that contains my Minidump folder and Memory.DMP file right after my most latest crash which is detailed extensively below.
Dump 11-28-20.zip
My PC Specs are:
OS Name Microsoft Windows 10 Pro
Version 10.0.19041 Build 19041
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Ryzen 5 1600 Six-Core Processor, 3200 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P3.00, 7/13/2017
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASRock
BaseBoard Product AB350 Pro4
BaseBoard Version
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name DESKTOP-SHU35TM\ahmed
Time Zone Central Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 11.6 GB
Total Virtual Memory 26.9 GB
Available Virtual Memory 17.8 GB
Page File Space 11.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
I have been having constant BSOD when playing intensive video games or just randomly. I replaced my RAM about a month ago and for about 6-8 months before that I would have random BSOD's like irql_not_less_or_equal or FAULTY HARDWARE CORRUPTED PAGE which was more common. After replacing the RAM, and also doing a fresh install of windows 10 pro as well, I stopped getting these errors for a little bit until I started getting BSOD's again but this time I have only had DPC Watchdog Violation.
I used WhoCrashed to figure out what was causing the crash and it said the following:
On Wed 11/11/2020 6:26:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=111111]ksusba64.sys[/COLOR] (ksusba64+0x5c4b5)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8030E0FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\system32\drivers\ksusba64.sys
product: [COLOR=111111]Sound Blaster USB Audio[/COLOR]
company: [COLOR=111111]Creative Technology Ltd.[/COLOR]
description: WDM USB Audio Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: ksusba64.sys (WDM USB Audio Driver, Creative Technology Ltd.).
Google query: [COLOR=111111]ksusba64.sys Creative Technology Ltd. DPC_WATCHDOG_VIOLATION[/COLOR]
[COLOR=111111]This pointed the issue to my external soundcard (SoundBlaster G6) and I ended up uninstalling all software and drivers for that and have stopped using it. For about 2-3 weeks I had no issues until recently I had another crash with DPC Watchdog Violation again and this is what it said:[/COLOR]
[COLOR=111111]On Sat 11/28/2020 7:36:14 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=111111]nvlddmkm.sys[/COLOR] (nvlddmkm+0xab701)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800446FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5dcb5bbf5c3edcf2\nvlddmkm.sys
product: [COLOR=111111]NVIDIA Windows Kernel Mode Driver, Version 457.30[/COLOR]
company: [COLOR=111111]NVIDIA Corporation[/COLOR]
description: NVIDIA Windows Kernel Mode Driver, Version 457.30
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation).
Google query: [COLOR=111111]nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION[/COLOR]
[/COLOR]
[COLOR=111111]On Sat 11/28/2020 7:36:14 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112820-7609-01.dmp
This was probably caused by the following module: [COLOR=111111]nvlddmkm.sys[/COLOR] (nvlddmkm+0x832e92)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800446FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5dcb5bbf5c3edcf2\nvlddmkm.sys
product: [COLOR=111111]NVIDIA Windows Kernel Mode Driver, Version 457.30[/COLOR]
company: [COLOR=111111]NVIDIA Corporation[/COLOR]
description: NVIDIA Windows Kernel Mode Driver, Version 457.30
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation).
Google query: [COLOR=111111]nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION[/COLOR]
[/COLOR]
[COLOR=111111]On Wed 11/11/2020 6:26:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111120-8625-01.dmp
This was probably caused by the following module: [COLOR=111111]amdppm.sys[/COLOR] (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8030E0FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: [COLOR=111111]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=111111]Microsoft Corporation[/COLOR]
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.[/COLOR]
The latest ones point to nvidia drivers and I have uninstalled and used DDU to fully uninstall all software and drivers, and then I redownloaded the latest driver for my GPU and reinstalled. I am typing this up right now after this latest crash.
I have also saved my minidump folder and MEMORY.DMP file if that is something that is required to figure out why I am having these issues.
Any help would be much appreciated!
Update (11/28/20 11:39PM): I ran sfc /scannow in my terminal (powershell) and it said it found some corrupted files and that it fixed them.
Also, I have noticed that when viewing the Event Viewer system logs, I always have two errors upon startup saying: "The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout."
Continue reading...
Here is the google drive link to the zip file that contains my Minidump folder and Memory.DMP file right after my most latest crash which is detailed extensively below.
Dump 11-28-20.zip
My PC Specs are:
OS Name Microsoft Windows 10 Pro
Version 10.0.19041 Build 19041
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Ryzen 5 1600 Six-Core Processor, 3200 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P3.00, 7/13/2017
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASRock
BaseBoard Product AB350 Pro4
BaseBoard Version
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name DESKTOP-SHU35TM\ahmed
Time Zone Central Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 11.6 GB
Total Virtual Memory 26.9 GB
Available Virtual Memory 17.8 GB
Page File Space 11.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
I have been having constant BSOD when playing intensive video games or just randomly. I replaced my RAM about a month ago and for about 6-8 months before that I would have random BSOD's like irql_not_less_or_equal or FAULTY HARDWARE CORRUPTED PAGE which was more common. After replacing the RAM, and also doing a fresh install of windows 10 pro as well, I stopped getting these errors for a little bit until I started getting BSOD's again but this time I have only had DPC Watchdog Violation.
I used WhoCrashed to figure out what was causing the crash and it said the following:
On Wed 11/11/2020 6:26:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=111111]ksusba64.sys[/COLOR] (ksusba64+0x5c4b5)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8030E0FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\system32\drivers\ksusba64.sys
product: [COLOR=111111]Sound Blaster USB Audio[/COLOR]
company: [COLOR=111111]Creative Technology Ltd.[/COLOR]
description: WDM USB Audio Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: ksusba64.sys (WDM USB Audio Driver, Creative Technology Ltd.).
Google query: [COLOR=111111]ksusba64.sys Creative Technology Ltd. DPC_WATCHDOG_VIOLATION[/COLOR]
[COLOR=111111]This pointed the issue to my external soundcard (SoundBlaster G6) and I ended up uninstalling all software and drivers for that and have stopped using it. For about 2-3 weeks I had no issues until recently I had another crash with DPC Watchdog Violation again and this is what it said:[/COLOR]
[COLOR=111111]On Sat 11/28/2020 7:36:14 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=111111]nvlddmkm.sys[/COLOR] (nvlddmkm+0xab701)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800446FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5dcb5bbf5c3edcf2\nvlddmkm.sys
product: [COLOR=111111]NVIDIA Windows Kernel Mode Driver, Version 457.30[/COLOR]
company: [COLOR=111111]NVIDIA Corporation[/COLOR]
description: NVIDIA Windows Kernel Mode Driver, Version 457.30
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation).
Google query: [COLOR=111111]nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION[/COLOR]
[/COLOR]
[COLOR=111111]On Sat 11/28/2020 7:36:14 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112820-7609-01.dmp
This was probably caused by the following module: [COLOR=111111]nvlddmkm.sys[/COLOR] (nvlddmkm+0x832e92)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800446FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5dcb5bbf5c3edcf2\nvlddmkm.sys
product: [COLOR=111111]NVIDIA Windows Kernel Mode Driver, Version 457.30[/COLOR]
company: [COLOR=111111]NVIDIA Corporation[/COLOR]
description: NVIDIA Windows Kernel Mode Driver, Version 457.30
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation).
Google query: [COLOR=111111]nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION[/COLOR]
[/COLOR]
[COLOR=111111]On Wed 11/11/2020 6:26:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111120-8625-01.dmp
This was probably caused by the following module: [COLOR=111111]amdppm.sys[/COLOR] (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8030E0FB320)
Error: [COLOR=111111]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: [COLOR=111111]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=111111]Microsoft Corporation[/COLOR]
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.[/COLOR]
The latest ones point to nvidia drivers and I have uninstalled and used DDU to fully uninstall all software and drivers, and then I redownloaded the latest driver for my GPU and reinstalled. I am typing this up right now after this latest crash.
I have also saved my minidump folder and MEMORY.DMP file if that is something that is required to figure out why I am having these issues.
Any help would be much appreciated!
Update (11/28/20 11:39PM): I ran sfc /scannow in my terminal (powershell) and it said it found some corrupted files and that it fixed them.
Also, I have noticed that when viewing the Event Viewer system logs, I always have two errors upon startup saying: "The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout."
Continue reading...