BSOD WIN8.1 twice already ran verifier

[myron]

Hello

So I got my first BSOD yesterday with the error ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Then the second on the restart when I switched off verifier settings today stating DRIVER_POWER_STATE_FAILURE.

It seems like there are alot of drivers involved.

Please help me get my head around it.

Ive updated BIOS and the laptop is two weeks old.

 

[Patrick]

0: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000004 00000000`0000012c ffffe000`7a35d040 fffff800`80428980

The 0x9F is an 0x4 1st parameter, therefore without a kernel-dump we can't check the locks to see what caused the synchronization failure, despite being verifier enabled.

Looking at the stack though quickly:

0: kd> k
Child-SP          RetAddr           Call Site
ffffd000`215fb990 fffff800`7eb294fe nt!KiSwapContext+0x76
ffffd000`215fbad0 fffff800`7eb28f79 nt!KiSwapThread+0x14e
ffffd000`215fbb70 fffff800`7eafb340 nt!KiCommitThreadWait+0x129
ffffd000`215fbbf0 fffff801`ed77de68 nt!KeWaitForSingleObject+0x2c0
ffffd000`215fbc80 fffff801`eb2f9883 nwifi!FilterPause+0x5c
ffffd000`215fbcc0 fffff801`eb32bffe ndis!ndisFInvokePause+0x33
ffffd000`215fbcf0 fffff801`eb2f97fd ndis!ndisPauseFilterInner+0xde
ffffd000`215fbd90 fffff801`eb2ee6a6 ndis!ndisPauseFilter+0x5d
ffffd000`215fbdd0 fffff801`eb2ee01c ndis!Ndis::BindEngine::Iterate+0x62e
ffffd000`215fbfe0 fffff801`eb2efba4 ndis!Ndis::BindEngine::UpdateBindings+0x64
ffffd000`215fc010 fffff801`eb2edd44 ndis!Ndis::BindEngine::DispatchPendingWork+0x50
ffffd000`215fc040 fffff801`eb32a21f ndis!Ndis::BindEngine::ApplyBindChanges+0x58
ffffd000`215fc090 fffff801`eb2f50f9 ndis!ndisPnPRemoveDevice+0x18b
ffffd000`215fc2e0 fffff801`eb32fc93 ndis!ndisPnPRemoveDeviceEx+0x59
ffffd000`215fc310 fffff801`eb2f0190 ndis!ndisPnPIrpRemoveDevice+0x4fa3
ffffd000`215fc370 fffff800`7f108911 ndis!ndisPnPDispatch+0x1f8
ffffd000`215fc3e0 fffff800`7f12503e nt!IovCallDriver+0x3cd
ffffd000`215fc430 fffff800`7f108911 nt!ViFilterDispatchPnp+0x16a
ffffd000`215fc470 fffff801`eaa97660 nt!IovCallDriver+0x3cd

My bet is given all of the network related calls from NDIS, we're dealing with a network conflict. For example, the FilterPause function is called by the filter driver (nwifi) from NDIS due to the start of execution. What's expected afterwards is we then call NdisFSendNetBufferListsComplete to return a linked list, among other functions that do misc. things. Instead however, we just.... do nothing. We timeout. Taking a look at the bug check output again, we actually timeout for 12c = 12 seconds.

For starters, get rid of avast! as it's probably the problem:

avast! removal - http://www.avast.com/uninstall-utility

Windows Defender (how to turn on after removal)

A.Navigate to Control Panel (with icons). You can do this by hitting Start > Search > Control Panel. Once in Control Panel, change the drop-down from Category to Large and/or Small icons.

B.Among the list of icons, find and click Action Center.

C.Assuming the removal of your prior antivirus software went properly, you will notice for both Spyware and unwated software protection (important) and Virus protection (important), it'll have a button labeled Turn on now. Click this button (it doesn't matter which, as Windows Defender serves as both in Windows 8/8.1).

 

[myron]

Patrick you're a good man.

I just installed avast the other day too. I'm uninstalling it and will let you know how it goes.

 

[Patrick]

Let me know how it goes : )