Question
Reply
 
Student
JoeMell
Posts: 1
Member Since: ‎01-24-2012
Message 1 of 2 (726 Views)

Blue Screen HP Folio 13t-1000 CTO - IMAGE_NAME: NETwNs64.sys

Just installed on my Folio 13T-1000 CTO laptop windows 7 enterprise 64 bit and all drivers from HP Website.  Frequent Blue screens.  Two Blue screens posted below.

 

1st Blue screen

DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp  subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8004003b60, The thread currently holding on to the Pnp lock. Arg4: fffff800048e63d0

Debugging Details: ------------------

DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  0

STACK_TEXT:  fffff880`035a1510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpSmallNPagedPoolLookasideLists+0x75a

STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x9F_4_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_0x9F_4_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner ---------

 

 2nd blue screen:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Software\Marcel Minidump\011812-11902-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0? Symbol search path is: C:\WINDOWS\Symbols Executable search path is: Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b670 Debug session time: Tue Jan 17 18:15:52.224 2012 (UTC - 6:00) System Uptime: 0 days 7:05:33.332 Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009815c80, fffff80000b9c3d8, fffffa800c587840}

*** WARNING: Unable to verify timestamp for mssmbios.sys Unable to load image \SystemRoot\system32\drivers\Wdf01000.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Wdf01000.sys *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys 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 Probably caused by : NETwNs64.sys ( NETwNs64+abbb8 )

Followup: MachineOwner ---------

0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8009815c80, Physical Device Object of the stack Arg3: fffff80000b9c3d8, Functional Device Object of the stack Arg4: fffffa800c587840, The blocked IRP

Debugging Details: ------------------

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800c587840

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  0

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffff80000b9c530

STACK_COMMAND:  dds 00B9C530-0x20 ; kb

STACK_TEXT:  00000000`00b9c510  ???????? 00000000`00b9c514  ???????? 00000000`00b9c518  ???????? 00000000`00b9c51c  ???????? 00000000`00b9c520  ???????? 00000000`00b9c524  ???????? 00000000`00b9c528  ???????? 00000000`00b9c52c  ???????? 00000000`00b9c530  ???????? 00000000`00b9c534  ???????? 00000000`00b9c538  ???????? 00000000`00b9c53c  ???????? 00000000`00b9c540  ???????? 00000000`00b9c544  ???????? 00000000`00b9c548  ???????? 00000000`00b9c54c  ???????? 00000000`00b9c550  ???????? 00000000`00b9c554  ???????? 00000000`00b9c558  ???????? 00000000`00b9c55c  ???????? 00000000`00b9c560  ???????? 00000000`00b9c564  ???????? 00000000`00b9c568  ???????? 00000000`00b9c56c  ???????? 00000000`00b9c570  ???????? 00000000`00b9c574  ???????? 00000000`00b9c578  ???????? 00000000`00b9c57c  ???????? 00000000`00b9c580  ???????? 00000000`00b9c584  ???????? 00000000`00b9c588  ???????? 00000000`00b9c58c  ????????

FOLLOWUP_IP: NETwNs64+abbb8 fffff880`0af26bb8 ??              ???

SYMBOL_NAME:  NETwNs64+abbb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETwNs64

IMAGE_NAME:  NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e39e7aa

FAILURE_BUCKET_ID:  X64_0x9F_VRFK_3_NETwNs64+abbb8

BUCKET_ID:  X64_0x9F_VRFK_3_NETwNs64+abbb8

Followup: MachineOwner ---------

 

Any Advice on what to do?

 

Grad Student
icp_wolverine
Posts: 260
Member Since: ‎12-28-2011
Message 2 of 2 (679 Views)

Re: Blue Screen HP Folio 13t-1000 CTO - IMAGE_NAME: NETwNs64.sys

i did some searching outside of hp... the issue you're having is the drivers for your network , wether it be wifi or line... tryy to use windows update to update the drivers or uninstall the drivers for the network controller and reinstall... the drivers you have installed are for Vista instead of Windows 7... also try going to intel.com and see if there are any updates for your system using their auto update feature

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation