Windows 10: How do I read/analyze this dump file so I know what is causing the BSO

I built a pc last week and I get the BSOD after a few minutes of playing any game I try. I only have the last dump file I got because the BSOD before the last wouldn't let me start my pc in safe mode or restore to a previous date so I had to reinstall windows 10. Here is my dump file, I know how to open it but I don't know how to analyze it and figure out what is causing the BSOD
here is my build
bk - Saved Part Lists - PCPartPicker


Thanks in advance!!!

:)

 

PC Crashing How do I analyze the dumps?

Ok in that case im going to install all my hardware drivers now to the latest versions with DriverView and see If i get any crashes while on every day use. Thanks again.

 

PC Crashing How do I analyze the dumps?

cmudaxp.sys dated 6/2/2015 C-Media Audio Driver

BugCheck C4, {2000, fffff80adb061377, 0, 494e4950}

Probably caused by : cmudaxp.sys ( cmudaxp+2e1377 )

I would first update that and the other major drivers using the exact manual described in my previous reply.

Video drivers sometimes need to be reverted back to a stable version. Thought that may not be required in this case.

------

If decide to Clean Install - If you do a Clean Installation that should fix the issue if is software. If not fixed then odds are it is a hardware problem.

If you do a Clean Install then it would be activated with the Digital Entitlement.

How to Prepare Bootable Install Media for Windows 10 - DVD, USB or SD Card

https://answers.microsoft.com/en-us/windows/for...

Start fresh with a clean installation of Windows 10

https://www.microsoft.com/en-us/software-downlo...

Clean Install Windows 10

http://answers.microsoft.com/en-us/windows/wiki...

Let us know how it is going.

 

Your dumpfile is a shortcut

Please use the BSOD posting instruction to provide theDumpfile BSOD - Posting Instructions - Windows 10 Forums
And fill in your System Specs.

 

Proper installing software for opening dump files tutorial
WinDBG - Install Configure - Windows 10 Forums

Basic analysis tutorial
WinDBG - The Basics for Debugging Crash Dumps in Windows 10 - Windows 10 Forums

 

I updated my specs and added the correct zip file with the minidump just like in the tutorial. I have more information, I ran memtest86 last night for hours and I got back zero errors with a number of passes, so I don't think the ram is the problem. Today I removed my video card and am in the process of installing starcraft 2 to see if the game crashed with integrated graphics.

 

I was able to play starcraft 2 for about 40 minutes without the gpu and with no problems, when I used the gpu the game would crash within the first 15 minutes and get the bsod

 

