BSOD on win 7 64

Associate
Joined
18 Dec 2011
Posts
27
I was wondering if someone could share some light on the ongoing issue I am having before it may cause some serious damage.

I built my PC my self last year buying all my items through OC. All was fine, about 6months in I got a blue screen but took no notice of it really. This soon became a regular thing but completely random.

Recently I have finally got around to giving my build a fresh install and removal of any dust but a week in I'm getting a blue screen. I had been on my PC all day when out of nowhere the BSOD appeared, stright away I checked processor temp (46) and motherboard (32). Booted back up fine and continued. Next day, i was on PC all day, not aslong this time when it happened.

I have tested my SSD + ran a memory test. With it also being a fresh install all drivers/ firmware have been re downloaded and installed using manufactures websites and not the discs that came.
The only thing I can notice is on my graphics card the last 4 of 14 LEDs on my card are red and have been since day one but I thing that's normal and there no instruction to check. The next common thing I can think of is if I have a corrupt copy of windows??

Any help would be appreciated
Gray

null_zps9b29e7ea.jpg

null_zps0d2c8c32.jpg


PC Spec
Asrock Z68 Extreme4 Gen3
Intel i7-2600k 3.4GHz (Sandybridge)
G.Skill RipJawsZ 16GB (4x4GB) DDR3
MSI ATI Radeon HB 6970 OC lightening 2048MB GDDR5 PCI-E
Crucial RealSSD M4 128GB

I am using a Samsung 32" 3D smart TV linked via 10 gold plated v1.4 oxy free HDMI cable 3d ready
 
Hmm, if you're saying the RAM definitely checks out I would look more closely at the drivers. Source what you can through Windows Update which tend to be more stable. My guess at the moment would be there is a flaky driver.
 
I too have had similar issues to you.

I was using 2x4GB Ripjaws in 2 machines, I have put them all together in a new Machine and Im suffering more BSODs than ever.

Last night I hit the limit and I have taken 2 out and so far, I have NOT had a BSOD.

Could be pure chance I know, but try that and se what happens?
 
Last edited:
Back
Top Bottom