Recent Crashing Problem.

[MBrown]

My rig has been crashing during gaming as of late, with either blue screens, lock ups or just completely turning off.

What I've done so far is

1. Took gpu back to completely stock figuration.
2. Next I will remove the CPU overclocking (Its the Asus tpu overlocking stuff)

I was getting the 0x000000050 stop error, but I couldn't really find anything helpful online other than post saying it was probably GPU related.

Does anyone else have any suggestions as to what could be happening. BTW rig was running very well up until this started happening a few day ago.

 

[james7679]

Bccode x50, almost always points to bad RAM. Download Memtest86+ and let it run over night.

 

[MBrown]

Bccode x50, almost always points to bad RAM. Download Memtest86+ and let it run over night.

I will do that.

But anyway With the video card at stock it just hard locked by just watching a youtube video. :/ Clocking down the cpu now and seeing what happens then.

 

[MBrown]

Just had couple more crashes since my last post.

A D1 stop error and a 1E.

 

[Slugbait]

There is a good possibility that you damaged your VRAM, which isn't all that uncommon for people who unlocked their 6950s.

If the VRAM isn't damaged, dropping back to stock config settings may not have been enough...if you went with the flash method to unlock, flash the original BIN back on it, see if that clears things up.

 

[Slugbait]

Looked around a bit, and found a VRAM tester: http://folding.stanford.edu/English/DownloadUtils. Not sure if it's truly any good, but if your shaders are stock, it shouldn't generate any errors.

 

[james7679]

Just had couple more crashes since my last post.

A D1 stop error and a 1E.

Fyi, those two, along with the x50, still point to RAM. Try doing a few passes with memtest real quick.

1st rule in BSOD; don't overclock anything.
2nd rule in BSOD; VERIFY RAM INTEGRITY.

Those are the most common causes of BSODs.

 

[MBrown]

Fyi, those two, along with the x50, still point to RAM. Try doing a few passes with memtest real quick.

1st rule in BSOD; don't overclock anything.
2nd rule in BSOD; VERIFY RAM INTEGRITY.

Those are the most common causes of BSODs.

Been running memtest for over an hour now. No failures yet. Nothing is overclocked.

 

[james7679]

Been running memtest for over an hour now. No failures yet. Nothing is overclocked.

Good deal. Let it run for a few hours, or overnight, if you can.

 

[SMOGZINN]

Been running memtest for over an hour now. No failures yet. Nothing is overclocked.

You are in the troubleshooting stage. As James said, run memtest overnight and see if it finds any problems. Then tomorrow, if memtest came back clean, pull the video card and run some benchmarks with onboard video and see if you get any errors. If you don't get any errors doing that then you almost certainly have a problem with the video card.

 

[MBrown]

Just ran in to an error. CPU2 halted. What could this be? Nothing is OCed at the moment.

 

[james7679]

Bad imc. Try running p95 and see how far you can get.

 

[james7679]

Bad imc.

STIKE THAT.

System specs?

Just run Prime95 and see if you get any errors. Watch your temps...

 

[MBrown]

STIKE THAT.

System specs?

Just run Prime95 and see if you get any errors. Watch your temps...

Running. So far the CPU temp has peaked at 42 with the case open. My rig is in my sig but everything should be bone stock at the moment especially since I turned off the Asus tpu stuff.

 

[james7679]

Running. So far the CPU temp has peaked at 42 with the case open. My rig is in my sig but everything should be bone stock at the moment especially since I turned off the Asus tpu stuff.

Okay. Give it a bit and see if anything comes up. If you are stable for an hour, then go back to Memtest and run again. Be prepared with a camera and upload an image of the error.

I have been on my phone, via Tapatalk, I have just seen your SigRig. Are you running the most current BIOS? Are you using the most current version of Memtest?

 

[MBrown]

Okay. Give it a bit and see if anything comes up. If you are stable for an hour, then go back to Memtest and run again. Be prepared with a camera and upload an image of the error.

I have been on my phone, via Tapatalk, I have just seen your SigRig. Are you running the most current BIOS? Are you using the most current version of Memtest?

Ok. So I ran p95 for about an hour on blend with no errors, and I hadn't had anything lock up on me since everything was at stock. So I decided to OC again. Instead of letting the Asus software do it, I did the OCing myself. I could only get 4300 @ 1.365v which seems alot worse than what everyone else can get with my same setup. This is with ram at stock speeds. So I ran p95 small FFT for about 5 hours with no errors. Not sure what was going on. Going to do some more p95 to be sure though.

 

[james7679]

Okay, but you had a lock at stock config running memtest. You really should re-run memtest, at stock settings, and see if the error comes back.

 

[MBrown]

I wasn't convinced that my everything was at stock because when I chose set optimized defaults on my Mobo my cpu stays at 3.6 and doesn't clock down. So I cleared the cmos and nothing changed. So then I cleared the cmos and removed the battery and nothing changed. I don't know what to do at this point. I will turn the TPU switch off again and to memtest again.

 

[MBrown]

even with the tpu switch off, it wont go down to stock settings now. I have no idea what to do know.

 

[james7679]

Go into cpu settings and be sure that speedstep is ebabled.

Are you looking at cpu-z @idle to confirm it's not downclocking?

 

[MBrown]

Go into cpu settings and be sure that speedstep is ebabled.

Are you looking at cpu-z @idle to confirm it's not downclocking?

It is enabled and yes I am looking at CPU-z It just ran memtest for about 8 hours at 3.3 after I set it there manually. No errors

 

[james7679]

Okay, well download furmark and.stress your gpu. Watch temps.

If you get a system failure, remove the gpu, as previously stated, and.run furmark onboard.

 

[MBrown]

Okay, well download furmark and.stress your gpu. Watch temps.

If you get a system failure, remove the gpu, as previously stated, and.run furmark onboard.

looks like that probably killed my GPU. Couldn't get anything on screen with my GPU after my system crashed at about 90% of the 15 minute test.

Edit: Took my 6950 out and used onboad graphics. Reinstalled my 6950 and it works. I am wondering now if its my PSU crapping out?

 

[james7679]

No, I doubt it killed your GPU. Unless, of course, it overheated because of bad air flow. How long has it been since you have cleaned out your rig with some canned air? Also, reinstalling it, and it then working is further evidence of a dirty rig, ie dirty contacts in the PCIe slot.

To get a general idea of your PSUs functionality, download HWMonitor and stress the system using a game. Watch your minimum and maximum volts and post them.

 

[MBrown]

No, I doubt it killed your GPU. Unless, of course, it overheated because of bad air flow. How long has it been since you have cleaned out your rig with some canned air? Also, reinstalling it, and it then working is further evidence of a dirty rig, ie dirty contacts in the PCIe slot.

To get a general idea of your PSUs functionality, download HWMonitor and stress the system using a game. Watch your minimum and maximum volts and post them.

While doing this I got a blue screen with stop error 19. Memtest was fine, prime 95 was fine (ran for 3.5 hours.) GPU stock. What am I missing?