1. #1

    BSOD Memory Management

    Hi all. I had this happen today for the first time. I researched this some and ran sfc/scannow. It found corrupted files that it was unable to repair. I ran a memory check utility and it found no problems. I have run the file collection app and you will find it here. My system is a Dell Inspiron 20 Model 3052, Windows 10 64 Bit, Intel Celeron CPU N3150@1.60GHz, 4GB ram SysnativeFileCollectionApp.zip


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Re: BSOD Memory Management

    I wanted to add that I had a recent episode while online. I forget what they call it but it was a warning that my system was infected and that I needed to call this number or my files would be locked. I ran task manger and was able to get out of it. I use Windows Defender and it alerted me to some infections. I also ran Malwarebytes free and it found a number of serious infections. I had to run it twice to get rid of them all. Since all of that happened my system seems to run slow. Everything seems slow. I have run additional scans and find nothing.

  3. #3
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    673
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD Memory Management

    Hi mike56,

    Please create a new thread at our Security Arena and read Malware Removal Posting Instructions

    If SFC keeps finding problems it cannot fix, please create a new thread at the Windows Update section and read Windows Update Forum Posting Instructions

    We need your system to be clean of both malware and Windows corruption, both can cause issues affecting BSODs.

  4. #4

    Re: BSOD Memory Management

    Okay. Thanks. Will do.

  5. #5

    Re: BSOD Memory Management

    Hi Mike56,

    The crash dump you posted indicates that the page read from the page file did not match the original page written to disk. This is likely due to pagefile/filesystem corruption which is often caused by sudden power failures, storage drivers misbehaving, or hardware failing.

    From the call stack, read bottom to top, there is a page fault, which means the system had to go to the page file to bring data back into RAM. After this, it goes through the storage stack, and reads the (compressed) data. Finally the system decompresses the data, and then compares the data's hash to the hash of the data before it was sent to the page file. Because they did not match, we know that it is corrupted, and therefore the system had to crash, which is why we see nt!KeBugCheckEx being called.

    Code:
     # Child-SP          RetAddr           Call Site
    00 ffffda01`458b4ce8 fffff800`a9a5586b nt!KeBugCheckEx
    01 ffffda01`458b4cf0 fffff800`a9928456 nt!MiValidatePagefilePageHash+0xa343b
    02 ffffda01`458b4dc0 fffff800`a9929e68 nt!MiWaitForInPageComplete+0x296
    03 ffffda01`458b4ec0 fffff800`a9915936 nt!MiIssueHardFault+0x1d8
    04 ffffda01`458b4fa0 fffff800`a99fdd72 nt!MmAccessFault+0xc96
    05 ffffda01`458b5190 fffff800`a9962bb0 nt!KiPageFault+0x132
    06 ffffda01`458b5320 fffff800`a99621b0 nt!RtlDecompressBufferXpressLz+0x60
    07 ffffda01`458b5350 fffff800`a9961e8d nt!RtlDecompressBufferEx+0x60
    08 ffffda01`458b53a0 fffff800`a9961cff nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x159
    09 ffffda01`458b5480 fffff800`a99616eb nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b
    0a ffffda01`458b54d0 fffff800`a99614bc nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x183
    0b ffffda01`458b5570 fffff800`a996312f nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x98
    0c ffffda01`458b5630 fffff800`a99b1fb1 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x6f
    0d ffffda01`458b5680 fffff800`a989e20b nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
    0e ffffda01`458b56b0 fffff800`a9959ad5 nt!KeExpandKernelStackAndCalloutInternal+0x8b
    0f ffffda01`458b5700 fffff800`a9950172 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
    10 ffffda01`458b57d0 fffff800`a994f9d2 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ae
    11 ffffda01`458b5820 fffff800`a9963faa nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce
    12 ffffda01`458b58a0 fffff800`a99a071a nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16a
    13 ffffda01`458b5910 fffff800`a992a459 nt!SmPageRead+0x2e
    14 ffffda01`458b5960 fffff800`a9929e20 nt!MiIssueHardFaultIo+0x11d
    15 ffffda01`458b59b0 fffff800`a9915936 nt!MiIssueHardFault+0x190
    16 ffffda01`458b5a50 fffff800`a99fdd72 nt!MmAccessFault+0xc96
    17 ffffda01`458b5c40 00007ffa`0f27134b nt!KiPageFault+0x132
    18 00000007`ab27e9e0 00000000`00000000 0x00007ffa`0f27134b

    The system event log is also showing some possible issues with your C: drive.

    Code:
    Event[2280]:  Log Name: System
      Source: Disk
      Date: 2017-09-13T21:17:00.793
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-I87918H
      Description: 
    The IO operation at logical block address 0xcc14a0 for Disk 1 (PDO name: \Device\000000a0) was retried.
    Code:
    Event[2281]:
      Log Name: System
      Source: Disk
      Date: 2017-09-13T21:17:00.793
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-I87918H
      Description: 
    An error was detected on device \Device\Harddisk1\DR18 during a paging operation.

    Have you experienced sudden and unexpected reboots of your system? This event is a bit worrying.

    Code:
    Event[8962]:
      Log Name: System
      Source: Microsoft-Windows-UserModePowerService
      Date: 2017-06-24T11:29:03.720
      Event ID: 22
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-I87918H
      Description: 
    Reapply power settings upon completion of the provisioning engine's turn 5

    Given that you are likely not using SCSI multipath in your laptop, this sounds like something is messed up with GPT on your disk(s).
    Code:
    Event[1287]:
      Log Name: System
      Source: Disk
      Date: 2017-09-27T14:50:02.081
      Event ID: 158
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-I87918H
      Description: 
    Disk 2 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.
    I would suggest running from an administrative prompt:

    Code:
    chkdsk.exe /R /X C:
    Press "Y" to schedule it on the next reboot. Then reboot your computer and let it run, this will attempt to find and repair any damage to your filesystem.

    After that, please post the resulting event log from chkdsk. Here is a guide on doing that.

    Then run HDTune, and run an error scan on your primary disk. Post a screenshot when that is finished.

  6. #6

    Re: BSOD Memory Management

    Hi Spectrum. I have not had any issues with the computer other than being slow IMO. That was the first blue screen and indication of a problem that I've had. I ran the chkdsk and the other things you suggested. HD Tune appears to show the hard drive okay. Should I still go to the Security Arena and post a thread?
    HDTune2.txtHDTune.txtSALog.txtAddition.txtFRST.txtchkdsk.txt

  7. #7
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    673
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB &amp; 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24&quot; Liyama ProLite XB2483HSU-B2 &amp; 24&quot; Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD Memory Management

    You should go to the Security Arena, it is not known what may still be on your system that can affect stability and performance.

    After you're declared clean, run a SFC scan. If SFC reports unrepaired errors, go to the Windows Update section.

  8. #8

    Re: BSOD Memory Management

    Okay. Will do.

  9. #9

    Re: BSOD Memory Management

    Well, I have done everything I've been requested to do. The computer seems to run better but SFC still reports corrupted files it can't repair. I posted in the update section two days ago. Haven't heard a thing.

  10. #10
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    673
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB &amp; 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24&quot; Liyama ProLite XB2483HSU-B2 &amp; 24&quot; Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD Memory Management

    It can take some days for them to get to your thread, there used to be a thread where you could let them know you're waiting for help after 3 days.

    If you don't get a response after 4-5 days, contact 1 of the analysts.

  11. #11

    Re: BSOD Memory Management

    Okay. Thanks!

Similar Threads

  1. BSOD Possibly Related to Memory
    By NachoFoot in forum BSOD, Crashes, Kernel Debugging
    Replies: 6
    Last Post: 01-26-2017, 12:02 AM
  2. Replies: 11
    Last Post: 08-04-2016, 05:36 PM
  3. Memory management, kernal power, system service exception BSOD
    By k12 in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 07-03-2015, 08:02 PM
  4. BSOD Memory Management Error - Windows 7 x64
    By holypepsi in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 08-12-2014, 03:42 AM
  5. BSOD Memory Management/irql_not_less_or_equal
    By DoDDy in forum BSOD, Crashes, Kernel Debugging
    Replies: 5
    Last Post: 04-05-2014, 09:24 AM

Log in

Log in