BSOD's every time I start computer 2-6x then works

Thanks, I ran the checker with the following: SFC /SCANNOW

It says: "Windows Resource Protection did not find any integrity violations." In the SFC page it says there is a log file - should I post that?

mgorman87 said:

Enable driver verifier
Driver Verifier - Enable and Disable

Code:

2/26/2009 1:04:13 AM   C:\Windows\system32\DRIVERS\Rt64win7.sys

Update your Realtek network drivers - here

Code:

9/27/2009 5:12:06 PM   C:\Windows\system32\DRIVERS\nvlddmkm.sys

Update your video card drivers - here


Also, uninstall uGuru.exe. It crashes over and over again in your app events. This could be the cause of your problems. It is also not compatible with Windows 7.

I just installed Uguru when you told me to update all the drivers, because it said there was a device missing in Windows, but I will uninstall it.

I'll update the other two. I had rolled back the Nvidia driver because I thought maybe it was the newest one causing problems, so basically I've been trying all different Nvidia drivers. It crashes with all the Nvidia drivers, and with the Windows generic driver, but I will install the newest one so everything is up to date regardless. I will update my logs when I update these.

I've enabled Driver Verifier and restarted. Since then I have had a few crashes. Here is my health report and crash reports.

I wonder if maybe someone else would be able to continue looking at the logs if you don't have time or don't want to? Thank you and I have added rep.

I also have ran memory tests and they found nothing wrong with the memory. I am at a loss.

It got really bad yesterday so I backed up everything and reinstalled Windows. Then, I loaded windows and it said it needed to install updates, so I let it, and almost immediately during the downloading of updates, it BSOD'd.

So, I am thinking hardware. I pulled out the last 4GB of my memory, and restarted. It has not BSOD'd, and in the morning, after a cold start, it just let me login - not login after 8 to 10 restarts and false startups.

I can't be sure that it has solved it but I am wondering if that was not one of the problems, if not the "only" problem. As soon as the computer is back on its feet I can post another report. I had ran several memory tests including the Windows one and nothing was caught, but I was at my wits end.

I suppose the real test will be putting the memory back in LOL! I can do that soon.