Stop Error Dump File Analysis - Dump file analysed: \091219-6921-01.dmp] on 12/09/19

Analysed using Loading Dump File [C:\Users\niall\Downloads\091219-6921-01.dmp] and PCT Analyser V5 (Copyright 2019)

Click on each button to view the relevant information

General Tips for Stop Errors (BSOD)

Firstly, you can follow the Microsoft online Blue Screen wizard here.

Hardware Diagnostic / Testing Tools

What are Stop Errors?

Firstly, it is worth clarifying that a BSOD is only attributed to Windows, for example, where Windows has a Blue Screen, Linux actually has something known as a System Panic. However, you’ll find Linux is much less prone to them.

Microsoft defines a blue screen very well:

“When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also commonly referred to as a system crash, a kernel error, a Stop error, or BSOD. A hardware device, its driver, or related software might have caused this error.”

In simple terms – it’s when Windows has detected a problem that could have caused damage or corruption to the operating system, or your computer itself, and therefore needed to STOP.

That’s why technically it’s called a stop error, stop code, or a bug check. They are more indicative of a fatal system crash. For the purpose of standardisation, we will call this a bug check (Bugcheck = BSOD).

So, there are some important considerations to take before continuing:

Summary

BugCheck A ----- IRQL_NOT_LESS_OR_EQUAL

Probably caused by : memory_corruption ( nt!MiIssueFlowThroughFault+2c )

Arg1: 00000000001a9281, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

Arg4: fffff80619457bf4, address which referenced memory

PROCESS_NAME: MsMpEng.exe

MODULE_NAME: nt

IMAGE_NAME: memory_corruption ----->


Bugcheck Description:

IRQL_NOT_LESS_OR_EQUAL

"This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL). This is typically either a bad pointer or a pageability problem. P1 is the address that could not be referenced."

About your bugcheck / typical cause:

"Bug check 0xA is usually caused by kernel mode device drivers using improper addresses. This is either a bad memory pointer or a pageability problem with the device driver code. Examine the third party drivers . Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen."

System Information

This includes BIOS, Motherboard, Processor, and Memory. Not all dump files will contain hardware information, and therefore this will not always be complete

BIOS Information

No data

Mainboard Information

No Data

Processor Information

No data

Memory Information

Slot Size Speed Part Number
Memory Slot 1 No Data
Memory Slot 2 No Data
Memory Slot 3 No Data
Memory Slot 4 No Data

Loaded Modules

To disable third party modules, use Autoruns (Microsoft Program)

Modules are listed from OLDEST to NEWEST - typically out of drivers should be looked at first. Total Modules Loaded = Total 13
1- ModuleName 2- Time Stamp 3- Company 4- Description
speedfan.sys 29/12/2012 Almico Speedfan Driver
RTKVHD64.sys 11/02/2014 Realtek Realtek HD Audio Driver
amdgpio3.sys 14/03/2016 AMD AMD GPIO Controller Driver
amdpsp.sys 05/06/2017 AMD AMD Chipset Driver
rt640x64.sys 14/11/2017 Realtek Realtek Audio Driver
AMDPCIDev.sys 12/04/2018 AMD AMD Ryzen OC Utility
amdgpio2.sys 12/11/2018 AMD AMD GPIO Controller Driver
UcmCxUcsiNvppc.sys 15/05/2019 NVIDIA USB Type C Port Controller Driver
rtwlanu.sys 28/05/2019 Realtek Realtek Wirless USB 2.0 Adapter Driver
ROGKB.sys 17/06/2019 UNKNOWN Unknown
ROGMS.sys 17/06/2019 UNKNOWN Unknown
nvhda64v.sys 21/06/2019 NVIDIA NVIDIA Audio HDMI Driver (nForce Chip)
nvlddmkm.sys 05/09/2019 NVIDIA NVIDIA Video Drivers

Dump File

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 17763 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Kernel base = 0xfffff806`19408000 PsLoadedModuleList = 0xfffff806`19823630

Debug session time: Thu Sep 12 09:37:37.609 2019 (UTC + 1:00)

System Uptime: 0 days 0:08:18.324

Loading Kernel Symbols

...............................................................

................................................................

.........................................................

Loading User Symbols

Loading unloaded module list

......

For analysis of this file, run !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {1a9281, 2, 0, fffff80619457bf4}

Probably caused by : memory_corruption ( nt!MiIssueFlowThroughFault+2c )

Followup: MachineOwner

---------

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

* *

* Bugcheck Analysis *

* *

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

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 00000000001a9281, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

Arg4: fffff80619457bf4, address which referenced memory

Debugging Details:

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

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: 17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE: 2

BUGCHECK_P1: 1a9281

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80619457bf4

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff806198cf400

fffff8061994a390: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

00000000001a9281

CURRENT_IRQL: 2

FAULTING_IP:

nt!MiIssueFlowThroughFault+2c

fffff806`19457bf4 458b99c0000000 mov r11d,dword ptr [r9+0C0h]

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: MsMpEng.exe

ANALYSIS_SESSION_HOST: DESKTOP-CL34DUR

ANALYSIS_SESSION_TIME: 09-12-2019 11:51:23.0272

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME: ffff960e2c1aa530 -- (.trap 0xffff960e2c1aa530)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffff960e2c1aa6e8 rbx=0000000000000000 rcx=ffff960e2c1aa880

rdx=ffffa980e05516b8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80619457bf4 rsp=ffff960e2c1aa6c0 rbp=ffff960e2c1aa880

r8=0000000000000000 r9=00000000001a91c1 r10=ffff97891a49b0c0

r11=fffff90000000028 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiIssueFlowThroughFault+0x2c:

fffff806`19457bf4 458b99c0000000 mov r11d,dword ptr [r9+0C0h] ds:00000000`001a9281=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff806195cd7e9 to fffff806195bbf50

STACK_TEXT:

ffff960e`2c1aa3e8 fffff806`195cd7e9 : 00000000`0000000a 00000000`001a9281 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

ffff960e`2c1aa3f0 fffff806`195c9bd4 : 00000000`00000003 00000000`00000000 fffff806`19423010 ffff960e`2c1aa488 : nt!KiBugCheckDispatch+0x69

ffff960e`2c1aa530 fffff806`19457bf4 : 000001c0`b175992f 00000000`00000000 fffff900`037f0e00 00000000`00000000 : nt!KiPageFault+0x454

ffff960e`2c1aa6c0 fffff806`19457ac9 : ffff960e`2c1aa810 ffff960e`2c1aa880 fffff900`04fe0510 00000000`00000000 : nt!MiIssueFlowThroughFault+0x2c

ffff960e`2c1aa6f0 fffff806`194c9155 : ffff9789`1b7dc5c0 00000001`aa01b880 ffff960e`2c1aa900 fffff900`04fe0510 : nt!MiHandleCollidedFault+0x79

ffff960e`2c1aa740 fffff806`194d1edb : 00000098`00000000 fffff806`19a294de ffff960e`2c1aaa20 00000000`00000000 : nt!MiResolveTransitionFault+0x975

ffff960e`2c1aa800 fffff806`194d011a : 00000000`00000004 00000000`00000001 00000000`c0000016 ffff9789`1b7dc0c0 : nt!MiDispatchFault+0x56b

ffff960e`2c1aa960 fffff806`195c9ac9 : ffff9789`1a49b0c0 000001c0`9c328b68 00000000`00003a98 ffff9789`1e752ae0 : nt!MmAccessFault+0x15a

ffff960e`2c1aab00 00007ff8`a347331f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x349

00000098`d1f7f3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`a347331f

THREAD_SHA1_HASH_MOD_FUNC: e16728d444e6b366cb44e09cb02ba2a277c14ec6

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 744dd3b07eea3e6790e51ee2c98b70710cd4f2de

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:

nt!MiIssueFlowThroughFault+2c

fffff806`19457bf4 458b99c0000000 mov r11d,dword ptr [r9+0C0h]

FAULT_INSTR_CODE: c0998b45

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiIssueFlowThroughFault+2c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.678

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 2c

FAILURE_BUCKET_ID: AV_nt!MiIssueFlowThroughFault

BUCKET_ID: AV_nt!MiIssueFlowThroughFault

PRIMARY_PROBLEM_CLASS: AV_nt!MiIssueFlowThroughFault

TARGET_TIME: 2019-09-12T08:37:37.000Z

OSBUILD: 17763

OSSERVICEPACK: 678

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: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 2c36

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!miissueflowthroughfault

