[8.1 x64] DPC_WATCHDOG_VIOLATION BugCheck 133, {0, 501, 500, 0}

[MrLuke]

Hello

I've recently been having a BSOD error on my Windows 8.1 machine:

DPC_WATCHDOG_VIOLATION


When does it occur?
This problem started around 2 weeks ago.

I started getting this after watching videos on Reddit/Live Leak etc, and noticed it only happened when on a internet browser. It would not happen via a trigger (clicking on a link, any button, time limit etc), it would happen randomly, up to 3 times a day.

I already have subscribed Malwarebytes installed and running fully, i ran a scan and found nothing, i also ran Adwcleaner and RKill and also found nothing (apart from lots of cookies which i removed). The problem persisted.

I then noticed, whilst mid-game of PlayerUnknowns Battlegrounds that it happened again, despite not having an Internet Browser open. My suspicions turned to something hardware related, instead of something malicious which i had originally thought.

I proceeded to sign up on this website, and whilst looking i found the Driver Verifier, and ran it. I did create a system restore, however the computer did a BSOD with error DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (portcls.sys). I decided to do a OS 'Refresh' which reinstalls Windows 8.1 but keeps my documents - i did this on the 19/1/18.

Earlier today (20/1/18 around 11:00) I clicked on the start button and the BSOD happened again.

What happens during the BSOD?

This is where it gets interesting - see the photo here uploaded to imgur: https://i.imgur.com/QD1VmuB.png

As you can see, my screen can be seen in a strip at the top of the monitor, with the BSOD page seemingly over the top.

This is what happens, step by step, when this event occurs:

1) my whole screen freezes, but my mouse can move still, however my mouse will not react to any objects on the screen (for example, changing to a pointing hand when over a button). I cannot alt+shift, control alt & delete, and when pressing the power button (which should cause my computer to initiate a normal shutdown sequence) it does nothing.
2) my mouse freezes
3) i wait between 10 seconds and 1 minute, and then the BSOD screen pops up as shown in the link above.
4) it reaches 100%, then the computer restarts and everything is normal

What have i tried?

as mentioned before, i've tried scans on malywarebytes, rkill and adwcleaner, as well as refreshing the OS.

i've done:

check disk
sfc /scannow
updated graphics drivers
updated all windows updates
disabled java and javascript for everything
tested my SSD for any errors (there aren't any)


My setup
Windows 8.1
x64
Original OS was Windows 8.1
Full retail version
System hardware is 4 years old, I built it around 3 years ago
I reinstalled the OS around 2 years ago, i also refreshed OS yesterday (19.1.18)


AMD FX-6300
2 x ASUS GeForce GTX 760 2GB (in SLI)
ASUS M5A99X EVO R2.0
Corsair 750w


Desktop (home built)


Storage:
250GB Samsung SSD 850 EVO
WD Blue 1TB
WD Blue 2TB

RAM:
16GB HyperX


Sorry if it's a bit messy, there was lots of stuff to cover. If there any any info I missed, please let me know and I'll add it in.

 

[philc43]

Re: BSOD on Windows 8.1

Hello MrLuke and welcome to Sysnative Forum :welcome:


I had a look at the two crash dumps and they both show the DPC Watchdog error. WinDBG is suggesting that the graphics driver is involved, I can see that you are using the latest driver but it does show up in the stack trace.

I would recommend uninstalling the driver and any NVidia graphics software completely using ​

DDU

and then just reinstalling the latest driver. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.​

 

[MrLuke]

Re: BSOD on Windows 8.1

I would recommend uninstalling the driver and any NVidia graphics software completely using ​

DDU

and then just reinstalling the latest driver. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.​

Done both now, I guess I'll only know if it's worked if I wait a day or two and see if it happens again - thanks!

 

[MrLuke]

Re: BSOD on Windows 8.1

I would recommend uninstalling the driver and any NVidia graphics software completely using ​

DDU

and then just reinstalling the latest driver. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.​

Done both now, I guess I'll only know if it's worked if I wait a day or two and see if it happens again - thanks!

That was short lived, same happened again! However, this is what the BSOD looked like...: https://i.imgur.com/aenzQTe.png

The same sequence happened again - i was in the middle of a PUBG game, it froze, and then a few seconds later, this. You can see part of my previous frozen screen in the top left, and the apparent BSOD in a strewn mess across the monitor.

 

[philc43]

Re: BSOD on Windows 8.1

In that case you will need to run Driver Verifier to see if it will flush out the drivers that are misbehaving on your system.

Follow the method described here: Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

 

[MrLuke]

Re: BSOD on Windows 8.1

In that case you will need to run Driver Verifier to see if it will flush out the drivers that are misbehaving on your system.

Follow the method described here: Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

I've done this, restarted - I'll see if it continues.

 

[philc43]

Re: BSOD on Windows 8.1

In that case you will need to run Driver Verifier to see if it will flush out the drivers that are misbehaving on your system.

Follow the method described here: Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

I've done this, restarted - I'll see if it continues.

When running with Driver Verifier if there are any BSOD events they will cause crash dumps to be written with details of the drivers that were a problem. Please post a new set of log files after you have finished which will contain these new crash dump files.

 

[MrLuke]

Re: BSOD on Windows 8.1

Is that using the File Collection App (as I did at the start)?

 

[philc43]

Re: BSOD on Windows 8.1

Is that using the File Collection App (as I did at the start)?

Yes that is correct.

 

[MrLuke]

Re: BSOD on Windows 8.1

I've just run WhoCrashed (a rather useful programme) and came out with this:

Read More:

Welcome to WhoCrashed (HOME EDITION) v 6.01--------------------------------------------------------------------------------


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.


Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.


This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit Resplendence Software - Contact Us


Click here to check if you have the latest version or if an update is available.


Just click the Analyze button for a comprehensible report ...






--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.


Please note that this version of WhoCrashed is not licensed for use by professional support engineers.


Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.




--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------


Computer name: LUKE-PC
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., M5A99X EVO R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 17075376128 bytes total








--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------


Crash dumps are enabled on your computer.


Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump


On Sun 21/01/2018 10:21:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012118-27906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
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 21/01/2018 10:21:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xc8e78)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
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 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION






