Constant BSOD on new custom build - Various Minidump Errors 0x0000003b

[Leo340]

Hey YoYo,

Sorry for the hiatus. Some things came up this past week that kept me from doing much troubleshooting. I should have some time to dive back in at the end of the week. I greatly appreciate all your help so far. Thanks to you I have renewed hope that this issue can be resolved. I will post a status update soon.

 

[YoYo155]

It's ok take your time .

 

[Leo340]

Hey YoYo,

So a few major things have changed since my last post. I have completely switched over to an MSI Z87-GD65 gaming mb. The good news is that since the mb switch I have not had anymore BSOD but the bad news is I'm running into another issue. My display driver keeps crashing over and over again.

The first few times it crashes it will usually recover and I will see a notification icon that says the following:

"Display driver stopped responding and has now recovered. Display driver Nvidia Windows kernel mode driver version 320.49"

I can tell it's about to crash because it usually starts lagging a few seconds before the crash. The worst part is that sometimes it does not recover and the system completely locks up. I can still see everything on screen but the mouse and keyboard are unresponsive. When that happens I have to power down the machine by holding the power button.

What do you think Yoyo? Is this a better position to be in than BSOD or worse?

 

[YoYo155]

Thanks for the update .
A few question please.

Hey YoYo,

So a few major things have changed since my last post. I have completely switched over to an MSI Z87-GD65 gaming mb.

Did you reinstall windows when you swapped the motherboard?

The good news is that since the mb switch I have not had anymore BSOD but the bad news is I'm running into another issue. My display driver keeps crashing over and over again.

The first few times it crashes it will usually recover and I will see a notification icon that says the following:

"Display driver stopped responding and has now recovered. Display driver Nvidia Windows kernel mode driver version 320.49"

I can tell it's about to crash because it usually starts lagging a few seconds before the crash. The worst part is that sometimes it does not recover and the system completely locks up. I can still see everything on screen but the mouse and keyboard are unresponsive. When that happens I have to power down the machine by holding the power button.

What do you think Yoyo? Is this a better position to be in than BSOD or worse?

What you're experiencing is called a TDR (Timeout Detection & Recovery).

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.

• More details HERE, please read.

Since we ran GPU in a different slot on the original motherboard, did you have any issues
while the GPU was used in that way?



We can't test the RAM just yet due to incompatibility with the new chipset we need to take the
trail and error approach if you may.
Take out one of the RAM modules and try to reproduce the error the same way you experienced
it up until now. Do the same to all of the RAM modules until the error is predictable
with one or more specific RAM modules.

 

[Leo340]

Yes. When I swapped motherboards I did a fresh install of the os.

After moving the GPU to slot 2 slot on the original Gigabyte motherboard I did not have the same issue.

 

[YoYo155]

Yes. When I swapped motherboards I did a fresh install of the os.

After moving the GPU to slot 2 slot on the original Gigabyte motherboard I did not have the same issue.

Thanks .

Roll back the driver the same we did before mentioned in details in post #4.
If that doesn't solve it, start taking all but one of the RAM modules out and systematically
putting them back in one by one until you can isolate the module that causes the problems.

We can't test the RAM just yet due to incompatibility with the new chipset we need to take the
trail and error approach if you may.
Take out one of the RAM modules and try to reproduce the error the same way you experienced
it up until now. Do the same to all of the RAM modules until the error is predictable
with one or more specific RAM modules.

 

[Leo340]

Hey Yoyo,

I tried rolling back the driver before posting. I had the most up-to-date version at first but now I'm using the version from July. I used the method you outlined in post #4 to wipe the old files before I installed July version, but I'm still having problems.

 

[YoYo155]

Hey Yoyo,

I tried rolling back the driver before posting. I had the most up-to-date version at first but now I'm using the version from July. I used the method you outlined in post #4 to wipe the old files before I installed July version, but I'm still having problems.

Try ruling out possible bad RAM like mentioned above.
It's important to remember the TDR are very tricky to diagnose due to the fact that they can
originate from several issues, which are detailed in the post linked in post #44 it is important you read it.

 

[Leo340]

Will do. Once I'm done I will post back

 

[Leo340]

Hey Yoyo,

I decided to take a little metal health break from troubleshooting. I've been struggling with this issue for a couple months now. Anyways I'm back in the swing of things and I'll let you know what I come up with.

I took all my RAM sticks out except one and I'm waiting to see what it does. I guess I'll use it a couple days before I move to the next stick in the bunch provided it doesn't crash sooner than that. I'll keep you posted!

 

[YoYo155]

No rush, it's up to you .

 

[Leo340]

Quick update. The display adapter error message showed up shortly after my last post using RAM stick number 1. I removed stick 1 and now I'm using stick 2. Will post back with my findings on stick 2.

 

[YoYo155]

Thank you for the update .
We need to eliminate it as a suspect so it might take longer than you thought but it has to be predictable
so if module 2 checks out, place module 1 (suspect module) in the same slot that you just uninstalled slot 2 (good module) from and see if it crashes.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Leo340]

Quick update. I tested stick 2 by itself and it crashed just like stick 1 did

I spoke with one of my buddies and he gave me one of his spare graphics cards to test with. I have it install right now and so far no issues. I'll keep this card installed through the weekend to see what it does.

It's a GeForce 9600 GSO so it's not comparable but I thought it might be a good thing to try out anyway.

 

[YoYo155]

What situation out of the two described in the quote above did you have happening?

 

[Leo340]

I can't say because I tested the sticks in the same slot. I didn't try testing them in different slots. Would the issue still be mother board or RAM related considering that I've replacing the mb 2 times and the RAM once throughout this process?

Side note. Since installing my friend's spare graphics card I haven't gotten the error.