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

Constant BSODs after multiple hardware upgrades


  • Please log in to reply
16 replies to this topic

#1 Jayrpl

Jayrpl

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 08 November 2016 - 09:03 AM

OS - Windows 10
· x64
· What was original installed OS on system? Windows 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? 
Purchased from retailer - Windows 10 education edition
· Age of system (hardware)
CPU,CPU cooler, Mobo, RAM, PC case all brand new
· Age of OS installation - have you re-installed the OS?
reinstalled OS few days ago
· CPU
Intel i5 6600k
· Video Card
AMD R9 280X
· MotherBoard - (if NOT a laptop)
ASRock Z170 Extreme4
· Power Supply - brand & wattage (skip if laptop)
Not sure of brand - AC 230V 500W PSU
· System Manufacturer
Custom-built
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop?
Custom-built desktop
 
Hi All,
Been plagued with a numerous amount of BSODs after upgrading the main parts of my system. The stop codes have consisted of but not limited to the following: Bad pool header, irq_less_or_not_equal, Memory_management, System_error. I have run windbg to try and diagnose the cause of the crashes and found a faulty driver that avast used. Uninstalled avast and ran special pool on the driver in question just in case and haven't received a bad pool header since but have got every other error code anyway!
Might be important to note it usually happens while playing games, but has happened while using a game editor, watching online videos and just normal browsing.
 
Any help would be greatly appreciated as I'm at my wits end with this.
Thank you!
 
Attached File  SysnativeFileCollectionApp.zip   591.71KB   1 downloads
 
Note: Perfmon report is hanging on a full bar and can't get it to complete!
 
 

 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 09 November 2016 - 11:49 AM

Your UEFI/BIOS (version P3.20) dates from 2016.  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 more recent update.
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).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

F: drive has much less than 1% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.  Systems with as little free space as yours have been known to throw BSOD's because of the limited free space.

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

This is a difficult series of BSOD's to analyze.

There's signs that this might be a software problem, but there's also signs that it might be a hardware problem.

In short, this probably isn't going to be an easy one to pin down.

So, for starters:

 

Beyond this I have these 5 suggestions:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your system from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If ALL of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Please note the CAM_V3.sys driver - it dates from 2008.

It most likely belongs to CAM 3 Advanced PC monitoring software by NZXT
I'd suggest uninstalling it to see if that helps the BSOD's

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Nov  8 08:06:34.871 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110816-20890-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:1 days 18:57:02.532
*** WARNING: Unable to verify timestamp for win32kfull.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys
Probably caused by :memory_corruption
BugCheck 1A, {3470, ffffbe81c76cf000, 9ee2632c0defc82a, 9ee2662c0defc82a}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000003470, The subtype of the bugcheck.
Arg2: ffffbe81c76cf000
Arg3: 9ee2632c0defc82a
Arg4: 9ee2662c0defc82a
BUGCHECK_STR:  0x1a_3470
PROCESS_NAME:  SourceTree.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P3.20
  BIOS Release Date             04/08/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  5 16:53:07.403 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110516-22046-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:0 days 20:36:50.064
*** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
Probably caused by :fileinfo.sys ( fileinfo+d6df )
BugCheck 3B, {c0000005, fffff800fec93212, ffff8280d3796300, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800fec93212, Address of the instruction which caused the bugcheck
Arg3: ffff8280d3796300, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  ShooterGame-Win32-Shipping.exe
FAILURE_BUCKET_ID: 0x3B_VRF_fileinfo!unknown_function
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P3.20
  BIOS Release Date             04/08/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  4 15:01:42.344 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110416-51515-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:0 days 0:51:09.965
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+b9d )
BugCheck 19, {e, ffffc084f9113970, 8cf6c0fc2884136d, 8cf684fc2884136d}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 000000000000000e,
Arg2: ffffc084f9113970
Arg3: 8cf6c0fc2884136d
Arg4: 8cf684fc2884136d
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID: 0x19_e_nt!ExDeferredFreePool
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P3.20
  BIOS Release Date             04/08/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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:

**************************Tue Nov  8 08:06:34.871 2016 (UTC - 5:00)**************************
CAM_V3.sys                  Sat Jul 26 09:29:37 2008 (488B26C1)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
semav6msr64.sys             Fri Jan 24 14:22:40 2014 (52E2BD80)
IntelHaxm.sys               Thu Jan 29 21:02:09 2015 (54CAE621)
dtlitescsibus.sys           Thu Sep 24 16:17:21 2015 (56045A51)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
SeLow_x64.sys               Sun Oct 18 07:12:14 2015 (56237E8E)
Neo6_x64_VPN.sys            Sun Oct 18 07:12:27 2015 (56237E9B)
dtliteusbbus.sys            Mon Dec 28 08:05:52 2015 (568133B0)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
AtihdWT6.sys                Sun Jul 24 15:51:39 2016 (57951C4B)
VBoxUSBMon.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxNetLwf.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxDrv.sys                 Mon Sep 12 12:18:02 2016 (57D6D53A)
atikmpag.sys                Thu Nov  3 20:13:28 2016 (581BD2A8)
atikmdag.sys                Thu Nov  3 20:59:52 2016 (581BDD88)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  4 15:01:42.344 2016 (UTC - 5:00)**************************
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswKbd.sys                  Thu Aug 18 10:12:06 2016 (57B5C236)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
atikmpag.sys                Fri Sep 16 14:50:37 2016 (57DC3EFD)
atikmdag.sys                Fri Sep 16 15:12:45 2016 (57DC442D)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)


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=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=semav6msr64.sys
http://www.carrona.org/drivers/driver.php?id=IntelHaxm.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=SeLow_x64.sys
Neo6_x64_VPN.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.
dtliteusbbus.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=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.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.

#3 Jayrpl

Jayrpl
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 11 November 2016 - 09:59 PM

Updated my UEFI to the latest version

Ran memtest for over 8 passes with no errors

removed CAM and daemon tools - removed the sptd.sys file

 

I test it by trying to play a game, and it runs for maximum 20 minutes and gives me this BSOD.

 

Attached File  SysnativeFileCollectionApp.zip   749.7KB   2 downloads



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 16 November 2016 - 06:02 AM

Sorry for the delay in responding.  Real life is interfering with my internet life! :0)

Also having problems with the debugger - so those topics that need memory dump analysis are slower than others.

Will post back when the dumps are finished.......


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.

#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 16 November 2016 - 06:25 AM

Have you run the rest of the diagnostics that I suggested?  Have you monitored the temps on the system?

Here's a bit on how to monitor temps:

 

please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps - if uncertain, please ask.[quote]To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan[quote]Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.[/quote]
NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

 

Once that's done, run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Fri Nov 11 20:50:02.811 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111216-24671-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 4:42:59.471
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by :ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5819BD1F820000 )
BugCheck 1000007E, {ffffffffc0000005, fffff8037b7fada8, ffffa8010d9b70a8, ffffa8010d9b68d0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8037b7fada8, The address that the exception occurred at
Arg3: ffffa8010d9b70a8, Exception Record Address
Arg4: ffffa8010d9b68d0, Context Record Address
BUGCHECK_STR:  5819BD1F
PROCESS_NAME:  ntoskrnl.wrong.symbols.exe
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703_5819BD1F_nt_wrong_symbols!5819BD1F820000
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P7.00
  BIOS Release Date             09/09/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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 Nov 11 20:50:02.811 2016 (UTC - 5:00)**************************
semav6msr64.sys             Fri Jan 24 14:22:40 2014 (52E2BD80)
IntelHaxm.sys               Thu Jan 29 21:02:09 2015 (54CAE621)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
SeLow_x64.sys               Sun Oct 18 07:12:14 2015 (56237E8E)
Neo6_x64_VPN.sys            Sun Oct 18 07:12:27 2015 (56237E9B)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
tap0901.sys                 Thu Apr 21 05:10:05 2016 (571898ED)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
AtihdWT6.sys                Sun Jul 24 15:51:39 2016 (57951C4B)
VBoxNetLwf.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxUSBMon.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxDrv.sys                 Mon Sep 12 12:18:02 2016 (57D6D53A)
atikmpag.sys                Thu Nov  3 20:13:28 2016 (581BD2A8)
atikmdag.sys                Thu Nov  3 20:59:52 2016 (581BDD88)


http://www.carrona.org/drivers/driver.php?id=semav6msr64.sys
http://www.carrona.org/drivers/driver.php?id=IntelHaxm.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=SeLow_x64.sys
Neo6_x64_VPN.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=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.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.

#6 Jayrpl

Jayrpl
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 06 December 2016 - 11:04 AM

Please excuse me for the long reply. Hardly had any time to run tests.
I have tested the GPU, RAM and checked all the temperatures and saw nothing out of the ordinary
however when I ran prime95 within a minute or so I received a BSOD with "memory_corruption_large" stated as the error.

 

I have attached the dumps here.

Attached File  SysnativeFileCollectionApp.zip   1.27MB   2 downloads



#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 07 December 2016 - 08:02 AM

Prime95 tests Iin general) 3 things - RAM, CPU Cache, and the memory controller (on the CPU in i5 and i7 processors).

I suggest running MemTest86+ for an extended period of time (at least 3 passes and run it overnight).
I also suggest running the Intel Processor Diagnostic Tool

