Ошибка amdpsp sys windows 7

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

I have run the dump files and you can see the full reports here:

Dump1: https://pste.eu/p/fMwV.html
Dump2: https://pste.eu/p/Mxgm.html

Summary of findings:

1: BugCheck EF —— CRITICAL_PROCESS_DIED
Probably caused by : services.exe

2: BugCheck 1000007E —— SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+51 )

Bugcheck Description:
CRITICAL_PROCESS_DIED — please see report for details
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — please see report for details

Some things to consider:

• Due to the bugcheck, just to be safe, I would Run SFC/ Scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated command prompt.
• In addition to all this, i can see you are using mixed RAM modules, unfortunately this could easily be your instability, have you added a module recently? — Did you install them in the correct slots as per your MB manual?
• There are lots of potential out of date drivers on your system however I would sooner look at my previous points above failing that- my attention in particular is being drawn to:

• I would absolutely ensure that your chipset and MB drivers are up to date via your motherboard manufacturers website as a first port of call.
• I would also check if you have a BIOS update available as your BIOS is from 2018.

DBUtil_2_3.Sys — Dell utility. I am not sure which one or what purpose of driver is. It might be okay, just seems old

Have you run Dell update here? https://www.dell.com/support/home/au/en/aubsd1/product-support/product/inspiron-5675-gaming-desktop/drivers

Try downloading newer WIFI (+ Bluetooth) drivers — https://support.killernetworking.com/download/killer-drivers-installation-64bit/

one was caused by services.exe crashing, another by cmd.exe crashing.

see if this helps
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

I did a sfc /scannow and also repair windows image and both had no problems. I ran Dell update on the website you gave me, but it didn’t find any updates so I don’t know if its reliable or if my pc is truly up to date. Also downloaded the newer WIFI (+Bluetooth) driver you sent so hope that helps. Is there anything else I could do or download to make sure everything is running as it should?

I have run the dump files and you can see the full reports here:

Dump1: https://pste.eu/p/fMwV.html
Dump2: https://pste.eu/p/Mxgm.html

Summary of findings:

Some things to consider:

• Due to the bugcheck, just to be safe, I would Run SFC/ Scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated command prompt.
• In addition to all this, i can see you are using mixed RAM modules, unfortunately this could easily be your instability, have you added a module recently? — Did you install them in the correct slots as per your MB manual?
• There are lots of potential out of date drivers on your system however I would sooner look at my previous points above failing that- my attention in particular is being drawn to:

DBUtil_2_3.Sys	03/11/2009	Unknown	Unknown Driver
RTKVHD64.sys	16/05/2017	Realtek	Realtek HD Audio Driver
rt640x64.sys	27/06/2017	Realtek	Realtek Audio Driver
amdpsp.sys	27/10/2017	AMD	AMD Chipset Driver
AMDRyzenMasterDriver.sys	14/11/2017	AMD	Ryzen Master Driver
AMDPCIDev.sys	12/04/2018	AMD	AMD Ryzen OC Utility
RzDev_021e.sys	23/04/2018	Razer	Razer Driver
RzDev_005c.sys	23/04/2018	Razer	Razer Driver
btfilter.sys	17/05/2018	Qualcomm	Atheros Bluetooth Driver
Qcamain10x64.sys	23/08/2018	Qualcomm	Qualcomm Atheros Wireless LAN device driver

• I would absolutely ensure that your chipset and MB drivers are up to date via your motherboard manufacturers website as a first port of call.
• I would also check if you have a BIOS update available as your BIOS is from 2018.

Thanks for the info and reply. I did both command prompts and no problems. I’m not sure about the ram modules since this is a prebuilt pc and I have not added anything to it yet. The potential out of date drivers I have no clue about, I checked on the Dell website and it said my pc was up to date so I don’t know.

