Windows 10: BSOD Issue

I am experiencing BSOD on multiple HP laptops on my environment with different models of HP laptops.

1. This issue is only affecting Laptops and does not affect HP desktops in same environment

2. STOP Code: RDR_FILE_SYSTEM and what failed: mrxsmb20.sys

3. We have offline files enabled in the Environment for laptops

4. BSOD occurs on Fridays of every week with multiple users.


see below analysis of dump



*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



RDR_FILE_SYSTEM (27)

If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the

exception record and context record. Do a .cxr on the 3rd parameter and then kb to

obtain a more informative stack trace.

The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined

as follows:

RDBSS_BUG_CHECK_CACHESUP = 0xca550000,

RDBSS_BUG_CHECK_CLEANUP = 0xc1ee0000,

RDBSS_BUG_CHECK_CLOSE = 0xc10e0000,

RDBSS_BUG_CHECK_NTEXCEPT = 0xbaad0000,

Arguments:

Arg1: 00000000baad0073

Arg2: ffffbd8b9eb69808

Arg3: ffffbd8b9eb69050

Arg4: fffff8063fbbbdf8



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : AV.Dereference

Value: NullClassPtr



Key : AV.Fault

Value: Read





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 ProBook 640 G3



SYSTEM_SKU: 1BS09UT#ABA



BIOS_VENDOR: HP



BIOS_VERSION: P83 Ver. 01.02



BIOS_DATE: 12/06/2016



BASEBOARD_MANUFACTURER: HP



BASEBOARD_PRODUCT: 82AA



BASEBOARD_VERSION: KBC Version 49.34



DUMP_TYPE: 2



BUGCHECK_P1: baad0073



BUGCHECK_P2: ffffbd8b9eb69808



BUGCHECK_P3: ffffbd8b9eb69050



BUGCHECK_P4: fffff8063fbbbdf8



EXCEPTION_RECORD: ffffbd8b9eb69808 -- (.exr 0xffffbd8b9eb69808)

ExceptionAddress: fffff8063fbbbdf8 (mrxsmb20!Smb2InvalidateFileInfoCacheEntry+0x0000000000000048)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 0000000000000008

Attempt to read from address 0000000000000008



CONTEXT: ffffbd8b9eb69050 -- (.cxr 0xffffbd8b9eb69050)

rax=0000000000000000 rbx=0000000000000000 rcx=ffff980db57e59e0

rdx=ffff980db5dc6b20 rsi=ffff980db57e59e0 rdi=ffffe7085632fa20

rip=fffff8063fbbbdf8 rsp=ffffbd8b9eb69a40 rbp=ffffbd8b9eb69b40

r8=ffffbd8b9eb69bb8 r9=00000000ffffffff r10=7ffffffffffffffc

r11=ffffe7085d6bf5d8 r12=ffff980db4a55db0 r13=0000000000000000

r14=ffff980db5dc6b20 r15=0000000000000001

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

mrxsmb20!Smb2InvalidateFileInfoCacheEntry+0x48:

fffff806`3fbbbdf8 8b4308 mov eax,dword ptr [rbx+8] ds:002b:00000000`00000008=????????

Resetting default scope



CPU_COUNT: 4



CPU_MHZ: a98



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 8e



CPU_STEPPING: 9



CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: EXCEL.EXE



CURRENT_IRQL: 0



FOLLOWUP_IP:

mrxsmb20!Smb2InvalidateFileInfoCacheEntry+48

fffff806`3fbbbdf8 8b4308 mov eax,dword ptr [rbx+8]



FAULTING_IP:

mrxsmb20!Smb2InvalidateFileInfoCacheEntry+48

fffff806`3fbbbdf8 8b4308 mov eax,dword ptr [rbx+8]



BUGCHECK_STR: 0x27



READ_ADDRESS: fffff8062e5723b8: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

0000000000000008



DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



EXCEPTION_CODE_STR: c0000005



EXCEPTION_PARAMETER1: 0000000000000000



EXCEPTION_PARAMETER2: 0000000000000008



ANALYSIS_SESSION_HOST: L-5CG8368DY6



ANALYSIS_SESSION_TIME: 10-21-2019 16:11:31.0421



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



LAST_CONTROL_TRANSFER: from fffff8063fbd5aa4 to fffff8063fbbbdf8



STACK_TEXT:

ffffbd8b`9eb69a40 fffff806`3fbd5aa4 : ffff980d`b57e59e0 ffffe708`5c9aed00 00000000`00000380 ffffe708`5c9aed00 : mrxsmb20!Smb2InvalidateFileInfoCacheEntry+0x48

ffffbd8b`9eb69c00 fffff806`3fb56245 : 00000000`00000000 00000000`00000000 ffffe708`00000000 00000000`00000000 : mrxsmb20!MRxSmb2SetFileInformation+0x224

ffffbd8b`9eb69c90 fffff806`3bec42d5 : ffff980d`b7c25ae0 ffffbd8b`9eb69dc0 ffffe708`5c9aed04 ffffe708`55cd01f0 : mrxsmb!SmbShellSetFileInformation+0x25

