Multiple Instances of Memory Management Stop Code after Streaming Audio and Video Content

Unable to find out why I'm experiencing multiple Windows 10 blue screens for memory management every time I stream any type of video (including YouTube, cable network TV streams, video conferencing programs, and my HP WebCam). This situation has been going on multiple times a day for more than a month. I've run the Windows diagnostic tests (including memory tests), HP hardware and performance diagnostic tests, updated the BIOS (dated 12/2019) and all drivers, among other things, with the blue screens still persisting with all these efforts. I've even ran the sfc /scannow and DISM scripts, and found nothing there, too (the sfc scan reported no integrity issues, and the DISM ScanHealth test returned no errors).

My review of minidump points repeatedly to hpdskflt.sys as culprit that is causing memory corruption. I really need to address this issue ASAP since I cannot facilitate video conferences while I'm teleworking and conversing via video conference with with federal govt customers. Every one of my video conferences crashed in the midst of these meetings. I've had crashes with streaming video browsers (Chrome, Firefox, Microsoft Edge) and through every one of the video conferencing programs, including Skype for Business, Microsoft Teams, WebEx, and Zoom. I had to switch to my mobile phone on 5/6/2020 after I experienced a system crash while attending a video conference using Microsoft Teams and again on 5/7/2020 when my system crashed while using Zoom for a personal video teleconference in the middle of meeting with a nursing home director who was providing COVID-19 updates for the facility.

 

As if the streaming video issues were not enough, I'm now encountering a new problem with running audio content, which now causes my system to crash with stop codes for memory management issues that involves the same driver (hpdskflt.sys). I assessed and played a podcast file using Chrome, and my system crashed minutes into playing the audio file from the browser. This exercise is terribly frustrating, since now it appears that I cannot stream both audio and video content using any resource that connects to the Internet.

 

This situation is unacceptable from both a business and personal level, since I am severely limited in facilitating and attending video conferences unless I turn off or avoid running any type of video stream on my HP laptop that is less than 2 years old.

* * *

HARD DRIVE INFORMATION:

Hardware Id for Local Disk (C:) -- 953GB TEAM TM8PS5001T (SATA (SSD))

SCSI\DiskTEAM____TM8PS5001T______Q060
SCSI\DiskTEAM____TM8PS5001T______
SCSI\DiskTEAM____
SCSI\TEAM____TM8PS5001T______Q
TEAM____TM8PS5001T______Q
GenDisk

 

Hardware Id for Local Data Disk (D:) -- 1863GB Seagate ST2000LM007-1R8174 (SATA (SSD))

SCSI\DiskST2000LM007-1R8174______RDM4
SCSI\DiskST2000LM007-1R8174______
SCSI\DiskST2000LM
SCSI\ST2000LM007-1R8174______R
ST2000LM007-1R8174______R
GenDisk

 

Information from the minidump after Windows 10 Stop Code for Memory Management:

*******************************************************************************
                                                       Bugcheck Analysis
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {4477, 20fc66c, 0, 0}

*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

5: kd> !analyze -v

*******************************************************************************
                                                       Bugcheck Analysis
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000004477, A driver tried to write to an unallocated address in the
user space of the system process. Parameter 2 contains the
address of the attempted write.
Arg2: 00000000020fc66c
Arg3: 0000000000000000
Arg4: 0000000000000000

 

Hello my name is Adam and I am a Microsoft user like you and an Independent Advisor. I am very happy to help you with your problem.

This driver is to protect regular HDDs is your HD an SSD? If it is SSD you can remove the file all together.

Here is a post in HP's forums...


"Default
Yea they say that this driver helps park the HDD header when laptop is shut so it wouldn't damage the internal disks on strong movements but there had been a lot of people complaining it causes BSOD and demanded it to be removed so there were suggestions like these Remove hpdskflt.sys - how to permanently delete the file from your computer which basically requires you search and delete all instances found on your HDD / SSD so no copies are re-installed upon deletion .