I don’t know what this is MINDFRAME.sys — I can only find it on 1 website that I can’t login to.. which doesn’t help
The BSOD caused by a driver, we just haven’t identified which as its not showing itself in the text.

tried running chkdsk on the drives?
open command prompt (Admin)
if you have a hdd, type chkdsk c: /f /r and press enter
If you have an ssd, type chkdsk c: /f and press enter
(difference between 2 is /r repairs sectors. ssd don’t have sectors)
2 paragraphs will pop up on screen
type Y and press enter to agree to run at startup
restart PC and let the scans run

I don’t know what this is MINDFRAME.sys — I can only find it on 1 website that I can’t login to.. which doesn’t help
The BSOD caused by a driver, we just haven’t identified which as its not showing itself in the text.

tried running chkdsk on the drives?
open command prompt (Admin)
if you have a hdd, type chkdsk c: /f /r and press enter
If you have an ssd, type chkdsk c: /f and press enter
(difference between 2 is /r repairs sectors. ssd don’t have sectors)
2 paragraphs will pop up on screen
type Y and press enter to agree to run at startup
restart PC and let the scans run

I had done some chkdsk in the past, but didn’t do the repairs sectors one so I did it and it seemed to be doing fine, but just now got another bsod, here’s the dmp file: https://drive.google.com/open?id=1SzfwFOlVxF4H1r9_31NFKzFESd9Hb-Si

thank you for the constant help btw

I have run the dump file(s) and you can see the full report(s) here: https://pste.eu/p/RnaY.html

Summary of findings:

MEMORY_MANAGEMENT
«Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

• Confirm that hardware is compatible with your system.
• View the third party modules of the report to view which drivers may be misbehaving.»

updating wifi didn’t change anything, the installed drivers now have same dates as a dump done 6 days ago

error has something to do with compressed memory.
only driver names mentioned are all parts of windows
filtmgr — Microsoft Filesystem Filter Manager
npfs — named pipe file system

Some light reading for PC — https://www.fireeye.com/content/dam/fireeye-www/blog/pdfs/finding-evil-in-windows-10-compressed-memory-wp.pdf

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

