Windows 10: BSOD - PROCESS_NAME: MemCompression

Discus and support BSOD - PROCESS_NAME: MemCompression in Windows 10 BSOD Crashes and Debugging to solve the problem; i don't understand the technical things here : Code: mini dump... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by eaglech, Feb 9, 2018.

  1. eaglech Win User

    BSOD - PROCESS_NAME: MemCompression


    i don't understand the technical things here :
    Code: mini dump 021018-30468-01.zip******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 000000000000098d, physical page number Arg3: 0000000014608ee0, zero Arg4: ffffbd816d1f8000, zero Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: PAGE_NOT_ZERO CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: MemCompression CURRENT_IRQL: 0 STACK_COMMAND: kb SYMBOL_NAME: REGION_PAGED_OUT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_PAGE_NOT_ZERO_REGION_PAGED_OUT BUCKET_ID: X64_PAGE_NOT_ZERO_REGION_PAGED_OUT Followup: MachineOwner The 2nd time BSOD result : ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000683, physical page number Arg3: 0000000013018db0, zero Arg4: ffffb601b659b000, zero Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: PAGE_NOT_ZERO DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: MemCompression CURRENT_IRQL: 0 STACK_COMMAND: kb SYMBOL_NAME: REGION_PAGED_OUT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_PAGE_NOT_ZERO_REGION_PAGED_OUT BUCKET_ID: X64_PAGE_NOT_ZERO_REGION_PAGED_OUT Followup: MachineOwner[/quote]

    :)
     
    eaglech, Feb 9, 2018
    #1
  2. mscommrd Win User

    Multiple BSODs since Windows 10 Creators Update

    I'm adding this from the debug analysis, in case it's helpful,

    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: MemCompression
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    EXCEPTION_CODE_STR: c0000006
    EXCEPTION_PARAMETER3: 00000000c0000185
    IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    EXCEPTION_STR: 0xc0000006_c0000185

    BUGCHECK_STR: 0x154_c0000006_c0000185

    Thanks,

    Ross
     
    mscommrd, Feb 9, 2018
    #2
  3. MST3Claye Win User
    BSoD Unexpected_Store_Exception - MemCompression - nt_wrong_symbols.sys problem

    Recently I've been having a BSoD that will say Unespected_Store_Exception... BlueScreenReview says MemCompression ntoskrnel.sys... WhoCrashed points to UNEXPECTED_STORE_EXCEPTION - nt_wrong_symbols.sys ... I just tried a Windows 10 reinstall, and I installed
    current nVidia GeForce Experience drivers.. I don't know what else to do.. Here's the dump file. This has happened when I play the PC game Rust and the game Player Unknown's Battleground..

    http://www.filefactory.com/file/p3x0rtnbwux/010818-24437-01.dmp
     
    MST3Claye, Feb 9, 2018
    #3
  4. axe0 New Member

    BSOD - PROCESS_NAME: MemCompression

    0x12B is a hardware related error.
    Someone besides the owner tried to access a page which contained unexpected data.
    Code: FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 000000000000098d, physical page number Arg3: 0000000014608ee0, zero Arg4: ffffbd816d1f8000, zero 1: kd> !error ffffffffc00002c4 Error code: (NTSTATUS) 0xc00002c4 (3221226180) - The system file %1 has become corrupt and has been replaced. 1: kd> knL # Child-SP RetAddr Call Site 00 ffffbd81`6a0b5348 fffff801`1b64a877 nt!KeBugCheckEx 01 ffffbd81`6a0b5350 fffff801`1b5b05b9 nt!ST_STORE<SM_TRAITS>::StDmPageError+0x117 02 ffffbd81`6a0b53a0 fffff801`1b4b87bf nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xf7dc5 03 ffffbd81`6a0b5480 fffff801`1b4b81ab nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b 04 ffffbd81`6a0b54d0 fffff801`1b4b7fce nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x183 05 ffffbd81`6a0b5570 fffff801`1b4b9bef nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xea 06 ffffbd81`6a0b5630 fffff801`1b52ba71 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x6f 07 ffffbd81`6a0b5680 fffff801`1b4a5d9b nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21 08 ffffbd81`6a0b56b0 fffff801`1b4e01f5 nt!KeExpandKernelStackAndCalloutInternal+0x8b 09 ffffbd81`6a0b5700 fffff801`1b4d6892 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad 0a ffffbd81`6a0b57d0 fffff801`1b4d60f2 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ae 0b ffffbd81`6a0b5820 fffff801`1b4baa6a nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce 0c ffffbd81`6a0b58a0 fffff801`1b51c18a nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16a 0d ffffbd81`6a0b5910 fffff801`1b485439 nt!SmPageRead+0x2e 0e ffffbd81`6a0b5960 fffff801`1b484e00 nt!MiIssueHardFaultIo+0x11d 0f ffffbd81`6a0b59b0 fffff801`1b470916 nt!MiIssueHardFault+0x190 10 ffffbd81`6a0b5a50 fffff801`1b577872 nt!MmAccessFault+0xc96 11 ffffbd81`6a0b5c40 00007ffa`e4a23b12 nt!KiPageFault+0x132 12 00000042`39ffd0c0 00000000`00000000 0x00007ffa`e4a23b12[/quote] From what it looks like, it is recommended to run SFC and chkdsk.
    In an admin command, copy & paste the following
    Code: sfc /scannow&chkdsk /r[/quote] This could take some time, with chkdsk you'll need to reboot the system, press Y when asked to plan chkdsk for reboot.
     
    axe0, Feb 9, 2018
    #4
  5. eaglech Win User
    "Someone besides the owner tried to access a page which contained unexpected data."

    SOMEONE hacking to my system OR "someone" here refers to other issue
    i will try to do this "
    "sfc /scannow&chkdsk /r"
     
    eaglech, Feb 9, 2018
    #5
  6. axe0 New Member
    'Someone else' as in a driver that didn't put the data there.
     
    axe0, Feb 9, 2018
    #6
  7. axe0 New Member
    Hi eaglech,

    How is it going?
     
    axe0, Apr 5, 2018
    #7