FAILURE_ID_HASH: {db20ee98-8ddd-5d1f-8375-1e297e166ba5}

Followup: MachineOwner

---------

@ win32kfull.sys 47c2299b

@ win32kbase.sys c66d5a41

@ cdd.dll 00000000

@ E:\WinDBG\Debuggers\x86\sym\win32k.pdb\5FC948DFBCBB1D235917205222B345C61\win32k.pdb b0321e5e

@ E:\WinDBG\Debuggers\x86\sym\ntkrnlmp.pdb\9A729548AB1A93E90D0A48528CE30B7A1\ntkrnlmp.pdb e555a2c9

@ hal.dll ac153306

@ kd.dll 7a776dcd

@ werkernel.sys 030a7cce

@ msrpc.sys ad3c8c27

@ tm.sys f1ac5a2f

@ CLFS.SYS 65900277

@ PSHED.dll 79fb7d7e

@ cmimcext.sys 4c6db670

@ ntosext.sys 6d6b5a0e

@ CI.dll 71370732

@ cng.sys 85008090

@ clipsp.sys 5d04b944

@ Wdf01000.sys af1cedd2

@ WDFLDR.SYS 47a236e4

@ WppRecorder.sys e67c59ba

@ SleepStudyHelper.sys d42abccc

@ acpiex.sys 0a439b7f

@ mssecflt.sys d07e4e59

@ SgrmAgent.sys f7ca286d

@ ACPI.sys a49a6357

@ WMILIB.SYS 7710989f

@ intelpep.sys ae0e514f

@ WindowsTrustedRT.sys bd0b79f0

@ WindowsTrustedRTProxy.sys 5192684a

@ pcw.sys c6c870f7

@ msisadrv.sys 418dc2e9

@ pci.sys 830a8a17

@ vdrvroot.sys 8ed5f3a9

@ pdc.sys 1368f445

@ CEA.sys 9b4697b8

@ partmgr.sys 2fe6062f

@ spaceport.sys a069c343

@ volmgr.sys 91784a41

@ volmgrx.sys 50da1ded

@ mountmgr.sys a8481dd2

@ storahci.sys e94316b7

@ storport.sys d6a4ba31

@ EhStorClass.sys f26184eb

@ fileinfo.sys 85b4f747

@ Wof.sys 237f6dfd

@ WdFilter.sys bdd671f8

@ Ntfs.sys 3885b4cf

@ Fs_Rec.sys cff89b5e

@ ndis.sys 0307a6f2

@ mcupdate_AuthenticAMD.dll f26dbe88

@ ksecdd.sys c0930b22

@ BOOTVID.dll 30b650ad

@ FLTMGR.SYS 9697298f

@ tcpip.sys f2e36ca1

@ fwpkclnt.sys 204b6f56

@ wfplwfs.sys 0aa4b522

@ NETIO.SYS c0e588af

@ ksecpkg.sys 1b3cb9d8

@ amdpsp.sys 5935cc3c

@ fvevol.sys b5cd826b

@ volume.sys cb3f72cf

@ rdyboost.sys 5b832bf2

@ mup.sys d5074ba1

@ iorate.sys a096cd2d

@ disk.sys eb969297

@ CLASSPNP.SYS ac33998d

@ crashdmp.sys fef3c415

@ cdrom.sys 590e43df

@ filecrypt.sys 798a13f4

@ tbs.sys 7de0f3e4

@ Null.SYS 23dc46f7

@ Beep.SYS e2569389

@ dxgkrnl.sys 02b3f361

@ watchdog.sys 8d7a0df0

@ BasicDisplay.sys d39d4b86

@ BasicRender.sys 500b5138

@ Npfs.SYS bbac2737

@ Msfs.SYS c2dfb7c4

@ tdx.sys afdabf6d

@ TDI.SYS e9708b47

@ netbt.sys 6bf64710

@ afunix.sys ce69ff46

@ afd.sys c0b0d284

@ vwififlt.sys b1239f86

@ pacer.sys bd6e6ba5

@ netbios.sys ba5b5fb4

@ rdbss.sys 021097cf

@ csc.sys 71977cc0

@ nsiproxy.sys 050877bf

@ npsvctrig.sys 7e4d1a78

@ E:\WinDBG\Debuggers\x86\sym\mssmbios.pdb\6AEB55D4626165B2915516C094CDA9681\mssmbios.pdb a51d1a67

