Built my PC about a month ago and have been experienceing BSODs

Toggle sidebar Toggle sidebar
I

isaac161000

Prominent
Aug 28, 2017
11
0
510
About a month ago I built my new PC and it has been experiencing BSODs several times. Most of them happen while I'm playing games and tonight I just had one while waking it from sleep.
I've gone through event log and have debugged the crashdumps. Ive searched the error codes associated with them and havent had much luck.
Ive tried things from reinstalling drivers to remounting the hardware but I still get BSODs.
Here are the dmp files https://1drv.ms/f/s!AqeHdTKjvoJdjRDjFIQ42h7reYXK
Is there anything that I'm missing?
My specs:
CPU: i7 7700k
CPU Cooler: Corsair H100i v2 liquid cooler
Memory: G-skill Trident Z 32GB (2x16) DDR4-3200
Storage: Samsung-960 evo 500GB m.2 ssd
Seagate Barracuda 3TB HDD
Video Card: EVGA geforce gtx 1080ti SC black
Power Supply: Corsair RMx 750W 80+ gold.
Case: Fractal Design Define R5 blackout edition with side panal window
Case Fans: 3x Corsair CO-9050017 white led 140mm fan
Operating system: Windows 10 Pro 64bit
 
Solution
J
ram errors can mess up any of the drivers.
generally you update the BIOS to the current version to get the best default timings and retest with memtest86 to confirm the settings are correct.
==============

BIOS Release Date 02/03/2017
(certain driver updates might require a BIOS update to work correctly)


Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime: 0 days 9:50:36.857
bugcheck was called
KillerControlCenter.exe
error code:
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

normally, I would try and update (and remove overclocking software until the...
Sort by date Sort by votes
try and remove the3 overclocking drivers::
C:\Program Files (x86)\MSI\DPC Latency Tuner\NTIOLib_X64.sys Wed Mar 29 00:24:10 2017 (58DB611A)
C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys Sun Jul 9 19:15:21 2017 (5962E339)
and
\C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Thu Jul 14 21:39:19 2016

see if you can reproduce the problem with out the overclocking drivers
 
Upvote 0 Downvote


While running the HDtune error scan on my HDD I got another BSOD and was unable to complete the test. I cant get a dump file of it either because the BSOD was staying on 0% and gave Service_exception_error
 
Upvote 0 Downvote


The issue started before those 3 programs were installed and happened during and after I uninstalled them

 
Upvote 0 Downvote
provide a updated memory dump
I stopped looking at the memory dump when saw the copies of overclocking drivers.
the most current memory dump has the overclocking drivers and a lot of suspect drivers loaded.

usb capture software, and some usb drivers that just will not work are installed.
USBPcap.sys

\SystemRoot\system32\drivers\SiLib.sys Thu Jul 15 15:08:26 2010
\SystemRoot\system32\drivers\SiUSBXp.sys Thu Jul 15 15:27:13 2010

your bios date:
BIOS Release Date 02/03/2017

usb drivers from 2010 will just not work. Look for drivers dated after april of 2012 to have a chance of working correctly




 
Upvote 0 Downvote

Here are the three most recent crash dumps.
The three overclocking utilities were uninstalled and USBpcap was uninstalled
https://1drv.ms/f/s!AqeHdTKjvoJdjRxG0CtqDLoMYRvH
 
Upvote 0 Downvote
looks like the intel overclock driver was removed but there are now 3 copies of NTIOLib_X64.sys running.
looks like the capture software was removed but old 2010 usb drivers are still installed.
SiLib.sys and SiUSBXp.sys
Silicone Labs USBXpress Development Kit

083017-11140-01.dmp
memory dump from Wed Aug 30 20:04:39.565 2017
still shows three copies of the overclock driver running
verifier is running and it caught some problem and called a bugcheck.
(should remove the overclock driver before running verifier, I think the old usb driver might fail verifier tests also)

note: run verifier.exe /reset
to disable verifier functions.

------
here are the locations where the overclock drivers are being loaded from:
C:\Program Files (x86)\MSI\DPC Latency Tuner\NTIOLib_X64.sys Wed Mar 29 00:24:10 2017 (58DB611A)
C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys Sun Jul 9 19:15:21 2017 (5962E339)
C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\NTIOLib_X64.sys Tue Apr 12 00:04:16 2016 (570C9DF0)
 
Upvote 0 Downvote

I did forget to mention that the SiLib.sys and SiUSBXp.sys appear to be used by my watercooler. I've tried updating it several times but it always says that it's up to date. As for the USB drivers, ive installed the ones from MSI and those two drivers remain there regardless
 
Upvote 0 Downvote


I was looking through eventviewer last night after the seatools check ran and I noticed another BSOD had happened sometime in the evening. https://1drv.ms/u/s!AqeHdTKjvoJdjSx0uiFNljWG1oqK

I have been running memtest overnight and it is showing errors in my RAM. Before I determine it is the RAM and do an RMA, would it be best to test each RAM stick in each DIMM individually to determine if the motherboard might be the issue?
 
Upvote 0 Downvote
ram errors can mess up any of the drivers.
generally you update the BIOS to the current version to get the best default timings and retest with memtest86 to confirm the settings are correct.
==============

BIOS Release Date 02/03/2017
(certain driver updates might require a BIOS update to work correctly)


Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime: 0 days 9:50:36.857
bugcheck was called
KillerControlCenter.exe
error code:
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

normally, I would try and update (and remove overclocking software until the issue is resolved, overclock drivers will be blamed if they are installed.)
Killer PCI-E Gigabit Ethernet Controller
Killer Control Center 64-bit
here is your driver version:
\SystemRoot\System32\drivers\e2xw10x64.sys Tue Aug 8 14:25:01 2017
maybe find updates with the motherboard vendor or http://www.killernetworking.com/

there is some sort of problem with your overclocking software. (might be sleep related)
C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys Sun Jul 9 19:15:21 2017
fffff80e`0a840000 fffff80e`0a847000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a830000 fffff80e`0a837000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a800000 fffff80e`0a807000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a810000 fffff80e`0a817000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a7f0000 fffff80e`0a7f7000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a850000 fffff80e`0a857000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a7d0000 fffff80e`0a7d7000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a7c0000 fffff80e`0a7c7000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a790000 fffff80e`0a797000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a7a0000 fffff80e`0a7a7000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a780000 fffff80e`0a787000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
fffff80e`0a7e0000 fffff80e`0a7e7000 NTIOLib_X64.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00007000
 
Upvote 0 Downvote
Solution


So I ran memtest86 on BIOS version 1.2 and I got 10 errors. Did a BIOS update to the current version with the plan to run memtest again.but now windows wont boot normally. I can boot into safe mode though. actually I booted to safe mode and restarted. now it boots just fine.
Ill update with the results of the memtest on the latest BIOS version now
 
Upvote 0 Downvote


Finished the memory testing. One stick failed the memtest and the other passed, board seems to have passed as well. Hopefully the RMA will go well and I get a good RAM stick
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom