BSOD randomly, mostly during Youtube

[BernyT]

Hi

I don't really know what to say, but I have been consistently getting the same BSOD when just using my computer for everyday things. I thought it was just a one off, but has now been occurring more frequently; once a day.

I had to edit some of the files (EventApp and EventSys) and delete some of the dumps because all the files ended up totaling 40MB. I hope there is enough info (I've left the dumps that occurred over the last 3 days in the folder).

Any tips for reducing the size of the file in the future?

Thanks

 

[richc46]

Welcome
Your post gave a good clue, problem while watching YouTube. This is usually, and in this case, a problem with the Graphics Driver. Update your Nvidea driver and you should be ok. If you still have problems, post back. Hope this handles your BSOD.
Click on graphic drivers so that your computer can be scanned for the most recent driver.
http://www.nvidia.com/Download/index.aspx?lang=en-us
Hopefully, this will end your BSODs

 

[BernyT]

I updated my graphics and it crashed shortly after the restart

 

[richc46]

If you get BSODs send us the files. Dont delete any of them.
I see that your driver was updated with a Feb 2012 date. If problem started after that rollback to prior driver.

 

[BernyT]

Here's the dump for the new crash.

 

[richc46]

Make a system restore point, now, so you can go back if necessary.
The file show nvidea as the cause, again. The driver is very new. Rollback to the prior driver and test, again.

 

[BernyT]

Since I have no way of forcing the blue screen I can't say for certain that I have eliminated the problem.

I followed your instructions and downgraded my graphics card to when it was before I installed Diablo 3 and things seem to be running noticeably smoother. No crashes so far is also a good sign.

Thanks for the fast responses by the way. +rep

 

[richc46]

TY for posting and the rep. Keep us in mind if the BSODs return. Glad that it looks ok, now.

 

[BernyT]

Well looks like my problem wasn't fixed. It crashed again shortly after restart.

I did a little of my own digging through the dump and every blue screen I have had points to a problem with ntoskrnl.exe

I've attached the dump below.

 

[richc46]

I am probably using differnet software than you, mine does not point to that driver. In any event that is a lead Microsoft Driver which controls other drivers, it is not the cause. Lets try driver verifier
Driver Verifier
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

 

[BernyT]

I actually started preforming that test shortly after that post with the new dump. I turned it off about 2 hours ago as I was not experiencing any crashes.

I have now turned it back on and will leave it running for the 36 hours you have suggested. Fingers crossed it was just a one off.