On Sat 20/01/2018 22:15:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012018-8937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
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 Sat 20/01/2018 11:15:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012018-30250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
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 Sat 20/01/2018 10:59:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012018-24437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
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.










--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------


5 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:


nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation)


If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.




Read the topic general suggestions for troubleshooting system crashes for more information.


Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[philc43]

Re: BSOD on Windows 8.1

They are all the 0x133 DPC_WATCHDOG crashes - we are looking for one triggered by driver verifier which will be a 0xC4 bugcheck code.

 

[MrLuke]

Re: BSOD on Windows 8.1

Attached new zip

 

[philc43]

Re: BSOD on Windows 8.1

Attached new zip

As WhoCrashed showed the new BSOD was a 0x133 bugcheck and not one caused by driver verifier. You will need to leave Driver Verifier working for the next 48h and then post again when or if you capture any new BSOD events. After this you can turn Driver Verifier off.

 

[MrLuke]

Re: BSOD on Windows 8.1

I've done some tests:

I uninstalled the driver I had on my GPUs and reinstalled a driver I had from before the problem occurred - the problem persists. So, I think it's something hardware related. I'll give my GPUs a clean and try only one (not in SLI) and see if the issue continues.

 

[xilolee]

RAM: 16GB HyperX

WinDbg says you are using 16GB (4x4GB) BLS4G3D169DS3.16FE and not Kingston hyperx.
Specs: Crucial Ballistix Sport XT BLS4G3D169DS3 4GB DDR3-1600 CL9 (9-9-9-24) 1.5V PC3-12800.
I didn't find it in MB QVL for RAM, but it should be compatible seeing its specs...
You can try to update the realtek RTL8111F ethernet driver (click).
Instead for the wi-fi atheros driver, you can try to update it via windows device manager (right-click on the item, update driver, search automatically).
It seems amd fx-6300 is the minimum requirement for playing PLAYERUNKNOWN'S BATTLEGROUNDS, hence this sentence could be true: "This bug check can also occur because of overheated CPUs (thermal issue).".

As WhoCrashed showed the new BSOD was a 0x133 bugcheck and not one caused by driver verifier. You will need to leave Driver Verifier working for the next 48h and then post again when or if you capture any new BSOD events. After this you can turn Driver Verifier off.

It seems verifier was enabled (DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP and VerifierExt.sys is present):