The dumpfile is
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff6befef46888, 2, 0, fffff800e9e6fa62} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+302 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: fffff6befef46888, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800e9e6fa62, address which referenced memory Debugging Details: ------------------ 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 fffff6befef46888 CURRENT_IRQL: 2 FAULTING_IP: nt!MiAgeWorkingSet+302 fffff800`e9e6fa62 498b1e mov rbx,qword ptr [r14] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: ShellExperienc ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre TRAP_FRAME: ffffd000f7fb3220 -- (.trap 0xffffd000f7fb3220) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000800000000000 rbx=0000000000000000 rcx=ffffe00201a71d40 rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000 rip=fffff800e9e6fa62 rsp=ffffd000f7fb33b0 rbp=ffffd000f7fb34b0 r8=8000000000000000 r9=0000007ffffffff8 r10=0000098000000000 r11=0000058000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!MiAgeWorkingSet+0x302: fffff800`e9e6fa62 498b1e mov rbx,qword ptr [r14] ds:00000000`00000000=0000000000000000 Resetting default scope LAST_CONTROL_TRANSFER: from fffff800e9f572e9 to fffff800e9f4c770 STACK_TEXT: ffffd000`f7fb30d8 fffff800`e9f572e9 : 00000000`0000000a fffff6be`fef46888 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd000`f7fb30e0 fffff800`e9f55ac7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffffd000`f7fb3220 fffff800`e9e6fa62 : 00000003`00000000 ffffe002`01c9a580 bb200002`6e5b3205 00000000`00000409 : nt!KiPageFault+0x247 ffffd000`f7fb33b0 fffff800`e9e3a4fa : ffffe002`01a71d40 ffffe001`fb2192a0 ffffe002`01a71d40 00000000`00000000 : nt!MiAgeWorkingSet+0x302 ffffd000`f7fb3700 fffff800`e9e39f4b : 00000000`00000000 ffffd000`f7fb3980 ffffd000`f7fb38b0 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x15a ffffd000`f7fb37b0 fffff800`e9e19b23 : fffff800`00000000 00000000`00000000 00000000`0000012a 00000000`00000002 : nt!MiProcessWorkingSets+0x1fb ffffd000`f7fb3960 fffff800`e9f302f9 : 00000000`00000006 00000000`00000006 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xa7 ffffd000`f7fb3a20 fffff800`e9e13125 : ffffe001`fb348040 00000000`00000080 fffff800`e9f301a8 004c004f`0050020c : nt!KeBalanceSetManager+0x151 ffffd000`f7fb3b10 fffff800`e9f51916 : ffffd000`f7e40180 ffffe001`fb348040 fffff800`e9e130e4 01d15334`f0f9dec8 : nt!PspSystemThreadStartup+0x41 ffffd000`f7fb3b60 00000000`00000000 : ffffd000`f7fb4000 ffffd000`f7fad000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiAgeWorkingSet+302 fffff800`e9e6fa62 498b1e mov rbx,qword ptr [r14] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiAgeWorkingSet+302 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 568b1c58 IMAGE_VERSION: 10.0.10586.63 IMAGE_NAME: memory_corruption BUCKET_ID_FUNC_OFFSET: 302 FAILURE_BUCKET_ID: AV_nt!MiAgeWorkingSet BUCKET_ID: AV_nt!MiAgeWorkingSet ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_nt!miageworkingset FAILURE_ID_HASH: {a2dd9c19-c4fc-761b-f40a-b8172b183d05} Followup: MachineOwner[/quote] The dumpfile does not point to something specific.
Also your drivers/ modules are all from 2015.

Maybe Driver Verifier will give the name of the offending driver(s).
You can enable "DriverVerifier" according to instructions from the below link.Enable and Disable Driver Verifier in Windows 10
"Verifier" is a Microsoft's own tool to stress test third partydrivers and find the buggy one. If it detects a violation, a blue screen willbe created immediately and the dump will give us the name of offending driverstraight forward. After enabling "Verifier" , system will be a bitslow and laggy during to the background verification process. After you got twoor more blue screens, please upload the new crash dumps and we will knowwhether the issue is caused by third party drivers or low level hardware (averifier enabled dump which blames Windows system files is a clear confirmationof hardware problem).
"Verifier" should be only used to monitor third party drivers.Selecting Microsoft system drivers is totally unnecessary and doing so may make the system nonbootable.
Additional:
(Check if your system is set to make Small memory dumps. If not read these instructions from the below link and set "Windows"to write "Small Memory dumps".
SetMiniDump ).

Or it could be that your Amd GPU is faulty.

 

The dumpfile does not point to something specific.
Also your drivers/ modules are all from 2015.

Maybe Driver Verifier will give the name of the offending driver(s).
You can enable "DriverVerifier" according to instructions from the below link.Enable and Disable Driver Verifier in Windows 10
"Verifier" is a Microsoft's own tool to stress test third partydrivers and find the buggy one. If it detects a violation, a blue screen willbe created immediately and the dump will give us the name of offending driverstraight forward. After enabling "Verifier" , system will be a bitslow and laggy during to the background verification process. After you got twoor more blue screens, please upload the new crash dumps and we will knowwhether the issue is caused by third party drivers or low level hardware (averifier enabled dump which blames Windows system files is a clear confirmationof hardware problem).
"Verifier" should be only used to monitor third party drivers.Selecting Microsoft system drivers is totally unnecessary and doing so may make the system nonbootable.
Additional:
(Check if your system is set to make Small memory dumps. If not read these instructions from the below link and set "Windows"to write "Small Memory dumps".
SetMiniDump ).

Or it could be that your Amd GPU is faulty.[/quote] I got another bsod while having driver verifier enabled with the instructions you provided, I attached another zipfoler (-Fri_01_22_2016__00516_16) I think it also contains the previous dump file but it definitely has the dump file that was created when driver verifier was running.

 

The new dumpfile is not a driver verifier enabled dumpfile, probably the bsod became before Driver Verifier started.
Code: Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {ffffdff040601700, 8000000001c80121, ffffd00022a073b0, a} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4418b ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: ffffdff040601700, Virtual address for the attempted write. Arg2: 8000000001c80121, PTE contents. Arg3: ffffd00022a073b0, (reserved) Arg4: 000000000000000a, (reserved) Debugging Details: ------------------ DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: ACS.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre TRAP_FRAME: ffffd00022a073b0 -- (.trap 0xffffd00022a073b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000042 rsi=0000000000000000 rdi=0000000000000000 rip=fffff802b9c4fd0c rsp=ffffd00022a07540 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0020100000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy nt!MiInsertPageInFreeOrZeroedList+0x21c: fffff802`b9c4fd0c f0480fc1ae00170000 lock xadd qword ptr [rsi+1700h],rbp ds:00000000`00001700=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff802b9d9928b to fffff802b9d46770 STACK_TEXT: ffffd000`22a071e8 fffff802`b9d9928b : 00000000`000000be ffffdff0`40601700 80000000`01c80121 ffffd000`22a073b0 : nt!KeBugCheckEx ffffd000`22a071f0 fffff802`b9c3d738 : fffffa80`0073e3c0 ffffd000`22a07340 ffffdff0`40600000 fffffd80`00001d58 : nt! ?? ::FNODOBFM::`string'+0x4418b ffffd000`22a07240 fffff802`b9d4f9bc : 00000000`00000001 fffffa80`006fbe80 00000000`00000042 00000000`00000000 : nt!MmAccessFault+0xbe8 ffffd000`22a073b0 fffff802`b9c4fd0c : fffffd80`000016f8 fffff802`b9f01280 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c ffffd000`22a07540 fffff802`b9ccbc37 : 00000000`00026a14 00000000`00000042 00000000`00000070 ffffe001`a5492b40 : nt!MiInsertPageInFreeOrZeroedList+0x21c ffffd000`22a07610 fffff802`b9c65a20 : fffffd80`00003800 ffffd001`00000000 00000000`00000002 00000000`000000c2 : nt!MiInsertLargePageInFreeOrZeroList+0xd7 ffffd000`22a07660 fffff802`b9c655da : 00000000`00000002 fffff802`00000070 00000000`00000000 fffff802`b9cd39f2 : nt!MiGetFreeOrZeroPage+0x370 ffffd000`22a076d0 fffff802`b9c638f3 : fffff802`b9f00bc0 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MiGetPage+0x7a ffffd000`22a07740 fffff802`b9c3cfe1 : 00000000`00000002 00000000`adbf9000 ffffd000`22a07a00 fffff680`0056dfc8 : nt!MiResolveDemandZeroFault+0x323 ffffd000`22a07890 fffff802`b9d4f9bc : ffffe001`a5b7f080 ffffe001`a5d79080 00000000`13524e78 00000000`00000020 : nt!MmAccessFault+0x491 ffffd000`22a07a00 00007fff`d67454bf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c 00000000`1ba0f790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`d67454bf STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4418b fffff802`b9d9928b cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4418b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 568b1c58 IMAGE_VERSION: 10.0.10586.63 BUCKET_ID_FUNC_OFFSET: 4418b FAILURE_BUCKET_ID: 0xBE_nt!_??_::FNODOBFM::_string_ BUCKET_ID: 0xBE_nt!_??_::FNODOBFM::_string_ ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!_??_::fnodobfm::_string_ FAILURE_ID_HASH: {463ab379-ba7d-e86a-84c4-449f00e9fb43} Followup: MachineOwner ---------[/quote] Usual causes: Device driver, Memory
Your other dumpfiles also mentioned memory corruption
Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+"to stress test the RAM.

