Can someone help me analyze some .dmp files that are causing bluescreens on my PC?

I built my first gaming rig in january 2013, and everything went well.

However about 2 days later i recieved my first BS0Ds, which was very dissapointing.

I neglected to fix the issues and now all these BSODS are driving me crazy.

I don't know how to analyze dmp files so any help would be much appreciated.

Besides the minidumps that windows collects i also have many errors & criticals in my event log but don't know how to resolve any. Any help with those will be appreciated. Thanks to all in advance.

Dropbox link/ Screenshot to dmp filese:

Seven Forum dmp viewr (.zip) :

Text list of all dmp filese:


I don't know hot to analyze those minidumps (sorry - primarily Linux guy, here), but when I installed Windows on my most recent build (built in December), I also had BSOD problems. For me, they were random, but always happening. It was a problem with my RAM, for me. Are you running them in the appropriate/recommended slots for your motherboard? Try using just one stick, then try just using the other. Try all 4 slots this way, and if the slots are all working, with both sticks of RAM, then it may be an OC/Voltage issue. Have you OCed your CPU, at all? It may need more voltage for your OC, or it may be throttling. Same goes for the GPU; may be overheating, or not have enough voltage/power. Did you manually set your memory timings/frequency/voltage, or are you using the XMP profiles?

Thanks for the thorough list of options.

- I have an mATX motherboard so i only have 2 ram slots; which are both filled with some 1600hz 8gb   patriots memory which my motherboard easily overclocked to 1866, however these problems were happenening way before i overclocked anything. I never manually overclocked my cpu, because my motherboard has preinstalled overclock percentage settings which does it for me. as for my gpu, i use AMD Vision Control Center to overclock but everything is at its default including my cpu and ram.  

-When playing games such as BF3 or FarCry 3 heavy demanding games my gpu and cpu would go up to 40C and sometimes but barely ever reach 50C never over. 


Any more suggestions

I dont download zip files use and post a screen shot of the bsod error 

Sure, however i used sevenforums .dmp tool file since i already have it and it does the sam thing.

Sorry about that i updated and added a link with the software you recommeneded. 


hey, just tell me the STOP code that shows up when the bsod happens. it will loke something like

STOP 0x######## (xxxxxxx,.....,.....,......)

just tell me what the #'s are and the x's are

I know what stop codes are, ive seen them in the BSODS before but i don't know how to find them. Event viewer only shows the event ID and sourece as well as the process that caused it sometimes.

reboot your computer, after the bios screen, but before the windows loading screen, press F8. (if your bios screen doesnt use f8, you can just spam it)


disable automatic rebooting... that way when you get a bsod, it doesnt restart in 2 seconds.

now go do whatever causes the bsod.

write it down.

post here.

i'll do it through my sysnative debugger.

ok, first off, ~70% of these are memory corruption error, dl and run memtest x86+. if there are any errors, post back. there are also some old/bad drivers:

ae1000w7.sys Fri Jan 15 02:15:48 2010 (4B502434)

Linksys AE1000 High-Performance Wireless-N Adapter

AsrAppCharger.sys Tue May 10 03:28:46 2011 (4DC8F73E)

ASRock App Charger Likely BSOD cause - haven't seen recently (15Jan2013)

AODDriver2.sys Tue Sep 6 02:11:44 2011 (4E65C7B0)

AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7

Rt630x64.sys Wed Oct 19 07:12:55 2011 (4E9EBEC7)

Realtek PCI/PCIe Adapters


summary of the bugcheck codes:

