Windows 8 and 8.1 Forums


Random BSOD errors several times a day.

  1. #1


    Posts : 4
    windows 8.1

    Random BSOD errors several times a day.


    So I got myself a new computer not long ago, and I had some issues with the windows install that gave me 5-6 bsod a day atleast. Managed to fix that issue eventually, but lately it started to pop up with the same thing again, everything from MEMORY_MANAGEMENT to KERNEL_ERROR.
    Latest one was DL/DI.DLL

    It can happen during playing games, watching videos on youtube, or even idle.

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1



    Please uninstall Gigabyte Easy Tune (ifinstalled) and Easy Saver. Older versions are known to cause BSOD's on someWindows systems (and your Easy Saver dates from 2009).


    Of your 13 dumpfiles 11 are related to memory corruption..

    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck 109, {a3a00f58c37c9567, b3b71bdf15fb6bc2, fffff800f1c31c38, 1}
    Probably caused by : memory_corruption
    Followup: memory_corruption
    ---------
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See Kernel patch protection for x64-based operating systems
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a00f58c37c9567, Reserved
    Arg2: b3b71bdf15fb6bc2, Reserved
    Arg3: fffff800f1c31c38, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
     0 : A generic data region
     1 : Modification of a function or .pdata
     2 : A processor IDT
     3 : A processor GDT
     4 : Type 1 process list corruption
     5 : Type 2 process list corruption
     6 : Debug routine modification
     7 : Critical MSR modification
    Debugging Details:
    ------------------
    
    PG_MISMATCH:  2
    MEMORY_CORRUPTOR:  ONE_BIT
    FAULTING_IP: 
    CI!I_PEVerifyBootDrivers+0
    fffff800`f1c31c38 4c8bdc          mov     r11,rsp
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    BUGCHECK_STR:  0x109
    PROCESS_NAME:  csrss.exe
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    STACK_TEXT:  
    ffffd000`357bb088 00000000`00000000 : 00000000`00000109 a3a00f58`c37c9567 b3b71bdf`15fb6bc2 fffff800`f1c31c38 : nt!KeBugCheckEx
    
    STACK_COMMAND:  kb
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !CI
        fffff800f1c32097 - CI!I_PEVerifyBootDrivers+45f
     [ cd:cf ]
    1 error : !CI (fffff800f1c32097)
    MODULE_NAME: memory_corruption
    IMAGE_NAME:  memory_corruption
    FOLLOWUP_NAME:  memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
    Followup: memory_corruption
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 24, {b500190637, ffffd000320fd5f8, ffffd000320fce00, fffff8019d1ca096}
    Probably caused by : memory_corruption
    Followup: memory_corruption
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 000000b500190637
    Arg2: ffffd000320fd5f8
    Arg3: ffffd000320fce00
    Arg4: fffff8019d1ca096
    Debugging Details:
    ------------------
    
    EXCEPTION_RECORD:  ffffd000320fd5f8 -- (.exr 0xffffd000320fd5f8)
    ExceptionAddress: fffff8019d1ca096 (Ntfs!NtfsCheckpointCurrentTransaction+0x0000000000000036)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    CONTEXT:  ffffd000320fce00 -- (.cxr 0xffffd000320fce00;r)
    rax=ffffd00032861790 rbx=ffffd00032861610 rcx=0000000000000727
    rdx=ffffd000328616f0 rsi=ffffd00032861610 rdi=ffffc0001a4f6010
    rip=fffff8019d1ca096 rsp=ffffd000320fd830 rbp=ffffe001a6a1b180
     r8=0000000000000001  r9=7fffe001a8304938 r10=ffffe001a8304938
    r11=ffffd000320fd810 r12=0000000000000000 r13=ffffd000320fde30
    r14=ffffe001a6a1b180 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
    Ntfs!NtfsCheckpointCurrentTransaction+0x36:
    fffff801`9d1ca096 48              ???
    Last set context:
    rax=ffffd00032861790 rbx=ffffd00032861610 rcx=0000000000000727
    rdx=ffffd000328616f0 rsi=ffffd00032861610 rdi=ffffc0001a4f6010
    rip=fffff8019d1ca096 rsp=ffffd000320fd830 rbp=ffffe001a6a1b180
     r8=0000000000000001  r9=7fffe001a8304938 r10=ffffe001a8304938
    r11=ffffd000320fd810 r12=0000000000000000 r13=ffffd000320fde30
    r14=ffffe001a6a1b180 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
    Ntfs!NtfsCheckpointCurrentTransaction+0x36:
    fffff801`9d1ca096 48              ???
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    BUGCHECK_STR:  0x24
    PROCESS_NAME:  SensorDetector
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING}  Ongeldige instructie  Er is geprobeerd een ongeldige instructie uit te voeren.
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING}  Ongeldige instructie  Er is geprobeerd een ongeldige instructie uit te voeren.
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8019d1d4d19 to fffff8019d1ca096
    STACK_TEXT:  
    ffffd000`320fd830 fffff801`9d1d4d19 : 00000000`00000000 ffffd000`328618a0 ffffd000`32861610 00000000`00000000 : Ntfs!NtfsCheckpointCurrentTransaction+0x36
    ffffd000`320fd860 fffff801`9d1ade9c : ffffc000`1a4f6010 ffffd000`32861610 ffffd000`32861610 ffffc000`1a4f6140 : Ntfs!NtfsDeleteFile+0x519
    ffffd000`320fdb20 fffff801`9d1bcddd : ffffe001`aaff8bb8 ffffe001`a98788b0 ffffd000`32861588 ffffe001`aa13e080 : Ntfs!NtfsCommonCleanup+0x2a03
    ffffd000`320fdf50 fffff803`263dd8f7 : ffffd000`32861588 00000000`00abe378 00000000`7f17c000 00000000`00bbf01c : Ntfs!NtfsCommonCleanupCallout+0x19
    ffffd000`320fdf80 fffff803`263dd8bd : ffffd000`32861600 00000000`00000000 00000000`00000002 fffff803`26360388 : nt!KxSwitchKernelStackCallout+0x27
    ffffd000`32861430 fffff803`26360388 : 00000000`00000006 ffffd000`32861600 00000000`00000006 00000000`00000000 : nt!KiSwitchKernelStackContinue
    ffffd000`32861450 fffff801`9d1c8f65 : fffff801`9d1bcdc4 ffffd000`32861588 ffffe001`a9878800 ffffe001`a9dfccd8 : nt!KeExpandKernelStackAndCalloutInternal+0x218
    ffffd000`32861540 fffff801`9ce02cf8 : ffffe001`a9dfcc00 00000000`00000012 ffffe001`a98788b0 00000000`00000000 : Ntfs!NtfsFsdCleanup+0x185
    ffffd000`32861850 fffff801`9ce010b6 : ffffe001`a81d0920 00000000`00000000 ffffe001`a98788b0 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd000`328618f0 fffff803`26678b32 : ffffe001`a98788b0 ffffe001`a96f2900 00000000`00000000 00000000`00010000 : fltmgr!FltpDispatch+0xb6
    ffffd000`32861950 fffff803`26677bf5 : ffffe001`a8ecd860 ffffd000`32861a99 00000000`00007ffe 00000000`00007ffe : nt!IopCloseFile+0x152
    ffffd000`328619e0 fffff803`263e57b3 : ffffe001`aa13e080 00000000`00000000 00000000`00abfdb0 00000000`00bbea30 : nt!NtClose+0x1c5
    ffffd000`32861b00 00000000`77312772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00abece8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77312772
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
        fffff8019d1ca097 - Ntfs!NtfsCheckpointCurrentTransaction+37
     [ 8d:8f ]
    1 error : !Ntfs (fffff8019d1ca097)
    MODULE_NAME: memory_corruption
    IMAGE_NAME:  memory_corruption
    FOLLOWUP_NAME:  memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MEMORY_CORRUPTOR:  ONE_BIT
    STACK_COMMAND:  .cxr 0xffffd000320fce00 ; kb
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
    Followup: memory_corruption
    ---------
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041793, The subtype of the bugcheck.
    Arg2: fffff680000d0090
    Arg3: 0000000000000013
    Arg4: 0000000000000012
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x1a_41793
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  Steam.exe
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff801ae80007c to fffff801ae7d4fa0
    STACK_TEXT:  
    ffffd000`33c1eda8 fffff801`ae80007c : 00000000`0000001a 00000000`00041793 fffff680`000d0090 00000000`00000013 : nt!KeBugCheckEx
    ffffd000`33c1edb0 fffff801`ae6f20b2 : ffffe000`8759a560 ffffe000`87f97540 00000000`00000000 ffffe000`53646156 : nt! ?? ::FNODOBFM::`string'+0x1abcc
    ffffd000`33c1f040 fffff801`ae6eef5d : ffffe000`852e93c0 00000000`00000010 ffffd001`00000000 ffffd001`00000000 : nt!MiDeleteVad+0xc22
    ffffd000`33c1f140 fffff801`ae7e07b3 : 00000000`00000000 ffffe000`83bc8c70 00000000`00000000 00000000`00000020 : nt!NtFreeVirtualMemory+0x89d
    ffffd000`33c1f2a0 fffff801`ae7d8c00 : fffff960`001b90c4 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
    ffffd000`33c1f438 fffff960`001b90c4 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`19ea0000 : nt!KiServiceLinkage
    ffffd000`33c1f440 fffff960`001bc8dc : 00000000`00000000 ffffd000`33c1f660 000018d3`00000000 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x594
    ffffd000`33c1f5f0 fffff960`001af386 : 00000000`00000001 00000000`0c0518d3 00000000`00000001 00000000`00000001 : win32k!SURFREF::bDeleteSurface+0x14
    ffffd000`33c1f620 fffff960`001b37d2 : 00000000`00000001 00000000`00001600 fffff901`42bc3bb0 00000000`00000002 : win32k!vCleanupSurfaces+0xca
    ffffd000`33c1f650 fffff960`001ac97f : 00000000`00001600 ffffd000`33c1f6e0 ffffd000`33c1f860 fffff901`4234b010 : win32k!NtGdiCloseProcess+0xa6
    ffffd000`33c1f680 fffff960`001adf1f : fffff901`4234b010 ffffd000`33c1f818 ffffe000`8377b390 00000000`00000000 : win32k!GdiProcessCallout+0x47
    ffffd000`33c1f720 fffff801`aea5fe1e : ffffd000`33c1f860 ffffd000`33c1f800 00000000`00000000 00060030`00010002 : win32k!W32pProcessCallout+0x53
    ffffd000`33c1f750 fffff801`aea60373 : ffffe000`83d47e40 00000000`00000000 00000000`00000000 ffffe000`86e89588 : nt!PsInvokeWin32Callout+0x42
    ffffd000`33c1f790 fffff801`aeb26874 : ffffd000`00000001 ffffe000`87f97540 ffffd000`33c1fb00 ffffe000`87f975e8 : nt!PspExitThread+0x4d3
    ffffd000`33c1f8a0 fffff801`ae6d959d : ffffe000`82d72010 ffffe000`885fb400 ffffe000`87cc6570 ffffffff`ffffffff : nt!KiSchedulerApcTerminate+0x18
    ffffd000`33c1f8d0 fffff801`ae7d9ec0 : 00000000`000008c8 ffffd000`33c1f950 fffff801`ae6c5368 00000000`00000000 : nt!KiDeliverApc+0x2ed
    ffffd000`33c1f950 fffff801`ae7e085a : ffffe000`86e897a8 00000000`00000000 00000000`00000001 fffff6fb`7da00000 : nt!KiInitiateUserApc+0x70
    ffffd000`33c1fa90 00000000`77c22772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
    00000000`0bdfeef8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c22772
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    win32k!SURFACE::bDeleteSurface+594
    fffff960`001b90c4 ba05000000      mov     edx,5
    SYMBOL_STACK_INDEX:  6
    SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+594
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5308949c
    IMAGE_VERSION:  6.3.9600.17031
    BUCKET_ID_FUNC_OFFSET:  594
    FAILURE_BUCKET_ID:  0x1a_41793_win32k!SURFACE::bDeleteSurface
    BUCKET_ID:  0x1a_41793_win32k!SURFACE::bDeleteSurface
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x1a_41793_win32k!surface::bdeletesurface
    FAILURE_ID_HASH:  {125d040d-6ab5-e24b-4b91-83f62ff976e6}
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {ffffffffc0000005, fffff8009c48ec40, 0, 2fe8}
    Probably caused by : ntkrnlmp.exe ( nt!HvpGetCellPaged+50 )
    Followup: MachineOwner
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8009c48ec40, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000002fe8, Parameter 1 of the exception
    Debugging Details:
    ------------------
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8009c3cf138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000002fe8 
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    FAULTING_IP: 
    nt!HvpGetCellPaged+50
    fffff800`9c48ec40 488b04c8        mov     rax,qword ptr [rax+rcx*8]
    EXCEPTION_PARAMETER2:  0000000000002fe8
    BUGCHECK_STR:  0x1E_c0000005_R
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME:  ffffd000378863f0 -- (.trap 0xffffd000378863f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000000005fd
    rdx=0000000000000278 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8009c48ec40 rsp=ffffd00037886588 rbp=ffffc000158f9000
     r8=ffffc00000c27340  r9=00000000000003ff r10=0000000000001003
    r11=ffffc00015a6f5ec r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!HvpGetCellPaged+0x50:
    fffff800`9c48ec40 488b04c8        mov     rax,qword ptr [rax+rcx*8] ds:00000000`00002fe8=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8009c219d47 to fffff8009c1cefa0
    STACK_TEXT:  
    ffffd000`37885b18 fffff800`9c219d47 : 00000000`0000001e ffffffff`c0000005 fffff800`9c48ec40 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`37885b20 fffff800`9c1dabc2 : 00000000`00000001 00000000`00000002 fffff6fb`7dbedc00 fffff6fb`7db80000 : nt! ?? ::FNODOBFM::`string'+0x3a897
    ffffd000`37886210 fffff800`9c1d9314 : 00000000`00000000 00000000`00181308 ffffc000`158f9000 ffffd000`378863f0 : nt!KiExceptionDispatch+0xc2
    ffffd000`378863f0 fffff800`9c48ec40 : fffff800`9c4acb4d 00000000`00000004 ffffc000`158f9000 00000000`00000054 : nt!KiPageFault+0x214
    ffffd000`37886588 fffff800`9c4acb4d : 00000000`00000004 ffffc000`158f9000 00000000`00000054 ffffd000`378865c0 : nt!HvpGetCellPaged+0x50
    ffffd000`37886590 fffff800`9c4acaf8 : ffffc000`15a6f5ec 00000000`00181308 ffffc000`014d104c ffffc000`158f9000 : nt!CmpCopyCell+0x1d
    ffffd000`378865c0 fffff800`9c574fdb : ffffc000`0084b0a0 ffffc000`0084b048 ffffc000`158fe028 00007ffe`00000000 : nt!CmpCopyKeyPartial+0x258
    ffffd000`37886640 fffff800`9c574c4e : ffffc000`158fe000 00007ffe`ffffff00 00000000`00000000 ffffc000`00c27000 : nt!CmpCopySyncTree2+0x363
    ffffd000`37886710 fffff800`9c63b745 : 00000000`00000020 ffffc000`01030380 ffffc000`00c27000 ffffc000`158f9000 : nt!CmpCopySyncTree+0x76
    ffffd000`37886760 fffff800`9c62e876 : 00000000`0000002b ffffd000`37886850 00000000`00000000 ffffd000`37886880 : nt!CmSaveKey+0x1d9
    ffffd000`37886800 fffff800`9c1da7b3 : ffffe001`ea7d4080 00000000`00000000 ffffd000`37886870 00020006`00020019 : nt!NtSaveKey+0x2ea
    ffffd000`378868b0 fffff800`9c1d2c00 : fffff800`9c62e778 ffffe001`eaf4df20 00000000`00000000 00000000`00000764 : nt!KiSystemServiceCopyEnd+0x13
    ffffd000`37886a48 fffff800`9c62e778 : ffffe001`eaf4df20 00000000`00000000 00000000`00000764 00000000`00000d98 : nt!KiServiceLinkage
    ffffd000`37886a50 fffff800`9c1da7b3 : ffffe001`ea7d4080 00000000`00000000 ffffffff`800011e0 ffffffff`80000b98 : nt!NtSaveKey+0x1ec
    ffffd000`37886b00 00007ffe`7b28c19a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000031`2acde1c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`7b28c19a
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!HvpGetCellPaged+50
    fffff800`9c48ec40 488b04c8        mov     rax,qword ptr [rax+rcx*8]
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  nt!HvpGetCellPaged+50
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  5318053f
    IMAGE_VERSION:  6.3.9600.17041
    BUCKET_ID_FUNC_OFFSET:  50
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!HvpGetCellPaged
    BUCKET_ID:  0x1E_c0000005_R_nt!HvpGetCellPaged
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!hvpgetcellpaged
    FAILURE_ID_HASH:  {f86e9d75-9ce4-8799-af45-48af90ca5aaf}
    Followup: MachineOwner
    ---------

    I advice you to check your memory with Memtest 86+ download from here Memory Diagnostics
    And tutorial from here RAM - Test with Memtest86+ - Windows 7 Help Forums
    Because we first need to know if a system has hardware problems, before we can try to solve any software problems.



    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    Note: first check the support/driver downloadsite of your OEM model or system for the latest windows 8.1 drivers.

    gdrv fffff800`f57e1000 fffff800`f57ea000 Fri Mar 13 04:22:29 2009 (49b9d175) 000105ce gdrv.sys
    Driver Description: Gigabyte Easy Saver - mobo power utility driver
    Driver Update Site: GIGABYTE ???? - ???, ???, ?????, ????, ?????, ???, ????, ??????

    speedfan fffff800`f54e5000 fffff800`f54ef000 Sat Dec 29 21:59:35 2012 (50df59b7) 0000ce4f speedfan.sys
    Driver Description: SpeedFan
    Driver Update Site: Download SpeedFan - Access temperature sensor in your computer

    e1i63x64 fffff800`f46c7000 fffff800`f473b000 Wed Mar 20 08:37:29 2013 (51496739) 0007ff34 e1i63x64.sys
    Driver Description: Intel(R) Gigabit Adapter
    Driver Update Site: Network Connectivity — Drivers and software for Gigabit Intel® Ethernet Adapters

    etocdrv fffff800`f57f0000 fffff800`f57f8000 Tue Apr 16 10:20:56 2013 (516d09e8) 00005f4d etocdrv.sys
    Driver Description: Gigabyte EasyTune driver
    Driver Update Site: GIGABYTE - Support & Downloads - Utility - Motherboard

      My System SpecsSystem Spec

  3. #3


    Posts : 4
    windows 8.1


    Thanks alot.

    I've been updating most of the drivers so far, and I'll run memtest over night to see if there's anything wrong with it.
    I also ran malwarebytes anti-malware on the safe side, and havent really had any issues with BSOD after that, but I'll drop in again after everything is taken care of.
      My System SpecsSystem Spec

  4. #4


    Posts : 4
    windows 8.1


    So I ran the memtest 86 over night and my ram came back clean, I've also been running fine without any issues considering the BSOD.
    But could there be anything else related to the memory errors that I had earlier, or was it simply the drivers that did it?
      My System SpecsSystem Spec

  5. #5


    Posts : 660
    windows 8.1


    It could be outdated drivers, but also software like Gigabyte Easy tune etc.. This utility does all kind of stuff with motherboard settings.

    But lets waits a week to be on the safe side, to see if your BSOD free.
      My System SpecsSystem Spec

  6. #6


    Posts : 4
    windows 8.1


    The only reason why I'm using Easy Tune is because of my watercooling system, and for some reason SpeedFan doesnt work alone to control the fanspeeds desired. But for now I'll keep an eye out if anything happens, feels good to have one day without any bluescreen atleast.
      My System SpecsSystem Spec

