Page 2 of 2 First 12
  1. #21

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    I'll switch it back to system managed for C:, however I believe I did that the first time and it still maxed it out at 4608 MB. But I'll give it a shot. I'll check for the firmware upgrade, and no I haven't tried less monitors yet- I'll give it a shot tomorrow. Thanks for the suggestions.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Ok, just rebooted with only the c: drive on system managed, and 'no page file' for the other drives, and it's telling me the page file is 8192 MB. So looks like I should be good to go, I'll find out if this helps tomorrow- time to catch some shut eye. Thanks again for the help.

  3. #23

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    I dunno if I missed this, but is there a C:\Windows\MEMORY.dmp file? If so, is the date on it recent?
    If so, please zip it up and then upload it to a free file-sharing service - and post a link here for us to download it.

    Perfmon /report shows missing Coprocessor drivers. I presume that this is your motherboard: http://www.msi.com/product/mb/GF615M...ml#/?div=Basic
    If so, then please download and install these chipset drivers (which should include the coprocessor drivers: http://www.nvidia.com/object/nforce_...bit_15.49.html Please be advised that this chipset is very old and probably isn't supported in Win8 - which may cause errors despite our best efforts.

    Please visit Windows Update and get all available updates. I only see 3 updates on your system - and other systems have upwards of 22 updates.

    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): http://crystalmark.info/?lang=en
    - Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
    Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - http://www.techsupportforum.com/foru...ml#post3537179
    29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
    MSINFO32 doesn't show any BSOD's, which makes me wonder if they're crashes that are visible to Windows.

    There have been issues with older Logitech software and Win8. Please ensure that you have the latest software available from Logitech. Uninstall the older software before installing any new software.

    Here's the Critical error in the System event log (there's a good number of these):
    Event[22]:
    Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 2012-06-20T19:15:40.260
    Event ID: 41
    Task: N/A
    Level: Critical
    Opcode: Info
    Keyword: N/A
    User: S-1-5-18
    User Name: NT AUTHORITY\SYSTEM
    Computer: unreal
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Please download and install a Temperature Monitor program and monitor/log the temps around the time that the system crashes. I suggest this one: http://www.hwinfo.com/

    Please run CHKDSK /R /F AND a full hard drive diagnostic on the Lenovo_Part volume/disk (because of the error below - and there's many others like this in the System event log). Here's a link to the hard drive diagnostic page: http://www.carrona.org/hddiag.html Please note that a problem with one hard drive can cause issues throughout the system - so it's advisable to run the diagnostics on ALL hard drives in the system (both internal and external)
    Event[1]:
    Log Name: System
    Source: Microsoft-Windows-Ntfs
    Date: 2012-06-20T19:16:27.833
    Event ID: 98
    Task: N/A
    Level: Error
    Opcode: Info
    Keyword: N/A
    User: S-1-5-18
    User Name: NT AUTHORITY\SYSTEM
    Computer: unreal
    Description:
    Volume LENOVO_PART (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

  4. #24

    Join Date
    Mar 2012
    Posts
    469

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    This problem is definitely coming from an issue with your SSD drive, possibly incompatibility with Windows. It would not stall on writing the crashdump onto the drive if this were not the case. I'd recommend with the others to update firmware for your SSD whenever possible. As a future recommendation, that should be the first thing you do when you acquire an SSD, because they have a tendency to be quite buggy at launch.

    Don't also rule out the possibility that Windows 8 currently is not compatible with your SSD drive and your drive's manufacturer or MS themselves have to get on the ball to make it happen.

  5. #25

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    @usasma: Since uploading those logs, I've updated to the latest ATI drivers, which also updated the Coprocessor driver, and it's not being flagged in device manager any longer. I have no \Minidump or memory.dmp file, for whatever reason when it crashes, it just goes to bluescreen and doesn't record anything (even though I have recovery settings set to do so). Note: I've also already run a full chkdsk, as well as a memtest on the system, everything came up clean.

    @Vir Gnarus: I have a Crucial M4 SSD, I'm downloading the new firmware as we speak. Thanks for the help.

  6. #26

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Welp, so much for that idea... the Firmware Updater says "There are no SSD drives on your machine that need updating."

  7. #27

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    I also visited Windows Update, and it said I only have 1 important update, which will be installed during system maintenance.

    I have both a wireless logitech mouse and keyboard, they are working fine, however- and I didn't install any drivers for them, they 'just worked'... should I still bother to upgrade the drivers?

    I also noticed that this BSOD happens mainly when I leave my computer alone for a couple minutes (If I'm actively using it, I won't have any problems... I walk away for 10 minutes and I'll come back to a BSOD).

  8. #28

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    OK, I was mistaken- I followed the directions and updated the SSD to the latest firmware, and booted back into windows. I'll see if that changes anything..

  9. #29

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    I'm also running chkdsk /R /F on ALL drives, I had previously only done it on the C: drive. The LENOVO_PART drive is a secondary storage drive that I pulled out of my Lenovo.

  10. #30
    Corrine's Avatar
    Join Date
    Feb 2012
    Location
    Upstate, NY
    Posts
    8,837

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Hi, revenuebuilder.

    My sincere compliments on the excellent information you are providing on the actions/steps you are taking! It is extremely helpful for the analysts in helping you solve the BSOD issues.


    Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

    Remember - A day without laughter is a day wasted.
    May the wind sing to you and the sun rise in your heart.

  11. #31

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Well, I left chkdsk running on my g: drive, and left the house for about 3 hours, and came back to.... a still up and running PC! So maybe we're good to go here- Normally if I would've left the PC running I would come back to a BSOD. Potentially solved, just running chkdsk on my other drive now.

    @Corrine: Thanks, I've worked in IT Support for a few years so I know the more info you give, the better :)

  12. #32

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    You must run chkdsk /r /f on the Lenovo drive - and the hard drive diagnostic ( http://www.carrona.org/hddiag.html )
    This is the drive that's spitting out problems in event viewer - so it's the one you've gotta test.

    While a failing drive can still work (thanks to very robust error checking mechanisms in the drives and in Windows), they can also cause BSOD's and can even make the system fail to boot.

  13. #33

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Thanks usasma, I did run chkdsk /R /F on the G: (lenovo) drive, unfortunately I didn't grab a screenshot and closed the window. I'm fairly sure it came back with 0 bad sectors/looked "clean". I'll run the hddiag tool once I'm done running chkdsk on my other drive.

  14. #34

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    If it passes the hard drive diagnostic test, then I'd suggest watching to see if you get any more of those errors in event viewer.
    If so, then something's causing them - and we'll have to try and figure out what it is.

    Another option is to disconnect the Lenovo drive and see if errors come back.

  15. #35

    Join Date
    Mar 2012
    Posts
    469

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    It if all looks good, I take it we can chalk it up to being bad firmware that needed updating?

  16. #36

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Yup, been running perfectly smooth for 2 days, looks like it must've been the firmware. Thanks everyone for your help!

  17. #37
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,326
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

    Awesome news!

    Thanks for posting back - much appreciated!

    Regards. . .

    jcgriff2

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

Page 2 of 2 First 12

Similar Threads

  1. Windows 8 BSOD DPC_watchdog_violation 0x133
    By averytare in forum BSOD, Crashes, Kernel Debugging
    Replies: 13
    Last Post: 04-29-2013, 04:26 PM
  2. Win 8 x64 BSOD's - DPC_WATCHDOG_VIOLATION
    By SuperchargedSoup in forum BSOD, Crashes, Kernel Debugging
    Replies: 21
    Last Post: 03-18-2013, 08:19 AM
  3. DPC_Watchdog_Violation (BSOD).
    By GoVisualTeam in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 02-07-2013, 06:08 PM
  4. Windows 8 x64 -- 0x133 BSOD - DPC_WATCHDOG_VIOLATION
    By shukim in forum BSOD, Crashes, Kernel Debugging
    Replies: 5
    Last Post: 12-14-2012, 07:44 AM
  5. Constantly getting a DPC_WATCHDOG_VIOLATION (BSOD)
    By mikesmith405 in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 07-16-2012, 01:33 PM

Log in

Log in