Other posts indicate that the driver re-installs from some unknown package of HP utilities they can't quite identify then they suggest you either uninstall all HP packages claiming they are nothing but bloatware or just clean install windows

But here is something i usually do when traditional methods fail , you can always use File Unlocker * to remove original file then replace it by a 0 byte text file you rename into same name ( hpdskflt.sys ) where you set its attributes to Read-Only & System , so it can't be replaced by background services later .

This previous mean is usually 99% efficient , but to be sure you should check event viewer in a day see if it started accumulating errors due to its absence which would mean that there are other HP apps on the system are trying to call it , this has its cons and pros if it happens actually , at least you will know what package the driver belongs to where you can un-install it , as con , if the package turned out to be essential package you can't just get rid of you may either just live with generated errors or just get the file back in place and call it today .

Of course if the file did not produce any errors then its as good as gone .

Cheers


* if File Unlocker fails a restart to Safe Mode or Windows P.E might be needed"

Original post by nIGHTmAYOR here: https://www.tenforums.com/members/nightmayor.html

https://www.tenforums.com/drivers-hardware/1386...

This is not an MS website as such...
Please beware of any random software that this or any site requests you to install. A quick search on the internet can prevent you from installing malicious software.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

correction not HP's forums it was tenforums.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Also the link did not come through for the guide to remove the file. Here it is...

http://speedutilities.com/remove/hpdskflt.sys.html

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Also the link did not come through for the guide to remove the file. Here it is...

http://speedutilities.com/remove/hpdskflt.sys.html

Unfortunately, the procedures provided here do not work, since I'm unable to disable or remove the driver. When I uninstalled the driver for the HP Mobile Data Protection Sensor under "System devices" in the Device Manager, rebooted, and then disabled the driver in the Windows\drivers folder, I was unable to boot my laptop. The system went in a diagnostic and repair mode immediately on boot up, and this process ended up in a loop because of the inability to repair itself. I ended up applying the last restore point. I even rolled back to the previous driver that was updated, but even that option wasn't viable -- BSODs when I try streaming video conferences or listen to a podcast or streaming any other audio and video content for that matter.

So, I'm right back where I started -- no apparent update for this buggy driver and no way to participate in or facilitate video conferences since my system crashes to a BSOD.

This is the first time that I'm using an HP laptop after sticking with Toshiba Satellite laptops until the company retired the Satellite line. With no solution and having been crippled from doing normal meetings during the work, my only other option is to buy an inexpensive laptop and leave this HP laptop behind. I won't be able to go on indefinitely with an ineffective laptop product that I'm using for the first time...and likely the for the last time given all the grief that I'm going through -- something that I've never had to deal with in all the decades that I used Toshiba laptops.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have the same problem with hpdskflt.sys.

Memory Management BSOD when playing video or using skype video chat.

WinDbg dump file analysis:

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000004477, A driver tried to write to an unallocated address in the
    user space of the system process. Parameter 2 contains the
    address of the attempted write.
Arg2: 0000000001edc510
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  HP ENVY Laptop 17-ae1xx

......

