Freezing/Blue Screen

[earthlingsdotcom]

Hello

My computer is 2 months old (I built it), it ran fine up until this morning.

My build is the following:
i7-2600
GTX 580
16 GB Ram
Windows 7 64 Bit Home Premium
Seasonic X650
Two (2) Mushkin 120GB SSD Raid 0 (240 GB)

Suddenly this morning, it keeps freezing (locking up), and it's usually followed by a blue screen (saying there's a problem, but it's not specific as to what the problem might be).

This usually happens while I'm gaming, or watching a movie.

I checked the temperature of my GTX 580, and 2600 while I was gaming, and watching video, and the temperature is normal.

My CPU idles at 35c, and it hits 60c-70c (max) while gaming.

My GPU idles at 35c, and hits 60c (max) while gaming.

I have the latest drivers from my GPU.

What could be causing my PC to suddenly freeze during gaming or watching a video?

 

[amuffin]

Windows should display some error during a BSOD. First, run memetest86 on your memory modules to see if there are any problems with your memory modules.

 

[Quaddro]

download this application

http://www.nirsoft.net/utils/blue_screen_view.html

you will have some display like this..

under technical information , read stop code..for example :0x100000d1

read the last code, and there it is the explanation..

_______________________________________________
Common BSOD Error Codes for Overclocking

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for Sandy Bridge

0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
-----------------------------------------------------------

For a complete list of BSOD error codes that may or may not be related to overclocking vist this link.
http://www.aumha.org/a/stop.php#0x9c

 

[earthlingsdotcom]

It froze again, I didn't get a blue screen. I had to restart my PC, because it completely locked up.

 

[Quaddro]

please check your system drive..
maybe your system freeze because of faulty of your raid system..

run only one drive..or get other drive and install fresh OS..

check and see if it freeze again..

 

[earthlingsdotcom]

I think it's the SSD's, it said RAID Stripe Failed...

 

[earthlingsdotcom]

So, something weird happened.

It took 3 tries to boot up into Windows.

The first 2 tries, it wouldn't boot, and it said my Raid0 Status Failed.

The 3rd try it booted up normally...

 

[earthlingsdotcom]

Picture of failed boot:



Picture of successful boot:



Does this mean one of the SATA ports is bad, or that one of the SSD's is bad?

 

[Quaddro]

replace your sata cable..

and if it still freeze or still hard to boot..that's mean one of your ssd is bad...or maybe both of your ssd..

 

[SteelLAD]

I've just had the EXACT same problem with my corsair force 3's in RAID 0, I RMA'd them and it turned out to be bad SSD's. Yes the same prob sometimes a BSOD, more often just a freeze.