BSOD once a day or so

[Chimi]

Been getting random BSOD maybe once a day for the past few days. Sometimes it's while I'm using my computer and sometimes I come home from work and see the message that my computer had just recovered from a crash. Had a bad stick of RAM that I ended up replacing but still getting the error. So not sure if the BSOD is related to that or something else.

 

[Chimi]

Sorry, I think I did it wrong the first time. Here is what I think you're looking for.

 

[Arc]

Hi Chimi.

Uninstall the installed display driver using Display Driver Uninstaller.

Then download and install 340.52 WHQL.

Follow http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html to have a perfect and clean driver installation.

Also test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
___________________________________________

BugCheck 3B, {c0000005, fffff8000349d63c, fffff880091f2b90, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+c )

Followup: MachineOwner
---------

BugCheck 1A, {41790, fffffa80048e5530, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

 

[Chimi]

Thanks for the help. I did what you said. Nothing came up in the RAM test. I had a corrupted stick of RAM over the weekend so I replaced the RAM a couple days ago so that's all brand new. I also uninstalled the display drivers (apparently I had three of them installed).

I guess at this point I just have to wait and see if anything happens. I'll let you know if anything does.

 

[Arc]

..... I replaced the RAM a couple days ago so that's all brand new.

So there was memory corruption in fact. Good to know that your got now RAM.

Let us know for any further issue.

 

[Chimi]

Hi there, I'm back. So I'm still experiencing BSOD. I've done multiple RAM tests over the past few days and just finished one right now that I let run for over 12 hours and 9 passes. No errors came up in that test or any of the the previous ones. So I'm guessing the RAM might be OK.

Here is an updated zip.

Thank you for the help so far, I really appreciate you taking the time.

 

[Arc]

Run disc cleanup to get rid of the old crash dumps. Those are useless and misleading after the RAM replacement.

Then, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
____________________________________________

BugCheck 4A, {7741161a, 2, 0, fffff88008c25b60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
---------

 

[Chimi]

I did those things and after about 8 hours or so of running Driver Verifier, it crashed.

Here is an updated upload.

 

[Arc]

It is not appearing to be Verifier enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

If verifier is enabled, the DEFAULT_BUCKET_ID reads as VERIFIER_ENABLED_VISTA_MINIDUMP.
Disable Verifier. Then enable it again. Make it sure that verifier is properly running. Open command prompt and enter the command ....

verifier /query

​

It will let us know whether verifier is running or not. It should not take so much time to get a BSOD with verifier enabled.

 

[Chimi]

I went in and tried that and it looks to be running now. I'll keep you updated once I get a BSOD.

 

[Chimi]

I've had quite a few BSOD's. I'm just continuing to update this post with a new ZIP after each one to avoid making new posts in the thread and causing annoying bumps.

 

[Arc]

A number of DV enabled minidumps are there.

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

But all are different, haphazard. Which gives a nice idea that driver is not the issue there.

One of them says ....

BugCheck 50, {fffff88025cf598a, 0, fffff8800162d03b, 2}


Could not read faulting driver name
[COLOR=Red]Probably caused by : hardware[/COLOR] ( TDI!Tdi[COLOR=Red]CopyBufferToMdl[/COLOR]+2b )

Followup: MachineOwner
---------

When a DV enabled BSOD blames hardware, it cannot be a driver.

How you tested RAM, and for haw many passes? Are you sure that the RAM is compatible with the board?

Take memtest86+ again. Take a camera snap of the memtest86+ screen before you close the program. Upload the camera snap here.

 

[Chimi]

Last time I tested the RAM it went 9 passes with 0 errors. I tested it a couple times before that and received 0 errors also. i'll do it again and take a picture of the screen.

Is it possible that it might be the graphics card?

 

[Arc]

Is it possible that it might be the graphics card?

Not impossible, It may be the graphics card, or the processor, or any other part of the hardware. But RAM is the primary suspect.

If you want, http://msdn.microsoft.com/en-us/library/windows/hardware/ff565024(v=vs.85).aspx

 

[Chimi]

I'll be honest, I have no idea what that is, haha

I have memtest running while I'm at work. I'll post a picture when I get home.

 

[Arc]

I'll be honest, I have no idea what that is, haha

I have memtest running while I'm at work. I'll post a picture when I get home.

No problem. It should take a good time.

 

[Chimi]

Just stopped my memtest. Hopefully I ran it long enough. Here is a pic of it.

 

[Arc]

So memtest86+ passed. Now let us test the other hardware as far as we can.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

If these tests go well too, remove either RAM stick and let the computer run with a single RAM stick only.

Let us know the results.

 

[Chimi]

I did the GPU test for 20min. If you need me to do it longer, I can. I uploaded the photo of the end of that test.

The CPU test I'll have to do tomorrow since it recommends 2 hours and I'm going to bed. I don't know if letting it run overnight is a good idea or not.

I checked the PSU calculator and it says it recommends 528 watts (min 478). My PSU is 700 watts.

 

[Arc]

GPU stress test passed without any problem. And heat is under control, too.

Your PSU is more than enough.

Let us see what the CPU stress test yields.