How to run "Memtest" - RAM -Test with Memtest86+ - Windows 7 Help Forums

Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory DiagnosticTool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.

These drivers predates windows 10, please update from supportpage mobo http://www.asrock.com/mb/Intel/Z170%...oad&os=Win1064
Also update all your other current drivers to the latest versions on this page.

e1d65x64 Thu Jun 18 18:37:56 2015
Driver Description: Intel(R) Gigabit Adapter NDIS 6.x driverDriver Update Site: http://downloadcenter.intel.com

iaStorA Mon Jul 27 11:26:48 2015
Driver Description: Intel RST (Rapid Storage Technology) driver
Driver Update Site: Drivers & Software

See if there are newer drivers avaliable
LGBusEnum Fri Apr 24 23:21:00 2015
LGJoyXlCore Fri Apr 24 23:20:57 2015
Both logitech devices

lgcoretemp Tue Jun 09 18:52:10 2015
Coretemp

 

Usual causes: Device driver, Memory
Your other dumpfiles also mentioned memory corruption
Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+"to stress test the RAM.

How to run "Memtest" - RAM -Test with Memtest86+ - Windows 7 Help Forums

Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory DiagnosticTool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.

These drivers predates windows 10, please update from supportpage mobo http://www.asrock.com/mb/Intel/Z170%...oad&os=Win1064
Also update all your other current drivers to the latest versions on this page.

e1d65x64 Thu Jun 18 18:37:56 2015
Driver Description: Intel(R) Gigabit Adapter NDIS 6.x driverDriver Update Site: http://downloadcenter.intel.com

iaStorA Mon Jul 27 11:26:48 2015
Driver Description: Intel RST (Rapid Storage Technology) driver
Driver Update Site: Drivers & Software

See if there are newer drivers avaliable
LGBusEnum Fri Apr 24 23:21:00 2015
LGJoyXlCore Fri Apr 24 23:20:57 2015
Both logitech devices

lgcoretemp Tue Jun 09 18:52:10 2015
Coretemp[/quote] I ran memtest86 (5.01) two nights ago for several hours got to 7 passes and it said zero errors

 

I decided to try driver verifier again and 6 hours in (still running) no crashes or bsod, pc is still running like normal, like i mentioned before I ran memtest86 (version 5.01 and no errors came up after several passes, does this mean there are no issues with my drivers? I don;t have realtek audio installed could that be causing a problem? If I play a game in safe mode and it crashes could that mean that it is a gpu hardware problem?

 

You need to run driver verifier for 48h hours, 6 hours doesn't mean the drivers are fine.

 

Updating the motherboard bios is what fixed the issue.

 

That's good to know, thanks for the update.