j_syk

Here are 3 BSOD from today. Each is different. I'm not the master at reading these, and frankly every time the screen seems to be different so i haven't looked any up yet. I was having some other BSODs maybe a week ago, and resolved those by removing nvidia network manager. During this time I did run memtest for about 2 hours, but for some reason I still think it may be RAM related.

__________________

WBaS

Is your system overclocked at all? Have you changed any voltages or any other settings?

EDIT: I had to laugh at your tag "crying myself to sleep" lol. I'd suggest clearing your CMOS and setting your vcore and vdimm voltages to specification if this is not already done. I'll check back tomorrow, it's time for bed

__________________
"Give a man a fish, feed him for a day. Teach a man to fish, feed him for a lifetime." -Lao Tzu

j_syk

Here's a current cpu-z screen
this OC has been stable for a long time.

if the thumbnail isn't working (I can't see my own)
1.248V Core (this seems way low, might be problem)
Core speed- 3195.0
Multiplier 15
bus speed 213
HT link 1065

Attached Thumbnails

 

__________________

thlnk3r

J_syk, for testing purposes can you please run your overclock at stock settings? How often does the BSOD's occur? Let us know if you continue to get BSOD's at stock. What kind of stability tests did you run in the past with the 3195Mhz OC? I'd also recommend checking the event viewer to see if there is any error messages listed (Start -> Run type, "eventvwr.msc").

Let us know

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

WBaS

That voltage seems way low. Try setting your cpu voltage to 1.4v. Also, what is your vdimm?

I'd also try what thlnk3r says, he's very knowledgeable when it comes to troubleshooting and has helped me out numerous times!

__________________
"Give a man a fish, feed him for a day. Teach a man to fish, feed him for a lifetime." -Lao Tzu

logan

I'm with WbaS on this one, that Vcore seem sfar to low for that kind of OC, especially for a windsor core. Most X2's run at about 1.35v stock (some of the lower wattage ones will run 1.25-1.3v), so I would at least set it there, but my guess is that you'll need either 1.375 or 1.4v to get it stable at that kind of speed.

And also, when you start having problems, it is usually very smart to eliminate alot of variables by taking your rig back to stock settings... it makes it much easier to troubleshoot, which is why Thlnk3r suggested it (and I'll throw in a good word for him too... he knows his stuff, thats for sure, and is ALWAYS helping people out... listen and learn).

Try the Vcore and see if that helps.

Good luck

__________________

noobdown

the 2 errors are relating to your ram and your sound drivers.

__________________

ATi 4830 Club

halifax1

Increase your Vcore! Just like everyone else said.

Increase that, and do something extensive, and see what happens.

I had so many BSODs because of Vcore problems.
It also was at one point my RAM was causing problems because it was set at 4:5 ratio, but I switched it to 1:1 and it solved everything.

Try setting it back to all defaults if the Vcore doesn't work.

thlnk3r

Noobdown, thanks for clarifying.

J_syk, it looks like fltmgr.sys is related to the "Microsoft Filesystem Filter Manager". I'm guessing an unstable overclock is causing this error to pop up. As Noobdown pointed out, the senfilt.sys file is related to your audio drivers.

I'd suggest backing down to stock clocks before your NTDLR becomes corrupt or any other crucial system files go missing.

Let us know

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

cquinndesign

+1 to up your voltage