STACK_TEXT: 
ffff8a85`20142ff8 fffff806`827fce80 : 00000000`0000001a 00000000`00004477 00000000`01edc510 00000000`00000000 : nt!KeBugCheckEx
ffff8a85`20143000 fffff806`826f8502 : 00000000`00000000 fffff806`846ae2e7 00000000`00000000 ffffe18f`801051a0 : nt!MiCheckFatalAccessViolation+0x1a2bd8
ffff8a85`20143040 fffff806`826c9c7c : ffffdb7f`ffffffff ffffdb00`00000000 ffffdb00`00000000 ffffdb6d`80000078 : nt!MiInPagePageTable+0x2f2
ffff8a85`20143190 fffff806`826c8fae : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt!MiUserFault+0x7dc
ffff8a85`20143240 fffff806`8263f8f4 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe18f`85449040 : nt!MmAccessFault+0x14e
ffff8a85`201433e0 fffff806`8272e257 : 00000000`00000002 ffffdb00`0000f6e0 ffff8a85`20143550 ffffdb6d`b6db6700 : nt!MiFaultInProbeAddress+0xbc
ffff8a85`20143490 fffff806`8272d61e : 00000000`00000000 00000000`00000000 ffff8a85`20143600 00000000`01edc510 : nt!MiLockPageLeafPageTable+0x2a7
ffff8a85`20143500 fffff806`8272d4a9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiProbeAndLockPages+0x15e
ffff8a85`20143650 fffff806`8463a0b1 : ffffe18f`809021f0 00000000`00000002 ffffe231`92361d00 ffffe18f`9a3d2c80 : nt!MmProbeAndLockPages+0x29
ffff8a85`20143680 fffff806`845dfb76 : ffffe18f`9a3d2c80 00000000`00000000 ffffe18f`8fa98a50 ffffe18f`8fa98a50 : storport!PortPassThroughBuildIrp+0xa9
ffff8a85`201436d0 fffff806`845d7940 : 00000000`00000000 ffffe18f`801051a0 ffffe18f`8fa98a50 00000000`00000000 : storport!RaUnitAtaPassThroughIoctl+0x1da
ffff8a85`201437a0 fffff806`845d75ba : 00000000`00000103 00000000`00000000 ffffe18f`7bb0d010 fffff806`84631000 : storport!RaUnitDeviceControlIrp+0x33c
ffff8a85`20143820 fffff806`8270a929 : ffffe18f`7bb0d010 ffffe18f`8fa98a50 ffffe18f`8fa98bf8 00000000`00000000 : storport!RaDriverDeviceControlIrp+0x5a
ffff8a85`20143860 fffff806`841011f6 : ffffe18f`8fa98bf8 ffffe18f`7bb0d010 ffffe18f`80a13a20 fffff806`85784109 : nt!IofCallDriver+0x59
ffff8a85`201438a0 fffff806`8270a929 : 00000000`00000007 ffffe18f`80a13a20 00000000`00000080 00000000`00000000 : ACPI!ACPIDispatchIrp+0x1e6
ffff8a85`20143920 fffff806`8578388b : ffffe18f`80a13a00 ffffe18f`80a13a20 00000000`00000000 00000000`00000008 : nt!IofCallDriver+0x59
ffff8a85`20143960 ffffe18f`80a13a00 : ffffe18f`80a13a20 00000000`00000000 00000000`00000008 00000000`00000000 : hpdskflt+0x388b
ffff8a85`20143968 ffffe18f`80a13a20 : 00000000`00000000 00000000`00000008 00000000`00000000 00000000`00000000 : 0xffffe18f`80a13a00
ffff8a85`20143970 00000000`00000000 : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe18f`80a13a20


THREAD_SHA1_HASH_MOD_FUNC:  2e83963284614ed1e0a2bbeb260642ce1cc94a42

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bd5f861c57d748721081126dc7fa63daaa1a7219

THREAD_SHA1_HASH_MOD:  942f9c54d5861c7168e4144f146bb62a54fd7175

FOLLOWUP_IP:
hpdskflt+388b
fffff806`8578388b 48c74424506079feff mov   qword ptr [rsp+50h],0FFFFFFFFFFFE7960h

FAULT_INSTR_CODE:  2444c748

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  hpdskflt+388b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hpdskflt

IMAGE_NAME:  hpdskflt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5bff9aab

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  388b

FAILURE_BUCKET_ID:  0x1a_4477_hpdskflt!unknown_function

BUCKET_ID:  0x1a_4477_hpdskflt!unknown_function

PRIMARY_PROBLEM_CLASS:  0x1a_4477_hpdskflt!unknown_function

TARGET_TIME:  2020-05-25T05:51:46.000Z

OSBUILD:  18362

OSSERVICEPACK:  836

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  8150

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_4477_hpdskflt!unknown_function

FAILURE_ID_HASH:  {c72d89e0-c65a-6ab7-e905-45a88384f304}

Followup:     MachineOwner
---------

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated July 24, 2020 Views 59 Applies to: