So much blue...

TimJim

Reputable
Sep 18, 2014
6
0
4,510
Hello everyone, I appreciate any help you guys can give.
I noticed that my computer had blue screened while I was asleep. Didn't think much about it, it will blue screen once every few months and seems to fix itself, however, this time as soon as I logged in, it blue screened again. I booted into safe mode, and even now safe mode seems to never blue screen. I ran a chkdsk and was able to get back into the normal OS and play some steam games. I was on for about 5 hours when it blue screened again. I ran a HDD diagnostic from safe mode from western digital and it passed an extended test. I tried to restore to a previous point, but that blue screened out. I ran memtest86 for a single passed and did receive an error, and will run that overnight for more passes to see if it may be a ram or motherboard issue. I have some crash dumps and was wondering if anyone had additional input, it's very greatly appreciated.
http://pastebin.com/rH7rGdEs
http://pastebin.com/pSWtkJBJ
 
First thing. Turn your PC off if you don't need it on.

From Safe Mode, have you also tried a computer repair?

The BSoD's are happening with ntsokrnl.exe and ntfs.sys

Is this a 100% legal copy of Windows?

It could be due to faulty ram. Wait for memtest to do its job.
 
if memtest86 generates errors then it is not a windows problem. It will be a BIOS, memory timing setting problem or a problem with hardware. (most often your RAM)

most often you would update your BIOS, confirm your memory settings are correct and not overclocked then run memtest86 and confirm no failures. Before you waste time looking for windows problems. Any windows code that gets loaded into bad RAM will be corrupted and if it actually gets run it will not run as expected and may bugcheck the system. Windows loads its code into different sections of RAM on each boot so you get different failures on each boot depending on which driver's code gets corrupted by the bad RAM. Also, only a select few drivers actually check for corruption because they are the target of malware many dirvers will not bugcheck if their data is corrupted.
 

TimJim

Reputable
Sep 18, 2014
6
0
4,510


I don't always leave it on but every now again, especially to run scheduled tasks like defrag and windows updates. I am able to get into the OS. I did try to run a windows repair but that seemed to fail out after 15 percent. This is a purchased OEM version of windows 7 64 bit. After running memtest it returned 9000 errors overnight. Is this primarily my issue? This is the ram that I'm using http://www.newegg.com/Product/Product.aspx?Item=N82E16820145321, I'll post a pic of the memtest.
 

TimJim

Reputable
Sep 18, 2014
6
0
4,510


I've never messed with the ram, http://www.newegg.com/Product/Product.aspx?Item=N82E16820145321, the memtest returned over 1200 errors, but this is the first time i've ever memtested it. My computer isn't completely unusable, i'm in the normal OS right now. I haven't had any new drivers recently install, this is a homebuilt PC with OEM windows on it.
 
Bunch of single bit errors in memory locations. You need to pull half of your RAM, rerun the memtest86 and see if you can Isolate your problem to a bad stick of RAM or a particular memory slot. Any code copied to bad ram will be modified and has a chance of failing if executed.




 

TimJim

Reputable
Sep 18, 2014
6
0
4,510
My build is
Motherboard: GIGABYTE GA-X58A-UD3R
PSU COOLMASTER| RS850-AMBAJ3-US RT
MEM 4Gx3|CORSAIR CMP12GX3M3A1600C9
2- HD 1T|WD 7K 64M SATAIII WD1002FAEX in RAID 0
MS WIN 7 HOME SP1 64BIT 1PK - OEM
CPU INTEL|CORE I7 960 3.20G R
CPU COOL CM|RR-UV8-XBU1-GP R

I've started to attempt to isolate the RAM.... would it be normal for all 3 sticks to be bad or if it seems that way should I suspect more that the motherboard is the issue? Also, does the ram being triple-channeled affect testing sticks 1 or 2 at a time.
 

TimJim

Reputable
Sep 18, 2014
6
0
4,510
I have noticed that the clocks that the mobo set by default were kind of odd but I don't know much about setting clocks and voltages... I'm curious as to why this issue would suddenly spark up such rampant blue screens, this computer was originally built at the end of 2011... I'm taking a look into the bios and clocks and will post back shortly... thank you very much for your help so far by the way