The 0x1A

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 0000000000173800
Arg3: 0000000067f8404d
Arg4: 00000000adba175e


ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff8601`bbd615a8 fffff804`5c863b96 nt!KeBugCheckEx
01 ffff8601`bbd615b0 fffff804`5c68e112 nt!MiValidatePagefilePageHash+0x10157a
02 ffff8601`bbd61690 fffff804`5c68d65d nt!MiWaitForInPageComplete+0x472
03 ffff8601`bbd617a0 fffff804`5c67317b nt!MiIssueHardFault+0x1ad
04 ffff8601`bbd618a0 fffff804`5c7cf120 nt!MmAccessFault+0x40b
05 ffff8601`bbd61a40 fffff804`5c75e140 nt!KiPageFault+0x360
06 ffff8601`bbd61bd8 fffff804`5c65d1a0 nt!RtlDecompressBufferXpressLz+0x50
07 ffff8601`bbd61bf0 fffff804`5c75fec9 nt!RtlDecompressBufferEx+0x60
08 ffff8601`bbd61c40 fffff804`5c75fd54 nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x155
09 ffff8601`bbd61d20 fffff804`5c75fbd2 nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
0a ffff8601`bbd61d70 fffff804`5c75f9fb nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
0b ffff8601`bbd61e10 fffff804`5c75f841 nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
0c ffff8601`bbd61ec0 fffff804`5c75f751 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
0d ffff8601`bbd61f40 fffff804`5c669ff8 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
0e ffff8601`bbd61f70 fffff804`5c762cb1 nt!KeExpandKernelStackAndCalloutInternal+0x78
0f ffff8601`bbd61fe0 fffff804`5c74b931 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
10 ffff8601`bbd620b0 fffff804`5c74b517 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
11 ffff8601`bbd62100 fffff804`5c761fc3 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
12 ffff8601`bbd62190 fffff804`5c76369f nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
13 ffff8601`bbd62200 fffff804`5c68e23b nt!SmPageRead+0x33
14 ffff8601`bbd62250 fffff804`5c68d939 nt!MiIssueHardFaultIo+0x117
15 ffff8601`bbd622a0 fffff804`5c67317b nt!MiIssueHardFault+0x489
16 ffff8601`bbd62350 fffff804`5c7cf120 nt!MmAccessFault+0x40b
17 ffff8601`bbd624f0 fffff80f`caa3ee9f nt!KiPageFault+0x360
18 ffff8601`bbd62680 fffff80f`caa3ed77 Npfs!NpCommonCleanup+0xef
19 ffff8601`bbd62730 fffff804`5c631f39 Npfs!NpFsdCleanup+0x27
1a ffff8601`bbd62760 fffff804`5eee55d9 nt!IofCallDriver+0x59
1b ffff8601`bbd627a0 fffff804`5eee3f16 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x159
1c ffff8601`bbd62820 fffff804`5c631f39 FLTMGR!FltpDispatch+0xb6
1d ffff8601`bbd62880 fffff804`5cbe3018 nt!IofCallDriver+0x59
1e ffff8601`bbd628c0 fffff804`5cbeb168 nt!IopCloseFile+0x188
1f ffff8601`bbd62950 fffff804`5cbf04ae nt!ObCloseHandleTableEntry+0x278
20 ffff8601`bbd62a90 fffff804`5c7d2915 nt!NtClose+0xde
21 ffff8601`bbd62b00 00007ff9`9839c2b4 nt!KiSystemServiceCopyEnd+0x25
22 00000074`0acff7f8 00000000`00000000 0x00007ff9`9839c2b4

2: kd> .trap 0xffff8601bbd624f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb9898280bb28 rbx=0000000000000000 rcx=ffffb989aa3bcc98
rdx=ffffb9897dfc7ca8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80fcaa3ee9f rsp=ffff8601bbd62680 rbp=ffff8601bbd626e8
 r8=ffff8601bbd626c0  r9=ffff8601bbd626b0 r10=fffff80fcaa3ed50
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Npfs!NpCommonCleanup+0xef:
fffff80f`caa3ee9f 483902          cmp     qword ptr [rdx],rax ds:ffffb989`7dfc7ca8=0000000800000009

2: kd> !pte ffffb9897dfc7ca8 
                                           VA ffffb9897dfc7ca8
PXE at FFFF8EC763B1DB98    PPE at FFFF8EC763B73128    PDE at FFFF8EC76E625F78    PTE at FFFF8EDCC4BEFE38
contains 0A00000315CBF863  contains 0A00000315CC0863  contains 0A0000014391B863  contains 0000000274561880
pfn 315cbf    ---DA--KWEV  pfn 315cc0    ---DA--KWEV  pfn 14391b    ---DA--KWEV  not valid
                                                                                  Transition: 274561
                                                                                  Protect: 4 - ReadWrite

0xEF is typically a RAM or drive issue, considering the 0x1A I’d bet the cause is the drive.

what brand are the drives? some brands like WD & Seagate have their own testing software.

Try running HD Sentinel trial as a 2nd opinion on HD Tune
Look on disk menu and run any tests you can — https://www.hdsentinel.com/hard_disk_sentinel_trial.php

The brand for the ssd is SK hynix and for the hdd is Toshiba. I tried running HD Sentinel, but most tests were not available in the trial. Is there any other program I should get for the drivers? Also should I still run memtest or figure out if its a problem with drivers?

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

Thank you for the insight, do you have any recommendations for any good drive I can buy?

Thank you for the insight, do you have any recommendations for any good drive I can buy?

I would get a Samsung EVO 500gb drive (any smaller will likely need to be replaced too soon although a 250 is big enough for win 10 currently). I have a 4 year old Evo and its still almost brand new according to HD Sentinel

I assume axe can tell if the drive was an ssd or not? since you have both and I gave you chkdsk for both?

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

HDDs are another debate in themselves, some would argue that Seagates latest figures are showing bigger failure rates, but there are still plenty going strong.

Can’t tell if it’s SSD or HDD from CHKDSK logs. What size and type are you looking for @javster22 ?

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

Nearly? Which wouldn’t be a good purchase?

I haven’t looked into SSDs and HDDs in months, but am looking myself for a new SSD (eyeing the 970 evo) and HDD.

Nearly? Which wouldn’t be a good purchase?

I haven’t looked into SSDs and HDDs in months, but am looking myself for a new SSD (eyeing the 970 evo) and HDD.

Honestly, I don’t know a single BAD one, but I know plenty that are better value for money from my perspective.
If you want an M.2 SSD then the Intel 660p has frankly stormed the market on that front, half the price of a Samsung equivalent.

Some 2.5″ SSDs that are still excellent are the Crucial MX series too, sometimes the value is too good to turn down.

Depends on what format you’re looking at and your usage, many people jump to NVMe when there is no real benefit for their usage.

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

Just saw this thread and was going to post the same. Any time you have Windows wanting to check the drive it’s installed on for errors every time it starts, 99.9% of the time it means the drive is going south (and it’s time to back up) no matter what little programs like HD Tune tell you.

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

HDDs are another debate in themselves, some would argue that Seagates latest figures are showing bigger failure rates, but there are still plenty going strong.

Can’t tell if it’s SSD or HDD from CHKDSK logs. What size and type are you looking for @javster22 ?

Well I’m not sure if I should replace both the SSD and HDD what do you think? Also not looking for anything specific just whatever good one you guys recommend that’s not too expensive.

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

I have run the dump files and you can see the full reports here:

Dump1: https://pste.eu/p/fMwV.html
Dump2: https://pste.eu/p/Mxgm.html

Summary of findings:

1: BugCheck EF —— CRITICAL_PROCESS_DIED
Probably caused by : services.exe

2: BugCheck 1000007E —— SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+51 )

Bugcheck Description:
CRITICAL_PROCESS_DIED — please see report for details
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — please see report for details

Some things to consider:

• Due to the bugcheck, just to be safe, I would Run SFC/ Scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated command prompt.
• In addition to all this, i can see you are using mixed RAM modules, unfortunately this could easily be your instability, have you added a module recently? — Did you install them in the correct slots as per your MB manual?
• There are lots of potential out of date drivers on your system however I would sooner look at my previous points above failing that- my attention in particular is being drawn to:

• I would absolutely ensure that your chipset and MB drivers are up to date via your motherboard manufacturers website as a first port of call.
• I would also check if you have a BIOS update available as your BIOS is from 2018.

DBUtil_2_3.Sys — Dell utility. I am not sure which one or what purpose of driver is. It might be okay, just seems old

Have you run Dell update here? https://www.dell.com/support/home/au/en/aubsd1/product-support/product/inspiron-5675-gaming-desktop/drivers

Try downloading newer WIFI (+ Bluetooth) drivers — https://support.killernetworking.com/download/killer-drivers-installation-64bit/

one was caused by services.exe crashing, another by cmd.exe crashing.

see if this helps
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

I did a sfc /scannow and also repair windows image and both had no problems. I ran Dell update on the website you gave me, but it didn’t find any updates so I don’t know if its reliable or if my pc is truly up to date. Also downloaded the newer WIFI (+Bluetooth) driver you sent so hope that helps. Is there anything else I could do or download to make sure everything is running as it should?

I have run the dump files and you can see the full reports here:

Dump1: https://pste.eu/p/fMwV.html
Dump2: https://pste.eu/p/Mxgm.html

Summary of findings:

Some things to consider:

• Due to the bugcheck, just to be safe, I would Run SFC/ Scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated command prompt.
• In addition to all this, i can see you are using mixed RAM modules, unfortunately this could easily be your instability, have you added a module recently? — Did you install them in the correct slots as per your MB manual?
• There are lots of potential out of date drivers on your system however I would sooner look at my previous points above failing that- my attention in particular is being drawn to:

DBUtil_2_3.Sys	03/11/2009	Unknown	Unknown Driver
RTKVHD64.sys	16/05/2017	Realtek	Realtek HD Audio Driver
rt640x64.sys	27/06/2017	Realtek	Realtek Audio Driver
amdpsp.sys	27/10/2017	AMD	AMD Chipset Driver
AMDRyzenMasterDriver.sys	14/11/2017	AMD	Ryzen Master Driver
AMDPCIDev.sys	12/04/2018	AMD	AMD Ryzen OC Utility
RzDev_021e.sys	23/04/2018	Razer	Razer Driver
RzDev_005c.sys	23/04/2018	Razer	Razer Driver
btfilter.sys	17/05/2018	Qualcomm	Atheros Bluetooth Driver
Qcamain10x64.sys	23/08/2018	Qualcomm	Qualcomm Atheros Wireless LAN device driver

• I would absolutely ensure that your chipset and MB drivers are up to date via your motherboard manufacturers website as a first port of call.
• I would also check if you have a BIOS update available as your BIOS is from 2018.

Thanks for the info and reply. I did both command prompts and no problems. I’m not sure about the ram modules since this is a prebuilt pc and I have not added anything to it yet. The potential out of date drivers I have no clue about, I checked on the Dell website and it said my pc was up to date so I don’t know.

I don’t know what this is MINDFRAME.sys — I can only find it on 1 website that I can’t login to.. which doesn’t help
The BSOD caused by a driver, we just haven’t identified which as its not showing itself in the text.

tried running chkdsk on the drives?
open command prompt (Admin)
if you have a hdd, type chkdsk c: /f /r and press enter
If you have an ssd, type chkdsk c: /f and press enter
(difference between 2 is /r repairs sectors. ssd don’t have sectors)
2 paragraphs will pop up on screen
type Y and press enter to agree to run at startup
restart PC and let the scans run

I don’t know what this is MINDFRAME.sys — I can only find it on 1 website that I can’t login to.. which doesn’t help
The BSOD caused by a driver, we just haven’t identified which as its not showing itself in the text.

tried running chkdsk on the drives?
open command prompt (Admin)
if you have a hdd, type chkdsk c: /f /r and press enter
If you have an ssd, type chkdsk c: /f and press enter
(difference between 2 is /r repairs sectors. ssd don’t have sectors)
2 paragraphs will pop up on screen
type Y and press enter to agree to run at startup
restart PC and let the scans run

I had done some chkdsk in the past, but didn’t do the repairs sectors one so I did it and it seemed to be doing fine, but just now got another bsod, here’s the dmp file: https://drive.google.com/open?id=1SzfwFOlVxF4H1r9_31NFKzFESd9Hb-Si

thank you for the constant help btw

I have run the dump file(s) and you can see the full report(s) here: https://pste.eu/p/RnaY.html

Summary of findings:

MEMORY_MANAGEMENT
«Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

• Confirm that hardware is compatible with your system.
• View the third party modules of the report to view which drivers may be misbehaving.»

updating wifi didn’t change anything, the installed drivers now have same dates as a dump done 6 days ago

error has something to do with compressed memory.
only driver names mentioned are all parts of windows
filtmgr — Microsoft Filesystem Filter Manager
npfs — named pipe file system

Some light reading for PC — https://www.fireeye.com/content/dam/fireeye-www/blog/pdfs/finding-evil-in-windows-10-compressed-memory-wp.pdf

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

The 0x1A

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 0000000000173800
Arg3: 0000000067f8404d
Arg4: 00000000adba175e


ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff8601`bbd615a8 fffff804`5c863b96 nt!KeBugCheckEx
01 ffff8601`bbd615b0 fffff804`5c68e112 nt!MiValidatePagefilePageHash+0x10157a
02 ffff8601`bbd61690 fffff804`5c68d65d nt!MiWaitForInPageComplete+0x472
03 ffff8601`bbd617a0 fffff804`5c67317b nt!MiIssueHardFault+0x1ad
04 ffff8601`bbd618a0 fffff804`5c7cf120 nt!MmAccessFault+0x40b
05 ffff8601`bbd61a40 fffff804`5c75e140 nt!KiPageFault+0x360
06 ffff8601`bbd61bd8 fffff804`5c65d1a0 nt!RtlDecompressBufferXpressLz+0x50
07 ffff8601`bbd61bf0 fffff804`5c75fec9 nt!RtlDecompressBufferEx+0x60
08 ffff8601`bbd61c40 fffff804`5c75fd54 nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x155
09 ffff8601`bbd61d20 fffff804`5c75fbd2 nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
0a ffff8601`bbd61d70 fffff804`5c75f9fb nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
0b ffff8601`bbd61e10 fffff804`5c75f841 nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
0c ffff8601`bbd61ec0 fffff804`5c75f751 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
0d ffff8601`bbd61f40 fffff804`5c669ff8 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
0e ffff8601`bbd61f70 fffff804`5c762cb1 nt!KeExpandKernelStackAndCalloutInternal+0x78
0f ffff8601`bbd61fe0 fffff804`5c74b931 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
10 ffff8601`bbd620b0 fffff804`5c74b517 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
11 ffff8601`bbd62100 fffff804`5c761fc3 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
12 ffff8601`bbd62190 fffff804`5c76369f nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
13 ffff8601`bbd62200 fffff804`5c68e23b nt!SmPageRead+0x33
14 ffff8601`bbd62250 fffff804`5c68d939 nt!MiIssueHardFaultIo+0x117
15 ffff8601`bbd622a0 fffff804`5c67317b nt!MiIssueHardFault+0x489
16 ffff8601`bbd62350 fffff804`5c7cf120 nt!MmAccessFault+0x40b
17 ffff8601`bbd624f0 fffff80f`caa3ee9f nt!KiPageFault+0x360
18 ffff8601`bbd62680 fffff80f`caa3ed77 Npfs!NpCommonCleanup+0xef
19 ffff8601`bbd62730 fffff804`5c631f39 Npfs!NpFsdCleanup+0x27
1a ffff8601`bbd62760 fffff804`5eee55d9 nt!IofCallDriver+0x59
1b ffff8601`bbd627a0 fffff804`5eee3f16 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x159
1c ffff8601`bbd62820 fffff804`5c631f39 FLTMGR!FltpDispatch+0xb6
1d ffff8601`bbd62880 fffff804`5cbe3018 nt!IofCallDriver+0x59
1e ffff8601`bbd628c0 fffff804`5cbeb168 nt!IopCloseFile+0x188
1f ffff8601`bbd62950 fffff804`5cbf04ae nt!ObCloseHandleTableEntry+0x278
20 ffff8601`bbd62a90 fffff804`5c7d2915 nt!NtClose+0xde
21 ffff8601`bbd62b00 00007ff9`9839c2b4 nt!KiSystemServiceCopyEnd+0x25
22 00000074`0acff7f8 00000000`00000000 0x00007ff9`9839c2b4

