Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD once a day or so

30 Oct 2014   #1
Chimi

Windows 7 Home Premium 64bit
 
 
BSOD once a day or so

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.


My System SpecsSystem Spec
.
30 Oct 2014   #2
Chimi

Windows 7 Home Premium 64bit
 
 

Sorry, I think I did it wrong the first time. Here is what I think you're looking for.
My System SpecsSystem Spec
30 Oct 2014   #3
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
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.
___________________________________________
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
---------
My System SpecsSystem Spec
.

31 Oct 2014   #4
Chimi

Windows 7 Home Premium 64bit
 
 

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.
My System SpecsSystem Spec
31 Oct 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by Chimi View Post
..... 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.
My System SpecsSystem Spec
01 Nov 2014   #6
Chimi

Windows 7 Home Premium 64bit
 
 

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.
My System SpecsSystem Spec
02 Nov 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
____________________________________________
Code:
BugCheck 4A, {7741161a, 2, 0, fffff88008c25b60}

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

Followup: MachineOwner
---------
My System SpecsSystem Spec
02 Nov 2014   #8
Chimi

Windows 7 Home Premium 64bit
 
 

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

Here is an updated upload.
My System SpecsSystem Spec
02 Nov 2014   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It is not appearing to be Verifier enabled.
Code:
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.
My System SpecsSystem Spec
02 Nov 2014   #10
Chimi

Windows 7 Home Premium 64bit
 
 

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

 BSOD once a day or so




Thread Tools Search this Thread
Search this Thread:

Advanced Search



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 18:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App