Read More:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 6.3.9600.18895 (winblue_ltsb.180101-1800)

SYSTEM_MANUFACTURER: To be filled by O.E.M.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: SKU

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2501

BIOS_DATE: 04/03/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: M5A99X EVO R2.0

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 6

CPU_MHZ: db8

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x133

PROCESS_NAME: TslGame.exe

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: XILO-PC

ANALYSIS_SESSION_TIME: 01-21-2018 21:25:42.0481

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER: from fffff80199395e3c to fffff8019935fea0

STACK_TEXT:
fffff801`9ac24c88 fffff801`99395e3c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`9ac24c90 fffff801`992bade7 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ee6c
fffff801`9ac24d20 fffff801`9999ab4f : 00000000`000000ff fffff801`998a7030 fffff801`999e6910 00000000`00007201 : nt!KeClockInterruptNotify+0x787
fffff801`9ac24f40 00000000`000000ff : fffff801`998a7030 fffff801`999e6910 00000000`00007201 ffffe001`55d8a300 : hal+0x7b4f
fffff801`9ac24f48 fffff801`998a7030 : fffff801`999e6910 00000000`00007201 ffffe001`55d8a300 fffff801`992d7bb3 : 0xff
fffff801`9ac24f50 fffff801`999e6910 : 00000000`00007201 ffffe001`55d8a300 fffff801`992d7bb3 fffff801`999e6870 : nt!ViCtxIsrStateBlocks+0x370
fffff801`9ac24f58 00000000`00007201 : ffffe001`55d8a300 fffff801`992d7bb3 fffff801`999e6870 00000000`00000008 : hal+0x53910
fffff801`9ac24f60 ffffe001`55d8a300 : fffff801`992d7bb3 fffff801`999e6870 00000000`00000008 fffff801`35f3df70 : 0x7201
fffff801`9ac24f68 fffff801`992d7bb3 : fffff801`999e6870 00000000`00000008 fffff801`35f3df70 fffff801`9ac1dc80 : 0xffffe001`55d8a300
fffff801`9ac24f70 fffff801`993613da : fffff801`999e6870 ffffe001`55d8a300 fffff801`9ac1dc80 fffff801`9ac1dc80 : nt!KiCallInterruptServiceRoutine+0xa3
fffff801`9ac24fb0 fffff801`993618a7 : 00000000`0000000a fffff801`9ac1da58 ffffe001`54585001 fffff801`9999958f : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`9ac1d950 fffff801`9928c62b : fffff801`994dfb88 fffff801`994384d8 ffffe001`54585080 fffff801`998907b4 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`9ac1dae0 fffff801`99360c46 : ffffe001`564be340 fffff801`3487a4fe 00000000`000000c8 fffff801`3487a4fe : nt!KxWaitForSpinLockAndAcquire+0x1f
fffff801`9ac1db10 fffff801`35a0da2f : ffffe001`5b41c6a0 fffff801`35f3df70 fffff801`9ac1dc80 00000000`00000000 : nt!KeSynchronizeExecution+0x36
fffff801`9ac1db50 ffffe001`5b41c6a0 : fffff801`35f3df70 fffff801`9ac1dc80 00000000`00000000 00000000`00000000 : dxgkrnl+0x9a2f
fffff801`9ac1db58 fffff801`35f3df70 : fffff801`9ac1dc80 00000000`00000000 00000000`00000000 fffff801`3486dedd : 0xffffe001`5b41c6a0
fffff801`9ac1db60 fffff801`9ac1dc80 : 00000000`00000000 00000000`00000000 fffff801`3486dedd fffff801`35f3df70 : nvlddmkm+0x112f70
fffff801`9ac1db68 00000000`00000000 : 00000000`00000000 fffff801`3486dedd fffff801`35f3df70 ffffe001`565c1000 : 0xfffff801`9ac1dc80


THREAD_SHA1_HASH_MOD_FUNC: 3613b809ef86b89fce7f15265d78fd21ad31227f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6497b2f3c76a7667f4b4b7e8666200669b8a2d66

THREAD_SHA1_HASH_MOD: 3cf2bb5dc40a108999dcc97d743b8c6354edaebe

FOLLOWUP_IP:
dxgkrnl+9a2f
fffff801`35a0da2f ?? ???

