Windows 8 and 8.1 Forums

Win 8.1 boot error ntoskrnl.exe - Address 0xfffff8022c35b9

  1. #1

    Posts : 3
    win 8.1

    Win 8.1 boot error ntoskrnl.exe - Address 0xfffff8022c35b9


    had today message on start win 8.1 that an error happend and then win boot again.

    The problem seems to be caused by the following file: ntoskrnl.exe.

    I downloaded as suggested DM Log collector Tool and ad zip as attachment.

    If anyone has an idea what can fix this I would be very glad and want to thanks in advance for your help.

      My System SpecsSystem Spec

  2. #2

    1: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
    1: kd> !irql
    Debugger saved IRQL for processor 0x1 -- 13
    //The system spent too long at IRQL above 2, in this case it was 13
    1: kd> kn
     # Child-SP          RetAddr           Call Site
    00 ffffd001`2c969c88 fffff802`2c37e490 nt!KeBugCheckEx //Took too long, BSOD
    01 ffffd001`2c969c90 fffff802`2c25e9b7 nt!KeAccumulateTicks+0x125e0 //Count the ticks
    02 ffffd001`2c969d20 fffff802`2c9a767f nt!KeClockInterruptNotify+0x787 //Notify of clock interrupt
    03 ffffd001`2c969f40 fffff802`2c2f0eb3 hal!HalpTimerClockInterrupt+0x4f //Clock interrupt
    04 ffffd001`2c969f70 fffff802`2c35ce2a nt!KiCallInterruptServiceRoutine+0xa3 //Call the ISR
    05 ffffd001`2c969fb0 fffff802`2c35d20f nt!KiInterruptSubDispatchNoLockNoEtw+0xea //Dispatch interrupt
    06 ffffd001`29aa7160 00000000`00000000 nt!KiInterruptDispatchLBControl+0x11
    It's very difficult to sayw hat went wrong here, most likely took too long to expire the timers on the linked list, something went wrong so the system got held up; the IRQL was above 2 so we bugchecked.

    1: kd> .bugcheck
    Bugcheck code 0000009F
    Arguments 00000000`00000004 00000000`0000012c ffffe000`57010680 ffffd001`fff5b980
    //Driver failed to complete a power IRP within the allocated time interval, the driver failed to syncrhonise with the pnp manager
    1: kd> !devstack ffffe00203325650
      !DevObj           !DrvObj            !DevExt           ObjectName
      ffffe00203599050  \Driver\RasPppoe   ffffe002035991a0  InfoMask field not found for _OBJECT_HEADER at ffffe00203599020
    > ffffe00203325650  \Driver\SoftwareDeviceffffc001e9da9700  InfoMask field not found for _OBJECT_HEADER at ffffe00203325620
    //One driver object associated with one device object, creating a simple stack
    1: kd> !thread ffffe0020b2a2880
    GetPointerFromAddress: unable to read from fffff8000856d000
    THREAD ffffe0020b2a2880  Cid 0004.0e50  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
        ffffe0020328a9e8  NotificationEvent
    IRP List:
        ffffe00209cbf010: (0006,0160) Flags: 00000000  Mdl: 00000000
    Not impersonating
    GetUlongFromAddress: unable to read from fffff800084b9300
    Owning Process            ffffe001feacc040       Image:         System
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      373845       
    Context Switch Count      9673           IdealProcessor: 0  NoStackSwap
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address nt!ExpWorkerThread (0xfffff80008255798)
    Stack Init ffffd0002169ac90 Current ffffd00021699aa0
    Base ffffd0002169b000 Limit ffffd00021695000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 3 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    ffffd000`21699ae0 fffff800`08258c6e : fffff800`084ff180 ffffe002`0b2a2880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76 //Change context to next thread
    ffffd000`21699c20 fffff800`082586c9 : ffffd000`21699fb0 ffffe001`fecb56f0 ffffd000`a5f094a0 fffff800`084ad6ca : nt!KiSwapThread+0x14e //Change thread execution
    ffffd000`21699cc0 fffff800`08268c9a : ffffc001`e9d9c980 00000000`00000000 ffffd000`a5f40000 00000000`00000801 : nt!KiCommitThreadWait+0x129 //Enter wait state
    ffffd000`21699d40 fffff800`9e937583 : ffffe002`0328a9e8 fffff800`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x22a //Wait for event, either notification or synchronisation event
    ffffd000`21699dd0 fffff800`9dca2fd8 : ffffc001`e9cf3778 fffff800`9e93d68d ffffe002`06c351d0 fffff800`9e8b3601 : ndis!NdisWaitEvent+0x43 //Network driver interface specification wait function
    ffffd000`21699e10 fffff800`9e94929f : ffffd000`21699f00 ffffd000`21699f59 ffffe002`06c351b0 ffffe002`0320ab80 : ndiswan!ProtoUnbindAdapterEx+0x198
    ffffd000`21699e60 fffff800`9e97c414 : ffffe002`0320ab80 ffffe002`035991a0 ffffe002`03599100 ffffe002`00000000 : ndis!ndisInvokeUnbindAdapter+0x2f
    ffffd000`21699ea0 fffff800`9e949ad0 : ffffe002`00000000 ffffe002`0359a5e8 ffffe002`0320ab80 ffffc001`e83952e0 : ndis!ndisUnbindProtocolOpen+0x168
    ffffd000`21699fc0 fffff800`9e93d252 : ffffc001`e83952e8 ffffd000`2169a100 ffffe002`0359a5e8 00000000`00000801 : ndis!ndisUnbindEachProtocolOpenOnMiniport+0x70 //Unbind functions
    ffffd000`2169a000 fffff800`9e93d47c : ffffe002`035991a0 ffffe002`035991a0 ffffd000`2169a200 ffffe002`0359a5e8 : ndis!Ndis::BindEngine::Iterate+0x802
    ffffd000`2169a210 fffff800`9e93b708 : ffffe002`0359a5e8 ffffd000`2169a400 ffffd000`2169a290 ffffd000`2169a400 : ndis!Ndis::BindEngine::UpdateBindings+0x64
    ffffd000`2169a240 fffff800`9e93d5b7 : ffffe002`0359a5e8 ffffe002`0359a5e8 00000000`00001001 fffff800`9e93d514 : ndis!Ndis::BindEngine::DispatchPendingWork+0x50
    ffffd000`2169a270 fffff800`9e93bbdc : ffffe002`035991a0 ffffe002`0359a5e8 ffffc001`d7a3de10 ffffd000`2169a300 : ndis!Ndis::BindEngine::ApplyBindChanges+0x37
    ffffd000`2169a2c0 fffff800`9e97c7ae : ffffe002`035991a0 ffffd000`2169a4a0 ffffe002`0359a5e8 ffffe002`06908760 : ndis!ndisMSetMiniportReadyForBinding+0x64 //Ready to bind the device
    ffffd000`2169a3a0 fffff800`9e9496d9 : ffffe002`035991a0 ffffd000`2169a6d0 ffffe002`035991a0 ffffe002`09cbf010 : ndis!ndisPnPRemoveDevice+0x1ae //Remove the device
    ffffd000`2169a5f0 fffff800`9e94965d : ffffe002`035991a0 ffffe002`035991a0 ffffe002`0359a300 ffffd000`00000000 : ndis!ndisPnPRemoveDeviceEx+0x59
    ffffd000`2169a620 fffff800`9e9495ba : ffffe002`035991a0 ffffd000`2169a6d0 ffffe002`09cbf010 ffffd000`2169a710 : ndis!ndisPnPIrpSurpriseRemovalInner+0x79
    ffffd000`2169a660 fffff800`9e93ef20 : ffffe002`09cbf010 ffffe002`035991a0 ffffd000`2169a7b0 00000000`00000000 : ndis!ndisPnPIrpSurpriseRemoval+0xa6 //Remove the device
    ffffd000`2169a690 fffff800`08623f76 : ffffe002`03599001 ffffe002`03599050 ffffd000`2169a701 00000000`00000002 : ndis!ndisPnPDispatch+0x1ec //Dispatch PnP transition
    ffffd000`2169a700 fffff800`086e3df8 : 00000000`00000017 ffffd000`2169a7c9 ffffe002`068b8010 ffffe002`03325650 : nt!IopSynchronousCall+0xfe //Perform IO then enter a wait state
    ffffd000`2169a770 fffff800`086e1243 : ffffc001`f4ed2c70 ffffc001`d7a16520 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0xe0 //IO device removal
    ffffd000`2169a830 fffff800`086e377e : ffffe002`068b8010 00000000`00000000 ffffc001`d7a16520 ffffc001`d7a16520 : nt!PnpSurpriseRemoveLockedDeviceNode+0xbb //Remove device node from PnP tree
    ffffd000`2169a890 fffff800`086e36be : 00000000`00000000 ffffc001`d7a16520 ffffe002`068b8010 fffff800`087aa046 : nt!PnpDeleteLockedDeviceNode+0x86 //Delete locked device node
    ffffd000`2169a8d0 fffff800`086e25e7 : ffffe002`0350f570 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
    ffffd000`2169a950 fffff800`0862b945 : ffffc001`f4ed2c00 00000000`00000008 ffffc001`00000003 ffffe002`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x30f
    ffffd000`2169aab0 fffff800`0862bd7d : ffffc001`f4ed2c70 00000000`00000000 00000000`00000000 fffff800`0862ba6c : nt!PnpProcessTargetDeviceEvent+0x9d //Target device
    ffffd000`2169aaf0 fffff800`08255a2b : fffff800`0862ba6c ffffc001`eca22010 ffffd000`2169abd0 ffffe002`068a7860 : nt!PnpDeviceEventWorker+0x311 //Worker thread execution
    ffffd000`2169ab50 fffff800`082f2514 : 498cd8d9`69b14d91 ffffe002`0b2a2880 ffffe002`0b2a2880 ffffe001`feacc040 : nt!ExpWorkerThread+0x293 //Start worker thread
    ffffd000`2169ac00 fffff800`083732c6 : ffffd000`a5f07180 ffffe002`0b2a2880 ffffe001`ff8aa880 7f283e39`b7db295b : nt!PspSystemThreadStartup+0x58 //System thread execution
    ffffd000`2169ac60 00000000`00000000 : ffffd000`2169b000 ffffd000`21695000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 //Start system thread
    1: kd> !irp ffffe00209cbf010
    Irp is active with 2 stacks 2 is current (= 0xffffe00209cbf128)
     No Mdl: No System Buffer: Thread ffffe0020b2a2880:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
                Args: 00000000 00000000 00000000 00000000
    >[ 1b,17]   0  0 ffffe00203599050 00000000 00000000-00000000    
                Args: 00000000 00000000 00000000 00000000
    The context isn't saved, as usual with a minidump, so there's not much use here.
    It appears a netwokr device is causing the IRP hold up, but with a Kernel dump and driver verifier enabled it's very difficult to say.
    Active I/O verification, IRP logging and Force IRQL checking, select all 3rd party drivers and reboot.
    Upload the Kernel dump from C:\Windows\MEMORY.dmp to a file sharing site such as Onedrive and post the link here.
      My System SpecsSystem Spec

  3. #3

    Posts : 3
    win 8.1

    first I want to thank you for all your effort and help.

    I loaded hole Memory dump. hope that was ok? If not I can try again.

    Thanks for all your help.

    Here the link:
      My System SpecsSystem Spec

  4. #4

    1: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
    //System spent too long at IRQL 13
    1: kd> kn
     # Child-SP          RetAddr           Call Site
    00 ffffd001`2c969c88 fffff802`2c37e490 nt!KeBugCheckEx //Bugcheck
    01 ffffd001`2c969c90 fffff802`2c25e9b7 nt!KeAccumulateTicks+0x125e0 //Count the ticks
    02 ffffd001`2c969d20 fffff802`2c9a767f nt!KeClockInterruptNotify+0x787 //Notify system of clock interrupt
    03 ffffd001`2c969f40 fffff802`2c2f0eb3 hal!HalpTimerClockInterrupt+0x4f //Clock interrupt
    04 ffffd001`2c969f70 fffff802`2c35ce2a nt!KiCallInterruptServiceRoutine+0xa3 //Call ISR
    05 ffffd001`2c969fb0 fffff802`2c35d20f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    06 ffffd001`29aa7160 fffff801`ba3df449 nt!KiInterruptDispatchLBControl+0x11f //Interrupt dispatch
    07 ffffd001`29aa72f8 fffff801`bac6dc05 nvlddmkm+0xf0449
    08 ffffd001`29aa7300 fffff801`ba45f813 nvlddmkm+0x97ec05
    09 ffffd001`29aa7340 fffff801`ba3f36ed nvlddmkm+0x170813
    0a ffffd001`29aa7510 fffff801`ba3f3262 nvlddmkm+0x1046ed
    0b ffffd001`29aa7650 fffff801`ba34b496 nvlddmkm+0x104262
    0c ffffd001`29aa77a0 fffff801`b9ecc839 nvlddmkm+0x5c496 //Private Nvidia functions
    0d ffffd001`29aa7840 fffff801`ba05d4cb dxgkrnl!ADAPTER_RENDER_DdiSubmitCommand+0x79 //Render function
    0e ffffd001`29aa7880 fffff801`ba09702f dxgmms1!VidSchiSendToExecutionQueue+0x4fb //Send to execution queue
    0f ffffd001`29aa7990 fffff801`ba098da5 dxgmms1!VidSchiSubmitRenderCommand+0x7cf //Submit render command
    10 ffffd001`29aa7b70 fffff801`ba098d1d dxgmms1!VidSchiRun_PriorityTable+0x85 //Check the run priority table
    11 ffffd001`29aa7bc0 fffff802`2c2e3280 dxgmms1!VidSchiWorkerThread+0x8d //Schedule work thread
    12 ffffd001`29aa7c00 fffff802`2c361fc6 nt!PspSystemThreadStartup+0x58
    13 ffffd001`29aa7c60 00000000`00000000 nt!KiStartSystemThread+0x16
    1: kd> lmvm nvlddmkm
    start             end                 module name
    fffff801`ba2ef000 fffff801`bafbe000   nvlddmkm   (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Dec 07 13:33:08 2014 (54845714)
        CheckSum:         00C8AF6B
        ImageSize:        00CCF000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your Nvidia driver is causing the system slowdown, I recommend you update the driver to the latest version and see how things go.
    Upload any new dumps when you crash (preferablly Kernel/Complete dumps).
    Last edited by Mysers Briggs; 15 Feb 2015 at 12:47.
      My System SpecsSystem Spec

  5. #5

    Posts : 3
    win 8.1


    thank you again for the fast replay. I now install the latest Driver WHQL 347.52.

    Thank you for all your work and help, I wish you a good Sunday.
      My System SpecsSystem Spec

Win 8.1 boot error ntoskrnl.exe - Address 0xfffff8022c35b9
Related Threads
Hey, I've recently switched from Windows 7 to Windows 8.1 - and I had a similar problem in Windows 7. I've attached the .zip from the SF debug tool (I also put in the report from BlueScreenView). While using Photoshop, my PC suddenly rebooted - no "Your PC ran into a problem" screen - leaving...
Hi all, I have had two BSOD so far of the ntoskrnl.exe variety. I have had the HDD tested, driver verified, scanned for viruses and malware, updated all my windows updates, and still here with no idea of whats going on. Please see attached for my Mem dumps. Much appreciated if anyone could...
Persisting ntoskrnl.exe error (Win8 x64) in BSOD Crashes and Debugging
Hi, So I have been getting Blue screens on and off for a fair time now ( few months ) from once per week to multiple times per day. I have been trying to fix the problem for a fair while but I feel I am getting nowhere in which the frequency of the blue screens doesn't seem to change no matter....
Hey, I am getting a BSOD since one week randomly with the message IRQL_NOT_LESS_OR_EQUAL. BlueScreen Viewer showes me, that it is caused by the driver ntoskrnl.exe. Before I got this BSOD I updated my Windows 8.1 to Windows 8.1.1 . Since this time, this error happens randomly! My system...
Hello, I am in desperate need of assistance. I have tried updating all drivers etc, (hoping I got the right ones), ran all windows updates, have replaced a CPU cooling fan and NorthBridge fan but I don't believe temperatures are my problem. Am kind of a noob with Computers so please bear with me...
Another ntoskrnl.exe error on Windows 8.1 in BSOD Crashes and Debugging
So I know its been posted a few times lately that some people are receiving a BSOD with reference to ntoskrnl.exe. Mines a bit different. I recently upgraded to 8.1 and every time I play a game my computer shuts down. No BSOD, no freezing, nothing... just cut to black with no power. This is the...
Access violation error at address 1002787D in BSOD Crashes and Debugging
I am getting the following error window popping up numerous times during the day and cannot figure out why..... access violation at address 1002787D in module "EzULIB.dll". Write of address DDDDDDE1 ideas?
Eight Forums Android App Eight Forums IOS App Follow us on Facebook