BSOD mini dump help


Feb 2, 2018
so I upgraded my CPU, motherboard and ram about a year ago now and reinstalled windows 10, Ever since im getting BSOD. I lived with it because it only happens once or twice a week but this week I had a project to do and I lost parts of my work because my computer crashed so its finally time to fix.

my dad said 90% of BSOD come from faulty drivers and memory so I ran memtest86 for 15 hours on my computer but it did not pick up any errors. I'm not sure what this mini dump is and how it works is there anything which is out of the ordinary?

computer spec (i7 4770k, MSI Z97S SLI KRAIT EDITION, 16gb 1866mhz ddr3, gtx 1080, ssd and hard drive with the OS on the ssd)

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

fffff809`3322c715 488b08 mov rcx,qword ptr [rax]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes

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

BUGCHECK_STR: 0x1e_c0000005





EXCEPTION_RECORD: fffff80265b7efe0 -- (.exr 0xfffff80265b7efe0)
ExceptionAddress: 0000000000000002
ExceptionCode: fcffda60
ExceptionFlags: ffff9407
NumberParameters: -164981792
Parameter[0]: 0000000000000000
Parameter[1]: ffff9407fcffdb70
Parameter[2]: fffff80265b7f3a8
Parameter[3]: 00000000c0000005
Parameter[4]: 0000000000000000
Parameter[5]: fffff8093322c715
Parameter[6]: 0000000000000002
Parameter[7]: 0000000000000000
Parameter[8]: ffffffffffffffff
Parameter[9]: 0000000000001002
Parameter[10]: ffff9407fdc8d870
Parameter[11]: 0000000000000000
Parameter[12]: ffff9407f3cc3700
Parameter[13]: fffff8026225ffbc
Parameter[14]: 000000000000000d

TRAP_FRAME: fffff7b140002938 -- (.trap 0xfffff7b140002938)
Unable to read trap frame at fffff7b1`40002938

LAST_CONTROL_TRANSFER: from fffff8026245526a to fffff8026239e670

CONTEXT: 508b480002e20a85 -- (.cxr 0x508b480002e20a85)
Unable to read context, Win32 error 0n30

fffff802`65b7e0c8 fffff802`6245526a : 00000000`0000001e ffffffff`c0000005 fffff809`3322c715 00000000`00000000 : nt!KeBugCheckEx
fffff802`65b7e0d0 fffff802`623a819d : fffff802`62607000 fffff802`62207000 000595bc`00965000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
fffff802`65b7e110 fffff802`622163a6 : fffff802`65b7e240 fffff802`65b7e700 00000000`00000000 fffff802`65b7f018 : nt!RtlpExecuteHandlerForException+0xd
fffff802`65b7e140 fffff802`622177c3 : fffff802`65b7f018 fffff802`65b7ed60 fffff802`65b7f018 00000000`00000000 : nt!RtlDispatchException+0x416
fffff802`65b7e830 fffff802`623b1902 : fffff802`65b7efe0 fffff802`62b6edf5 fffff7b1`40002938 ffff9407`fdc8d701 : nt!KiDispatchException+0x1f3
fffff802`65b7eee0 fffff802`623ad5c9 : ffff9407`fc7c3180 00000000`00000000 ffff9407`fc7c3180 ffff9407`0000000d : nt!KiExceptionDispatch+0xc2
fffff802`65b7f0c0 fffff809`3322c715 : ffff9408`000b5af0 fffff802`65b7f309 00000000`00000000 ffff9408`000b5f6b : nt!KiGeneralProtectionFault+0x389
fffff802`65b7f250 fffff809`3321c1e6 : 00000000`00000000 ffff9407`fcffda60 fffff802`65b7f339 00000000`00000002 : Wdf01000!FxIoQueue::processCancelledRequests+0x49
fffff802`65b7f2c0 fffff809`332196e5 : ffff9407`fcffda60 ffff9408`000b5a02 00000000`00000000 ffff9407`fcffda60 : Wdf01000!FxIoQueue::DispatchEvents+0xc16
fffff802`65b7f3a0 fffff809`332172fb : ffff9407`00000001 fffff809`00000000 00000000`00000002 00006bf8`0a728498 : Wdf01000!FxRequest::CompleteInternal+0x305
fffff802`65b7f460 fffff809`38d79bad : 00000000`ffffff02 ffff9407`f58d7b60 ffff9407`fcffdea0 ffff9407`f58d7d00 : Wdf01000!imp_WdfRequestComplete+0x8b
fffff802`65b7f4c0 fffff809`38d781d0 : ffff9407`fcffde40 ffff9407`fdc43190 ffff9407`f58d7d00 ffff9407`f58d7e60 : USBXHCI!Isoch_Transfer_CompleteCancelable+0x1f1
fffff802`65b7f520 fffff809`38d77540 : ffff9407`f58d7d00 ffff9407`00000001 ffff9407`f58d7d00 ffff9407`fcffde01 : USBXHCI!Isoch_Stage_CompleteTD+0x248
fffff802`65b7f5b0 fffff809`38d75ca0 : fffff802`612e1f00 fffff802`00000000 ffff9407`feb9d250 fffff802`6226b492 : USBXHCI!Isoch_ProcessTransferEventWithED1+0x278
fffff802`65b7f650 fffff809`38d712c3 : ffff3374`2aa7f721 ffff9407`f7e5d000 00000000`00000000 00000000`00f1bd38 : USBXHCI!Isoch_EP_TransferEventHandler+0x10
fffff802`65b7f680 fffff809`38d64608 : 00000000`00000000 00000000`00000004 ffff9407`f6419ff0 fffff802`65b7f781 : USBXHCI!TR_TransferEventHandler+0x17
fffff802`65b7f6b0 fffff809`38d837ae : fffff802`65b7f818 fffff802`65b7f7e8 00000000`00000000 fffff802`65b7f7f0 : USBXHCI!Endpoint_TransferEventHandler+0x148
fffff802`65b7f740 fffff809`38d6744d : ffff9407`f6419f20 fffff802`65b7f839 ffff9407`f6419ff0 000000c4`ffd11ce7 : USBXHCI!UsbDevice_TransferEventHandler+0x92
fffff802`65b7f7a0 fffff809`38d67e6c : fffff802`65b7f8f0 ffff9407`f63cc000 00000000`00000000 ffff9407`f6419d20 : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
fffff802`65b7f8a0 fffff809`33211fad : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000004 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff802`65b7f8d0 fffff802`62265cc7 : fffff802`65b7fa00 00000000`00000000 00000000`00040001 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d
fffff802`65b7f910 fffff802`6226531b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e7
fffff802`65b7fa50 fffff802`623a23aa : 00000000`00000000 fffff802`612dc180 00000000`001a6560 fffff802`62681400 : nt!KiRetireDpcList+0x1db
fffff802`65b7fc60 00000000`00000000 : fffff802`65b80000 fffff802`65b7a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a



MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image


STACK_COMMAND: .cxr 0x508b480002e20a85 ; kb


Followup: MachineOwner

*** Memory manager detected 48271 instance(s) of page corruption, target is likely to have memory corruption.


The most typical causes for the ‘0xC0000005: Access Violation’ error are: corrupt registry, malware, faulty RAM or device driver, incorrectly written, installed or updated software or even Windows security features.

How to fix the 0xC0000005 error
0xc0000005 error case 1: Registry

The 0xC0000005 error is often caused by poor maintenance of your computer and corrupt registry entries that pile up as you install and delete programs, especially when you install new programs over old ones that were not completely deleted. To get rid of the 0xC0000005 error you could check all the registry entries manually but this procedure is long and complicated. If you are not a computer expert checking your registry manually may take a few days. In addition, you may damage important registry entries. So if you are not a PC guru use special software to repair your registry.

0xc0000005 error case 2: Virus

Your computer may have a virus and the 0xC0000005 error informs that the system prevented execution of a malicious application. Install the latest

0xc0000005 error case 3: Bad RAM Memory

Quite often this problem results from a faulty RAM memory. This is most likely the reason if you started getting the 0xC0000005 error message after installing a new RAM memory. To check this you can remove the new memory and see if the 0xC0000005 error disappears. If so, get a refund or ask to replace the faulty memory with a good one.
Don’t forget to do the following before you start removing the memory:
1) Turn off your computer and remove all cables (power, network, etc.)
2) Remove the battery (if you have a laptop)
3) Ground yourself out before you touch the memory!!(for example, touch metal screw on a lightswitch).

my dad said 90% of BSOD come from faulty drivers and memory so I ran memtest86 for 15 hours on my computer but it did not pick up any errors.
Your dad sounds like me. So its not error cause 3. Try error cause 2 (scan for viruses) and see below to update drivers.

Did you download and run MSI live update 6? It would check for out of date drivers, given it was updated on May 21 2018 it should get the latest.

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)


Jun 5, 2017
Please do the following to provide additional information
- Go to and download the SysnativeBSODCollectionApp.exe
- Run the tool and give it approx. 10-20 minutes to finish, on some machines it may take some time
- When the tool is finished, it will have created a zip file on your desktop and open the desktop folder and a file called BSODPostingInstructions.txt. Upload the zip file ton onedrive, google drive or dropbox and post a share link.