Random Bsod on fresh install

KillswitchScar

Honorable
Aug 20, 2013
28
0
10,530
First off, heres my specs

SPECS
CPU: a8-5600k
MOBO: MSI FM2-A75MA-P33 FM2
HDD: western digital Cvi blue 500gb
RAM: 4gb of gskill 1866mhz
PSU: corsair cx500w

Now on to my problem, i just built my computer and as i was instaling Win 7 it gave me a blue screen of death. I reset the computer then it gave me a differnet Bsod. Now my BIOS says all my hardwre is in working order, i even trouble shot my gear and i still got random Bsod during the install process. i also tried instaling linux and it got to the last step without a problem. i of course did not finish the install though. Any thoughts on my issue guys? i'm at a loss on it.














 
Solution
Doesn't matter what the errors are. RAM isn't repaired, it is replaced. If you have more than 1 stick of memory, swap out sticks of memory until you don't get errors so you know which stick is bad.

The error codes are the memory locations and what the results were on the read after it performed a specific write pattern on that memory location. It uses a database to write specific patterns to cells, then reads back what it wrote and compares the read to the data base. If the read = what the db says it should be, then that's a pass. If it doesn't match what is supposed to be there indicated by the db then it's a fail, and the memory location didn't accept or possibly hold the correct value.

At this point, you have a bad stick of...

KillswitchScar

Honorable
Aug 20, 2013
28
0
10,530
Impossible. the air coming from my case fans is cold and my CPU is at 38C. I could post some error codes if you guys want? New Bsod says an attempt was made to write to read only memory. it happend after plugged my mouse in. gives a win32ksys error.
 

ShadeTreeTech

Distinguished
Jun 23, 2011
95
0
18,660
I would start with a solid scan of your memory. I've found non-repeated BSODs are most commonly caused by bad memory. Reach for memtest 86+ (from the .org site). Burn the ISO to a disc and let it loop for 24hrs or until it starts showing errors, whichever comes first. If it runs for 24hrs without error you can be 95% sure it's not the memory.
 

KillswitchScar

Honorable
Aug 20, 2013
28
0
10,530
also should i grab the .gz or .zip ISO of memtest? and are you sure it will work without n OS o some form? i'm fairly noobish in the software relam. i mostly build PCs and do web design fr people. :D
 

KillswitchScar

Honorable
Aug 20, 2013
28
0
10,530


Ok, should i get the .gz or.zip pre compiled memtest ISO? or does it not matter.
 

ShadeTreeTech

Distinguished
Jun 23, 2011
95
0
18,660
Doesn't matter what the errors are. RAM isn't repaired, it is replaced. If you have more than 1 stick of memory, swap out sticks of memory until you don't get errors so you know which stick is bad.

The error codes are the memory locations and what the results were on the read after it performed a specific write pattern on that memory location. It uses a database to write specific patterns to cells, then reads back what it wrote and compares the read to the data base. If the read = what the db says it should be, then that's a pass. If it doesn't match what is supposed to be there indicated by the db then it's a fail, and the memory location didn't accept or possibly hold the correct value.

At this point, you have a bad stick of memory and it should be replaced.
 
Solution