Page 1 of 2 12 Last
  1. #1

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

    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.
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    Re: BSOD on Windows 8.1

    Hello MrLuke and welcome to Sysnative Forum


    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.

  3. #3

    Re: BSOD on Windows 8.1

    Quote Originally Posted by philc43 View Post
    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!

  4. #4

    Re: BSOD on Windows 8.1

    Quote Originally Posted by MrLuke View Post
    Quote Originally Posted by philc43 View Post
    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.

  5. #5

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    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

  6. #6

    Re: BSOD on Windows 8.1

    Quote Originally Posted by philc43 View Post
    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.

  7. #7

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    Re: BSOD on Windows 8.1

    Quote Originally Posted by MrLuke View Post
    Quote Originally Posted by philc43 View Post
    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.

  8. #8

    Re: BSOD on Windows 8.1

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

  9. #9

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    Re: BSOD on Windows 8.1

    Quote Originally Posted by MrLuke View Post
    Is that using the File Collection App (as I did at the start)?
    Yes that is correct.

  10. #10

    Re: BSOD on Windows 8.1

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

    Read More:

  11. #11

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    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.

  12. #12

    Re: BSOD on Windows 8.1

    Attached new zip
    Attached Files Attached Files

  13. #13

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

    Re: BSOD on Windows 8.1

    Quote Originally Posted by MrLuke View Post
    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.

  14. #14

    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.

  15. #15
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,145
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

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

    Quote Originally Posted by MrLuke View Post
    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).".

    Quote Originally Posted by philc43 View Post
    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:
    Last edited by xilolee; 01-21-2018 at 07:00 PM.

  16. #16

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

    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.

  17. #17

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

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

    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.

  18. #18

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

    How do I stop Driver Verifier?

  19. #19

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    85

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

    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.

  20. #20

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

    Quote Originally Posted by MrLuke View Post
    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 :)

Page 1 of 2 12 Last

Similar Threads

  1. Bugcheck 0x162 - KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
    By jcgriff2 in forum BSOD Processing Apps Download | Information | Discussions
    Replies: 7
    Last Post: 08-19-2016, 12:22 AM
  2. BSOD: bugcheck was: 0x0000009f ...
    By calamitag in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 08-18-2014, 06:50 PM
  3. 0x9F Bugcheck
    By partof in forum BSOD, Crashes, Kernel Debugging
    Replies: 5
    Last Post: 05-14-2013, 10:59 AM
  4. Bugcheck 0x139 v. 0x109
    By jcgriff2 in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 6
    Last Post: 04-18-2013, 03:10 AM
  5. F4 Bugcheck wininit
    By cathersal in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 08-25-2012, 03:30 AM

Log in

Log in