Random BSOD errors several times a day.
Related Threads
Hey, this happend a couple of times now and I have honestly no idea when or why it started. The BLUE Screen says KERNEL_SECURITY_CHECK_FAILURE and needing some time to dump files before restart. It occurs, while porgramming, surfing on the internet (no watching videos) or even playing some easy...
Random BSOD at random times in BSOD Crashes and Debugging
Hello, Im new here so bare with me :think: I built my custom pc a year ago now. Since day one iv been experiencing BSOD. At first it happened during or just after the first boot up of that day and was always Memory Management error. Soon after, i upgraded my ram from 4gb to 8 gb. After doing this...
BSOD Random times. in BSOD Crashes and Debugging
I've had numerous BSOD crashes recently. The past two have occurred around 5 hours of pc uptime. At the time i was skyping and watching a youtube video, for both of these times. Help would be appreciated. 56549 Specs: Windows 8.1 64bit Intel 4790k Geforce 660ti 16GB Ram.
BSOD Random Times in BSOD Crashes and Debugging
For the past two days, I have been getting the BSOD randomly. The only error code I get is Kernal_Data_Inpage_Error. Thank you for your help! 56576
BSOD at Random Times for Random Reasons in BSOD Crashes and Debugging
DCP Watchdog, Memory Management, Kernel Security Failure and several others at random times - especially during large file transfers between drives. I did a memory test and it stated there was an issue but I removed the culprit and the random BSOD continues. Thanks for your help
BSOD random times in BSOD Crashes and Debugging
Hi, I have getting bsod randomly times while using computer, no matter what i do. On win7 i haven't any bsod, since i install win8 problems become. SF_Diagnostic_Tool file in attachment. I hope that someone can help. Sorry for my bad english. 41936
BSOD at random times in BSOD Crashes and Debugging
I don't know what cause the problem but I would like someone to assist on my problem. Thanks. :)
Eight Forums Android App Eight Forums IOS App Follow us on Facebook