Thema:

BSOD - PROCESS_NAME: MemCompression

Loading...
  1. BSOD - PROCESS_NAME: MemCompression - Similar Threads - BSOD PROCESS_NAME MemCompression

  2. BSOD

    in Windows 10 BSOD Crashes and Debugging
    BSOD: I had just recently finished building my pc and was using it. It was all fine. Then I got the BSOD stop code: irql_not_less_or_equal Apparently it happens to new pc's often and maybe a driver problem. So I wanted to update my drivers after I restarted my pc. But when...
  3. bsod

    in Windows 10 Customization
    bsod: can this please be flagged to a admin been nearly 3 weeks since last reply https://answers.microsoft.com/en-us/windows/forum/all/bsod/25c9e451-b714-47a8-885c-10608bae95f6 this is not good customer service...
  4. BSOD

    in Windows 10 Ask Insider
    BSOD: When my PC is under load like playing games, the games either crash, freeze or my PC goes to the BSOD. The error codes I have seen are Stop Code Memory Management, Critical Structure Corruption and Page Fault In Nonpaged Area. Nothing in the PC is overclocked. I tried to...
  5. BSOD

    in Windows 10 BSOD Crashes and Debugging
    BSOD: Got a BSOD but dont know how to read and find the source of the problems ******************************************************************************* * * * Bugcheck Analysis...
  6. BSoD

    in Windows 10 BSOD Crashes and Debugging
    BSoD: Hi, I have been getting BSoD errors of varying types for a while now, It has most recently been happening while running Elgato's Game Capture HD Software PC Specs: GPU: NVIDIA GeForce GTX 980Ti CPU: AMD Ryzen 7 3700X MOBO: ROG STRIX X570-F Gaming RAM: Corsair...
  7. MemCompression accesses internet?!

    in Windows 10 Ask Insider
    MemCompression accesses internet?!: Just learned w10 has memory compression because my firewall alerted me this function tried to access the internet. Anyone know if the compressor is supposed to do that or is that something else mascerading? Trying to open the responsible application didnt work since i only...
  8. Win32k_callout_watchdog_livedump BSOD or not BSOD?

    in Windows 10 Ask Insider
    Win32k_callout_watchdog_livedump BSOD or not BSOD?: [ATTACH] Hello. Hello. I think i was get bsod but not sure. System was hanged and lags after crash in game to desktop. After 1 minute i get system reboot ( like power cut ) and logged to system. Screen from event log: 20:17:30 reported time of unexpected reboot. There...
  9. Win32k_callout_watchdog_livedump BSOD or not BSOD?

    in Windows 10 BSOD Crashes and Debugging
    Win32k_callout_watchdog_livedump BSOD or not BSOD?: Hello. My question is. I get crash in game when i click exit to desktop. Black screen for 1 minute,nothing responding. Then desktop appeared ,screen appeared and after 1 minute pc just reset itself. I open eventog and there was only about KERNEL-POWER 41,but not bugcheck. So...
  10. BSOD's, BSOD's, BSOD's....

    in Windows 10 BSOD Crashes and Debugging
    BSOD's, BSOD's, BSOD's....: Hello you people out there, Here I am again, this time with recurring BSOD-problems on a different laptop, here in our cottage. I include a zip-file, mainly filled with .MDP's from our last visit, about 2 weeks ago....

Users found this page by searching for:

  1. PROCESS_NAME: MemCompression

    ,
  2. windows debug memcompression

    ,
  3. win8_driver_fault MemCompression

    ,
  4. bugcheck_str: 0x154process_name: memcompression