Thread: Solved Third BSOD today.
View Single Post
09 Aug 2011  
Maguscreed

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

lol you can stop definitely have a bad ram stick there.
If you have more than one stick you can try pulling one while testing the other to try and pick out which one has gone bad.
There's no need for you to continue running the scan though.
That's definitely bad ram if it blew up that quickly on the errors.

Seems the address on that stick is completely destroyed, doesn't look like it can read or write at all.
My System SpecsSystem Spec