Help - BSOD - Hijackthis and Minidumps Posted


  1. Posts : 6
    Windows 7 Home Premium
       #1

    Help - BSOD - Hijackthis and Minidumps Posted


    I've been getting BSODs VERY frequently. Could be my imagination, but it seems that it happens when I'm downloading large torrent files. Also seems to crash about 20 minutes after I leave my computer. I've been downloading with uTorrent, BitLord, and GetRight, but have since uninstalled GetRight. could be another problem, but it seems to happen when I'm using these programs, then again I'm nearly always using these programs.

    I've uploaded my minidump files as well as a hijackthis log to the following directory:

    Index of /md

    I'm fairly tech savvy, but BSOD troubleshooting is a bit new to me so I'm learning as I go. Any help would be greatly appreciated! Thanks in advance!

    Note: I will be away from my computer until Friday
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    I downloaded the last one and found that it's a STOP 0xFE error. More info on that here: BSOD Index

    Since you've got issues with downloads and this is a USB driver issue - what do you use that's involved in both?
      My Computer


  3. Posts : 6
    Windows 7 Home Premium
    Thread Starter
       #3

    I do use a USB wireless adapter... and come to think of it I really haven't had these issues until I started using it. The oldest minidump file I have is dated Dec 14th and that's around the time I started using the adapter. Is this the likely culprit?

    Just as an aside, I noticed that the STOP 0xfe error was only one of the errors and not nearly a frequent one. The most frequent errors are 0x1e, 0x3b, and 0x116. Don't know if that helps or not.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    Running all 17 of the dump files now. From what I've seen, there's no pattern to the errors (which usually means hardware). The December errors seem to be video driver timeouts, but I haven't gone past that in my analysis.

    OK, all 17 are done - mostly showing issues with video and networking. Since it's USB and networking - I'd have to suspect the wireless USB adapter (most likely it's driver). Especially since the driver is outdated: athrxusb.sys Mon Jan 29 07:57:10 2007 Please update the drivers for the wireless USB device. Make sure to get the latest Win7 compatible 64 bit version. If there isn't one, please post back with the make and model of the USB Adapter and we'll see what we can find.

    Also, visit Welcome to NVIDIA - World Leader in Visual Computing Technologies and download the latest Win7 64 bit driver for your video card.
    Uninstall the nVidia stuff on your system from Control Panel...Programs...Uninstall a program
    Then install the freshly downloaded drivers.

    After all that is updated, please wait and see if you continue to get BSOD's. If you do, please zip them up and upload them separately (using the paperclip icon)

    Here's a summary of the BSOD's:
    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Dec 14 03:50:08.550 2009 (GMT-5)
    System Uptime: 0 days 0:00:39.266
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    BugCheck 116, {fffffa800977e010, fffff88004816490, 0, 2}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+13490 )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Dec 14 03:48:17.836 2009 (GMT-5)
    System Uptime: 0 days 0:51:59.942
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    BugCheck 116, {fffffa8009c0c4e0, fffff8800486b490, 0, 2}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+13490 )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Dec 28 18:25:01.973 2009 (GMT-5)
    System Uptime: 0 days 1:27:54.096
    BugCheck 116, {fffffa8006fc44e0, fffff8800ff65230, 0, 2}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Jan  2 19:04:39.684 2010 (GMT-5)
    System Uptime: 0 days 0:14:04.791
    BugCheck 3B, {c0000005, fffff80002e590ae, fffff88008339cf0, 0}
    Probably caused by : memory_corruption ( nt!MiDereferencePerSessionProtos+2e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Jan  2 18:49:17.544 2010 (GMT-5)
    System Uptime: 0 days 2:04:20.276
    BugCheck 1E, {0, 0, 0, 0}
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Jan  2 19:07:13.130 2010 (GMT-5)
    System Uptime: 0 days 0:01:17.237
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Probably caused by : athrxusb.sys ( athrxusb+ee17 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Jan  2 16:44:08.471 2010 (GMT-5)
    System Uptime: 0 days 6:26:51.578
    BugCheck D1, {ffffffffc000366e, 2, 0, fffff88005322101}
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Probably caused by : athrxusb.sys ( athrxusb+68101 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Jan  2 19:12:34.890 2010 (GMT-5)
    System Uptime: 0 days 0:04:32.996
    BugCheck 3B, {c0000005, fffff80002e982e5, fffff88007e4f140, 0}
    Probably caused by : ntkrnlmp.exe ( nt!NtWaitForWorkViaWorkerFactory+2d4 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jan  3 12:42:39.915 2010 (GMT-5)
    System Uptime: 0 days 1:15:27.022
    BugCheck 18, {0, fffffa8008f09a50, 2, f32fe06ace6b286a}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan  4 22:56:25.525 2010 (GMT-5)
    System Uptime: 0 days 0:29:54.632
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Probably caused by : athrxusb.sys ( athrxusb+500d1 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan  4 19:31:04.483 2010 (GMT-5)
    System Uptime: 0 days 0:34:01.590
    BugCheck 3B, {c0000005, fffff80002e4dd28, fffff88008097c80, 0}
    Probably caused by : ntkrnlmp.exe ( nt!WmipDoFindRegEntryByProviderId+10 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Skype.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan  4 18:56:28.267 2010 (GMT-5)
    System Uptime: 0 days 1:07:19.000
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CLASSPNP.SYS
    *** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
    Probably caused by : CLASSPNP.SYS ( CLASSPNP+160c9 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan  4 17:47:50.023 2010 (GMT-5)
    System Uptime: 0 days 1:15:08.130
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jan  5 06:05:53.884 2010 (GMT-5)
    System Uptime: 0 days 7:08:12.991
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+fa )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jan  5 17:31:43.568 2010 (GMT-5)
    System Uptime: 0 days 0:22:31.285
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    BugCheck 116, {fffffa800c3e74e0, fffff8800ffaf230, 0, 2}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+10d230 )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jan  5 14:14:44.267 2010 (GMT-5)
    System Uptime: 0 days 8:07:35.374
    BugCheck 3B, {c0000005, fffff80002ec9063, fffff880098e90a0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+73 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  avgcmgr.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jan  5 17:08:37.125 2010 (GMT-5)
    System Uptime: 0 days 1:02:33.857
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    BugCheck FE, {6, fffffa8008baba10, 50456368, 0}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
      My Computer


  5. Posts : 6
    Windows 7 Home Premium
    Thread Starter
       #5

    Okay, I've updated the network adapter driver and my router firmware. It was purchased recently so I thought to do that too. My graphics are just onboard. nVidia 9100. Is there a driver for that? Not sure and I couldn't find one on nVidia's site...

    A couple months ago I had an issue with my GPU overheating. It would run around 120°C just idling. I reset the heatsink on it and that seemed to take care of it, for a while anyway. It would run around 70°C then even while playing video games. Here lately though it's been running hot again. (91°C right now) The colors on my display have been a bit off for a few days also. (Kind of more intense than usual) I haven't changed any settings lately, today I reset every color and display setting I could find to default, and I also adjusted the gamma a bit but to no avail. I'm not sure if any of this is pertinant, but I just wanted to give all the info I could. Also the color issue is starting to bug me...

    I started some torrents downloading and left them for about a half hour. So far so good. I'll post if I get any more BSODs.
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    You can probably use these video drivers for your system: NVIDIA DRIVERS 195.62 WHQL

    If they don't work, then the HP one's are dated from Oct 26, 2009 - so they should be OK.

    Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

    Overheating of the video card will not only mess with the video, but will also affect other nearby components. I'd suggest regularly monitoring the GPU temps to ensure that's not causing the BSOD's
      My Computer


  7. Posts : 6
    Windows 7 Home Premium
    Thread Starter
       #7

    Reinstalled the nVidia driver and that fixed the color issue. No BSODs yet, seems that it's all fixed. Thanks for your help!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:08.
Find Us