Crashing: Repost

[TheMyst]

Alright, I am moving my post about crashing to here since it would probably make more sense.

Original thread here:
http://www.sevenforums.com/performance-maintenance/13910-crashing-gotten-me-my-wits-end.html

Dump file here:
Will Host For Food!

Perfmon report:
http://www.willhostforfood.com/access.php?fileid=71283

 

[Dzomlija]

Alright, I am moving my post about crashing to here since it would probably make more sense.

Dump file here:
Will Host For Food!

What, exactly, is your query? Are you getting a STOP error? Is the computer freezing? Restarting randomly? Which build are you using? What are your system specs? etc...

 

[TheMyst]

Everything about my computer is already on my profile. And it's your typical BSOD. It just occurs all the ****ing time.
DRIVER_IRQL
SYSTEM_SERVICE_EXCEPTION

Any day, any time for any reason, it will crash. No exceptions. And I have just about had it.

 

[Dzomlija]

Everything about my computer is already on my profile. And it's your typical BSOD. It just occurs all the ****ing time.

Assuming you computer stays on long enough:

1. Click the "Start Orb"
2. Right-click on "Computer", then select "Properties"
3. In the left pane, click "Advanced system settings" (you may need to respond to a UAC prompt)
4. In the "Startup and Recovery" section, click "Settings"
5. In the "System Failure" section, remove the check from "Automatically restart"
6. Click "OK" to close "Startup and Recovery"
7. Click "OK" to close "System Properties"

If your computer does not stay on long enough to complete the above (or the BSOD happens during boot), try the following:

1. When your computer restarts, repeatedly press the F8 key (if you BIOS asks from which drive you want to boot, select the correct drive, the continue pressing F8
2. In the Windows startup menu, select the "Disable automatic restart on system failure" option, and press ENTER

The next time you get a BSOD, make a note of the name, the code and any filenames it may mention, then report back.
although from your last post, it would appear to be a bad driver...

 

[TheMyst]

I already disabled the automatic restart on BSOM$LAZYNESS.

Things I have seen mentioned are:

hidclass.sys
nvlddmkm.sys
usbehci.sys

among numerous others that I haven't written down.

 

[Dzomlija]

I already disabled the automatic restart on BSOM$LAZYNESS.

Things I have seen mentioned are:

hidclass.sys
nvlddmkm.sys
usbehci.sys

among numerous others that I haven't written down.

hidclass.sys would indicate a problem with a Human Interface device, probable keyboard and/or mouse drivers.

nvlddmkm.sys i believe would belong to your nVidia drivers.

usbehci.sys is for your usb controller.

Either way, if the filename being mentioned differes each time (as I'm guessing so do the actual STOP codes?), then your problem is more severe than we may believe.

Which build of 7 are you using, have you turned off UAC and what anti-virus software are you using. Do not neglect even the smallest detail.

 

[TheMyst]

UAC (AKA: Bring me a bottle MS): Disabled.

AV: AVG Antivirus.

I recently flashed my bios from stock to the latest version. Stock was like... 403 I think?

The DIMMs are in sockets A2 and B2 since I can't fit them into A and B 1. The Dominator heatsinks are too big to coexist with my CPU's Thermaltake Heatsink, but I'll get another heatsink if that is what it boils down to.

Again, my windows build info is in my profile, although (not to sass a mod or anything) perhaps an illustration may help.

 

[usasma]

Troubleshooting BSOD's isn't as simple as reading the memory dump files (oh how I wish it were! )

Here's a link where I've briefly described what I do when reviewing a BSOD post:
http://www.sevenforums.com/general-discussion/13020-bsod-tcpip-sys-crash.html#post129991

TheMyst's original post is here: http://www.sevenforums.com/performance-maintenance/13910-crashing-gotten-me-my-wits-end.html

Lot's of issues noted on different forums when using Win7 on the Asus P5Q mobo's
Am I correct in assuming that you had issues with BSOD's when you were running Windows XP, and that they have continued with Win7? Do you recall if the error messages were similar? (If so, this may point to a hardware problem).

Please go to Start and type in "perfmon /report" (without the quotes) and press Enter. Once the report generates, please save it, then zip it up and upload it with your next post.

I've downloaded the dump files and will post back shortly with some observations.

 

[TheMyst]

Troubleshooting BSOD's isn't as simple as reading the memory dump files (oh how I wish it were! )

Here's a link where I've briefly described what I do when reviewing a BSOD post:
http://www.sevenforums.com/general-discussion/13020-bsod-tcpip-sys-crash.html#post129991

TheMyst's original post is here: http://www.sevenforums.com/performance-maintenance/13910-crashing-gotten-me-my-wits-end.html

Lot's of issues noted on different forums when using Win7 on the Asus P5Q mobo's
Am I correct in assuming that you had issues with BSOD's when you were running Windows XP, and that they have continued with Win7? Do you recall if the error messages were similar? (If so, this may point to a hardware problem).

Yes, I had the problems in XP as well, but the new RAM I got is on the QVL for my mobo, so that should not be a problem anymore.

Here's the perfmon report:
http://www.willhostforfood.com/access.php?fileid=71283

 

[usasma]

Perfmon report link directs me to an upload page. Could you recheck the link please?
Almost done generating the dump files....

 

[TheMyst]

Perfmon report link directs me to an upload page. Could you recheck the link please?
Almost done generating the dump files....

Already did... like... 10 minutes ago...

 

[usasma]

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/downloads/products2009/kavremover9.zip

Once it's removed, reboot and see if that improves things for you.


Here's a summary of the dump files:

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

 

[TheMyst]

Have you uninstalled Kaspersky recently?

Once it's removed, reboot and see if that improves things for you.

Yep, I have. One problem though, the removal tool didn't detect KAV on my computer. Maybe it's because I removed the KAV folder?

 

[usasma]

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.

 

[TheMyst]

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.

 

[usasma]

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).

 

[usasma]

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.

 

[TheMyst]

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).

No it's a Linksys PCI adapter. Specifically, it's the WMP54GS adapter.

The only USB devices I have plugged in at the moment are my Logitech G9 Mouse, Logitech G11 keyboard, and a Best Buy Geeksquad 8GB flashdrive. One of those drives with the U3 BS loading it down.

 

[usasma]

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.

 

[TheMyst]

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=download&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.