Memory Management BSOD

Posted: Tue Jul 24, 2012 5:43 pm

heres a single stick, the other link i posted is a much better deal and you get more

http://www.amazon.com/Corsair-VS2GB1333D3-PC3-10666-1333Mhz-240-pin/dp/B002BXA7UC/ref=sr_1_5?s=electronics&ie=UTF8&qid=1343176884&sr=1-5&keywords=2+GB+1333MHz+PC3-10666+240-pin+DDR3

personally i would go with the 8 gigs in the other link, better ram, cheaper etc

But that single module does have the proper speed and latency

You can use faster ram but you would have to OC, so if your not going to OC stick with the 1333

Posted: Tue Jul 24, 2012 6:35 pm

OK, I am going to stew on this for a bit. I may even take the bad stick and swap locations with 1-1 and see if the errors follow to that location. It should if that is the bad stick. Assuming that the locations do relate properly in their slots. Once I am fairly sure it is the Stick, I will then weigh the options and proceed from there.

So let me understand something here. If I go the route of the 2 X 4 GB by Corsair in bank 0 and then stick 2 X 2 GB EKmemory in Bank 1 then I will have a total of 12 GB of Ram in Dual channel mode and will have increased performance values or just capacity? Or does this whole matched ram thing mean that I am somehow compromising performance by not sticking with matching pairs of the same MFR, Model, Specs, etc......?

If I go the route of simply replacing the defective stick with that Corsair 2 GB will that return me to my previous state, minus the BSODs?

Every thing you linked me to is well within my price range, however since returning to the States in January I have been trying to live a more sensible life with regards to finances.

Posted: Tue Jul 24, 2012 6:49 pm

fblevins1 wrote:

If I go the route of simply replacing the defective stick with that Corsair 2 GB will that return me to my previous state, minus the BSODs?

it should, you had a good idea about swapping the slots, go ahead and do that to confirm its the stick and not the slot. Your board has white slots and red slots for ram, so matching sticks in each color. So if you buy the pair, put them in say the red slots. If you buy the single, it doesn't matter.

Posted: Tue Jul 24, 2012 9:57 pm

Figures,

Once I swapped the modules it passed.

Well, I guess the best I can do now is wait it out. I know being a technician that it could have very well been a dodgy connection and re-seating the module took care of it. But I had already done that once before so I did not think that was going to fix it.

When I have more time I will run several passes and see what happens.

Posted: Wed Jul 25, 2012 4:15 am

Well all i can say is I have had heaps and heaps of trouble with memory dumps over the last couple weeks,, My new rig was great for a couple days than one dump after the other,, most of which were 0x000000109 Etc Etc,, I removed 2 sticks and it went ok for a couple days than it all started again,, I was getting random dumps copy movies off my extenal, watching a movie, or just sitting idel,, than I had a ssd failuar,, I wouldn't show i bios,, if i flash my bios it would show but when i went to start i got a black screen and after about 2/3 min I'd get a message to reboot and select a boot device,, if I went back into bios there was no SSD,, So i got onto rog.asus.com and for some advice,, I ended up doing a full disasemble and check everything,, the clip set pins. sata ports, ram and pci scockets, than did a bear bones rebuild, just power, one stick of ram, my ssd and a graphic card, flash the bios with the last one and still no good..
I tried my old HDD and it wonted to work but has a vista OEM so windows just wouldn't load. The ssd has faild and gone back for warraty and I just today put a new HDD in to get me going with just 2x4gb of ram and touch wood it's been running great, Bit slow compaired to the SSD but hey it's running..
Check my posts out I go buy Nackers at rog.asus..
There's some very smart guys here if you what some ideas

http://rog.asus.com/forum/showthread.php?19438-Am-I-going-crazy&country=&status=

Posted: Wed Jul 25, 2012 8:31 am

Yep, no matter what you do, you will always buy defective gear. It can leave a factory good to go, then bump number 15 on the central expressway causes it to go cold on one of the joints.

Besides that in a perfect world I still think that SSD's (I have one) are perhaps a little too fast for many configurations to handle.

I use soluto to delay a few of my start up processes because the PC is so fast that utorrent is up and looking for the files to start seeding before the drive the files are on finished initializing. After a while I figure out one by one which programs need to be delayed to get a nice clean start up.