BugCheck 1E, {ffffffffc0000005, fffff8001e4efe2c, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+8c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 50, {fffff901080bf5b4, 0, fffff96000862802, 2} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c000001d, fffff96000120496, fffff8800e4c70c0, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck C2, {7, 11c1, 0, fffffa8007ed0778} <br />Probably caused by : Ntfs.sys ( Ntfs!ExFreeToNPagedLookasideList+3f ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 7F, {8, fffff880009cbd30, fffff8800d020fc0, fffff800b571351b}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck BAD0020, {8, fffff8800bbdf8f0, fffff8800bbdf198, fffff8800bbde9d0} <br />Probably caused by : klif.sys ( klif+5129a ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c000001d, fffff800536991ce, fffff8800e158e90, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 3B, {c0000005, fffff80074859f87, fffff880100e7db0, 0} <br />Probably caused by : win32k.sys ( win32k+2398d ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000096, fffff88009c09c0c, fffff8800e0f6c20, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 50, {fffff90100381000, 0, fffff9600009ba20, 0} <br />Probably caused by : win32k.sys ( win32k!memcpy+a0 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 7F, {8, fffff8003abe4e70, fffff8800bda8fc0, fffff8003af1351b}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 50, {fffff6fb40000000, 0, 0, 6} <br />Probably caused by : CI.dll ( CI!MinCrypK_TrimMemory+ab ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff88002177647, fffff8800e3669c8, fffff8800e366200}
Probably caused by : NETIO.SYS ( NETIO!PtEnumOverTable+d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 1000007E, {ffffffffc000001d, fffff88009a84ffd, fffff8800e367078, fffff8800e3668b0} <br />Probably caused by : ae1000w7.sys ( ae1000w7+14ffd ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff8800205c466, fffff88010186900, 0}
Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+145 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 109, {a3a039d89d68ba8e, b3b7465eefe727e2, fffff880020d02b8, 1} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff801def410ed, fffff8800d01edb0, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+1d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 1000007E, {ffffffffc0000005, fffff8800930109a, fffff8800adb7278, fffff8800adb6ab0} <br />Probably caused by : atikmdag.sys ( atikmdag+f309a ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff88001c1d647, fffff8800e5269c8, fffff8800e526200}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 3B, {c0000005, fffff8010d72f0e5, fffff8800f4e6bc0, 0} <br />Probably caused by : memory_corruption ( nt!MiGetNextNode+15 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff96000287ca6, fffff8800e87e080, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck D1, {fffff80204957a1c, 2, 8, fffff80204957a1c} <br />Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+261 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff8800939109a, fffff8800f8bf278, fffff8800f8beab0}
Probably caused by : atikmdag.sys ( atikmdag+f309a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck D1, {2, 2, 1, fffff88001b734fd} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89b5df6a7, b3b7465eeddc6064, fffff8800187f1e0, 1}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 7A, {1, ffffffffc0000005, fffffa800a02e940, fffff6803d07d000} <br />Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+26a30 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 109, {a3a037d8a172752b, b3b7445ef3f0def8, fffff8800183c1d8, 1} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 24, {b50019060b, fffff88003128d88, fffff880031285c0, fffff80039f30108} <br />Probably caused by : ntkrnlmp.exe ( nt!IopQueueThreadIrp+58 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 109, {a3a039d899f4fc27, b3b7465eec7365f4, fffff880018571d8, 1} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 109, {a3a039d89d68b998, b3b7465eefe79c2d, fffff880017280c0, 1} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 24, {b50019060b, fffff8800ef88008, fffff8800ef87840, fffff803f6af7d35} <br />Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 109, {a3a039d89910f5ad, b3b7465eeb8f5f6a, fffff880018b61d8, 1} <br />Probably caused by : memory_corruption <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck 3B, {c0000005, fffff9600030351f, fffff8800b1c4f00, 0} <br />Probably caused by : win32k.sys ( win32k+1bc51f ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ <br />BugCheck AB, {1, 31e10, 0, 4af} <br />Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+3619a ) <br />¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Sorry about that i didi a chkdsk scan first which took foreveeerrrr.

So eventually i got to run mem test  ran s an error in on test and listed it as having 10 errors, then on the second one it started getting more errors faster. Within 5 min i had 60 errors then in about 3 more mins it jumps to 6300 errors.

I'm a bit frustrated now and assume the only thing i could do is spend more money and buy new memory.

thank you alot for the analysis though.

Going to try one stick at time now in meme test.

Just finished running memtest. So i placed in my first stick of ram and it ran fine in both slots. Then i placed my second stick and as expected i received 10 errors however i tested it in the other slot and fine. No erro

As for the wireleess adapter i guess ill try getting an ethernet, I'll unistall the appcharger but i don't know what is the relteck pci adapter.

Any ideas?