@ MpKsla8bc7090.sys 2409fbe1

@ MpKsl3f2cacd8.sys 2409fbe1

@ gpuenergydrv.sys da1c403f

@ dfsc.sys e60cddbc

@ fastfat.SYS eb9fc2e9

@ bam.sys 1653310c

@ ahcache.sys 2f11a0dc

@ Vid.sys f42473ac

@ winhvr.sys 8836b629

@ CompositeBus.sys dd86440a

@ kdnic.sys 05131801

@ umbus.sys 83197d71

@ USBXHCI.SYS fdacad1e

@ ucx01000.sys 7e0a5f72

@ volsnap.sys ac1c69a4

@ rt640x64.sys 5a0a844e

@ ks.sys f785d292

@ UcmCxUcsiNvppc.sys 5cdb7679

@ UcmCx.sys 26609ad2

@ AMDPCIDev.sys 5acef961

@ serial.sys 3d30e0f0

@ serenum.sys 604b8a02

@ amdgpio2.sys 5be94cbf

@ msgpioclx.sys 4b2a44e1

@ amdppm.sys f2b45e34

@ wmiacpi.sys f2622d42

@ amdgpio3.sys 56e69038

@ UEFI.sys b5d8263e

@ NdisVirtualBus.sys 333ae742

@ swenum.sys 8b90f92a

@ rdpbus.sys 7b2e1a48

@ UsbHub3.sys 4b5abbef

@ USBD.SYS c7e3b3e8

@ nvhda64v.sys 5d0d318d

@ ksthunk.sys d43d6b7c

@ RTKVHD64.sys 52fa036f

@ HIDPARSE.SYS 2aa4ebb4

@ nvlddmkm.sys 5d716596

@ HDAudBus.sys 121b41c6

@ portcls.sys 8dfe43a2

@ drmk.sys 394317ab

@ dxgmms2.sys 0c7b8e50

@ luafv.sys 637f4174

@ wcifs.sys 22d58be9

@ cldflt.sys f1aae47f

@ storqosflt.sys 29923efb

@ lltdio.sys f5108909

@ mslldp.sys a36249fa

@ rspndr.sys c42f95a5

@ wanarp.sys 08c5c028

@ nwifi.sys 6c547e92

@ ndisuio.sys 117f9087

@ winquic.sys 6e5c0414

@ HTTP.sys f6495506

@ bowser.sys 30059e68

@ mpsdrv.sys 4e67ce41

@ mrxsmb.sys 1e562dc2

@ mrxsmb20.sys 0d59a79b

@ srvnet.sys 4e6f5832

@ Ndu.sys 18babc47

@ peauth.sys 857dc62d

@ mmcss.sys d143bb7e

@ tcpipreg.sys 42abe6c4

@ srv2.sys 7ff4aff4

@ usbccgp.sys 82d4cb5c

@ monitor.sys 41fa7930

@ hidusb.sys 02e73966

@ HIDCLASS.SYS 1255155c

@ mouhid.sys 45af4341

@ ROGMS.sys 5d073c26

@ mouclass.sys 80f98b92

@ kbdhid.sys 5e1d49fd

@ ROGKB.sys 5d073bfe

@ WdNisDrv.sys 65b5d483

@ kbdclass.sys db4b5540

@ rassstp.sys 6c3c4681

@ NDProxy.sys 78f862cf

@ dump_diskdump.sys a0767573

@ dump_storahci.sys e94316b7

@ dump_dumpfve.sys 3511e596

@ AgileVpn.sys 5459b0dc

@ rasl2tp.sys ca2a942b

@ raspptp.sys 340ea9a3

@ raspppoe.sys a6ba0271

@ MpKsl303bdf26.sys 2409fbe1

@ vwifimp.sys 172f45a0

@ ndistapi.sys d2b2edc9

@ ndiswan.sys 1596b64d

@ wcnfs.sys 45669b7d

@ speedfan.sys 50df59b7

@ condrv.sys 314bacf1

@ rtwlanu.sys 5cecd33f

@ wdiwifi.sys 63bdaa31

@ vwifibus.sys 623d4a3f

sysinfo: could not find necessary interfaces.

sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

sysinfo: could not find necessary interfaces.

sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

Additional Commands

No additional commands run in this instance