New
#11
This looks to be a driver issue, but it's not clear what it is. It's gonna take me a while to review 16 minidumps, so please be patient.
The most obvious things are internet apps, and kl1.sys. I seem to recall that you mentioned that you were using AVG. Have you uninstalled Kaspersky recently?
This leads us to a discussion about Internet Security applications. They work fine when they're working - but if something goes wrong they wreak havoc with your system. In this case (because of the recent reinstall) I'd guess that this was a conflict between AVG and Kaspersky.
So, the first thing to do would be to remove all traces of the Kaspersky from your system. Here's a link to the Kaspersky removal tool page: Service messages
And a direct link to the download: http://support.kaspersky.com/downloa...avremover9.zip
Once it's removed, reboot and see if that improves things for you.
Here's a summary of the dump files:
Code:Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Mon Jun 15 19:59:50.469 2009 (GMT-4) System Uptime: 0 days 0:11:48.999 BugCheck 3B, {c000001d, fffff880010f5ff9, fffff8800a024d20, 0} Probably caused by : fltmgr.sys ( fltmgr!GetContextFromStreamList+99 ) PROCESS_NAME: chrome.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Mon Jun 15 19:43:29.349 2009 (GMT-4) System Uptime: 0 days 11:36:20.331 BugCheck 1E, {ffffffffc0000005, fffff8800104fcc2, 1, 1} Probably caused by : hardware ( fltmgr!FltpFreeIrpCtrl+2 ) PROCESS_NAME: Steam.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Mon Jun 15 01:38:48.644 2009 (GMT-4) System Uptime: 0 days 2:07:51.283 BugCheck D1, {fffff50008e5e420, 2, 0, fffff8800416b280} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : hardware ( dxgmms1!VidSchiProcessDpcVSyncCookie+428 ) PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 19:03:44.014 2009 (GMT-4) System Uptime: 0 days 0:27:49.544 BugCheck 3B, {c0000005, fffff80002bb9bc1, fffff88004714ab0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 ) PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 17:57:54.035 2009 (GMT-4) System Uptime: 0 days 0:07:48.001 BugCheck D1, {0, 2, 0, fffff88000c2ef44} Probably caused by : ataport.SYS ( ataport!IdePortCompletionDpc+0 ) PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 18:11:11.658 2009 (GMT-4) System Uptime: 0 days 0:00:19.562 BugCheck 3B, {c0000005, fffff880010c323f, fffff88006266d10, 0} Probably caused by : fltmgr.sys ( fltmgr!FltpCreate+22f ) PROCESS_NAME: winlogon.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 18:30:25.446 2009 (GMT-4) System Uptime: 0 days 0:18:10.975 BugCheck 50, {fffff800155763a8, 8, fffff800155763a8, 2} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3de60 ) PROCESS_NAME: avp.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 16:44:27.619 2009 (GMT-4) System Uptime: 0 days 18:30:59.398 BugCheck D1, {fffffa804fe0b1a0, 2, 1, fffff88003a166ff} Probably caused by : hardware ( USBPORT!USBPORT_Core_iCheckAbortList+15f ) PROCESS_NAME: hl2.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 17:48:18.069 2009 (GMT-4) System Uptime: 0 days 0:30:53.661 BugCheck 3D, {fffff80000ba2490, 0, 0, fffff8800578b545} Probably caused by : hardware ( USBPORT!USBPORT_IsrDpc+239 ) PROCESS_NAME: hl2.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 16:54:05.409 2009 (GMT-4) System Uptime: 0 days 0:08:33.173 BugCheck D1, {fffff87f8c39c3f8, 2, 1, fffff8800440fafc} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_TxCsqFindIrp+0 ) PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Tue Jun 16 18:04:02.461 2009 (GMT-4) System Uptime: 0 days 0:00:58.365 BugCheck 50, {ffffc106d10ca918, 1, fffff96000110351, 7} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+50351 ) PROCESS_NAME: csrss.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Fri Jun 19 21:27:03.889 2009 (GMT-4) System Uptime: 3 days 2:21:50.896 BugCheck D1, {1, 2, 0, fffff88003ef353e} *** WARNING: Unable to verify timestamp for kl1.sys *** ERROR: Module load completed but symbols could not be loaded for kl1.sys Probably caused by : kl1.sys ( kl1+5e53e ) *** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Sat Jun 20 23:55:01.270 2009 (GMT-4) System Uptime: 0 days 0:12:44.613 BugCheck D1, {9, 2, 1, fffff88004430660} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpIrpMajorRead+20c ) PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Sat Jun 20 23:40:23.170 2009 (GMT-4) System Uptime: 0 days 0:43:31.441 BugCheck 3B, {c0000005, fffff80002bafa69, fffff88005af5ed0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+459 ) PROCESS_NAME: vspc1000.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Sat Jun 20 10:37:48.872 2009 (GMT-4) System Uptime: 0 days 0:47:29.807 BugCheck D1, {fffff880056843aa, 2, 8, fffff880056843aa} Probably caused by : NDProxy.SYS ( NDProxy!SepSddlParseWideStringUlong+be ) PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Debug session time: Sat Jun 20 08:48:32.887 2009 (GMT-4) System Uptime: 0 days 1:48:20.229 BugCheck D1, {ffffffffffffff8e, 2, 0, fffff880042bc9c7} *** WARNING: Unable to verify timestamp for bcmwl664.sys *** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys Probably caused by : hardware ( bcmwl664+709c7 ) *** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys PROCESS_NAME: System
Got the perfmon report (must not have refreshed the page)- there's an error with one of your services failing. Could you check in Event Viewer (Windows Logs...System log files) to see if you can locate it? Please let us know what you find.
Ok, the only critical error I am seeing stems from Kernel-Power, event ID 41. That one happened within the last hour (hmm, I wonder if it is related to the BSOD I had a half hour ago...)
There are other errors reported as well, but that's the only one that has coincided with a Bluescreen.
OK, reviewed the dump files. They spit data all over the OS, so it's difficult to pinpoint anything for certain.
The only other addition to my earlier list of possibilities is USB stuff and network stuff. Do you use a USB wireless adapter? If so, what's the make and model? There have been some compatibility issues with certain USB adapters and the 64 bit OS (requiring a trip to RaLink to get compatible drivers).
The service errors won't necessarily coincide with a BSOD. They probably aren't causing any problems that you can notice - but they may offer further clues to this mess.
Yep, the Kernel Power error is likely related to the BSOD.
What we're looking for here is one that says that a service encountered an error and that it failed. With the name of that service and the error description we may be able to get some more clues.
OK, then I think that it's time to sit back and wait for the next BSOD to see if the Kaspersky removal tool got rid of the problem.
If we're lucky, you'll be waiting for a long time!
That's not the adapter with issues, so let's not worry about that.
The USB issues could be associate with the BSOD's but are not likely. There have been some issues on the forums with Logitech drivers, but again nothing serious enough to be concerned over.
So, what we're left with is ... is this a single issue that's causing all the BSOD's? If so (and I think it is), then we're probably on the right track to fixing this. If it's multiple issues, then we'll have to troubleshoot them one at a time. I'd start wondering about the networking stuff if the BSOD's return.
Well the thing is that I am running pretty much all Windows drivers save for my Graphics card. That one I got from nVIDIA (installed over the one Windows automatically installs.).
Also, like I said, the remover tool never did anything. It didn't detect anything. I must have deleted something relevant to its interests while I was noodling around in my drive.
The BSODs come most often while I'm playing games (specifically, Orange Box Source), so I'll try playing TF2 and report back if I crash.
Here is the relevant Minidump that was made when I crashed while playing TF2 yesterday if you are interested.
http://willhostforfood.com/?Action=d...d&fileid=71239
Also, the service error that was generated occured because of another service I disabled. Specifically it was Server. I typically disable services I don't use.