BSOD on a new build

Toggle sidebar Toggle sidebar
J

Joshua_6

Reputable
Sep 5, 2015
14
0
4,510
uploaded the minidump files and system info snapshots from speccy. The BSOD happen when I try to play games. I've tried to make sure all my drivers are up to date. Just getting really frustrated lol

http://1drv.ms/1OVo2Fe
 
Sort by date Sort by votes
as a first guess i would look at the machine vendor for a update to
Intel(R) Serial IO GPIO Host Controller
your version is dated May 04 05:41:36 2015
------
looking at most current bugcheck first:
first one: a one bit memory corruption in a critical windows file csrss.exe ( Client Server Run-Time Subsystem)
the system detected the corruption and shutdown.
I don't see corruption in other system files in the debugger.

I could not read the BIOS info from the memory dump.
I would think this is a hardware error or a bug in one of the new drivers relating to how data is transferred to memory.
most virus infections would modify more than one bit.

I would go to the vendor website and look for BIOS and chipset updates.
I would also start cmd under windows as an admin and run

sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

on the chance that the copy of the file is corrupted on disk. (if it is not then it is getting corrupted as it is copied into memory)

you might run memtest86 and confirm you memory is ok.

got to go, will try to look at another bughceck when I get back.

 
Upvote 0 Downvote
second bugcheck was also 1 bit corruption in a network component.
still could be the intel serial IO driver or a hardware problem.
this time one bit error in
\SystemRoot\system32\drivers\HTTP.sys Thu Jul 09 20:14:33 2015
(on the previous crash dump this file was ok)

what is the make and model of the machine?

third bugcheck was a memory corruption reading data from a pagefile
the debugger does not show any corruption of any core windows files.
but the mapping of where data/programs are paged from storage to RAM was messed up and the machine bugchecked.

This could be the controller or maybe a firmware bug in the BIOS or in the drive.
It could be a bad spot in the pagefile.sys file also.

ok, the 4th bugcheck was a memory corruption in the storage.
the system tried to remove data from RAM and put it into storage or run a TRIM function to tell the underlying storage to run its cleanup routines. This cause the bugcheck because of the memory corruption.
See if there is a BIOS update related to storage or a firmware update related to the actual storage driver.
(it can still be a bug in the intel host controller driver) These errors would not be detected by memtest86, most likely the ram is working fine and data is being corrupted when it is being put into the pagefile or by the firmware of the drive. (common to have bugs in cleanup routines if the drive is newly released type)



 
Upvote 0 Downvote
custom build. the specs are in that snapshot in the onedrive folder.

Windows 10 home 64 bit
Intel core i5 6600k 3.50 GHz
EVGA Z170 stinger mobo
8GB(2x4GB) corsair DDR4 3000 (PC4 24000)
EVGA GeForce GTX 960 2GB
Mushkin Enhanced Reactor 512GB SATA 3 SSD
WD 1 TB hdd 7200 RPM SATA 6 Gb/s 64 MB
 
Upvote 0 Downvote
since I can not read your BIOS info from the memory dump you should confirm you have the latest BIOS
http://www.evga.com/support/download/
bios verison 1.05 dated 10/13/2015 (has a fix for memory compatibility)

then pick up the chipset drivers dated 8-5-2015
they will have fixes that the ones from may will not have.
(intel might even have more current ones but at least get the current vendor offered driver)

you can run crystaldiskinfo.exe and read the smart data from your drive to find the firmware version of your
Mushkin Enhanced Reactor 512GB SATA 3 SSD. Then see if there is a firmware update on there website.
(assuming the intel driver update does not fix the problem)

you could also turn off your system pagefile.sys and the system will create a pagefile in your system RAM.
This might help isolate the cause of the problem.




 
Upvote 0 Downvote
I updated the BIOS and the chipset. The mushkin updater is not detecting my ssd even though I ran it as an administrator like the instructions said so I can't update that firmware right now. Will test if the updated BIOS work and get back to you
 
Upvote 0 Downvote
looks like the BIOS update fixed the crash dump info for the BIOS.
Still looks like you are getting memory corruption. The first new bugcheck was in a TRIM function.

You might consider, changing your SATA port connection to a different port or controller if your board has two SATA controllers. Then boot into BIOS and leave your SSD drive powered but idle after 5 minutes the drive will try to run its internal cleanup routines from its firmware. Sometimes if there is a firmware bug, it gets really behind and the drive stops responding. Normally you would not get data corruption though, just drive timeouts. Anyway, wait a few hours with power and idle then try to update the SSD firmware again.

machine info:
BIOS Version 1.05
BIOS Starting Address Segment f000
BIOS Release Date 10/01/2015
Manufacturer EVGA INTERNATIONAL CO.,LTD
Product 111-SS-E172
Version 1.0

Processor Version Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3500MHz

memory: (bank 0 and 2)
Speed 2133MHz
Manufacturer 0215
Serial Number
Asset Tag Number
Part Number CMK8GX4M2B3000C15

bank 1 and 3 are empty

CMK8GX4M2B3000C15 is corsair ddr4 1.34v memory You should confirm the volatage and memory timings.

the debugger did not detect any memory corruptions in actual windows files.

the second bugcheck looked like internal kernel error. The kernel is not corrupted but the data that a network driver was using was bad.

you might consider turning off your nvidia streaming software. The nvidia streaming tends to expose bugs in the network drivers even if you are not using the streaming.
 
Upvote 0 Downvote
yep, just for the case where a SSD firmware needs to complete without having files in use that block the garbage collection routines. Most often this happens after you format a SSD or delete a large directory like windows.old or pagefile.sys



 
Upvote 0 Downvote
the last bughceck was memory corruption again. The mapping table that tracks what is in physical memory and what is in the pagefile.sys was corrupted. Again the system reports that you have a single bit error.

I don't see any drivers to suspect, the only thing that is strange is this:
\SystemRoot\System32\drivers\iaLPSS2_GPIO2.sys Mon May 04 05:41:36 2015
\SystemRoot\System32\drivers\iaLPSS2_UART2.sys Mon May 04 05:41:32 2015
\SystemRoot\System32\drivers\iaLPSS2i_I2C.sys Sun Sep 20 20:08:09 2015

you have 3 drivers that look like they should be in the same build set but 2 are old pre windows 10 ship and one is updated. these are all intel drivers
Intel(R) Serial IO UART Driver
Intel® Serial IO host controller driver
Intel(R) Serial IO GPIO Host Controller
you might try a automatic scan using intels driver update tool:
https://downloadcenter.intel.com/

-you might try and pull out 1/2 of your memory, or swap the sticks or put them in different slot pairs.
-disable any cache that you have on your drive (if you can)

your system runs for about 20 mins, the problem seems like data is being corrupted depending on the location in memory the data is being written to or from. see if you can isolate it to a memory stick or a memory slot.





 
Upvote 0 Downvote
Device PCI\VEN_8086&DEV_A127&SUBSYS_10423842&REV_31\3&11583659&0&F0 requires further installation.

this is in the information section for the Intel(R) Serial IO UART Host Controller - A127
not sure if that might be part of the problem
 
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