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.

Photo

Multiple BSOD, different causes every time, please help.


  • Please log in to reply
1 reply to this topic

#1 phil0sophy

phil0sophy

  • Members
  • 46 posts
  • OFFLINE
  •  
  • Local time:01:02 PM

Posted 02 January 2017 - 03:21 PM

I am at a complete loss as to what could be causing this now, it's a different reason every single time, have also used driver verifier on multiple occasions as well, I have tested my ram, have tested my hard drive, have tested my temps, everything is working perfectly fine from a hardware perspective.

 

Honestly I am at my wits end with it, it's clearly a driver accessing the kernel or something, this has been happening since the last windows update (I refuse to update windows 10 again because everytime I do it just installs more bad drivers and gives me more BSOD.)

 

Anyway, I have attached the sys files as requested but for some reason it won't allow me to run perfmon report as it throws up the following error:

 
"The Data Collector Set or one of its dependencies is already in use." what could be causing that?
 
*Edit* Managed to fix the perfmon issue, deleted the perfmon folder with all the older logs and now it's working, have attached that file also.

Attached Files


Edited by phil0sophy, 02 January 2017 - 03:42 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 05 January 2017 - 07:47 AM

Different BSOD errors usually mean a hardware, compatibility, or low-level driver problem.

BSOD's occur due to problems in the kernel space - where drivers do their work.  But they can either be due to hardware or software

Driver Verifier stresses drivers and causes BSOD's.  Depending on the settings that you used, it may not tell you anything if it's not a driver that's being tested that's at fault (as is the case of a hardware problem).

You have tested RAM/Hard Drive/temps - that is not all of the hardware on your system - there is plenty of hardware left to test, and there's plenty of hardware that doesn't even have test software for it.

Finally, I start each analysis with asking you to update Windows to it's fullest.  If you refuse to do this, then I'm afraid that there's nothing that I can do to help you.

 

All of this not withstanding, I will offer an initial analysis that will (I hope) get you pointed in a good direction......

 

Only 6 Windows Update hotfixes installed.  Most build 14393 (1607) 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.
 

Your UEFI/BIOS (version 4206) dates from 2013.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Your wireless network adapter is disabled.
Please enable it, then update it's drivers.  Feel free to disable it again AFTER you have updated the drivers

The drivers load when Windows starts - and are still loaded when the device is disabled in Device Manager.

 

Corsair Link software is known to cause BSOD's on some Windows systems.

Please uninstall it while we are troubleshooting.

Feel free to reinstall a freshly downloaded, W10 compatible version to install AFTER we are finished troubleshooting.

 

Out of 14 memory dumps there were 9 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 ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results

The CAM_V3.sys driver dates from 2008 and may not be compatible w/W10.  I've seen a couple of these recently, and believe that this might be a sign that these are no longer compatible w/W10.

This driver likely belongs to the CAM software from NZXT - so please uninstall it and see if that stops the BSOD's

FYI - this program also uses the WinRing library drivers - which have also been known to cause BSOD's on some Windows systems.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
[QUOTE]**************************Mon Jan  2 15:00:03.686 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010217-26484-01.dmp]
Windows 10 Kernel Version 14393 MP (12 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:0 days 0:09:30.436
*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+20020 )
BugCheck 1A, {61941, 223a41f2a25, 9, ffff838092786260}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 00000223a41f2a25
Arg3: 0000000000000009
Arg4: ffff838092786260
BUGCHECK_STR:  0x1a_61941
PROCESS_NAME:  wevtutil.exe
FAILURE_BUCKET_ID: 0x1a_61941_VRF_nt!_??_::FNODOBFM::_string_
CPUID:        "Intel® Core™ i7-3970X CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  4206
  BIOS Release Date             07/05/2013
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             RAMPAGE IV EXTREME
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 14:39:55.449 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010217-15812-01.dmp]
Windows 10 Kernel Version 14393 MP (12 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:0 days 6:12:04.146
Probably caused by :ntkrnlmp.exe ( nt!_report_gsfailure+25 )
BugCheck F7, {ffffc181a94fa890, bab423feedbb, ffff454bdc011244, 0}
BugCheck Info: DRIVER_OVERRAN_STACK_BUFFER (f7)
Arguments:
Arg1: ffffc181a94fa890, Actual security check cookie from the stack
Arg2: 0000bab423feedbb, Expected security check cookie
Arg3: ffff454bdc011244, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
BUGCHECK_STR:  0xF7
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure
CPUID:        "Intel® Core™ i7-3970X CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  4206
  BIOS Release Date             07/05/2013
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             RAMPAGE IV EXTREME
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  1 07:26:31.271 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010117-14359-01.dmp]
Windows 10 Kernel Version 14393 MP (12 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:0 days 0:04:31.966
Probably caused by :GenuineIntel
BugCheck 124, {0, ffffe10b306c8028, be000000, 800400}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe10b306c8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
CPUID:        "Intel® Core™ i7-3970X CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  4206
  BIOS Release Date             07/05/2013
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             RAMPAGE IV EXTREME
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler


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:

**************************Mon Jan  2 15:00:03.686 2017 (UTC - 5:00)**************************
CAM_V3.sys                  Sat Jul 26 09:29:37 2008 (488B26C1)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
iaStorA.sys                 Fri May  2 19:06:56 2014 (53642510)
e1c65x64.sys                Sun Feb 15 08:39:57 2015 (54E0A1AD)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
TeeDriverW8x64.sys          Mon Jun 29 13:22:00 2015 (55917EB8)
mt7612US.sys                Wed Dec  9 01:44:11 2015 (5667CDBB)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
xboxgip.sys                 Fri Jul 15 22:27:49 2016 (57899BA5)
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
DevAuthE.sys                Fri Jul 15 22:29:16 2016 (57899BFC)
xinputhid.sys               Sat Aug 20 01:20:50 2016 (57B7E8B2)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 14:39:55.449 2017 (UTC - 5:00)**************************
WinRing0x64.sys             Wed May  1 22:19:47 2013 (5181CD43)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  1 07:26:31.271 2017 (UTC - 5:00)**************************
WinRing0x64.sys             Sat Jul 26 09:29:37 2008 (488B26C1)
iqvw64e.sys                 Wed Apr 22 07:46:58 2015 (55378A32)
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 31 16:15:32.459 2016 (UTC - 5:00)**************************
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 30 16:19:03.920 2016 (UTC - 5:00)**************************
BthHfAud.sys                Fri Jul 15 22:18:21 2016 (5789996D)
BthA2DP.sys                 Thu Sep 15 12:41:53 2016 (57DACF51)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  3 10:38:32.180 2016 (UTC - 5:00)**************************
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)


CAM_V3.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.
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
e1c65x64.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.
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
mt7612US.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.
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=xboxgip.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
DevAuthE.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.
xinputhid.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.
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=BthHfAud.sys
http://www.carrona.org/drivers/driver.php?id=BthA2DP.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
 
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