2: kd> .trap 0xffff8601bbd624f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb9898280bb28 rbx=0000000000000000 rcx=ffffb989aa3bcc98
rdx=ffffb9897dfc7ca8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80fcaa3ee9f rsp=ffff8601bbd62680 rbp=ffff8601bbd626e8
 r8=ffff8601bbd626c0  r9=ffff8601bbd626b0 r10=fffff80fcaa3ed50
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Npfs!NpCommonCleanup+0xef:
fffff80f`caa3ee9f 483902          cmp     qword ptr [rdx],rax ds:ffffb989`7dfc7ca8=0000000800000009

2: kd> !pte ffffb9897dfc7ca8 
                                           VA ffffb9897dfc7ca8
PXE at FFFF8EC763B1DB98    PPE at FFFF8EC763B73128    PDE at FFFF8EC76E625F78    PTE at FFFF8EDCC4BEFE38
contains 0A00000315CBF863  contains 0A00000315CC0863  contains 0A0000014391B863  contains 0000000274561880
pfn 315cbf    ---DA--KWEV  pfn 315cc0    ---DA--KWEV  pfn 14391b    ---DA--KWEV  not valid
                                                                                  Transition: 274561
                                                                                  Protect: 4 - ReadWrite

0xEF is typically a RAM or drive issue, considering the 0x1A I’d bet the cause is the drive.

