BSOD Any ideas?

[dankcik09]

Well I just had my 2nd BSOD 2 days in a row. Besides that my comp has been 100% healthy. Any ideas?

Here is my report

http://dl.dropbox.com/u/12373144/report.html

 

[scout_03]

check if all your driver are up to date

 

[terryd75]

Well I just had my 2nd BSOD 2 days in a row. Besides that my comp has been 100% healthy. Any ideas?

Here is my report

http://dl.dropbox.com/u/12373144/report.html

What were you doing both times it happened? Gaming? etc?
Are you watching your temps? Is it over clocked at all?

http://www.ehow.com/how_5085175_replace-ntoskrnlexe.html

That web site may be helpful. Your report says that both BSOD's were caused by ntoskrnl.exe.

 

[dankcik09]

interesting I will check that out. I do know, but I had reinstalled win 7 awhile back and it actually had an error. So i cleaned the disk and it worked the second install. Do you think my system could have a corrupt file?

The first BSOD was when I was rendering a large video in After Effects. About a 3.5 hour render. The second time, today, crashed after I had played bf3 for 30 minutes. But really it makes no sense. I've had constant problems with the ntoskrnl file.

Ive replaced my whole comp several times.

my SSD 3x
Mobo 3x
GPU 1x
Had to replace my memory recently 1 stick went out.
So I could only assume it could have something to do with a faulty disk maybe?

Also I had the ntoskrnl issue for months. but havn't had any problems for a solid 2 months since i replaced my Mobo.

 

[aicom]

ntoskrnl didn't actually cause those issues. It just reported them. The SYSTEM_SERVICE_EXCEPTION BSOD is usually a RAM issue or video driver problem. Make sure your video drivers are up to date. The DRIVER_POWER_STATE_FAILURE is another driver problem. According to parameter 1 of the bugcheck message and the MSDN documentation, it appears that some thread held the PnP lock for 258 seconds which prevented a power state transition from being able to take place in a timely fashion.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

 

[dankcik09]

Thank you. I will look into this later after work.

 

[dankcik09]

it seems as though the gpu drivers were out of date. Havn't had any issues since then. I'm not sure what initially cause this but its fixed now. Thanks!

 

[dankcik09]

Best answer selected by dankcik09.