Help with BSOD Please?


  1. Posts : 3
    Windows 7 Enterprise x64
       #1

    Help with BSOD Please?


    I've had a number of blue screens on a home-grown system that I built.

    To date, I've...
    1. Verified BIOS and device drivers are current.
    2. Ran Microsoft Memory Diagnostics with either 3 or 5 passes with no errors found.
    3. Ran MemTest86+ for about 3.5 hours with no errors.
    4. Ran Prime95 for about 4 hours.
    5. Ran ran the memory.dmp file through WinDbg and a copy of the console output is attached. (I'd never used WinDbg until now so I probably missed capturing all useful information. Let me know if you need me to do more with it cause I'm all about learning.
    6. I also followed the instructions found here and attached the files/folders.
    7. Joined SevenForums and posted this

    Other info requested in How-To post about this....

    HARDWARE
    CPU: AMD Phenom II X4 965 Black Edition Deneb @3.40GHz AM3 125W Quad-Core Processor
    Memory: 8GB G.Skill RipJaws Series (2 x 4GB Dual Channel) DDR3 1600MHz 9-9-9-24 1.65V (OS shows 7.75GB Usable)
    Motherboard: Asus M4A88TD-V EVO/USB3 880G R, BIOS Version: 1601, BIOS Date: 09-08-2010
    Video: Onboard Video ATI Radeon HD 4250
    PS: CoolMaster RS 750 750-watt PSU

    Windows OS: Windows 7 Enterprise 64-bit
    Licensing: Microsoft Evaluation Version
    System Age: System built a few weeks ago from new parts (except HDD) all of which were purchased in November 2010.
    OS History: The current OS is the first OS installed on this system.

    Question: Did I run Prime95 and MemTest86+ long enough for a thorough test? If not, how long should I let them run?

    Thanks to all who make this site possible. Very useful information that's straight and to the point. I like it!

    It could always be worse - so GIARI!
    John
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome, and well done on all the work you've done so far.

    I suspect Prime95 has been run long enough. As for Memtest86, I usually recommend people to run it for longer, but the truth is, if RAM was the issue, Prime95 would have probably errored out. So let's work on other things.

    The Kaspersky process was running in one dump; another blames your Realtek Ethernet drivers. I would suggest that you remove Kaspersky, following these directions: Removal tool for Kaspersky Lab products | Kaspersky Lab United States

    Replace it with MSE: http://www.microsoft.com/security_essentials

    Install these updated Realtek Ethernet drivers as well: Realtek

    Hopefully that will do the trick; if not, please enable driver verifier: Driver Verifier - Enable and Disable

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec  6 03:12:51.883 2010 (UTC - 5:00)
    System Uptime: 0 days 8:01:12.194
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+409b4 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xBE
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+409b4
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Dec  3 14:11:14.316 2010 (UTC - 5:00)
    System Uptime: 0 days 0:52:06.001
    Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+159 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTryUnwaitThread+159
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Nov 27 19:30:50.261 2010 (UTC - 5:00)
    System Uptime: 0 days 6:23:36.572
    Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+110
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Nov 27 12:00:55.297 2010 (UTC - 5:00)
    System Uptime: 0 days 1:00:38.983
    Probably caused by : ntkrnlmp.exe ( nt!NtQueryInformationFile+214 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  avp.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!NtQueryInformationFile+214
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Nov 26 15:27:20.036 2010 (UTC - 5:00)
    System Uptime: 0 days 4:06:28.347
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+1e2 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+1e2
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Nov 19 10:39:56.232 2010 (UTC - 5:00)
    System Uptime: 0 days 0:52:14.917
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 17:58:51.257 2010 (UTC - 5:00)
    System Uptime: 0 days 0:03:12.958
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+145ca )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+145ca
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 3
    Windows 7 Enterprise x64
    Thread Starter
       #3

    Thanks for the fast reply Jonathan.

    I'll remove Kaspersky, update the Realtek Ethernet drivers, and report back before enabling driver verifier.

    Question: If it does BS again after Kaspersky removal and Realtek driver updates, do I need to repeat the "jcgriff2" processes that I ran and attached to my first post?

    JohnH858
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    If the BSODs persist after the Kaspersky removal and Realtek driver update, the next step is to enable driver verifier.

    After Verifier has caused a few BSODs, please create a new jcgriff2 report.
      My Computer


  5. Posts : 3
    Windows 7 Enterprise x64
    Thread Starter
       #5

    Thanks Jonathan.

    I removed Kaspersky, replaced with MS Security Essentials and updated the Realtek NIC driver. I'll run Verifier if problem persists and let you know.

    Again, thanks for your help.

    John
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    That sounds like a good plan, hopefully it did the trick!
      My Computer


 

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 06:26.
Find Us