Recent content by taydee

Yup, feels good to be running smooth! Thanks for your diagnosing expertise in narrowing down my problem kemical. Thanks for your help as well Trouble, and I agree. I'm not sure who to blame manufacturer-wise, but it seems like this whole problem should have been a non-existent issue or that...

Okay, well good news for me, 6-6-6-16 @ 1066 appears to be stable and bsod free. Additionally it actually beats 9-9-9-24 @ 1600 in some games according to this (and isn't far behind in application speeds like winrar compression): Gaming And PCMark Vantage Results : DDR3 Memory Scaling On AMD's...

Here's the bsods I got while trying to run ten instances of tf2, each in their own sandbox (the task I found to always cause a bsod if I was using 4 sticks at 1333 or higher): Sorry to be dense but could you summarize the main point I should be taking from that thread or link the specific post...

If Trouble or someone else sees this, what timings should I set if the RAM is specced for 9-9-9-24 at 1600mhz? I'm assuming trouble was using ram that was 9-9-9-24 at 1333, so could I go lower than 7-7-7-20 at 1066?

Ok, here's my RAM on newegg. Easier than typing it all out: Newegg.com - G.SKILL Ripjaws Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9Q-16GBRL

Being the retard I am, I didn't realize the thread had reached a second page so I'm just now seeing all these posts. It is definitely the overburdened C2 IMC, as I can do everything fine with two sticks. Well it seemed that after searching some forums that overvolting the CPU-NB is the best...

Okay, so all the sticks passed one by one, so I'll try upping my NB frequency and NB/CPU volts. I think I have figured out a sure fire way to cause the bsod so hopefully this will fix it.

Still testing the ram, done the first two sticks to ten passes. I have a feeling that this post from another forum may be very relevant to me since I have a c2 phenom II. Hardware Canucks - View Single Post - Trouble Shooting Ram Still not going to mess with any settings until I rule out a bad...

Thanks for all your help so far! That last BSOD was before I had uninstalled avast so that makes sense. And I've done a lot of memtests86+ passes already but I haven't tried them one at a time, so I'll have to try that. How many passes should I do? Now I've done everything you mentioned in that...

OK I think I got rid of the old mouse drivers fully using this method. Remove Old Drivers After Upgrading to New Hardware - How-To Geek

Also it appears that the mouse driver you mentioned is for an old mouse I no longer use because it isn't listed under my current mouse drivers in device manager. Is it safe to delete the file, or should I just change it from a .sys file to a .BAK file as per this thread: These recurrently BSOD...

Ok so far all I've done is update the bios, which went ok, my audio doesn't detect any output now however, which is probably a result of the out of date realtek driver. I was going to update that next when I got this BSOD: Problem signature: Problem Event Name: BlueScreen OS Version...

UPDATE: Ok the driver definately didn't help. Had the exact same bsod as last time. Heres the .dmp: Any help would be greatly appreciated. I'm at a loss, I'll probably run a memtest again for an extended period.

Here's my most recent error (zipped SF diagnostic folder attached): Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 1e BCP1: 0000000000000000 BCP2...