Windows 8 and 8.1 Forums

kernel data inpage error

  1. #1

    kernel data inpage error


    I was using my computer and thought I might have heard a quick beep but nothing happened so I wasn't sure if I was just hearing things but then perhaps 5 minutes later I got a blue screen with a message saying my computer had to shut down and restart. It said I could get more information about why it was doing this ny checking on line for kernel_data_inpage_error (msrpc.sys).
    I googled it and the first suggestion was to run a virus scan which I did and didn't have any viruses. It then suggested running chkdsk but I'm not really sure how to do that. Is that the next step I should be taking?

      My System SpecsSystem Spec

  2. #2


    Posts : 22,582
    64-bit Windows 10


    Hello Sheryltoo,

    Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    One of our BSOD experts will hopefully be by later to further help when you have posted the needed information.
      My System SpecsSystem Spec

  3. #3


    Thanks. Here's my zip file.
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Sheryltoo ^_^,

    I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-
    Code:
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: ffffe0015a0ed880, The thread currently holding on to the Pnp lock.
    Arg4: ffffd000db106950, nt!TRIAGE_9F_PNP on Win7 and higher
    
    Debugging Details:
    ------------------
    
    Implicit thread is now ffffe001`5a0ed880
    
    DRVPOWERSTATE_SUBCODE:  4
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53089439
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff801b670b000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    ffffd000`e13f2800 fffff803`ac856d1e : ffffd000`db119180 ffffe001`5a0ed880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
    ffffd000`e13f2940 fffff803`ac856779 : 00000000`00000101 00000000`00000000 ffffe001`563e4460 fffff801`b70973ab : nt!KiSwapThread+0x14e
    ffffd000`e13f29e0 fffff803`ac866dfa : ffffe001`563e4700 00000000`00000000 00000000`00000002 00000000`00000086 : nt!KiCommitThreadWait+0x129
    ffffd000`e13f2a60 fffff803`ac8cfa0a : ffffd000`e13f2b28 ffffe001`00000000 00000000`00000000 fffff803`00000000 : nt!KeWaitForSingleObject+0x22a
    ffffd000`e13f2af0 fffff801`b7350b91 : 00000000`00000000 fffff803`00000003 ffffe001`51968a30 ffffe001`59a592a0 : nt!ExWaitForRundownProtectionReleaseCacheAware+0xaa
    ffffd000`e13f2b60 fffff801`b712f962 : ffffe001`5250ac10 00000000`00000008 ffffe001`541c4620 ffffd000`e13f2de0 : tcpip!FlPnpEvent+0x1c5
    ffffd000`e13f2bd0 fffff801`b712f8c3 : ffffe001`51968a30 ffffd000`e13f2de0 ffffe001`541c4620 ffffd000`e13f2de0 : ndis!ndisInvokeNetPnPEvent+0x42
    ffffd000`e13f2c10 fffff801`b716d8a6 : 00000000`c00000bb ffffe001`541c4620 ffffe001`5250ac10 00000000`0000000c : ndis!ndisDeliverNetPnPEventSynchronously+0x47
    ffffd000`e13f2c50 fffff801`b712fa25 : ffffd000`e13f2de0 ffffd000`e13f2e59 ffffe001`519f51a0 ffffe001`5250ac10 : ndis!ndisPnPNotifyBinding+0x86
    ffffd000`e13f2d70 fffff801`b713bcc3 : ffffe001`5250ac10 ffffe001`519f51a0 ffffd000`e13f2fb0 fffff801`b7131531 : ndis!ndisPnPNotifyBindingUnlocked+0x35
    ffffd000`e13f2dc0 fffff801`b713bbff : 00000000`00000000 00000000`00000000 ffffc001`5abf9440 ffffd000`e13f3000 : ndis!ndisPauseProtocolInner+0x6b
    ffffd000`e13f2ec0 fffff801`b712fd61 : ffffe001`519f51a0 ffffd000`e13f3000 ffffe001`519f65e8 00000000`00000000 : ndis!ndisPauseProtocol+0x5f
    ffffd000`e13f2f00 fffff801`b713047c : ffffe001`519f51a0 ffffe001`519f51a0 ffffd000`e13f3100 ffffe001`519f65e8 : ndis!Ndis::BindEngine::Iterate+0x311
    ffffd000`e13f3110 fffff801`b712e708 : ffffe001`519f65e8 ffffd000`e13f32c0 ffffd000`e13f3190 ffffd000`e13f32c0 : ndis!Ndis::BindEngine::UpdateBindings+0x64
    ffffd000`e13f3140 fffff801`b71305b7 : ffffe001`519f65e8 ffffe001`519f65e8 ffffe001`52336b01 fffff801`b7130514 : ndis!Ndis::BindEngine::DispatchPendingWork+0x50
    ffffd000`e13f3170 fffff801`b716f78b : ffffe001`519f51a0 ffffe001`519f65e8 ffffe001`5a38d3a0 ffffe001`52336ba0 : ndis!Ndis::BindEngine::ApplyBindChanges+0x37
    ffffd000`e13f31c0 fffff801`b713c6d9 : ffffe001`519f51a0 ffffe001`519f5050 ffffe001`519f51a0 ffffe001`519f5050 : ndis!ndisPnPRemoveDevice+0x18b
    ffffd000`e13f3410 fffff801`b7175ca7 : 00000000`00000000 ffffe001`519f5050 ffffe001`51fb2010 ffffe001`00000000 : ndis!ndisPnPRemoveDeviceEx+0x59
    ffffd000`e13f3440 fffff801`b7131f06 : ffffe001`51fb2010 ffffd000`e13f34e0 ffffe001`519f51a0 00000000`00000000 : ndis!ndisPnPIrpRemoveDevice+0x6ba7
    ffffd000`e13f34a0 fffff801`b6546660 : ffffd000`e13f3601 ffffd000`e13f3620 ffffe001`561cc201 00000000`00000001 : ndis!ndisPnPDispatch+0x1d2
    ffffd000`e13f3510 fffff801`b64d2cf3 : 00000000`00000001 00000000`00000000 ffffd000`e13f3600 ffffe001`00000000 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x94
    ffffd000`e13f3540 fffff801`b64ba936 : ffffe001`561cc240 ffffd000`e13f3610 00000000`00000000 ffffe001`58ad6960 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x127
    ffffd000`e13f35b0 fffff801`b64b5a18 : ffffe001`51fb2010 ffffe001`51fb2010 00000000`00000000 ffffe001`51ead640 : Wdf01000!FxPkgPnp::Dispatch+0xd2
    ffffd000`e13f3620 fffff803`acbb1f4e : 00000000`00000000 00000000`00000000 ffffd000`e13f37b0 00000000`00000005 : Wdf01000!FxDevice::DispatchWithLock+0x7d8
    ffffd000`e13f3700 fffff803`acccae24 : 00000000`00000002 ffffd000`e13f37c9 ffffe001`51b57b40 ffffe001`51b571f0 : nt!IopSynchronousCall+0xfe
    ffffd000`e13f3770 fffff803`ac91b6bb : ffffc001`5f9d51a0 00000000`0000000a ffffe001`51b57b40 00000000`0000000a : nt!IopRemoveDevice+0xe0
    ffffd000`e13f3830 fffff803`accca771 : ffffe001`51b571f0 ffffe001`51b57b40 ffffc001`5cec6680 ffffe001`51b571f0 : nt!PnpRemoveLockedDeviceNode+0x1a7
    ffffd000`e13f3890 fffff803`accca6ea : 00000000`00000000 ffffc001`5cec6680 ffffe001`51b57b40 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d
    ffffd000`e13f38d0 fffff803`accc97f3 : ffffe001`51b571f0 ffffd000`00000002 00000000`00000000 fffff803`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
    ffffd000`e13f3950 fffff803`acba4139 : ffffc001`5f9d5100 00000000`00000002 ffffc001`00000000 ffffe001`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x4ef
    ffffd000`e13f3ab0 fffff803`acba4571 : ffffc001`5f9d51a0 00000000`00000000 00000000`00000000 fffff803`acba4260 : nt!PnpProcessTargetDeviceEvent+0x9d
    ffffd000`e13f3af0 fffff803`ac853adb : fffff803`acba4260 ffffc001`5fbe1dc0 ffffd000`e13f3bd0 ffffe001`59692f10 : nt!PnpDeviceEventWorker+0x311
    ffffd000`e13f3b50 fffff803`ac8cf794 : fffff901`41217b30 ffffe001`5a0ed880 ffffe001`5a0ed880 ffffe001`50e53040 : nt!ExpWorkerThread+0x293
    ffffd000`e13f3c00 fffff803`ac95a5c6 : ffffd000`dfb40180 ffffe001`5a0ed880 ffffe001`58975040 fffff803`ac898388 : nt!PspSystemThreadStartup+0x58
    ffffd000`e13f3c60 00000000`00000000 : ffffd000`e13f4000 ffffd000`e13ee000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  6.3.9600.17031
    
    FAILURE_BUCKET_ID:  0x9F_4_NETwew00_IMAGE_pci.sys
    
    BUCKET_ID:  0x9F_4_NETwew00_IMAGE_pci.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_4_netwew00_image_pci.sys
    
    FAILURE_ID_HASH:  {c2046996-1784-ae05-f9cd-27723d905439}
    
    Followup: MachineOwner
    ---------
    
    6: kd> !thread ffffe0015a0ed880
    GetPointerFromAddress: unable to read from fffff803acb54000
    THREAD ffffe0015a0ed880  Cid 0004.1a30  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
        ffffd000e13f2b28  SynchronizationEvent
    IRP List:
        ffffe00151fb2010: (0006,03e8) Flags: 00000000  Mdl: 00000000
    Not impersonating
    GetUlongFromAddress: unable to read from fffff803acaa0300
    Owning Process            ffffe00150e53040       Image:         System
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      681189       
    Context Switch Count      1280           IdealProcessor: 7  NoStackSwap
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address nt!ExpWorkerThread (0xfffff803ac853848)
    Stack Init ffffd000e13f3c90 Current ffffd000e13f27c0
    Base ffffd000e13f4000 Limit ffffd000e13ee000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    ffffd000`e13f2800 fffff803`ac856d1e : ffffd000`db119180 ffffe001`5a0ed880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
    ffffd000`e13f2940 fffff803`ac856779 : 00000000`00000101 00000000`00000000 ffffe001`563e4460 fffff801`b70973ab : nt!KiSwapThread+0x14e
    ffffd000`e13f29e0 fffff803`ac866dfa : ffffe001`563e4700 00000000`00000000 00000000`00000002 00000000`00000086 : nt!KiCommitThreadWait+0x129
    ffffd000`e13f2a60 fffff803`ac8cfa0a : ffffd000`e13f2b28 ffffe001`00000000 00000000`00000000 fffff803`00000000 : nt!KeWaitForSingleObject+0x22a
    ffffd000`e13f2af0 fffff801`b7350b91 : 00000000`00000000 fffff803`00000003 ffffe001`51968a30 ffffe001`59a592a0 : nt!ExWaitForRundownProtectionReleaseCacheAware+0xaa
    ffffd000`e13f2b60 fffff801`b712f962 : ffffe001`5250ac10 00000000`00000008 ffffe001`541c4620 ffffd000`e13f2de0 : tcpip!FlPnpEvent+0x1c5
    ffffd000`e13f2bd0 fffff801`b712f8c3 : ffffe001`51968a30 ffffd000`e13f2de0 ffffe001`541c4620 ffffd000`e13f2de0 : ndis!ndisInvokeNetPnPEvent+0x42
    ffffd000`e13f2c10 fffff801`b716d8a6 : 00000000`c00000bb ffffe001`541c4620 ffffe001`5250ac10 00000000`0000000c : ndis!ndisDeliverNetPnPEventSynchronously+0x47
    ffffd000`e13f2c50 fffff801`b712fa25 : ffffd000`e13f2de0 ffffd000`e13f2e59 ffffe001`519f51a0 ffffe001`5250ac10 : ndis!ndisPnPNotifyBinding+0x86
    ffffd000`e13f2d70 fffff801`b713bcc3 : ffffe001`5250ac10 ffffe001`519f51a0 ffffd000`e13f2fb0 fffff801`b7131531 : ndis!ndisPnPNotifyBindingUnlocked+0x35
    ffffd000`e13f2dc0 fffff801`b713bbff : 00000000`00000000 00000000`00000000 ffffc001`5abf9440 ffffd000`e13f3000 : ndis!ndisPauseProtocolInner+0x6b
    ffffd000`e13f2ec0 fffff801`b712fd61 : ffffe001`519f51a0 ffffd000`e13f3000 ffffe001`519f65e8 00000000`00000000 : ndis!ndisPauseProtocol+0x5f
    ffffd000`e13f2f00 fffff801`b713047c : ffffe001`519f51a0 ffffe001`519f51a0 ffffd000`e13f3100 ffffe001`519f65e8 : ndis!Ndis::BindEngine::Iterate+0x311
    ffffd000`e13f3110 fffff801`b712e708 : ffffe001`519f65e8 ffffd000`e13f32c0 ffffd000`e13f3190 ffffd000`e13f32c0 : ndis!Ndis::BindEngine::UpdateBindings+0x64
    ffffd000`e13f3140 fffff801`b71305b7 : ffffe001`519f65e8 ffffe001`519f65e8 ffffe001`52336b01 fffff801`b7130514 : ndis!Ndis::BindEngine::DispatchPendingWork+0x50
    ffffd000`e13f3170 fffff801`b716f78b : ffffe001`519f51a0 ffffe001`519f65e8 ffffe001`5a38d3a0 ffffe001`52336ba0 : ndis!Ndis::BindEngine::ApplyBindChanges+0x37
    ffffd000`e13f31c0 fffff801`b713c6d9 : ffffe001`519f51a0 ffffe001`519f5050 ffffe001`519f51a0 ffffe001`519f5050 : ndis!ndisPnPRemoveDevice+0x18b
    ffffd000`e13f3410 fffff801`b7175ca7 : 00000000`00000000 ffffe001`519f5050 ffffe001`51fb2010 ffffe001`00000000 : ndis!ndisPnPRemoveDeviceEx+0x59
    ffffd000`e13f3440 fffff801`b7131f06 : ffffe001`51fb2010 ffffd000`e13f34e0 ffffe001`519f51a0 00000000`00000000 : ndis!ndisPnPIrpRemoveDevice+0x6ba7
    ffffd000`e13f34a0 fffff801`b6546660 : ffffd000`e13f3601 ffffd000`e13f3620 ffffe001`561cc201 00000000`00000001 : ndis!ndisPnPDispatch+0x1d2
    ffffd000`e13f3510 fffff801`b64d2cf3 : 00000000`00000001 00000000`00000000 ffffd000`e13f3600 ffffe001`00000000 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x94
    ffffd000`e13f3540 fffff801`b64ba936 : ffffe001`561cc240 ffffd000`e13f3610 00000000`00000000 ffffe001`58ad6960 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x127
    ffffd000`e13f35b0 fffff801`b64b5a18 : ffffe001`51fb2010 ffffe001`51fb2010 00000000`00000000 ffffe001`51ead640 : Wdf01000!FxPkgPnp::Dispatch+0xd2
    ffffd000`e13f3620 fffff803`acbb1f4e : 00000000`00000000 00000000`00000000 ffffd000`e13f37b0 00000000`00000005 : Wdf01000!FxDevice::DispatchWithLock+0x7d8
    ffffd000`e13f3700 fffff803`acccae24 : 00000000`00000002 ffffd000`e13f37c9 ffffe001`51b57b40 ffffe001`51b571f0 : nt!IopSynchronousCall+0xfe
    ffffd000`e13f3770 fffff803`ac91b6bb : ffffc001`5f9d51a0 00000000`0000000a ffffe001`51b57b40 00000000`0000000a : nt!IopRemoveDevice+0xe0
    ffffd000`e13f3830 fffff803`accca771 : ffffe001`51b571f0 ffffe001`51b57b40 ffffc001`5cec6680 ffffe001`51b571f0 : nt!PnpRemoveLockedDeviceNode+0x1a7
    ffffd000`e13f3890 fffff803`accca6ea : 00000000`00000000 ffffc001`5cec6680 ffffe001`51b57b40 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d
    ffffd000`e13f38d0 fffff803`accc97f3 : ffffe001`51b571f0 ffffd000`00000002 00000000`00000000 fffff803`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
    ffffd000`e13f3950 fffff803`acba4139 : ffffc001`5f9d5100 00000000`00000002 ffffc001`00000000 ffffe001`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x4ef
    ffffd000`e13f3ab0 fffff803`acba4571 : ffffc001`5f9d51a0 00000000`00000000 00000000`00000000 fffff803`acba4260 : nt!PnpProcessTargetDeviceEvent+0x9d
    ffffd000`e13f3af0 fffff803`ac853adb : fffff803`acba4260 ffffc001`5fbe1dc0 ffffd000`e13f3bd0 ffffe001`59692f10 : nt!PnpDeviceEventWorker+0x311
    ffffd000`e13f3b50 fffff803`ac8cf794 : fffff901`41217b30 ffffe001`5a0ed880 ffffe001`5a0ed880 ffffe001`50e53040 : nt!ExpWorkerThread+0x293
    ffffd000`e13f3c00 fffff803`ac95a5c6 : ffffd000`dfb40180 ffffe001`5a0ed880 ffffe001`58975040 fffff803`ac898388 : nt!PspSystemThreadStartup+0x58
    ffffd000`e13f3c60 00000000`00000000 : ffffd000`e13f4000 ffffd000`e13ee000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    6: kd> !irp ffffe00151fb2010
    Irp is active with 5 stacks 4 is current (= 0xffffe00151fb21b8)
     No Mdl: No System Buffer: Thread ffffe0015a0ed880:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 1b, 2]   0  0 ffffe001519f5050 00000000 00000000-00000000    
              Unable to load image \SystemRoot\system32\DRIVERS\NETwew00.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for NETwew00.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwew00.sys
     \Driver\NETwNe64
                Args: 00000000 00000000 00000000 00000000
     [ 1b, 2]   0  0 ffffe001523b0bc0 00000000 00000000-00000000    
               \Driver\vwifibus
                Args: 00000000 00000000 00000000 00000000
    I have highlighted the driver causing this in RED(You would need to scroll till end). Now according to the dump file, the driver which is culprit in this case is "NETwNE64.sys" which is the Intel® Wireless WiFi Link Adapter driver. Below has been provided a list of 3rd party drivers found over your system :-
    Code:
    **************************Tue Jul 22 02:13:37.796 2014 (UTC + 5:30)**************************
    MarvinBus64.sys              Sat Sep 24 02:47:03 2005 (433470CF)
    wacommousefilter.sys         Fri Feb 16 23:42:17 2007 (45D5F401)
    wacomvhid.sys                Tue Sep 22 04:59:14 2009 (4AB80C4A)
    PxHlpa64.sys                 Tue Apr 24 22:56:29 2012 (4F96E245)
    WirelessButtonDriver64.sys   Thu Aug 30 08:41:29 2012 (503ED9E1)
    ISCTD64.sys                  Wed Nov 28 01:22:34 2012 (50B51A02)
    Accelerometer.sys            Wed Feb 27 01:38:10 2013 (512D162A)
    hpdskflt.sys                 Wed Feb 27 01:38:12 2013 (512D162C)
    INETMON.sys                  Thu Mar 14 02:41:58 2013 (5140EB9E)
    iBtFltCoex.sys               Thu Apr 18 19:47:24 2013 (51700074)
    btmaux.sys                   Tue Apr 23 16:58:02 2013 (51767042)
    btmhsf.sys                   Thu Jun 27 01:41:34 2013 (51CB4AF6)
    TeeDriverx64.sys             Wed Jul  3 00:08:08 2013 (51D31E10)
    iwdbus.sys                   Thu Jul 25 06:36:12 2013 (51F07A04)
    Rt630x64.sys                 Fri Jul 26 12:31:35 2013 (51F21ECF)
    SynTP.sys                    Fri Aug  2 06:21:42 2013 (51FB029E)
    Smb_driver_Intel.sys         Fri Aug  2 06:24:20 2013 (51FB033C)
    ikbevent.sys                 Wed Aug  7 05:11:35 2013 (520189AF)
    imsevent.sys                 Wed Aug  7 05:15:57 2013 (52018AB5)
    stwrt64.sys                  Fri Aug 16 15:56:26 2013 (520DFE52)
    nvlddmkm.sys                 Sun Aug 18 23:51:08 2013 (52111094)
    RtsPer.sys                   Wed Aug 21 12:53:24 2013 (52146AEC)
    intelppm.sys                 Thu Aug 22 14:16:35 2013 (5215CFEB)
    iaStorA.sys                  Thu Aug 29 03:43:22 2013 (521E7602)
    dump_iaStorA.sys             Thu Aug 29 03:43:22 2013 (521E7602)
    IntcDAud.sys                 Thu Aug 29 20:12:53 2013 (521F5DED)
    igdkmd64.sys                 Mon Sep  9 22:57:52 2013 (522E0518)
    clwvd6.sys                   Tue Oct 29 12:28:10 2013 (526F5C82)
    clwvd.sys                    Tue Jan 28 09:28:36 2014 (52E72AEC)
    NETwew00.sys                 Tue Feb 25 18:34:56 2014 (530C94F8)
    
    http://www.carrona.org/drivers/driver.php?id=MarvinBus64.sys
    http://www.carrona.org/drivers/driver.php?id=wacommousefilter.sys
    http://www.carrona.org/drivers/driver.php?id=wacomvhid.sys
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    http://www.carrona.org/drivers/driver.php?id=WirelessButtonDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
    http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys
    http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys
    http://www.carrona.org/drivers/driver.php?id=INETMON.sys
    http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=stwrt64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    clwvd6.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=clwvd.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    According to the stack, there is presence of too much Networking Related drivers.
    Please follow the below steps one step at a time and checking if you are getting any BSOD's or not :-

    1. Please update the drivers highlighted in RED.
    2. Please check if there is any update for your Intel Wireless Card from HP or not.
    3. If the problem is still not solved then please follow the below steps :-


    • Press the Windows(Start) button and type in Device Manager.
    • Open it. Click on the small arrow in the left side of the Network Adapters dropdown.
    • Search for your Intel Wireless Card. Right Click on it and select Uninstall.
    • Once it has been uninstalled, restart your PC and see if you are getting any BSOD's or not. Do not install any other driver over this. Let Windows automatically install the driver for it.


    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  5. #5


    The first driver you said I should update points to a Pinnacle program but I don't see anything about driver updates. I am using a version that wasn't really compatible with Windows 8 and had someone from pinnacle helping me make it work by installing a patch, along with doing some other things. I don't really use the program so if it's really necessary to find some new driver, I'd rather just uninstall it.
    I updated the Wacom driver and updated the Network driver.
    So far all is working ok but then everything seemed to work ok once the computer restarted after the blue screen.
    It's really interesting that the wireless adapter seems to be the problem because I was having a problem with my wireless internet connection cutting out and had to call HP to help me get it fixed. Perhaps it still wasn't fixed although I didn't think I was having any more issues with it.
    If I have any more problems or get the BSOD again, maybe HP will have to replace my wireless adapter. My computer is still under warranty.
    Thanks for your help.
      My System SpecsSystem Spec

  6. #6


    After updating my wireless adapter, I'm back to having Internet connection problems. I'm going to give HP a call again and see what they have to say. I had called them about the bsod and all they had me do was a hard reset. I didn't feel very confident that that fixed my problem and maybe it didn't. I had done that before trying your suggestions.
      My System SpecsSystem Spec

  7. #7


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Sheryltoo ^_^,

    I don't think that updating the driver would be required. Just uninstall the driver so that the Windows installs it's own generic drivers and see if the BSOD's are still happening or not.

    You could also see the scenario where you uninstall the driver and then do not restart the system to see if it is the network driver only causing the problems.

    In your next reply I would like a freshly generated SF Diagnostic File if further crashes occur so that those could be analyzed ^_^.
      My System SpecsSystem Spec

kernel data inpage error
Related Threads
Kernel data inpage error in BSOD Crashes and Debugging
I'll start off by saying that any attempt I've made at changing settings in order for the BSoD to give me a minidump has been a failure. Any time the BSoD comes up, the error report gets stuck at 0% indefinitely. This error has been popping up daily for a little over a week now, right after I...
BSOD kernel data inpage error in BSOD Crashes and Debugging
Hello guys, im new to this forum. I keep getting blue screen all the time, its so frustrating, ive reinstalled for 2nc time now and this error doesnt go away. I dont know what to do, i dont know if it is a hardware problem or a software problem, ive run RAM and HDD tests and passed both. And...
Solved Kernel Data Inpage Error every now and then in BSOD Crashes and Debugging
Hi, Lately I've been getting this BSOD every now and then .. usually when I'm multi-tasking (several apps working together) any ideas ?
BSOD - Kernel data inpage error in BSOD Crashes and Debugging
Hi all, I have started having BSODs since last week. They seemingly seem to occur at random after using my computer around an hour. My computer is 2 years old, and I have never had problems with it, nor have I made any changes in the last weeks. I have run chkdsk on both my drives, and...
Solved Kernel Data Inpage Error in BSOD Crashes and Debugging
hey guys. i recently got a new laptop. installed the OS, installed the drivers, everything is working fine except: the first time i turn the laptop on, it gives me the error "kernel_data_inpage_error", then it either turns itself off(at which point it works normally when i turn it back on) or...
Solved BSOD Kernel Data Inpage Error in BSOD Crashes and Debugging
Hello, I have a Gateway GT5408, purchased in 2007 that came with Vista. Last week my system failed to boot and I kept getting the black repair screen on an endless loop. So I replaced what I thought was a faulty hard drive and installed Windows 8. I’m now getting a BSOD that reads Kernel Data...
Kernel Data Inpage Error in Performance & Maintenance
The error often occurs when my Ultrabook wakes up after Standby... 9974 I am using the windows 8 student version from the dreamspark website. Is my version different from the "real" version that was released today? Should I update? Any other ideas? Thanks in advance.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook