BSOD at night after closing laptop, ntoskrnl.exe 0x0000000A


  1. Posts : 1
    Microsoft Windows 7 Enterprise 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSOD at night after closing laptop, ntoskrnl.exe 0x0000000A


    Most nights when I close my laptop to go to bed, I wake up in the morning to either a BSOD, or the laptop will be off. I'll turn it back on to find the "start windows normally" screen, and a dialogue box asking to search for solutions to the error. This happens almost every night for the past few weeks.

    I have recently reinstalled/update a lot of my drivers, but nothing is seeming to work. Any help would be greatly appreciated.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    It is caused by Netgear Geanie.

    Either you may attempt to update it or you may want to uninstall it.

    Let us know the results as per your decision.
    ________________________________________
    Code:
    ........................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa8039769178, 2, 1, fffff80002edf035}
    
    *** WARNING: Unable to verify timestamp for npf.sys
    *** ERROR: Module load completed but symbols could not be loaded for npf.sys
    Probably caused by : npf.sys ( npf+2bb2 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa8039769178, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002edf035, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310e100
    GetUlongFromAddress: unable to read from fffff8000310e1c0
     fffffa8039769178 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeAcquireSpinLockRaiseToDpc+55
    fffff800`02edf035 f0480fba2900    lock bts qword ptr [rcx],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    TRAP_FRAME:  fffff880033066d0 -- (.trap 0xfffff880033066d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8039769178
    rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002edf035 rsp=fffff88003306860 rbp=fffffa8039769178
     r8=fffffa8006a0a528  r9=0000000000000000 r10=fffffffffffffffe
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KeAcquireSpinLockRaiseToDpc+0x55:
    fffff800`02edf035 f0480fba2900    lock bts qword ptr [rcx],0 ds:fffffa80`39769178=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ed4469 to fffff80002ed4ec0
    
    STACK_TEXT:  
    fffff880`03306588 fffff800`02ed4469 : 00000000`0000000a fffffa80`39769178 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`03306590 fffff800`02ed30e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`033066d0 fffff800`02edf035 : 00000000`00000000 fffff880`018255b2 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`03306860 fffff880`06082bb2 : 00000000`00000001 fffffa80`0b7d41a0 fffffa80`0b928ce0 fffffa80`39766000 : nt!KeAcquireSpinLockRaiseToDpc+0x55
    fffff880`033068b0 00000000`00000001 : fffffa80`0b7d41a0 fffffa80`0b928ce0 fffffa80`39766000 00000000`00060000 : npf+0x2bb2
    fffff880`033068b8 fffffa80`0b7d41a0 : fffffa80`0b928ce0 fffffa80`39766000 00000000`00060000 fffff880`033068d8 : 0x1
    fffff880`033068c0 fffffa80`0b928ce0 : fffffa80`39766000 00000000`00060000 fffff880`033068d8 fffff880`033068d8 : 0xfffffa80`0b7d41a0
    fffff880`033068c8 fffffa80`39766000 : 00000000`00060000 fffff880`033068d8 fffff880`033068d8 00000000`00000000 : 0xfffffa80`0b928ce0
    fffff880`033068d0 00000000`00060000 : fffff880`033068d8 fffff880`033068d8 00000000`00000000 fffffa80`0b928ce0 : 0xfffffa80`39766000
    fffff880`033068d8 fffff880`033068d8 : fffff880`033068d8 00000000`00000000 fffffa80`0b928ce0 fffff880`018c038b : 0x60000
    fffff880`033068e0 fffff880`033068d8 : 00000000`00000000 fffffa80`0b928ce0 fffff880`018c038b fffffa80`2ac3a6d0 : 0xfffff880`033068d8
    fffff880`033068e8 00000000`00000000 : fffffa80`0b928ce0 fffff880`018c038b fffffa80`2ac3a6d0 fffffa80`2ac3a6d0 : 0xfffff880`033068d8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    npf+2bb2
    fffff880`06082bb2 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  npf+2bb2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: npf
    
    IMAGE_NAME:  npf.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c24de72
    
    FAILURE_BUCKET_ID:  X64_0xA_npf+2bb2
    
    BUCKET_ID:  X64_0xA_npf+2bb2
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa_npf+2bb2
    
    FAILURE_ID_HASH:  {5f20b508-1aab-ff9b-98bc-ef920917c6aa}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm npf
    start             end                 module name
    fffff880`06080000 fffff880`0608c000   npf      T (no symbols)           
        Loaded symbol image file: npf.sys
        Image path: \??\C:\Windows\system32\drivers\npf.sys
        Image name: npf.sys
        Timestamp:        Fri Jun 25 22:20:58 2010 (4C24DE72)
        CheckSum:         00011844
        ImageSize:        0000C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:09.
Find Us