BSOD often after sleep

Status
Not open for further replies.
Solution
note 2: current version of the BIOS is f6 dated 2015/04/23
you have version f3 from 04/25/2014 (the first bios release for this board)
I would update the BIOS to get the various fixes.


note: you have memory F3-14900CL8-4GBXM G.skill ripjawx
Confirm your memory timings, it is kind of common for BIOS to incorrectly set default voltages and the 2N command rates.Latency 9-10-9-28-2N
http://www.gskill.com/en/product/f3-14900cl9d-4gbxm
or update the BIOS to get better default settings for RAM. This could explain why you had a memory address of zero passed to the file system. (just guessing)


update the drivers for window 10 from gigabyte, and get rid of the Scarlet.Crush driver.
reboot delete/move your old memory dumps. Reboot...
note 2: current version of the BIOS is f6 dated 2015/04/23
you have version f3 from 04/25/2014 (the first bios release for this board)
I would update the BIOS to get the various fixes.


note: you have memory F3-14900CL8-4GBXM G.skill ripjawx
Confirm your memory timings, it is kind of common for BIOS to incorrectly set default voltages and the 2N command rates.Latency 9-10-9-28-2N
http://www.gskill.com/en/product/f3-14900cl9d-4gbxm
or update the BIOS to get better default settings for RAM. This could explain why you had a memory address of zero passed to the file system. (just guessing)


update the drivers for window 10 from gigabyte, and get rid of the Scarlet.Crush driver.
reboot delete/move your old memory dumps. Reboot your machine and see if you can get another bugcheck. If so, post the memory dump again.

The bugcheck was caused by a bad memory address passed to the file system.
normally, I would suspect a file filter but you have other bad drivers that should be updated before looking into other potential causes of the failure.


http://www.gigabyte.com/products/product-page.aspx?pid=4953#driver

update your bigfoot LAN driver. Your 2013 version causes memory corruption.

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
remove this driver:ScpVBus.sys Sun May 05 14:31:26 2013
it causes memory corruption. This driver is hard to remove, use this method to remove it from the driverstore or it will just become hidden.
https://technet.microsoft.com/en-us/library/cc771484(v=ws.10).aspx

Microsoft LifeCam, This is a very old driver, likely to have issues. I would remove it or see if there is a update from Microsoft.
VX3000.sys Tue Oct 06 18:49:00 2009
----------
machine info:
BIOS Version F3
BIOS Starting Address Segment f000
BIOS Release Date 04/25/2014
Manufacturer Gigabyte Technology Co., Ltd.
Product Z97X-Gaming 5
Version x.x
Processor Version Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3500MHz





 
Solution

elk123

Distinguished
Jan 10, 2010
218
1
18,695


my ram is set to xml profile. should i still manually set the timings?
 
update the BIOS to get the new defaults ram timings, run memtest86, if you get failures, then manually set your RAM timings. I am not saying that your RAM 2n timings are bad, just that often the vendors assume 1T or 1N RAM. This means the RAM only requires 1 clock tick to setup commands. Your RAM spec indicates 2N which is 2 clock ticks to set up RAM access commands. Often it will work 99.995 % of the time but with a lot of RAM access that is a high error rate. You can pick up the value of the last contents of the wrong memory address if the memory is read too fast. (zeros can be read as ones and vice versa)

Memtest is good about finding these problems and it boots on its own image so you don't have to worry about bad drivers for windows corrupting memory.



 
Status
Not open for further replies.