Links for both of these can be found here:  http://www.carrona.org/hwdiag.html

 

Finally, I suggest watching your temps as you run Prime95 - to see if it's overheating that caused the BSOD's:

Please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps.  If uncertain, please ask.

To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.
NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

 

Your UEFI/BIOS (version P7.00) dates from 2016.  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 more recent update.
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).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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 8 memory dumps there were 6 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

Your Cam 3 software from NZXT has a driver dated from 2008.  I suspect that this driver isn't compatible w/W10

I've seen several of these in dump files over the past few weeks - this may be a sign that a compatibility problem has been exposed. 

Please uninstall this software and see if that stops the BSOD's

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Dec  6 09:55:29.519 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120616-25296-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 12:34:22.180
*** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
Probably caused by :fileinfo.sys ( fileinfo+f768 )
BugCheck 50, {ffff808ff90aef78, 2, fffff8072be49ce9, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffff808ff90aef78, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8072be49ce9, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: AV_VRF_INVALID_fileinfo!unknown_function
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P7.00
  BIOS Release Date             09/09/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec  5 21:20:29.933 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120616-22937-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 4:59:05.594
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 3B, {c0000005, fffff801d08a33ce, ffff8a0135e7eed0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801d08a33ce, Address of the instruction which caused the bugcheck
Arg3: ffff8a0135e7eed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P7.00
  BIOS Release Date             09/09/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec  5 16:20:45.809 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120516-26156-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:33:11.470
Probably caused by :ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
BugCheck 139, {3, ffffaa815736e920, ffffaa815736e878, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffaa815736e920, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffaa815736e878, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x139_VRF_3_nt!KiFastFailDispatch
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  P7.00
  BIOS Release Date             09/09/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z170 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:
**************************Tue Dec  6 09:55:29.519 2016 (UTC - 5:00)**************************
semav6msr64.sys             Fri Jan 24 14:22:40 2014 (52E2BD80)
IntelHaxm.sys               Thu Jan 29 21:02:09 2015 (54CAE621)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
SeLow_x64.sys               Sun Oct 18 07:12:14 2015 (56237E8E)
Neo6_x64_VPN.sys            Sun Oct 18 07:12:27 2015 (56237E9B)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
tap0901.sys                 Thu Apr 21 05:10:05 2016 (571898ED)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
AtihdWT6.sys                Sun Jul 24 15:51:39 2016 (57951C4B)
VBoxUSBMon.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxNetLwf.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxDrv.sys                 Mon Sep 12 12:18:02 2016 (57D6D53A)
cpuz140_x64.sys             Wed Oct  5 05:53:07 2016 (57F4CD83)
atikmpag.sys                Thu Nov  3 20:13:28 2016 (581BD2A8)
atikmdag.sys                Thu Nov  3 20:59:52 2016 (581BDD88)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec  5 21:20:29.933 2016 (UTC - 5:00)**************************
b?wse?.sy?                  Wed Nov  2 06:23:23 2016 (5819BE9B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 15 13:35:04.190 2016 (UTC - 5:00)**************************
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov  8 08:06:34.871 2016 (UTC - 5:00)**************************
CAM_V3.sys                  Sat Jul 26 09:29:37 2008 (488B26C1)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
dtlitescsibus.sys           Thu Sep 24 16:17:21 2015 (56045A51)
dtliteusbbus.sys            Mon Dec 28 08:05:52 2015 (568133B0)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  4 15:01:42.344 2016 (UTC - 5:00)**************************
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswKbd.sys                  Thu Aug 18 10:12:06 2016 (57B5C236)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
atikmpag.sys                Fri Sep 16 14:50:37 2016 (57DC3EFD)
atikmdag.sys                Fri Sep 16 15:12:45 2016 (57DC442D)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)


http://www.carrona.org/drivers/driver.php?id=semav6msr64.sys
http://www.carrona.org/drivers/driver.php?id=IntelHaxm.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=SeLow_x64.sys
Neo6_x64_VPN.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=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
cpuz140_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=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
b?wse?.sy? - 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=xusb22.sys
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=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
dtliteusbbus.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=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys

 

Edited by usasma, 07 December 2016 - 08:30 AM.

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.

#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 07 December 2016 - 08:34 AM

Please ensure that Driver Verifier is turned off.


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.

#9 Jayrpl

Jayrpl
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 07 December 2016 - 09:38 AM

Hi I forgot to mention I have ran all hardware diagnostics tests, including MemTest for at least 16 hours. However I have two sticks of RAM and tested with both in, do you suggest I do the test with one stick in at a time?

Also I have uninstalled both NZXT and Daemon tools, are the drivers still showing up?

I had logged the temperatures before the crash while testing in prime95 and the CPU temperatures were still very low - around 40 celsius. I keep an eye on them when playing games and they still stay low.

I also used FurMark and monitored the GPU temperatures and it maxed out at 72 which I read is normal for my card. 

My BIOS is also updated to the most recent one.

 

Lastly, how do i make sure driver verifier is turned off?



#10 technonymous

technonymous

  • Members
  • 2,480 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:58 PM

Posted 07 December 2016 - 12:26 PM

Since you got errors running memtest86 you need to nail that down if it is bad module or ram timings not set right. It may be ram that just doesn't work with that motherboard.

 

What is the specs of your PSU......Brand, Model, AMPs for the 12+ rail?



#11 Jayrpl

Jayrpl
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 07 December 2016 - 06:53 PM

Just to correct you I got no errors running memtest.

I Suspected it might be a PSU fault so I bought and installed a new one the other day, still got the BSOD after about 5 minutes of gameplay.

EVGA 550 GS is my current PSU: 12V rail rating is 45A.



#12 technonymous

technonymous

  • Members
  • 2,480 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:58 PM

Posted 08 December 2016 - 04:56 AM

Just to correct you I got no errors running memtest.

I Suspected it might be a PSU fault so I bought and installed a new one the other day, still got the BSOD after about 5 minutes of gameplay.

EVGA 550 GS is my current PSU: 12V rail rating is 45A.

Sorry about that I got prime and memtest mixed up in your post #6. However, the error that you mentioned was memory related "memory_corruption_large". Many of the reports that USASMA has posted also suggested memory corruption. If you did do a memtest85, 3 passes may not be enough for it present itself.

 

It's good that we can rule out the PSU. However, It can be many things even a faulty motherboard. Damage to the video card (being warped) and pcie slot, cpu Arctic silver shorting out, bent pins in the pga socket, bent pins in the dimm memory socket, bad swelled or leaky capacitors on the motherboard. Even though the motherboard looks normal it can still just be a lemon. Only way to really know is to take it to a shop and have them do a full hardware diagnostic on it or replace it. Check device manager and see if anything is showing errors in there. See if things are not listed and should be installed such as a on-board nic. All are possible signs of a faulty motherboard. Check for hard drive corruption, reset the sata cable again, swap out the sata cable for new one, check cables for shorts & crappy lighting strips drawing to much power etc..

 

To tell you the truth I have replaced more than a enough Asrock motherboards than I care to remember.



#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 08 December 2016 - 05:57 AM

You turn verifier off by opening up verifier.exe (from the Run dialog), selecting "Delete existing settings", then click on the "Finish" button.

Reboot in order for the changes to take effect.

 

I'd suggest trying each of the sticks individually while running the Prime95 Blend test (waiting for it to crash to the BSOD as it did previously).

Use the stick-by-stick procedure in my Memory Diagnostics page (starting at step 7):  http://www.carrona.org/memdiag.html - but use the BSOD crash as your criteria (rather than the errors that MemTest would show).

You'll either rule out the sticks/slots or you won't.
If you don't rule them out, then we have to start wondering about the motherboard.

 

If uncertain of the diagnostic results, I always suggest purchasing a part from a shop that will allow you to return it for your money back (if it's not needed).

As for RAM testing, I don't see any need for running it stick by stick.  I only suggest stick by stick when you know you have a bad stick or slot, but don't know whicch one it is.


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.

#14 Jayrpl

Jayrpl
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:58 AM

Posted 16 December 2016 - 03:56 PM

Just an update:

Turned off driver verifier and still got a blue screen.

Tested ram and no errors whatsoever.

I also gave it in to a repair shop for some interesting results. They told me that all the components were perfectly fine and not faulty or damaged.

But they suggested a RAM upgrade (besides the point as my PC still blue screened for games I had more than enough RAM for)

and also found malware that is being missed by malware bytes. It said the malware was in the Adwcleaner folder.

Ran an independent scan from ESET and threats are being picked up, could this be the cause of the BSODs?



#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:58 AM

Posted 20 December 2016 - 05:13 PM

My apologies for the delay in responding, lot's of personal stuff going on - and now I have a cast on my left arm :(

 

It's possible that malware can cause BSOD's.

I'd suggest posting over in the Am I Infected forum:  http://www.bleepingcomputer.com/forums/f/103/am-i-infected-what-do-i-do/
Please read the pinned topics at the top of the forum for instructions on how to post there.

Please zip up and upload the contents of the C:\Windows\Minidump folder

If unable to zip it there, cppy it to your Desktop and zip it up there.

The Driver Verifier memory dumps may tell us what's causing the BSOD's


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