C
Cynical Hack
So I bought a used custom built PC about 3 weeks ago and I've been having one single problem with it. When I play ANY games other than the new Call of Duty, I get a BSOD with DPC_WATCHDOG_VIOLATION error after almost exactly 2 hours into playing. Happens with every game I've tried to play, aside from Call of Duty as I said. The guy I got it from said he's never had this issue before and has been really nice and tried to help me multiple times in fixing it. But obviously there is a reason he was selling this PC. Can't get my money back and everything is closed because of the pandemic. Can't bring it anywhere to get it repaired and I've gone through Geek Squad remote support six different times. I've tried updating all of my drivers, replacing the SSD I download games on, preforming disk checks and system scans (came up empty handed), and just about everything else. I have thought maybe my BIOs were the culprit but I'm uncomfortable trying to update those myself (rather be able to play one game than none at all). I've spent countless nights on youtube and forums trying to find fixes for it but nothing has worked so far. If anyone could help me I would appreciate it so much. Not much to do in quarantine other than play games lol. I've downloaded WhoCrashed to view my dump files and it says this:
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: usbxhci.sys (usbxhci+0x3606f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021FB73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI 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 storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Sun 4/12/2020 5:54:05 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041220-6546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021FB73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 4/12/2020 2:53:12 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041220-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0xD1 (0xFFFFF805CF3CDF72, 0x2, 0x8, 0xFFFFF805CF3CDF72)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I've read that WhoCrashed isn't super reliable, but even if it was I'm racking my brain trying to fix this myself with this info. If any more info is needed let me know and i'll do my best to provide it. Thanks in advance!
Continue reading...
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: usbxhci.sys (usbxhci+0x3606f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021FB73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI 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 storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Sun 4/12/2020 5:54:05 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041220-6546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021FB73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 4/12/2020 2:53:12 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041220-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0xD1 (0xFFFFF805CF3CDF72, 0x2, 0x8, 0xFFFFF805CF3CDF72)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I've read that WhoCrashed isn't super reliable, but even if it was I'm racking my brain trying to fix this myself with this info. If any more info is needed let me know and i'll do my best to provide it. Thanks in advance!
Continue reading...