Unpredictable BSODs Various error codes New Build


  1. Posts : 3
    Windows 7 Home Premium 64 bit
       #1

    Unpredictable BSODs Various error codes New Build


    I recently built a new computer from scratch and put a fresh install of 7 home premium 64 bit (full retail).
    I've done a couple of memtest passes with nothing found.
    I'm out of ideas and would appreciate any help. I think it is an ssd problem, but am not sure.

    Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
    ASUSTeK Computer INC. P8Z68-V PRO
    BIOS Date: 02/05/10 19:13:52 Ver: 08.00.10
    Corsair 8.00 GB RAM
    HD: (1) ST3320620AS (2) WDC WD1001FALS-00Y6A0 (3) OCZ-SOLI D3 SCSI Disk Device (boot disk)
    ATI Radeon HD 5770
      My Computer


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

    Hello,

    It seems the first crash (September 5) was video-related, either hardware or software. Since then, you changed out your nVidia card for the 5770, outruling the possibility of both. The rest of the crashes are unrelated.

    The other crashes all mention that McAfee was the running process at the time of the crash. While this does not prove its guilt, it does suggest a couple of things. Most likely, there is a network issue present, though it could also be a problem with McAfee. Start with the easy solution, updating the Intel ethernet driver: http://downloadcenter.intel.com/Deta...=%0ADrivers%0A
    Code:
    e1c62x64.sys     Tue Sep 21 17:34:15 2010 (4C9924D7)
    Install the ATK0110 driver from the utilities section here: ASUSTeK Computer Inc. - Motherboards- ASUS P5KPL-CM

    Your motherboard is a different version, but the driver is the same. The version installed is known to cause problems in Windows 7.
    Code:
    ASACPI.sys       Thu Aug 12 22:52:52 2004 (411C2D04)
    If the problem persists, run driver verifier: Driver Verifier - Enable and Disable

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Fri Aug  5 03:40:07.368 2011 (UTC - 4:00)
    System Uptime: 0 days 2:24:08.196
    Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAcquireResourceSharedLite+4e
    BiosReleaseDate = 04/29/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Sep  8 06:52:26.225 2011 (UTC - 4:00)
    System Uptime: 0 days 1:19:17.053
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1377 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1377
    BiosReleaseDate = 06/24/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Aug 24 03:49:56.920 2011 (UTC - 4:00)
    System Uptime: 1 days 2:10:50.122
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1377 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1377
    BiosReleaseDate = 06/24/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Aug 10 11:14:19.258 2011 (UTC - 4:00)
    System Uptime: 0 days 0:52:48.086
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1377 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1377
    BiosReleaseDate = 04/29/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Mon Aug  8 03:57:28.959 2011 (UTC - 4:00)
    System Uptime: 0 days 5:44:23.161
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1377 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1377
    BiosReleaseDate = 04/29/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sat Aug  6 06:18:29.908 2011 (UTC - 4:00)
    System Uptime: 0 days 2:01:45.110
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1377 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  mcshield.exe
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1377
    BiosReleaseDate = 04/29/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16841.x86fre.win7_gdr.110622-1503
    Debug session time: Mon Sep  5 11:47:56.719 2011 (UTC - 4:00)
    System Uptime: 0 days 0:36:20.311
    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    BiosReleaseDate = 05/07/2009
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    First of all Mr. King, I want to thank you for your help. I thought your answer had solved it as I had had not bsods in over a week, then tonight I had a couple of weird internet related issues (an itunes store error message despite that fact that I wasn't using it at the time and a browser crash also without any imput). Finally, I got another bsod so the dump files are attached. on a side note I'm not sure what you were saying about nvidia drivers, this is a fresh install on a system with an ati card there shouldn't be any nvidia drivers.
      My Computer


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

    We're still looking at a network issue, as you have already deduced. My next guess would be McAfee itself is the problem. Remove it according to these directions: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

    Install MSE in its place, until you determine what the problem was.

    Virus, Spyware & Malware Protection | Microsoft Security Essentials

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Tue Sep 20 05:40:26.494 2011 (UTC - 4:00)
    System Uptime: 0 days 7:28:12.696
    Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d
    BiosReleaseDate = 06/24/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  5. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #5

    I had another bsod but the hard drive did not initialize (it just sat for about 20mins before I powered off) so no dump file was recovered. An additional clue to that problem is that if I just restart from the bsod, bios does not recognize the ssd my os is on (it does recognize the two hhds in the system) I need to power off the system before restart, then it recognizes it fine.
      My Computer


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

    Have you tried installing Windows to one of your HHDs and seeing if you get BSODs there? If so, and you do, I'd suggest you return the drive and get a replacement of a different one altogether.
      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 05:51.
Find Us