Page 2 of 2 First 12
  1. #21
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,057
    • 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}

    It could be possible.
    Where's the new minidump?
    When did you install malwarebytes?
    Before or after the problem?
    Did you try without it?
    Did you try a GPU stress test (click)?


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

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

    Quote Originally Posted by xilolee View Post
    It could be possible.
    Where's the new minidump?
    When did you install malwarebytes?
    Before or after the problem?
    Did you try without it?
    Did you try a GPU stress test (click)?
    I've been checking WhoCrashed every crash, and it's always the same thing - the Nvidia Driver.
    I installed Malwarebytes months ago, and it had been running fine since. In fact, this whole episode happened randomly, with no known updates, changes or anything of the sort for at least 3 days prior.
    No, I haven't tried the PC without Malwarebytes, however I don't see how it would affect it?
    I haven't tried a GPU stress test, I will do that tonight.


    I had my suspicions that one of my GPUs had a hardware issue. As mentioned before, I had my GPUs in SLI. As the problem was occurring quite often, I decided to take out GPU 1 (the primary one) and make GPU 2 the primary one, to see if the issue lies with the hardware.

    To my relief, after quite a number of hours playing PUBG, CSGO and surfing the internet, I had NO BSODs last night. I was also monitoring my core temps for my GPUs and CPUs, before and after, and the temperatures were no different.

    I'm going to keep testing it for the next couple of days and see if it holds up.


    It all sort of makes sense anyway - the error logs never specified the Graphics driver, just an NVidia Kernel driver, which suggests something hardware or power related. Hopefully I'm correct, and not just being lucky that it worked all of last night with no problems.

Page 2 of 2 First 12

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