what brand are the drives? some brands like WD & Seagate have their own testing software.

Try running HD Sentinel trial as a 2nd opinion on HD Tune
Look on disk menu and run any tests you can — https://www.hdsentinel.com/hard_disk_sentinel_trial.php

The brand for the ssd is SK hynix and for the hdd is Toshiba. I tried running HD Sentinel, but most tests were not available in the trial. Is there any other program I should get for the drivers? Also should I still run memtest or figure out if its a problem with drivers?

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

You probably need to reinstall Windows if Windows is installed on that drive, don’t worry about the activation, that will resolve itself automatically.

If you want to keep things, back it up before replacing the drive.

Thank you for the insight, do you have any recommendations for any good drive I can buy?

Thank you for the insight, do you have any recommendations for any good drive I can buy?

I would get a Samsung EVO 500gb drive (any smaller will likely need to be replaced too soon although a 250 is big enough for win 10 currently). I have a 4 year old Evo and its still almost brand new according to HD Sentinel

I assume axe can tell if the drive was an ssd or not? since you have both and I gave you chkdsk for both?

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

HDDs are another debate in themselves, some would argue that Seagates latest figures are showing bigger failure rates, but there are still plenty going strong.

Can’t tell if it’s SSD or HDD from CHKDSK logs. What size and type are you looking for @javster22 ?

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