ffffbd8b`9eb69cc0 fffff806`3be4011c : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe708`5632fa20 : csc!CscSetFileInformation+0x11a5

ffffbd8b`9eb6a120 fffff806`3be3e658 : ffff980d`b57e59e0 ffff980d`bd6eb4b0 ffffe708`5632fa20 ffff980d`bd6eb500 : rdbss!RxSetRenameLinkClusterInfo+0x33c

ffffbd8b`9eb6a210 fffff806`3bde3064 : ffff980d`b57e59e0 ffff980d`b57e5900 00000000`00000002 ffff980d`b4a55db0 : rdbss!RxCommonSetInformation+0x798

ffffbd8b`9eb6a300 fffff806`3be1d9d6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdbss!RxFsdCommonDispatch+0x5f4

ffffbd8b`9eb6a490 fffff806`3fb7ba6d : 00000000`00000000 00000000`10000004 00000000`00000000 00000000`00000000 : rdbss!RxFsdDispatch+0x86

ffffbd8b`9eb6a4e0 fffff806`2e031f39 : ffff980d`b91bfbb0 ffff980d`bd6eb4b0 ffffe708`46831f50 ffffe708`59037110 : mrxsmb!MRxSmbFsdDispatch+0xfd

ffffbd8b`9eb6a530 fffff806`336ee615 : 00000000`00000001 fffff806`336ee3c9 ffff980d`b91bfc60 ffff980d`b90e31f8 : nt!IofCallDriver+0x59

ffffbd8b`9eb6a570 fffff806`336ee159 : ffffe708`46831f50 fffff806`336e8000 fffff806`336e8000 ffff980d`bd6eb4b0 : mup!MupiCallUncProvider+0xb5

ffffbd8b`9eb6a5e0 fffff806`336f7a9a : 00000000`00000000 ffff980d`bcd12410 ffff980d`b9b4bbc0 ffff980d`bd6eb4b0 : mup!MupStateMachine+0x59

ffffbd8b`9eb6a610 fffff806`2e031f39 : ffff980d`b77ef8a0 00000000`00000000 ffff980d`b91bfbb0 ffff980d`b9b4bbc0 : mup!MupSetInformationFile+0x1fa

ffffbd8b`9eb6a670 fffff806`317155de : ffff980d`b77ef8a0 ffff980d`b9b4bbc0 ffff980d`bd6eb658 00000000`00000000 : nt!IofCallDriver+0x59

ffffbd8b`9eb6a6b0 fffff806`31713f16 : ffffbd8b`9eb6a750 00100002`00000000 ffffffff`80002f01 ffff980d`b9b67460 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15e

ffffbd8b`9eb6a730 fffff806`2e031f39 : 00000000`00000000 ffffbd8b`9eb6a728 00000000`00000640 00000000`00000000 : FLTMGR!FltpDispatch+0xb6

ffffbd8b`9eb6a790 fffff806`2e106291 : 01d58500`6053557c 00000000`00000020 ffff37c5`722bc662 00000000`0000000a : nt!IofCallDriver+0x59

ffffbd8b`9eb6a7d0 fffff806`2e029579 : ffff980d`bd6eb4b0 00000000`00000000 00000000`00000000 ffff980d`00000000 : nt!IopCallDriverReference+0xf1

ffffbd8b`9eb6a840 fffff806`2e1d2915 : 00000000`000017a8 00000000`0cf2e448 00000000`0cf2eb70 ffffbd8b`000000cc : nt!NtSetInformationFile+0x6f9

ffffbd8b`9eb6a990 00007ff9`5719c5b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

00000000`0cf2e348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`5719c5b4





THREAD_SHA1_HASH_MOD_FUNC: 3c17275787df94c4940468928101b4f78804bac4



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f5bfe10ba75bc7b21d30261fff2dfc486ed5e8d6



THREAD_SHA1_HASH_MOD: e79dcc65ef582b329efe280586a5f8fb19fba949



FAULT_INSTR_CODE: a808438b



SYMBOL_STACK_INDEX: 0



SYMBOL_NAME: mrxsmb20!Smb2InvalidateFileInfoCacheEntry+48



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: mrxsmb20



IMAGE_NAME: mrxsmb20.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 2a968ecc



IMAGE_VERSION: 10.0.18362.267



STACK_COMMAND: .cxr 0xffffbd8b9eb69050 ; kb



BUCKET_ID_FUNC_OFFSET: 48



FAILURE_BUCKET_ID: 0x27_mrxsmb20!Smb2InvalidateFileInfoCacheEntry



BUCKET_ID: 0x27_mrxsmb20!Smb2InvalidateFileInfoCacheEntry



PRIMARY_PROBLEM_CLASS: 0x27_mrxsmb20!Smb2InvalidateFileInfoCacheEntry



TARGET_TIME: 2019-10-17T15:34:34.000Z



OSBUILD: 18362



OSSERVICEPACK: 329



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: 2016-04-22 09:00:30



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



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



ANALYSIS_SESSION_ELAPSED_TIME: 7bda



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x27_mrxsmb20!smb2invalidatefileinfocacheentry



FAILURE_ID_HASH: {25087bb5-b9be-59d5-5d4e-ec0fec68d285}



Followup: MachineOwner




Any Suggestion?

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast:

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.