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.
Sorry, I think I did it wrong the first time. Here is what I think you're looking for.
Hi Chimi.
Uninstall the installed display driver using Display Driver Uninstaller.
Then download and install 340.52 WHQL.
Follow NVIDIA Drivers - Avoid Problems to have a perfect and clean driver installation.
Also test your RAM modules for possible errors.
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.
___________________________________________
Code:BugCheck 3B, {c0000005, fffff8000349d63c, fffff880091f2b90, 0} Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+c ) Followup: MachineOwner ---------Code:BugCheck 1A, {41790, fffffa80048e5530, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 ) Followup: MachineOwner ---------
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.
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.
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. Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy 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.
WarningBefore 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.
Let us know the results, with the subsequent crash dumps, if any.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.
____________________________________________
Code:BugCheck 4A, {7741161a, 2, 0, fffff88008c25b60} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) Followup: MachineOwner ---------
I did those things and after about 8 hours or so of running Driver Verifier, it crashed.
Here is an updated upload.
It is not appearing to be Verifier enabled.
If verifier is enabled, the DEFAULT_BUCKET_ID reads as VERIFIER_ENABLED_VISTA_MINIDUMP.Code:DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
Disable Verifier. Then enable it again. Make it sure that verifier is properly running. Open command prompt and enter the command ....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.verifier /query
I went in and tried that and it looks to be running now. I'll keep you updated once I get a BSOD.
Quote