Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD Diagnosis

  • Please log in to reply
1 reply to this topic

#1 nblanton


  • Members
  • 1 posts
  • Local time:04:55 PM

Posted 04 June 2016 - 10:29 AM

Win 10 Pro




I believe this system is an update from Win 8->Win 8.1->Win 10. Possibly all the way back to Win 7. Been a while and can't remember exactly the last time it was completely virgin. 

Retail version


Hardware of various ages, most less than 2 years old. Oldest component in system 2 WD Black 500gb that are from 2009ish. 


Can't remember the last time I did a complete fresh install. Probably around 2012.

i7 4770k


Sapphire NITRO Radeon R9 Fury


ASRock Fatal1ty Z87 Killer


Corsair AX760i 760W

Lots of BSODs, tried a lot of things hardwarewise without any luck (delidded the i7, ran Memtest86, added watercooler-Corsair H100i-, upgraded PS, video card,...) but I've never able to get a stable system.  I thought I was having a temperature issue, hence the work to get the i7 down cooler and cooler. Delidding definitely helped, as prior to that I wasn't able to run PassMark. I can now run it without exceeding 80C. However, I've still had fairly persistent BSODs. Hoping to get an answer. I'm leaning towards either video drivers or CorsairLink causing the problems, but I have no basis for that at all.

Thanks in advance!



Attached Files

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:55 PM

Posted 05 June 2016 - 05:49 AM

Your UEFI/BIOS (version P1.60) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a recent update.

Only 4 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Out of 14 memory dumps there were 7 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Additionally, at least one of the memory dumps directly blames hardware.

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html


Also, please be sure that you've turned Driver Verifier off.

To do this, open up verifier.exe and select "Delete existing settings", then click on "Finish" and reboot for the settings to take effect.



The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Fri Jun  3 19:42:21.303 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\060316-9328-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
System Uptime:3 days 23:46:24.043
Probably caused by :ntkrnlmp.exe ( nt!CmpParseKey+19e8 )
BugCheck 3B, {c0000005, fffff80362a7c978, ffffd000654d7920, 0}
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80362a7c978, Address of the instruction which caused the bugcheck
Arg3: ffffd000654d7920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  CorsairLink4.S
CPUID:        "Intel® Core™ i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3499
  BIOS Version                  P1.60
  BIOS Release Date             04/28/2015
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z87 Killer
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Fri Jun  3 19:42:21.303 2016 (UTC - 4:00)**************************
AsrAppCharger.sys           Tue May 10 04:28:46 2011 (4DC8F73E)
AsrDrv101.sys               Tue Jan 15 01:25:51 2013 (50F4F66F)
AsrRamDisk.sys              Thu May  9 04:50:45 2013 (518B6365)
usbaapl64.sys               Thu Jun 11 02:08:10 2015 (557925CA)
TeeDriverW8x64.sys          Thu Jun 11 21:52:49 2015 (557A3B71)
RTKVHD64.sys                Wed Jul 15 06:16:44 2015 (55A6330C)
iaStorA.sys                 Mon Jul 27 05:26:48 2015 (55B5F958)
e22w10x64.sys               Fri Aug 28 17:05:38 2015 (55E0CD22)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
bwcW10x64.sys               Fri Nov 20 13:59:13 2015 (564F6D81)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
atikmpag.sys                Fri May 20 16:57:24 2016 (573F7A34)
amdacpksd.sys               Fri May 20 17:12:33 2016 (573F7DC1)
AtihdWT6.sys                Fri May 20 17:16:57 2016 (573F7EC9)
atikmdag.sys                Fri May 20 17:21:14 2016 (573F7FCA)
**************************Mon May 30 15:09:35.787 2016 (UTC - 4:00)**************************
AtihdWT6.sys                Mon Feb 15 19:20:29 2016 (56C26B4D)
atikmpag.sys                Fri Apr 29 14:49:22 2016 (5723ACB2)
amdacpksd.sys               Fri Apr 29 14:59:14 2016 (5723AF02)
atikmdag.sys                Fri Apr 29 15:25:32 2016 (5723B52C)
**************************Mon May 30 14:46:37.721 2016 (UTC - 4:00)**************************
AsrAutoChkUpdDrv.sys        Mon Mar 10 06:33:09 2014 (531D94E5)
**************************Fri May  6 08:42:26.785 2016 (UTC - 4:00)**************************
e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
atikmpag.sys                Fri Apr 15 16:10:56 2016 (57114AD0)
atikmdag.sys                Fri Apr 15 16:47:27 2016 (5711535F)


e22w10x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
cpuz139_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
AsrAutoChkUpdDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users