Blue Screen D:

[Flash]

I feel for you OP. I had the exact same BSOD, but I really don't remember how I fixed it.
It could've been sound update. Do you have a realtek onboard?
Make sure you update your sound, videocard, Mobo chipset if you have the option, etc.
I know for sure I did some updates and I got rid of it.

 

[Easy Rhino]

if this kind of shit happened in my mod forums i would nuke the whole god-da$ned thread. either help the OP with his problem or GTFO!

 

[bigtye]

To the OP, did you by chance install windows with the overclock in place?
I have heard this can result in instabilities. I to lean towards the memory problem.

When you run the mem at stock, are you using the memory profile (EMP?) setting in the bios or setting it manually?

I had similar problem that turned out to be memory settings, but it passed memtest for several hours just fine.

Tye

 

[Mussels]

I have no non-essential hardware, I only boot with the windows needed programs, and 7 others, so I will try shutting those off. I do not leave my computer on if I am not at it or at home, nor do I plan to.




Overheating is not a problem, nothing goes over 50*C, except my video card, which never goes over 60*C. I will stock it up and check everything as soon as I can

relying on software readings from sensors is a bad idea. so much stuff has no temp sensors for you to read. try a finger walk on your VRM's and memory and see how hot they really are.

 

[sneekypeet]

Please stay on topic.

 

[Exile_Chavez]

I get this error when I put in devices that the motherboard does not recognize. IE when I try and run 5.25" floppy drives on newer hardware, sometimes this pops up. Anything with an incompatible driver can cause this. Windows might have installed an update automatically that broke a piece of your hardware.

How long has this been going on? If recently, you can roll back updates to get rid of the error possibly. Just a thought:

http://img.techpowerup.org/101118/Capture079.jpg

This has been going on for a couple months now, its really only happened 3 or 4 times, but now in the last 2 weeks its happened 2 more times. Updates could be possible, but have never given me issues before.

I feel for you OP. I had the exact same BSOD, but I really don't remember how I fixed it.
It could've been sound update. Do you have a realtek onboard?
Make sure you update your sound, videocard, Mobo chipset if you have the option, etc.
I know for sure I did some updates and I got rid of it.

I do have a realtek onboard for sound and LAN, and my drivers should be up to date, I will check into that.

To the OP, did you by chance install windows with the overclock in place?
I have heard this can result in instabilities. I to lean towards the memory problem.

When you run the mem at stock, are you using the memory profile (EMP?) setting in the bios or setting it manually?

I had similar problem that turned out to be memory settings, but it passed memtest for several hours just fine.

Tye

I did install windows with the clock still on it, so that may have done it. When I run the RAM at stock I am using the fail-safe settings.

relying on software readings from sensors is a bad idea. so much stuff has no temp sensors for you to read. try a finger walk on your VRM's and memory and see how hot they really are.

Did that and its barely warm to the touch

 

[Mussels]

When I run the RAM at stock I am using the fail-safe settings.

BIOS defaults are not your stock settings. you will still need to manually set timings and voltages.

 

[Exile_Chavez]

BIOS defaults are not your stock settings. you will still need to manually set timings and voltages.

That sucks.

 

[cadaveca]

That sucks.

I had an ASUS P5W-DH 775 board that would push 2.0v through my cpu if left on auto. "AUTO" settings suck.

You really need to set everything manually. Memory specifically, as I have found many boards will set secondary timings far tighter than they should be, which will affect long-term stability.

Of course, finding out what those secondary timnigs should be can be a huge issue, as it's not documented very often. But I love to hear people say "Why did you set "X" timing so loose?" Maybe because I know better than those that programmed the bioses auto settings, and test stability harder than anyone else?

 

[TheMailMan78]

I had an ASUS P5W-DH 775 board that would push 2.0v through my cpu if left on auto. "AUTO" settings suck.

You really need to set everything manually. Memory specifically, as I have found many boards will set secondary timings far tighter than they should be, which will affect long-term stability.

Of course, finding out what those secondary timnigs should be can be a huge issue, as it's not documented very often. But I love to hear people say "Why did you set "X" timing so loose?" Maybe because I know better than those that programmed the bioses auto settings, and test stability harder than anyone else?

That and you're a penis.

 

[cadaveca]

That and you're a penis.

Yeah, but at least I'm educated.











You really need to stop listening to my wife...

 

[bigtye]

BIOS defaults are not your stock settings. you will still need to manually set timings and voltages.

My memory problems occured when running at bios defaults. Switching to using the EMP (Extreme Memory Profile) setting from the memory sticks in bios fixed this issue for me.

Tye

 

[Mussels]

My memory problems occured when running at bios defaults. Switching to using the EMP (Extreme Memory Profile) setting from the memory sticks in bios fixed this issue for me.

Tye

yes, exactly.

XMP can set voltages for you, while normal SPD cant. your problem is likely the same as the OP's, in that he never set the ram up properly (namely: voltage)

 

[Exile_Chavez]

Ok guys, fanfreakingtastic news. I got a DIFFERENT BSOD this time, I had forgotten to reset the OC settings to default, so i just continued like normal, got the BSOD and this time it had "System_Servie_Exception" in it. This is peachy, but I now have all settings back to the complete default the hardware is meant to run at(I can notice the difference ), and am hoping it will not happen again. So since I have a lifetime warranty on my RAM, I plan to email OCZ for an RMA and will hopefully have no problems after that. But if I do, then idk what to do.

 

[Mussels]

Ok guys, fanfreakingtastic news. I got a DIFFERENT BSOD this time, I had forgotten to reset the OC settings to default, so i just continued like normal, got the BSOD and this time it had "System_Servie_Exception" in it. This is peachy, but I now have all settings back to the complete default the hardware is meant to run at(I can notice the difference ), and am hoping it will not happen again. So since I have a lifetime warranty on my RAM, I plan to email OCZ for an RMA and will hopefully have no problems after that. But if I do, then idk what to do.

have you manually set the voltages and timings yet? if you havent, warranty wont do anything.

 

[JrRacinFan]

Before you do that, leave your cpu at default bios settings but bring your cpu-nb voltage up to about 1.35v. See if you still get the BSOD's.

 

[Exile_Chavez]

have you manually set the voltages and timings yet? if you havent, warranty wont do anything.

Voltages are where they are supposed to be, compared the documents with the BIOS and they match up.

Before you do that, leave your cpu at default bios settings but bring your cpu-nb voltage up to about 1.35v. See if you still get the BSOD's.

I will restart out of safe mode and check that in the mean time, be back in like 2 mins

 

[Mussels]

Voltages are where they are supposed to be, compared the documents with the BIOS and they match up.




I will restart out of safe mode and check that in the mean time, be back in like 2 mins

uhh... no.

your BIOS will default to 1.5v for DDR3 ram, the JEDEC standard. you have 1600Mhz ram, which likely runs at 1.65v. you need to go by what your RAM requires, not by what your motherboard defaults to.


if you dont understand why this is happening, i'll give you a simple explanation:

AM3 only supports 1333Mhz ram by default, at 1.5v - much like intels socket 1336 is 1066Mhz DDR3 by default. you have 1600Mhz ram that requires overclocking your memory controller to reach its stock speeds (OCing by AMD's standards, not your motherboard or RAM) - and since you got high speed ram, it likely requires above standard voltages, even when not at 1600Mhz.

 

[Exile_Chavez]

Before you do that, leave your cpu at default bios settings but bring your cpu-nb voltage up to about 1.35v. See if you still get the BSOD's.

Ok, it was default at that level.





Mussel, I will restart with the voltage at 1.65, the requirements for this RAM.(I checked that)


Getting the BSOD to appear is the tricky part, it does it quite randomly, sometimes within a few minutes, or might go away for months. This is the unhappy part.

 

[JrRacinFan]

uhh... no.

your BIOS will default to 1.5v for DDR3 ram, the JEDEC standard. you have 1600Mhz ram, which likely runs at 1.65v. you need to go by what your RAM requires, not by what your motherboard defaults to.


if you dont understand why this is happening, i'll give you a simple explanation:

AM3 only supports 1333Mhz ram by default, at 1.5v - much like intels socket 1336 is 1066Mhz DDR3 by default. you have 1600Mhz ram that requires overclocking your memory controller to reach its stock speeds (OCing by AMD's standards, not your motherboard or RAM) - and since you got high speed ram, it likely requires above standard voltages, even when not at 1600Mhz.

Just assisting and continuing your post hope you dont mind:
Exactly why the mention of cpu-nb voltage. If it's defaulting at 1.35v, try 1.4v. Also maybe try underclocking the ram to 1333 cl9 1.5v, 80% of ddr3 can do this without issue.

 

[Exile_Chavez]

Just assisting and continuing your post hope you dont mind:
Exactly why the mention of cpu-nb voltage. If it's defaulting at 1.35v, try 1.4v. Also maybe try underclocking the ram to 1333 cl9 1.5v, 80% of ddr3 can do this without issue.

Thats the thing, it is currently running at 1066, not even 1600 like it should, I had to OC to get it to 1600. And I set the voltage to 1.67(I dont have 1.65), and all my monitoring software(CPU-Z, and SIW) still says its at 1.5v, I changed the DRAM Voltage. Is that the wrong one?

 

[Mussels]

Thats the thing, it is currently running at 1066, not even 1600 like it should, I had to OC to get it to 1600. And I set the voltage to 1.67(I dont have 1.65), and all my monitoring software(CPU-Z, and SIW) still says its at 1.5v, I changed the DRAM Voltage. Is that the wrong one?

software cant read ram voltages. you changed the right one.

 

[Exile_Chavez]

Now I have active phase switching, and it is flipping out switching between 1 and 4 lights, is that bad? Normally I have that turned off and it stays at 4