Hi,
We have various bugchecks from the attached DMP files:
DRIVER_POWER_STATE_FAILURE (9f)
This bug check indicates that the driver is in an inconsistent or invalid power state.
If we run an !irp on the 4th parameter of the bugcheck (blocked IRP address), we get the following:
Code:
>[ 16, 2] 0 0 fffffa8009edd050 00000000 00000000-00000000
Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
\Driver\NETwNs64
NETwNs64.sys is the Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7. Usually when we have network relate crashes like this it's due to one of two reasons:
1. Network drivers themselves need to be updated (or another 3rd party device driver causing conflicts and or corruption).
2. 3rd party antivirus or firewall software causing network conflicts. What security software do you have installed, if any?
-----------------------------------------------------
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
This is the general bug check code for fatal errors found by Driver Verifier.
If we take a look at the call stack:
Code:
2: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`039a1488 fffff800`035554ec : 00000000`000000c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`039a1490 fffff800`03555f2b : fffffa80`04ca6b00 fffff800`030f284c ffffffff`ffffffff fffff800`031cfd0b : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`039a14d0 fffff800`03566ba8 : 00000000`6547654c 00000000`00000080 00000000`00000010 fffff880`0000003f : nt!ExAllocatePoolSanityChecks+0xcb
fffff880`039a1510 fffff800`03566e17 : 00000000`00000000 00000000`00000000 fffff980`6547654c fffff980`2370cfec : nt!VeAllocatePoolWithTagPriority+0x88
fffff880`039a1580 fffff880`0796d5a1 : 00000000`00000000 00000000`00000000 fffff980`2370cfd0 fffff800`0356213c : nt!VerifierExAllocatePoolWithTagPriority+0x17
fffff880`039a15c0 fffff880`0796c7bb : fffff880`07973c20 fffff980`2370cfd0 fffff980`23766f90 fffff980`2370cfd0 : tcpipreg!InterfaceAddressRegKeyChangeHandler+0x109
fffff880`039a16f0 fffff880`0796ba59 : fffff880`00000001 00000000`00000103 fffff980`23766f70 00000000`00000001 : tcpipreg!TcpipRegQueryAndUpdateKeyValue+0x363
fffff880`039a1780 fffff880`01e55754 : fffff880`07971a60 00000000`00000004 00000000`00000000 fffff880`07974318 : tcpipreg!TcpipRegStartRegistryKeyNotification+0xbd
fffff880`039a17d0 fffff880`0796c293 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07977073 : NETIO!RtlInvokeStartRoutines+0x34
fffff880`039a1810 fffff800`034b2747 : fffffa80`00000006 fffffa80`0d07d420 fffffa80`0d07e000 00000000`00000001 : tcpipreg!DriverEntry+0x257
fffff880`039a1860 fffff800`034b2b45 : fffff880`07fd5a80 00000000`00000000 00000000`00000001 00000000`00000001 : nt!IopLoadDriver+0xa07
fffff880`039a1b30 fffff800`030d1251 : fffffa80`00000000 ffffffff`80001120 fffff800`034b2af0 fffff980`0d88ed50 : nt!IopLoadUnloadDriver+0x55
fffff880`039a1b70 fffff800`03365ede : 00000000`00000000 fffffa80`06734040 00000000`00000080 fffffa80`0671b040 : nt!ExpWorkerThread+0x111
fffff880`039a1c00 fffff800`030b8906 : fffff880`037d7180 fffffa80`06734040 fffff880`037e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`039a1c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
Lots of tcpipreg.sys calls / NETIO.sys.. again, network related. This problem has only been observed after the machine's TCP/IP configuration has been changed from a static IP address to a dynamic address with DHCP, which leaves an empty value for the IPAddress registry key for the network interface.
Remove the registry key that can cause the null-byte allocation (verifier can remain enabled)
a. Boot the machine into Safe Mode
b. Run regedt32.exe
c. Find the following registry key, and if the Data value is empty, remove the registry key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<your-adapter-interface>
Name: IPAddress
Type: REG_MULTI_SZ
Data:
NOTE: If the Data is non-NULL, then this is not the cause of this STOP error and the IPAddress registry value should
not be deleted. If IPAddress shows no Data value, then delete the IPAddress entry and restart the machine.
Regards,
Patrick