Windows 8 and 8.1 Forums


DPC Watchdog Violation BSOD Caused By Driver: ntoskrnl.exe

  1. #21


    Redmond
    Posts : 651
    Windows 8.1 x64


    It's the ASUS kernel mode driver IOMap64.sys, running in the GpuFanHelper.exe process (sounds like you're running ASUS GPU tweak..... don't).

    Both dumps are the same, basically:

    Code:
    // It's a 0xC9 driver verifier bugcheck - DRIVER_MANAGER_IOMANAGER_VIOLATION:
    1: kd> .bugcheck
    Bugcheck code 000000C9
    Arguments 00000000`00000226 fffff801`03693708 ffffcf81`9b9a2ea0 00000000`00000000
    
    // The first paramter to the bugcheck was 226, so the 3rd parameter is the IRP that triggered
    // the bugcheck:
    1: kd> !irp ffffcf819b9a2ea0 1
    Irp is active with 1 stacks 2 is current (= 0xffffcf819b9a2fb8)
     No Mdl: No System Buffer: Thread ffffe00152d4d580:  Irp is completed.  
    Flags = 40000404
    ThreadListEntry.Flink = ffffe00152d4dbd8
    ThreadListEntry.Blink = ffffe00152d4dbd8
    IoStatus.Status = 00000000
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = ffffcf819b9a2ed0
    UserEvent = ffffd0002374d998
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = ffffcf819b9a2f18
    Tail.Overlay.Thread = ffffe00152d4d580
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = 00000000
    Tail.Overlay.ListEntry.Blink = 00000000
    Tail.Overlay.CurrentStackLocation = ffffcf819b9a2fb8
    Tail.Overlay.OriginalFileObject = ffffe00152e5e780
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [ 12, 0]   0  0 ffffe00152edd710 ffffe00152e5e780 00000000-00000000    
              ffffe00152edd710: Could not read device object or _DEVICE_OBJECT not found
                Args: 00000000 00000000 00000000 00000000
    
    // That IRP has completed, but has failed to signal as such back up the stack - this is VERY
    // bad, as future I/O requests can now hang, crash, do all sorts of bad things.  Now,
    // knowing it's a "stuck" IRP, we look at the second param (the driver address):
    1: kd> !address fffff80103693708
    ...
    Usage:                  
    Base Address:           fffff800`00000000
    End Address:            fffff803`3f1750e7
    Region Size:            00000003`3f1750e7
    VA Type:                BootLoaded
    VAD Address:            0x27676e69727473
    Commit Charge:          0x100000003
    Protection:             0x7ff8ebfca2f0 []
    Memory Usage:           Private
    No Change:              yes
    More info:              !vad 0xfffff80000000000
    
    // Looking at the loaded modules list, the memory address (fffff801`03693708) falls within
    // the start/end range of IOMap64:
    1: kd> lm
    start             end                 module name
    ...
    fffff801`03692000 fffff801`0369b000   IOMap64  T (no symbols)   
    ...
    There's your culprit. No need necessarily to totally reinstall, but I'd recommend removing *all* of the ASUS software from the box (uninstall, not disable), starting with GPU tweak.

    If you're curious, there's an MSDN page documenting this particular bugcheck type in detail.

      My System SpecsSystem Spec

  2. #22


    United Kingdom
    Posts : 22
    Windows 8.1 Pro


    Quote Originally Posted by cluberti View Post
    It's the ASUS kernel mode driver IOMap64.sys, running in the GpuFanHelper.exe process (sounds like you're running ASUS GPU tweak..... don't).

    Both dumps are the same, basically:

    Code:
    // It's a 0xC9 driver verifier bugcheck - DRIVER_MANAGER_IOMANAGER_VIOLATION:
    1: kd> .bugcheck
    Bugcheck code 000000C9
    Arguments 00000000`00000226 fffff801`03693708 ffffcf81`9b9a2ea0 00000000`00000000
    
    // The first paramter to the bugcheck was 226, so the 3rd parameter is the IRP that triggered
    // the bugcheck:
    1: kd> !irp ffffcf819b9a2ea0 1
    Irp is active with 1 stacks 2 is current (= 0xffffcf819b9a2fb8)
     No Mdl: No System Buffer: Thread ffffe00152d4d580:  Irp is completed.  
    Flags = 40000404
    ThreadListEntry.Flink = ffffe00152d4dbd8
    ThreadListEntry.Blink = ffffe00152d4dbd8
    IoStatus.Status = 00000000
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = ffffcf819b9a2ed0
    UserEvent = ffffd0002374d998
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = ffffcf819b9a2f18
    Tail.Overlay.Thread = ffffe00152d4d580
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = 00000000
    Tail.Overlay.ListEntry.Blink = 00000000
    Tail.Overlay.CurrentStackLocation = ffffcf819b9a2fb8
    Tail.Overlay.OriginalFileObject = ffffe00152e5e780
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [ 12, 0]   0  0 ffffe00152edd710 ffffe00152e5e780 00000000-00000000    
              ffffe00152edd710: Could not read device object or _DEVICE_OBJECT not found
                Args: 00000000 00000000 00000000 00000000
    
    // That IRP has completed, but has failed to signal as such back up the stack - this is VERY
    // bad, as future I/O requests can now hang, crash, do all sorts of bad things.  Now,
    // knowing it's a "stuck" IRP, we look at the second param (the driver address):
    1: kd> !address fffff80103693708
    ...
    Usage:                  
    Base Address:           fffff800`00000000
    End Address:            fffff803`3f1750e7
    Region Size:            00000003`3f1750e7
    VA Type:                BootLoaded
    VAD Address:            0x27676e69727473
    Commit Charge:          0x100000003
    Protection:             0x7ff8ebfca2f0 []
    Memory Usage:           Private
    No Change:              yes
    More info:              !vad 0xfffff80000000000
    
    // Looking at the loaded modules list, the memory address (fffff801`03693708) falls within
    // the start/end range of IOMap64:
    1: kd> lm
    start             end                 module name
    ...
    fffff801`03692000 fffff801`0369b000   IOMap64  T (no symbols)   
    ...
    There's your culprit. No need necessarily to totally reinstall, but I'd recommend removing *all* of the ASUS software from the box (uninstall, not disable), starting with GPU tweak.

    If you're curious, there's an MSDN page documenting this particular bugcheck type in detail.
    I only have AI Suite 3 installed :3
      My System SpecsSystem Spec

  3. #23


    Redmond
    Posts : 651
    Windows 8.1 x64


    Then you do have all the tweak and fan programs installed whether you realize it or not. Please remove the suite and all components.
      My System SpecsSystem Spec

  4. #24


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):
    Blue Screen of Death (BSOD) Posting Instructions
      My System SpecsSystem Spec

  5. #25


    United Kingdom
    Posts : 22
    Windows 8.1 Pro


    Quote Originally Posted by cluberti View Post
    Then you do have all the tweak and fan programs installed whether you realize it or not. Please remove the suite and all components.
    I'm currently running driver verifier - so far so good no BSOD upon start-up; I'll leave it running for a few more hours.

    SF Debug Tool output files:
    https://drive.google.com/file/d/0B5V...ew?usp=sharing
      My System SpecsSystem Spec

  6. #26


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I didn't see any Asus stuff in the Programs section of MSINFO32.
    As such, if the BSOD's continue, post back and I'll suggest a way to safely remove the offending drivers manually
      My System SpecsSystem Spec

  7. #27


    United Kingdom
    Posts : 22
    Windows 8.1 Pro


    Quote Originally Posted by usasma View Post
    I didn't see any Asus stuff in the Programs section of MSINFO32.
    As such, if the BSOD's continue, post back and I'll suggest a way to safely remove the offending drivers manually
    Just froze again :/ . Driver verifier never blue screened; turned it off now.
      My System SpecsSystem Spec

  8. #28


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Let's have a look at the freeze events:
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog)
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
      My System SpecsSystem Spec

  9. #29


    United Kingdom
    Posts : 22
    Windows 8.1 Pro


    Happy New Year,

    There's nothing different to the previous Admin.evtx I posted.
    New: https://drive.google.com/file/d/0B5V...ew?usp=sharing

    (Note: The VSS error was being created by a registry scanner program, switched back to CCleaner now)

    Finally my CPU and GPU temperatures are absolutely fine. Of course I can't monitor them after I have frozen.

    EDIT: Just froze again! woo... Is it relevant that after it has frozen, if I unplug the mouse, keyboard or monitor and plug them back in they will remain 'off' eg no single, keyboard/mouse LEDs will be off as well.
    Attachment 55996
    Last edited by AlexWonga117; 02 Jan 2015 at 06:27.
      My System SpecsSystem Spec

  10. #30


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please note the "Max" value in your screenshot. That'll catch the temp at it's maximum. It may even work in the background during the freeze - but we're just looking for trends here, so something that's a bit high would be of interest to us. FWIW - there's no sign of a problem in that screenshot.

    the Admin event log is a summary of some of the other events - it's not meant to be an all-encompassing logfile (we may end up looking in greater detail at the Application and System logfiles if this doesn't help).
    But, the majority of issues in the Admin log are network related.
    You have these 3 network devices listed in systeminfo.txt:
    Network Card(s): 3 NIC(s) Installed.
    [01]: Realtek RTL8192SE Wireless LAN 802.11n PCI-E NIC
    Connection Name: Wi-Fi
    DHCP Enabled: Yes
    DHCP Server: 192.168.1.1
    IP address(es)
    [01]: 192.168.1.112
    [02]: fe80::d0a5:9174:112e:1c89

    [02]: Intel(R) Ethernet Connection (2) I218-V
    Connection Name: Ethernet
    Status: Media disconnected

    [03]: TAP-Windows Adapter V9
    Connection Name: Local Area Connection
    DHCP Enabled: No
    IP address(es)
    [01]: 10.3.0.1
    [02]: fe80::9c52:a840:3ca9:a080
    Of the 3, the one that causes the most problems (that I've seen) is the TAP-Windows Adapter V9
    From MSINFO32, I note that the driver is from before Win8.1 was released:
    Driver c:\windows\system32\drivers\tap0901.sys (9.0.0.9, 39.71 KB (40,664 bytes), 22/08/2013 13:40)
    IMO the best thing to do would be:
    1) Remove the TAP Adapter and uninstall it's software.
    2) Download fresh copies of the latest, Win8.1 compatible drivers for each of the 3 devices
    Realtek: http://www.realtek.com.tw/downloads/...Downloads=true
    Intel: https://downloadcenter.intel.com/Det...23071&lang=eng
    TAP: I am uncertain of the manufacturer or provider of this device. Get the most recent version (and make sure that it's Win8.1 compatible) from the provider's/manufacturer's support website
    3) Uninstall the Realtek and Intel drivers. Then install the freshly downloaded drivers (DO NOT install the TAP drivers yet)
    4) Monitor for further BSOD's/freezes
    5) Should the system BSOD or freeze, please run this data collection app ( SF Diagnostic Tool - Using for Troubleshooting - Windows 7 Help Forums ) immediately after rebooting. It'll contain the System and Application logfiles (EventApp.txt and EventSys.txt) those are the files that we'll need. FYI - the program sometimes has pop unders and sometimes it's difficult to tell if it's finished. Luckily the logfiles are done in the early stages - but just in case, just let it run until you get the window labelled "Success"

    Once that's done, then install the freshly downloaded, Win8.1 compatible TAP adapter driver and test it the same way.
      My System SpecsSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast
DPC Watchdog Violation BSOD Caused By Driver: ntoskrnl.exe
Related Threads
Caused By Driver : ntoskrnl.exe in BSOD Crashes and Debugging
hi, (SkyStar 2 USB HD CI) I get the blue screen error when I am running my TV card.(windows 8.1 Pro) it works properly in windows 7 Dump File : 121814-7625-01.dmp Crash Time : 18.12.2014 18:10:10 Bug Check String : Bug Check Code : 0x00000139 Parameter 1 :...
Hello everybody, my name is Patricio, and I have been experimenting some random BSOD with error 0x0000000a caused by driver ntoskrnl.exe. I have tried to pinpoint the driver by myself but i failed to see which one is causing this. I have reinstalled all motherboard drivers (AMD Southbridge + Video...
Hey,,, I am having a lots of BSOD while downloading torrents. I tried updating wifi drivers. It worked for a week, now again having same problem. Tried changing torrent client from utorrent to bittorrent. Still having problem. Follwing is link to 5 dmp files and one system information...
Solved hal dll and ntoskrnl.exe watchdog violation in BSOD Crashes and Debugging
problems with random crashes, seems to be completely random as i can't find any triggers or anything... will try to post more info but crashes varying from every 10 minutes to 10 days with not much in common kinda makes it hard to post. (3rd attempt btw) *update* minidumps were deleted as of...
BSOD randomly, caused by driver ntoskrnl.exe in BSOD Crashes and Debugging
Hi, i've been getting random BSOD and from Bluescreenview, it says caused by ntoskrnl.exe . I think its caused by a bad/ outdated driver possibly from my video card but im not so sure.:confused: Help would be appreciated.
Solved BSOD DPC watchdog violation in BSOD Crashes and Debugging
Hey there! It's the first time I got this blue screen, I don't know if it'll happen again. I searched for it on google and I didn't understand very well why it is caused. Anyway, I haven't updated my drivers yet, could it be the problem? thanks in advance! :)
Eight Forums Android App Eight Forums IOS App Follow us on Facebook