SYMBOL_STACK_INDEX: e

SYMBOL_NAME: dxgkrnl+9a2f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 59e1c8f5

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9a2f

FAILURE_BUCKET_ID: 0x133_VRF_DPC_dxgkrnl!unknown_function

BUCKET_ID: 0x133_VRF_DPC_dxgkrnl!unknown_function

PRIMARY_PROBLEM_CLASS: 0x133_VRF_DPC_dxgkrnl!unknown_function

TARGET_TIME: 2018-01-21T10:21:14.000Z

OSBUILD: 9600

OSSERVICEPACK: 18895

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

OSEDITION: Windows 8.1 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-01-02 04:56:56

BUILDDATESTAMP_STR: 180101-1800

BUILDLAB_STR: winblue_ltsb

BUILDOSVER_STR: 6.3.9600.18895

ANALYSIS_SESSION_ELAPSED_TIME: 1ba6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_vrf_dpc_dxgkrnl!unknown_function

FAILURE_ID_HASH: {fff6c2c2-af88-5b60-76f1-65db310f2887}

Followup: MachineOwner
---------


0: kd> lmDvmVerifierExt
Browse full module list
start end module name
fffff801`34868000 fffff801`348dc000 VerifierExt (deferred)
Image path: \SystemRoot\system32\drivers\VerifierExt.sys
Image name: VerifierExt.sys
Browse all global symbols functions data
Timestamp: Sat Sep 14 13:40:56 2013 (52344B48)
CheckSum: 00031D3F
ImageSize: 00074000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[MrLuke]

Sorry I thought I knew it was the HyperX RAM but I assumed wrong

I took my PC apart yesterday and the thermal paste on my CPU was minimal as it's been pressed out over time, I'll get some off Amazon and see if it helps. I've also removed the dust from all components so it should thermally run better in general.

The overheating wouldn't really explain why the problem occurred when clicking on something though would it? Surely it would just be 'random' during high load?


Upon starting attempts to fix this problem, I've noticed my PC being very sluggish - PUBG was stuttering, and when clicking folders on File Browser, it takes a lot longer to load, which it didn't do until 1 day ago. Could this be because of Driver Verifier?

I will update the ethernet driver and the wi-fi driver, note I barely use the wi-fi, I have it as a backup.


I'll do everything I've mentioned above and respond in a few days if it's made any difference.

 

[philc43]

Driver Verifier does indeed slow down your system so that would explain the stuttering. It also why we do not recommend leaving it running longer than necessary.

 

[MrLuke]

How do I stop Driver Verifier?

 

[philc43]

Just start verifier and then choose "Delete Existing Settings" and then Finish.

Alternatively you can enter Verifier /reset in a command prompt and then reboot.

 

[MrLuke]

Sorry I thought I knew it was the HyperX RAM but I assumed wrong

I took my PC apart yesterday and the thermal paste on my CPU was minimal as it's been pressed out over time, I'll get some off Amazon and see if it helps. I've also removed the dust from all components so it should thermally run better in general.

The overheating wouldn't really explain why the problem occurred when clicking on something though would it? Surely it would just be 'random' during high load?


Upon starting attempts to fix this problem, I've noticed my PC being very sluggish - PUBG was stuttering, and when clicking folders on File Browser, it takes a lot longer to load, which it didn't do until 1 day ago. Could this be because of Driver Verifier?

I will update the ethernet driver and the wi-fi driver, note I barely use the wi-fi, I have it as a backup.


I'll do everything I've mentioned above and respond in a few days if it's made any difference.

Ok so I got some thermal paste, re-pasted my CPU (properly, I have done it countless times), PC on, played about 40 mins of PUBG, and the BSOD, same errors on WhoCrashed. I checked my CPU temp on my BIOS screen as soon as it reloaded, it was 46deg, and went down a degree every 10 or so seconds, so it can only have been on 60deg celcius MAX when it crashed which is no where near its peak. My fans weren't spinning any faster, no signs of it getting too hot at all.

Could it potentially be my GPUs getting too hot, or simply a hardware failure? After all, they're constantly being flagged up in the crash dumps, the drivers don't seem to matter and everything is pointing at them.


oh and it was Driver Verifier slowing the PC down, thanks for letting me know about that :)