Nearly? Which wouldn’t be a good purchase?

I haven’t looked into SSDs and HDDs in months, but am looking myself for a new SSD (eyeing the 970 evo) and HDD.

Nearly? Which wouldn’t be a good purchase?

I haven’t looked into SSDs and HDDs in months, but am looking myself for a new SSD (eyeing the 970 evo) and HDD.

Honestly, I don’t know a single BAD one, but I know plenty that are better value for money from my perspective.
If you want an M.2 SSD then the Intel 660p has frankly stormed the market on that front, half the price of a Samsung equivalent.

Some 2.5″ SSDs that are still excellent are the Crucial MX series too, sometimes the value is too good to turn down.

Depends on what format you’re looking at and your usage, many people jump to NVMe when there is no real benefit for their usage.

I would recommend replacing the drive, a dozen of chkdsk scans with repeated issues in just a couple of days, a clear sign of drive failure.

Just saw this thread and was going to post the same. Any time you have Windows wanting to check the drive it’s installed on for errors every time it starts, 99.9% of the time it means the drive is going south (and it’s time to back up) no matter what little programs like HD Tune tell you.

Frankly nearly any Samsung will be a good purchase, just now in SSDs there are some good competitors when it comes to value. But can’t really go wrong with almost any Samsung SSD.

HDDs are another debate in themselves, some would argue that Seagates latest figures are showing bigger failure rates, but there are still plenty going strong.

Can’t tell if it’s SSD or HDD from CHKDSK logs. What size and type are you looking for @javster22 ?

Well I’m not sure if I should replace both the SSD and HDD what do you think? Also not looking for anything specific just whatever good one you guys recommend that’s not too expensive.