BSOD over night

[markjsanderson]

Hi All,

I have built a new system for 3d modelling and rendering which initially had a lot of bsod's at random times.

Sometimes just using google chrome would cause a crash. Other times the computer would be idle and it would crash.

I did some troubleshooting but couldn't narrow the fault down. I thought it was video card drivers or some other driver conflict. I also thought it might be memory corruption. I did windows memory test and it found faults. I took the memory to the computer store that I bought the memory from and got them to do a proper memtest but they said the memory passed both passes.

I was at a loss and decided to reinstall windows. Everything seemed to be working fine for a while. No random crashes during use. I put it down to a new system that may not have installed windows correctly or there was old motherboard bios/drivers at the time of install. I really don't know.

SO, last night is the first crash in a while. When I say while I mean 1 month. It happened in the early hours of the morning just before 4am.

I am pretty tech savvy but this is way over my head now and I need help. I do not know how to decipher the dump file.

Machine specs.
Asus prime x299-a
i9 7980xe
corsair ax1200i psu
Windows 10 home x64
g.skill 32gb (4x8gb) ddr4 Trident z 3200mhz

Link to dump file.
https://drive.google.com/open?id=1w1-hYEyWH2GOk60w3Ckn6WfX8_wPUeuY

Thanks in advance to anyone that can help me or at least point me in the right direction.


cheers,
Mark

 

[fidelio]

It may be any number of things from the power supply to bad drivers. Open the reliability monitor in Windows and compare error messages from the last month. If the system hasn't crashed in a while and is booting into Windows fine, I'd be shocked if were drivers.

 

[markjsanderson]

It may be any number of things from the power supply to bad drivers. Open the reliability monitor in Windows and compare error messages from the last month. If the system hasn't crashed in a while and is booting into Windows fine, I'd be shocked if were drivers.

Hi fidelio,
Yes, you are right. It could be anything, and it's beyond me now. So I need help to narrow it down. Thanks for the advice. I actually didn't know about the reliability history. I have two recent crashes. I didn't know about the previous one.

Do I search the "Code"? What do the parameters mean?

Source
Windows

Summary
Shut down unexpectedly

Date
‎7/‎03/‎2018 11:37 PM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: 1000007e
Parameter 1: ffffffffc0000005
Parameter 2: fffff800eaee72a0
Parameter 3: fffffa09659a9438
Parameter 4: fffffa09659a8c80
OS version: 10_0_16299
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 3081

Source
Windows

Summary
Shut down unexpectedly

Date
‎11/‎03/‎2018 3:53 AM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff803f8391605
Parameter 3: ffff93889b91e290
Parameter 4: 0
OS version: 10_0_16299
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 3081

 

[johnbl]

the bugcheck just indicated a bad memory address. not clear as to the cause.
my best guess is you are hitting some sort of bug in the Samsung magician driver that is messing up the timing of the windows memory management cache manager.

I would remove the Samsung software or look for a update. I assume you have a SSD, you might run crystaldiskinfo.exe and read out the firmware version and check for firmware updates.

you also have custom backup software running, and overclocking driver running.




-------------

you might want to remove the below drivers, basically USB specs have changed over the years and the changes required bios updates. Running old USB drivers before 2012 tend to have problems with bios versions dated after 2012 (your bios is dated in 2017)

you also have a custom backup utility running, it may not work well with the Samsung software.


------------

I would suspect your old CSR Casira Bluetooth driver

I would remove your old USB drivers
\SystemRoot\System32\Drivers\csrusbfilter.sys Wed Feb 22 23:05:43 2012

overclock driver running:
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Fri Sep 15 03:22:21 2017

old usb drivers that will not work correctly with your updated bios:
https://www.sysnative.com/drivers/driver.php?id=SiLib.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 Samsung SSD Magician software seems to be having some problem also.

 

[markjsanderson]

the bugcheck just indicated a bad memory address. not clear as to the cause.
my best guess is you are hitting some sort of bug in the Samsung magician driver that is messing up the timing of the windows memory management cache manager.

I would remove the Samsung software or look for a update. I assume you have a SSD, you might run crystaldiskinfo.exe and read out the firmware version and check for firmware updates.

you also have custom backup software running, and overclocking driver running.




-------------

you might want to remove the below drivers, basically USB specs have changed over the years and the changes required bios updates. Running old USB drivers before 2012 tend to have problems with bios versions dated after 2012 (your bios is dated in 2017)

you also have a custom backup utility running, it may not work well with the Samsung software.


------------

I would suspect your old CSR Casira Bluetooth driver

I would remove your old USB drivers
\SystemRoot\System32\Drivers\csrusbfilter.sys Wed Feb 22 23:05:43 2012

overclock driver running:
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Fri Sep 15 03:22:21 2017

old usb drivers that will not work correctly with your updated bios:
https://www.sysnative.com/drivers/driver.php?id=SiLib.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 Samsung SSD Magician software seems to be having some problem also.

Hi John,

Thank you for the advice. I will have a look tonight and report back.

Okay! I have checked and updated firmware and drivers to all my ssd's. Then I uninstalled the ssd software (Samsung magician and Corsair toolbox).
I uninstalled the CSR usb drivers and deleted the csrusbfilter.sys file. It is now using a generic windows driver and seems to be working fine.
I also uninstalled Intel(R) Extreme Tuning Utility as I am not overclocking

I cannot delete the SiLib.sys or SiUSBXp.sys as there must be software using them I read up a bit on those files and it seems that it can come from various software but hard to find which one. I will leave those for now and monitor it.

See how that goes. I will report back if anything changes.
Thanks for all your help.

Cheers,
Mark

 

[markjsanderson]

Hi All,

Just a quick update. All the suggestions helped reduce the blue screen issues but it was ultimately the RAM.
Initially, the RAM was ruled out as being the cause because after 2 passes there were no errors. The test was done at the computer shop after I did windows memory test at home which found errors.
After chasing my tail trying to figure out the cause, and after doing all the aforementioned troubleshooting, I decided to do my own memstest86 and let it run overnight. There was an error during the 4th pass and about 10 after that on the following passes.

The memory was tested at the shop and found to be faulty. It was replaced, and that memory was tested to be sure there would be no more problems. Lucky it was still under warranty.

So all in all the problems were coming from corrupt RAM.

Hope this helps others.
Mark