WIN8_DRIVER_FAULT and page corruption sometimes after sleep


  1. Posts : 37
    win10
       #1

    WIN8_DRIVER_FAULT and page corruption sometimes after sleep


    sometimes after returning from sleep ill get bsod WIN8_DRIVER_FAULT. Ive attached the latest and some other dumps.

    Does not happen everytime,- so hard to find out what is the problem

    example of some ocr debugs:

    Code:
    Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.Show DivPrimary Analysis
    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 17763 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`36a0b000 PsLoadedModuleList = 0xfffff800`36e2aa10
    Debug session time: Tue Oct  9 09:59:37.225 2018 (UTC - 4:00)
    System Uptime: 1 days 3:54:54.891
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffde8c9af3b028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000801136, Low order 32-bits of the MCi_STATUS value.
    
    
    Debugging Details:
    ------------------
    
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  HxTsr.exe
    
    
    CURRENT_IRQL:  f
    
    
    BAD_PAGES_DETECTED: 22635
    
    
    STACK_TEXT:  
    ffffac80`21ea5a88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: Unknown_Module
    
    
    IMAGE_NAME:  Unknown_Image
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    BUCKET_ID:  PAGE_NOT_ZERO
    
    
    Followup: MachineOwner
    ---------
    
    
     *** Memory manager detected 140853 instance(s) of page corruption, target is likely to have memory corruption.



    Code:
    Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.Show DivPrimary Analysis
    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 17763 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`6d80b000 PsLoadedModuleList = 0xfffff800`6dc2aa10
    Debug session time: Thu Oct 11 09:59:32.458 2018 (UTC - 4:00)
    System Uptime: 0 days 23:49:02.095
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffff940a9df30028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000801136, Low order 32-bits of the MCi_STATUS value.
    
    
    Debugging Details:
    ------------------
    
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  ekrn.exe
    
    
    CURRENT_IRQL:  f
    
    
    BAD_PAGES_DETECTED: 213d2
    
    
    STACK_TEXT:  
    ffffe780`d8ea5a88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: Unknown_Module
    
    
    IMAGE_NAME:  Unknown_Image
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    BUCKET_ID:  PAGE_NOT_ZERO
    
    
    Followup: MachineOwner
    ---------
    
    
     *** Memory manager detected 136146 instance(s) of page corruption, target is likely to have memory
      My Computer

  2. swarfega's Avatar
    Posts : 7,085
    Windows 10 Pro 64-bit
       #2

    For what device is this for. It seems to be a Windows 8 driver.
      My Computers


  3. Posts : 37
    win10
    Thread Starter
       #3

    im using a nuc NUC7i3BN, the common thing is WIN8_DRIVER_FAULT and whea_uncorrectable_error.
    Im really at a loss what is causing it, will run another memtest later, but last time it did not find anything.

    found an older minidump with same thing

    Code:
    Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.Primary AnalysisCrash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR  Unique Expertise, Guaranteed Results)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 17763 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff807`22eaa000 PsLoadedModuleList = 0xfffff807`232c9a10
    Debug session time: Thu Oct  4 23:27:31.357 2018 (UTC - 4:00)
    System Uptime: 0 days 14:52:11.631
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffb583c08e8880, Physical Device Object of the stack
    Arg3: fffffe0feb62f7d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: ffffb583df793de0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    DRVPOWERSTATE_SUBCODE:  3
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAULTING_MODULE: fffff80722e13000 hal
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    BAD_PAGES_DETECTED: 296df
    
    STACK_TEXT:  
    fffffe0f`eb62f798 fffff807`2317c546 : 00000000`0000009f 00000000`00000003 ffffb583`c08e8880 fffffe0f`eb62f7d0 : nt!KeBugCheckEx
    fffffe0f`eb62f7a0 fffff807`2317c452 : ffffb583`d26f2e20 00000000`00000008 ffffb583`d26f2e98 fffff807`230dab69 : nt!PopIrpWatchdogBugcheck+0xea
    fffffe0f`eb62f810 fffff807`22f0d729 : ffffb583`d26f2e58 00000000`000000ff fffffe0f`eb62fa18 00000000`00000008 : nt!PopIrpWatchdog+0x22
    fffffe0f`eb62f860 fffff807`22f0c6e7 : 00000000`00000004 00000000`00989680 ffff9301`68a10100 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
    fffffe0f`eb62f950 fffff807`2305e94a : ffffffff`00000000 ffff9301`68a00180 00000000`00000000 ffff9301`68a10100 : nt!KiRetireDpcList+0x4a7
    fffffe0f`eb62fb60 00000000`00000000 : fffffe0f`eb630000 fffffe0f`eb629000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  PAGE_NOT_ZERO
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    BUCKET_ID:  PAGE_NOT_ZERO
    
    Followup: MachineOwner
    ---------
    
    
     *** Memory manager detected 169695 instance(s) of page corruption, target is likely to have memory corruption.
      My Computer


 

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

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




Windows 10 Forums