BSOD Errors, Mainly 0x00000000D1 help

Arc · 16 Mar 2014

Scotty Mac said:

Please let me know what you think. Thanks.

Your next step should be what Zuhl3156 suggested.

Zuhl3156 said:

Oops! Test each stick one at a time.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

Scotty Mac · 16 Mar 2014

Well since I already have tested each stick individually in slot #2, I can call that slot good. All sticks have passed. Just ran a pair through the night in slots 2 and 4. 8 passes, no errors. Now retesting one stick from last night in slot 4. I have to leave for work in a little bit. I'll have my wife snap a pic for me sometime after noon today. Poor PC has been doing nothing except running memtest86 for days now

Arc · 16 Mar 2014

Scotty Mac said:

Poor PC has been doing nothing except running memtest86 for days now

If it feels really bad, you may change the RAM modules all together.

But, if the error is from the motherboard's part, then the BSODs will continue to occur.

Scotty Mac · 16 Mar 2014

This process sucks yes, but I'm not going to spring for new ram just yet. I'll continue to test the current ones in each dimm slot first.

Arc · 16 Mar 2014

Scotty Mac · 16 Mar 2014

Well the testing was going good. Got home tonight and was going to test another stick. Well, now my PC won't even boot up. I've tried all sticks in all the slots and nothing. I made sure the ram, cables, etc was all set and secure and still nothing. I have power, and 1 of my monitors turns on, but no boot up. The board could be flaking out? I did sense something weird a while back but really never though twice about this. On the main bios screen where it has the boot priority icons, well my mechanical hd isn't showing up there, however it does show up when I to go the board explorer tab. When I go I that tab and look to see what I have plugged into the USB ports, they all say empty. All in all, the mechanical hd and keyboard and mouse all work fine. Guess I'll have to look into an RMA. I only had this since October. Do you think there is a point of trying to get it to boot again? I have another PC, but it does not support ddr3 type memory. It's a custom build from 2006.

Arc · 17 Mar 2014

You havent unplugged anything else other than the RAM, right?

In this case, try to re-seat the RAM. make it sure that you are doing it properly.

But, if random errors come up in the way you are explaining over a few posts, you may plan to RMA the board.

Scotty Mac · 17 Mar 2014

Arc said:

You havent unplugged anything else other than the RAM, right?

In this case, try to re-seat the RAM. make it sure that you are doing it properly.

But, if random errors come up in the way you are explaining over a few posts, you may plan to RMA the board.

It looks like I'll be doing an RMA for this board. I tried again to get it to boot. Nothing. I seated all the ram properly and made sure everything else was plugged in and secure. Is this a common thing with motherboards? Never happen to me before. Think the motherboard going bad will damage the ram?
I was reading the RMA process for MSI and it takes from 5-25 business days. That's a little ridiculous! And the bad part is, they'll give me a refurbished one.

Ok, update! As I was getting ready to totally disassemble my system, I decided to try something. I took the battery out and left it out for a few minutes. Put it back in, powered it on and it booted right up! :) From there I decided to flash the bios to the latest version. I had a scare, but it's booted up and idling right now. I'm going to leave it on for the night and when I get home from work tomorrow, I'll try to play a game and see if I get any more blue screens. I'll keep ya posted.

Arc · 18 Mar 2014

Good job, and good luck. :)

Scotty Mac · 20 Mar 2014

Arc said:

Good job, and good luck. :)

Well I finally got around to doing some gaming and everything went well! Got about 2 hours worth in and no crashes. Which before, I couldn't even get 1/2 hour in. With that being said, this is everything running on bone stock settings in bios and only SLI enabled. No overclock of any kind (except when the GPUs boost on their own). My ram speed is 2133mhz, but I guess that's considered overclocking when it comes to my bios with xmp enabled. Right now it's at default of 1600mhz. I'm not going to consider this solved quite yet. I'm going to do some other things to see if I get those bsods. (1 at a time of course). I'll keep this updated. For my reference and any others reading this.