Win 8.1 boot error ntoskrnl.exe - Address 0xfffff8022c35b9

Ichi

New Member
Messages
3
Hello,

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 Computer

System One

  • OS
    win 8.1
Code:
1: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
[COLOR=#000000]
1: kd> !irql
Debugger saved IRQL for processor 0x1 -- 13[/COLOR][COLOR=#800080]

//The system spent too long at IRQL above 2, in this case it was 13[/COLOR]

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 [COLOR=#800080]//Count the ticks[/COLOR]
02 ffffd001`2c969d20 fffff802`2c9a767f nt!KeClockInterruptNotify+0x787 [COLOR=#800080]//Notify of clock interrupt[/COLOR]
03 ffffd001`2c969f40 fffff802`2c2f0eb3 hal!HalpTimerClockInterrupt+0x4f [COLOR=#800080]//Clock interrupt[/COLOR]
04 ffffd001`2c969f70 fffff802`2c35ce2a nt!KiCallInterruptServiceRoutine+0xa3 [COLOR=#800080]//Call the ISR[/COLOR]
05 ffffd001`2c969fb0 fffff802`2c35d20f nt!KiInterruptSubDispatchNoLockNoEtw+0xea [COLOR=#800080]//Dispatch interrupt[/COLOR]
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.


Code:
1: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000004 00000000`0000012c ffffe000`57010680 ffffd001`fff5b980
[COLOR=#800080]
//Driver failed to complete a power IRP within the allocated time interval, the driver failed to syncrhonise with the pnp manager[/COLOR]

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
[COLOR=#800080]
//One driver object associated with one device object, creating a simple stack
[/COLOR]
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 [COLOR=#800080]//Change context to next thread[/COLOR]
ffffd000`21699c20 fffff800`082586c9 : ffffd000`21699fb0 ffffe001`fecb56f0 ffffd000`a5f094a0 fffff800`084ad6ca : nt!KiSwapThread+0x14e [COLOR=#800080]//Change thread execution[/COLOR]
ffffd000`21699cc0 fffff800`08268c9a : ffffc001`e9d9c980 00000000`00000000 ffffd000`a5f40000 00000000`00000801 : nt!KiCommitThreadWait+0x129 [COLOR=#800080]//Enter wait state[/COLOR]
ffffd000`21699d40 fffff800`9e937583 : ffffe002`0328a9e8 fffff800`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x22a [COLOR=#800080]//Wait for event, either notification or synchronisation event[/COLOR]
ffffd000`21699dd0 fffff800`9dca2fd8 : ffffc001`e9cf3778 fffff800`9e93d68d ffffe002`06c351d0 fffff800`9e8b3601 : ndis!NdisWaitEvent+0x43 [COLOR=#800080]//Network driver interface specification wait function[/COLOR]
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 [COLOR=#800080]//Unbind functions[/COLOR]
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 [COLOR=#800080]//Ready to bind the device[/COLOR]
ffffd000`2169a3a0 fffff800`9e9496d9 : ffffe002`035991a0 ffffd000`2169a6d0 ffffe002`035991a0 ffffe002`09cbf010 : ndis!ndisPnPRemoveDevice+0x1ae [COLOR=#800080]//Remove the device[/COLOR]
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 [COLOR=#800080]//Remove the device[/COLOR]
ffffd000`2169a690 fffff800`08623f76 : ffffe002`03599001 ffffe002`03599050 ffffd000`2169a701 00000000`00000002 : ndis!ndisPnPDispatch+0x1ec [COLOR=#800080]//Dispatch PnP transition[/COLOR]
ffffd000`2169a700 fffff800`086e3df8 : 00000000`00000017 ffffd000`2169a7c9 ffffe002`068b8010 ffffe002`03325650 : nt!IopSynchronousCall+0xfe [COLOR=#800080]//Perform IO then enter a wait state[/COLOR]
ffffd000`2169a770 fffff800`086e1243 : ffffc001`f4ed2c70 ffffc001`d7a16520 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0xe0 [COLOR=#800080]//IO device removal[/COLOR]
ffffd000`2169a830 fffff800`086e377e : ffffe002`068b8010 00000000`00000000 ffffc001`d7a16520 ffffc001`d7a16520 : nt!PnpSurpriseRemoveLockedDeviceNode+0xbb [COLOR=#800080]//Remove device node from PnP tree[/COLOR]
ffffd000`2169a890 fffff800`086e36be : 00000000`00000000 ffffc001`d7a16520 ffffe002`068b8010 fffff800`087aa046 : nt!PnpDeleteLockedDeviceNode+0x86 [COLOR=#800080]//Delete locked device node[/COLOR]
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 [COLOR=#800080]//Target device[/COLOR]
ffffd000`2169aaf0 fffff800`08255a2b : fffff800`0862ba6c ffffc001`eca22010 ffffd000`2169abd0 ffffe002`068a7860 : nt!PnpDeviceEventWorker+0x311 [COLOR=#800080]//Worker thread execution[/COLOR]
ffffd000`2169ab50 fffff800`082f2514 : 498cd8d9`69b14d91 ffffe002`0b2a2880 ffffe002`0b2a2880 ffffe001`feacc040 : nt!ExpWorkerThread+0x293 [COLOR=#800080]//Start worker thread[/COLOR]
ffffd000`2169ac00 fffff800`083732c6 : ffffd000`a5f07180 ffffe002`0b2a2880 ffffe001`ff8aa880 7f283e39`b7db295b : nt!PspSystemThreadStartup+0x58 [COLOR=#800080]//System thread execution[/COLOR]
ffffd000`2169ac60 00000000`00000000 : ffffd000`2169b000 ffffd000`21695000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 [COLOR=#800080]//Start system thread[/COLOR]

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    
           \Driver\RasPppoe
            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 Computer

System One

  • OS
    Windows 7
Code:
1: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
[COLOR=#800080]
//System spent too long at IRQL 13[/COLOR]

1: kd> kn
 # Child-SP          RetAddr           Call Site
00 ffffd001`2c969c88 fffff802`2c37e490 nt!KeBugCheckEx [COLOR=#800080]//Bugcheck[/COLOR]
01 ffffd001`2c969c90 fffff802`2c25e9b7 nt!KeAccumulateTicks+0x125e0 [COLOR=#800080]//Count the ticks[/COLOR]
02 ffffd001`2c969d20 fffff802`2c9a767f nt!KeClockInterruptNotify+0x787 [COLOR=#800080]//Notify system of clock interrupt[/COLOR]
03 ffffd001`2c969f40 fffff802`2c2f0eb3 hal!HalpTimerClockInterrupt+0x4f [COLOR=#800080]//Clock interrupt[/COLOR]
04 ffffd001`2c969f70 fffff802`2c35ce2a nt!KiCallInterruptServiceRoutine+0xa3 [COLOR=#800080]//Call ISR[/COLOR]
05 ffffd001`2c969fb0 fffff802`2c35d20f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 ffffd001`29aa7160 fffff801`ba3df449 nt!KiInterruptDispatchLBControl+0x11f [COLOR=#800080]//Interrupt dispatch[/COLOR]
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 [COLOR=#800080]//Private Nvidia functions[/COLOR]
0d ffffd001`29aa7840 fffff801`ba05d4cb dxgkrnl!ADAPTER_RENDER_DdiSubmitCommand+0x79 [COLOR=#800080]//Render function[/COLOR]
0e ffffd001`29aa7880 fffff801`ba09702f dxgmms1!VidSchiSendToExecutionQueue+0x4fb [COLOR=#800080]//Send to execution queue[/COLOR]
0f ffffd001`29aa7990 fffff801`ba098da5 dxgmms1!VidSchiSubmitRenderCommand+0x7cf[COLOR=#800080] //Submit render command[/COLOR]
10 ffffd001`29aa7b70 fffff801`ba098d1d dxgmms1!VidSchiRun_PriorityTable+0x85 [COLOR=#800080]//Check the run priority table[/COLOR]
11 ffffd001`29aa7bc0 fffff802`2c2e3280 dxgmms1!VidSchiWorkerThread+0x8d [COLOR=#800080]//Schedule work thread[/COLOR]
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:

My Computer

System One

  • OS
    Windows 7
Hello,

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 Computer

System One

  • OS
    win 8.1
Back
Top