For me, I move the UAC Slider to the bottom and delay about 4 processes. That results in a very fast boot into windows. utorrent and the others chime in after about 1 minute of activity or so.

Posted: Sun Jul 29, 2012 1:14 pm

Ok, it took 5 days (about right) but I just had another Memory Management BSOD. I am running the Memtest now. I hope that the location of the problem follows the suspect module over to the 1 - 0 Slot rather than the 1-1.

If it gives me the exact same locations that I had before then that might lend itself to the MB Slot being somehow defective or maybe in need of some preventive maintenance. Simply re-seating the sticks did not work. It could be a simple overheating defect and it just takes some random combination of usage and heat to trigger a BSOD.

Well, let's see where this goes from here.

Edit: Memory passed, so I suppose I am back to square one, but with a little more information to consider. I still do not think that shotgunning the memory will produce good results. I suppose I could enable just a GB of virtual memory just to appease the possible requirements to have it on.

OK, I enabled virtual memory from 1 - 2 GB using my ops drive SSD.

Posted: Fri Aug 03, 2012 6:13 pm

Hi, as you know I had heaps of similar trouble with my rig too,, I didn't have my memory set to XMP in my bios, I set that up and haven't hade a dump yet, TOUGH WOOD,, I tried switching it back off and she bsod in half hour,,if your memory has XMP and your MB and bios supports it give that a go, shouldn't hurt anything..
Ps with my rig doing this also change cpu voltage setting to manual, I switch it back to auto..

Posted: Fri Aug 03, 2012 6:37 pm

Methinks your computers are all smoking way to much pot

Posted: Fri Aug 03, 2012 10:21 pm

trollster wrote:

Methinks your computers are all smoking way to much pot

or not enough to think clearly.. Wink

Posted: Tue Aug 14, 2012 3:16 pm

Well the BSOD's returned to their normal weekly and sometimes more.

I ran the MemTest again and again it found a problem with one of the locations...same location as before which is strange because I swapped the suspect stick into another slot.

Two possibilities: One: The Slot is bad...not the stick. Two: I have identified the wrong slot/stick.

I assummed that since the location was somewhere in the 7 G range that it was the last slot covering the 6 - 8 GB.

However since I am not completely sure how the location relates to the physical location of the stick, I am not sure which stick it would be...if it is indeed a stick.

I need to learn what the error location in Memtest relates to location.

Edit: It looks like the last column shows which slot is the problem if you run a multi slot configuration.

Posted: Tue Aug 14, 2012 4:04 pm

Well good to know you have narrowed it down anyway. Hopefully its one of the sticks of ram rather than the slot and its easily fixed.

Posted: Tue Aug 14, 2012 9:10 pm

Despite the fact that there is a channel listing in the red information, there not actually any channels shown...just blank.

So, if someone well versed in ancient Egyptian hieroglyphics could take a look at those numbers and tell me what they mean that would be just grand.

I can tell you that those numbers look very familiar to the ones I have done in the past. Especially the chunk number.

Moving forward.

Posted: Wed Aug 15, 2012 1:52 am

personally dont know of any way to identify a failing address in terms of the physical slot. As far as I know its a case of taking out RAM etc and eliminating which RAM faulty using memtest. Tedious and time consuming i know. Unless you can find some program which identifies the phsical slot or similar?

Posted: Wed Aug 15, 2012 8:34 am

bazzer101 wrote:

personally dont know of any way to identify a failing address in terms of the physical slot. As far as I know its a case of taking out RAM etc and eliminating which RAM faulty using memtest. Tedious and time consuming i know. Unless you can find some program which identifies the phsical slot or similar?

I guess I already knew that but was just hoping someone could whip out their magic wand and either fix it for me or tell me which stick was bad.

Ok I will run all four sticks, one at at time in Bank 1 slot 0 and then if it identifies a bad stick, mark it and then run the same test in Slot 1 and change the sequence of when I put the suspected bad stick in for testing. if it identifies the same stick, then I am going to call it bad and replace it.

Now am I better off simply replacing the single stick or should I buy one matched pair of the 2 GB sticks?