BSOD help needed please


  1. Posts : 6
    Windows 7 Pro x64
       #1

    BSOD help needed please


    Hey Guys,
    I can not pinpoint what is causing my BSOD so I'm asking the experts for some needed help with my situation. I've followed the BSOD posting instructions and have attached the zipped file. Any help would be appreciated. Thank you.
      My Computer


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

    Hello,

    It seems we are looking at a hardware issue. Start right off with some diagnostics.

    Run each of the three Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

    Run Memtest86 for 8 passes: RAM - Test with Memtest86+

    Test the hard drive with SeaTools: SeaTools for Windows | Seagate

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Oct 13 12:17:13.909 2010 (UTC - 4:00)
    System Uptime: 0 days 19:00:37.235
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  Neti.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 09/10/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 11 16:26:47.914 2010 (UTC - 4:00)
    System Uptime: 0 days 2:44:23.241
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 09/10/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Sep 22 17:15:36.464 2010 (UTC - 4:00)
    System Uptime: 0 days 9:28:18.790
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+22172 )
    BUGCHECK_STR:  0xC1_81
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0xC1_81_VRF_nt!_??_::FNODOBFM::_string_+22172
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Sep 15 08:03:54.919 2010 (UTC - 4:00)
    System Uptime: 0 days 1:08:30.135
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep  9 15:35:48.183 2010 (UTC - 4:00)
    System Uptime: 0 days 7:19:45.510
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Aug 30 08:30:03.031 2010 (UTC - 4:00)
    System Uptime: 0 days 0:32:44.544
    Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiProcessExpiredTimerList+110
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Aug 19 08:06:09.788 2010 (UTC - 4:00)
    System Uptime: 0 days 0:36:48.115
    Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiProcessExpiredTimerList+110
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Aug 16 15:43:39.941 2010 (UTC - 4:00)
    System Uptime: 0 days 7:38:48.600
    Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  JobServerFacto
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!MiEmptyPageAccessLog+dc
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat Aug  7 18:13:33.537 2010 (UTC - 4:00)
    System Uptime: 0 days 0:05:04.864
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt+70600 )
    BUGCHECK_STR:  0xC1_24
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat Aug  7 17:45:03.817 2010 (UTC - 4:00)
    System Uptime: 0 days 0:08:44.144
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt+70600 )
    BUGCHECK_STR:  0xC1_24
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat Aug  7 17:35:33.376 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:20.592
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt+70600 )
    BUGCHECK_STR:  0xC1_24
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BiosReleaseDate = 06/30/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Mon Jul 18 09:44:58.199 2011 (UTC - 4:00)
    System Uptime: 0 days 0:32:30.152
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetNext+5b )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x50_VRF_fileinfo!FIStreamGetNext+5b
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Mon Jul 18 10:00:58.778 2011 (UTC - 4:00)
    System Uptime: 0 days 0:14:43.731
    Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x24
    FAILURE_BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsPreRequestProcessingExtend+7a
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Wed Jul 13 09:32:32.312 2011 (UTC - 4:00)
    System Uptime: 0 days 0:06:18.264
    Probably caused by : ntkrnlmp.exe ( nt!CcUninitializeCacheMap+ce )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  sidebar.exe
    FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!CcUninitializeCacheMap+ce
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Tue Jul 12 09:12:00.199 2011 (UTC - 4:00)
    System Uptime: 0 days 0:31:55.151
    Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+375 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KeReleaseSemaphore+375
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Tue Jul  5 10:43:45.466 2011 (UTC - 4:00)
    System Uptime: 0 days 2:00:30.213
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Thu Jun 30 17:40:58.652 2011 (UTC - 4:00)
    System Uptime: 0 days 0:22:36.604
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Fri Jun 24 08:59:41.582 2011 (UTC - 4:00)
    System Uptime: 0 days 15:02:41.534
    Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+215 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  WerFault.exe
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!MmCopyToCachedPage+215
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Wed Jun 22 16:10:31.498 2011 (UTC - 4:00)
    System Uptime: 0 days 7:00:57.340
    *** 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+202845 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+202845
    BiosReleaseDate = 04/20/2011
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Tue Jun 14 11:22:45.047 2011 (UTC - 4:00)
    System Uptime: 0 days 1:15:19.000
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
    BUGCHECK_STR:  0x19_3
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x19_3_VRF_nt!ExDeferredFreePool+a53
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Mon Jun 13 16:07:11.441 2011 (UTC - 4:00)
    System Uptime: 0 days 7:01:10.679
    *** 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
    BUGCHECK_STR:  0xc4_62
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xc4_62_VRF_LEAKED_POOL_IMAGE_nvlddmkm.sys
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Fri Jun 10 10:52:13.982 2011 (UTC - 4:00)
    System Uptime: 0 days 2:39:31.823
    Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  RedStapler.scr
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpGetNameControlBlock+12e
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Mon Jun  6 09:03:15.000 2011 (UTC - 4:00)
    System Uptime: 2 days 15:13:46.952
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  digsby-app.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Wed May 25 10:51:54.219 2011 (UTC - 4:00)
    System Uptime: 0 days 17:39:51.171
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Fri May 20 11:50:04.699 2011 (UTC - 4:00)
    System Uptime: 0 days 17:51:17.651
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  firefox.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Wed May 11 12:52:35.921 2011 (UTC - 4:00)
    System Uptime: 0 days 3:45:05.873
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+232f2 )
    BUGCHECK_STR:  0xC1_82
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  everest.exe
    FAILURE_BUCKET_ID:  X64_0xC1_82_VRF_nt!_??_::FNODOBFM::_string_+232f2
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Thu May  5 09:00:56.967 2011 (UTC - 4:00)
    System Uptime: 0 days 0:42:22.920
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Apr 26 13:19:25.123 2011 (UTC - 4:00)
    System Uptime: 0 days 4:49:19.076
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    Probably caused by : afd.sys ( afd+53759 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_VRF_afd+53759
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Apr  5 13:59:31.700 2011 (UTC - 4:00)
    System Uptime: 0 days 0:05:53.652
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Thu Mar 31 13:38:07.102 2011 (UTC - 4:00)
    System Uptime: 0 days 5:10:18.054
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetNext+5b )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x50_VRF_fileinfo!FIStreamGetNext+5b
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Mon Mar 28 13:07:03.721 2011 (UTC - 4:00)
    System Uptime: 0 days 4:18:21.689
    Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!ExAllocatePoolWithTag+537
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Thu Mar 24 09:24:37.897 2011 (UTC - 4:00)
    System Uptime: 0 days 0:54:47.849
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Thu Mar 17 09:40:27.122 2011 (UTC - 4:00)
    System Uptime: 0 days 1:07:34.074
    *** WARNING: Unable to verify timestamp for mrxsmb10.sys
    *** ERROR: Module load completed but symbols could not be loaded for mrxsmb10.sys
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1570 )
    BUGCHECK_STR:  0xC5_2
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_0xC5_2_VRF_nt!ExDeferredFreePool+1570
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Mar 15 13:01:23.735 2011 (UTC - 4:00)
    System Uptime: 0 days 4:28:59.687
    *** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
    Probably caused by : Npfs.SYS ( Npfs+c5ea )
    BUGCHECK_STR:  0xC5_2
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  plugin-contain
    FAILURE_BUCKET_ID:  X64_0xC5_2_VRF_Npfs+c5ea
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Fri Feb 25 05:02:45.054 2011 (UTC - 4:00)
    System Uptime: 0 days 7:12:01.006
    Probably caused by : usbhub.sys ( usbhub!UsbhQueueWorkItem+11d )
    BUGCHECK_STR:  0xC1_81
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xC1_81_VRF_usbhub!UsbhQueueWorkItem+11d
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Thu Feb 24 12:44:21.405 2011 (UTC - 4:00)
    System Uptime: 0 days 3:21:08.358
    *** ERROR: Module load completed but symbols could not be loaded for SNTUSB64.SYS
    Probably caused by : SNTUSB64.SYS ( SNTUSB64+f60 )
    BUGCHECK_STR:  0xc9_24c
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xc9_24c_VRF_SNTUSB64+f60
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Thu Feb 17 13:54:17.031 2011 (UTC - 4:00)
    System Uptime: 0 days 2:16:47.358
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Tue Feb 15 10:49:20.271 2011 (UTC - 4:00)
    System Uptime: 0 days 15:27:47.598
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  ejsme.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Feb  4 12:09:26.281 2011 (UTC - 4:00)
    System Uptime: 0 days 1:35:20.608
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for cng.sys - 
    Probably caused by : cng.sys ( cng!BCryptResolveProviders+3f4 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x50_VRF_cng!BCryptResolveProviders+3f4
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Jan 26 12:11:15.209 2011 (UTC - 4:00)
    System Uptime: 0 days 2:12:12.535
    Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownFromLcb+20d )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_Ntfs!NtfsTeardownFromLcb+20d
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Jan 24 17:03:38.245 2011 (UTC - 4:00)
    System Uptime: 2 days 1:50:05.405
    Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+213 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_Ntfs!NtfsFlushVolume+213
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Jan 19 11:44:06.677 2011 (UTC - 4:00)
    System Uptime: 0 days 18:19:06.004
    *** 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+1debd5 )
    BUGCHECK_STR:  0xC1_32
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+1debd5
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Jan  6 06:19:46.902 2011 (UTC - 4:00)
    System Uptime: 0 days 11:05:19.118
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  0x109
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Dec 26 14:03:55.403 2010 (UTC - 4:00)
    System Uptime: 5 days 22:49:27.511
    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!CmpDereferenceNameControlBlockWithLock+22
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Dec 10 13:04:54.689 2010 (UTC - 4:00)
    System Uptime: 0 days 3:53:29.016
    *** ERROR: Module load completed but symbols could not be loaded for SNTUSB64.SYS
    Probably caused by : SNTUSB64.SYS ( SNTUSB64+f60 )
    BUGCHECK_STR:  0xc9_24c
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xc9_24c_VRF_SNTUSB64+f60
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Dec  2 16:08:14.125 2010 (UTC - 4:00)
    System Uptime: 0 days 0:04:39.452
    Probably caused by : ntkrnlmp.exe ( nt!AlpcpFreeMessageZone+10 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!AlpcpFreeMessageZone+10
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Dec  2 16:02:38.309 2010 (UTC - 4:00)
    System Uptime: 0 days 20:19:07.141
    *** 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+32c5b )
    BUGCHECK_STR:  0xC1_23
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  plugin-contain
    FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_nvlddmkm+32c5b
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Nov 24 10:36:21.673 2010 (UTC - 4:00)
    System Uptime: 0 days 1:31:23.000
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by : usbhub.sys ( usbhub+68ba )
    BUGCHECK_STR:  0xC5_2
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xC5_2_VRF_usbhub+68ba
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Nov 16 03:47:24.589 2010 (UTC - 4:00)
    System Uptime: 0 days 8:54:45.805
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_VRF_nt!_??_::FNODOBFM::_string_+33906
    BiosReleaseDate = 10/25/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov  4 12:01:02.513 2010 (UTC - 4:00)
    System Uptime: 0 days 3:34:03.839
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+22172 )
    BUGCHECK_STR:  0xC1_81
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  RhinoVersionCh
    FAILURE_BUCKET_ID:  X64_0xC1_81_VRF_nt!_??_::FNODOBFM::_string_+22172
    BiosReleaseDate = 09/10/2010
    SystemProductName = OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 6
    Windows 7 Pro x64
    Thread Starter
       #3

    Hey,
    I will run those suggested diagnostics and post my results. Thanks for your time.
      My Computer


  4. Posts : 6
    Windows 7 Pro x64
    Thread Starter
       #4

    I followed the instructions for Prime95. What am I suppose to get from it that will be useful? (sorry this is foreign to me) The process seems to be very slow it has been running for about 30 mins and is at .07%. I will run the Memtest over night tonight. I'm pretty confident the hard drive is good w/out problems. This computer is less than a year old and I run defraggler once a week.

    Do you have any alternative's to try other than the suggestions previously posted? My initial thought was that I may need a higher watt PSU. I would imagine insufficient power could cause the BSOD too right? Is there something I can download to diagnose sufficient power usage? Thanks again and sorry for my noob questions and assumptions in advance.
      My Computer


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

    The purpose of Prime95 is to stress test your computer hardware and test for large prime numbers. We only make use of the stress testing portion, which reports any hardware issues it may encounter. As this reply is now 10 hours after your post, stop the test, if you haven't already. Were any errors mentioned?

    I wouldn't expect the PSU to be the issue, although it's possible. There are no software programs to test the PSU or power usage, though you can find power supply calculators online which add up the power usage of all your components. If you were to use one, it would report you need a PSU much lower than you currently have anyway. How old is the PSU? Old PSUs do lose power capabilities, so there is a chance you may still need a new one.

    It may be worth it to test the hard drive anyway. I've had half a dozen drives fail on me within their 1 year warranty period, and defragmenting does little for the health of the drive.
      My Computer


  6. Posts : 6
    Windows 7 Pro x64
    Thread Starter
       #6

    Jonathan_King said:
    The purpose of Prime95 is to stress test your computer hardware and test for large prime numbers. We only make use of the stress testing portion, which reports any hardware issues it may encounter. As this reply is now 10 hours after your post, stop the test, if you haven't already. Were any errors mentioned?

    I wouldn't expect the PSU to be the issue, although it's possible. There are no software programs to test the PSU or power usage, though you can find power supply calculators online which add up the power usage of all your components. If you were to use one, it would report you need a PSU much lower than you currently have anyway. How old is the PSU? Old PSUs do lose power capabilities, so there is a chance you may still need a new one.

    It may be worth it to test the hard drive anyway. I've had half a dozen drives fail on me within their 1 year warranty period, and defragmenting does little for the health of the drive.
    I let prime95 run for about 2 hours before stopping it due to the CPU temps getting pretty high and I had work that needed to be done for my job. No errors were mentioned. I ran Memtest V4.20 over night, no errors. I will run the hard drive diagnostics over night and see if anything comes back. The hard drive is less than a year old and is a WD Caviar Black 750gb HDD, FYI.

    The PSU may not be the issue huh? When I unplugged a few unnecessary fans from the MB and a internal hot swap bay(which wasn't ever used) the BSOD some what stopped or at least wasn't as frequent. This is which led me to believe it was a PSU issue. The PSU is a Ultra X4 750w and was bought the same time as everything else (almost a year old).

    My assumption is it must be a hardware or driver issue somewhere in the system. Can you recommend a FREE driver updater? All the one's I've seen will scan the system for free but will not update them till you purchase their software.

    Thanks again for your help and hope we can work together to find a solution for me.
      My Computer


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

    The best driver updater: Google

    I don't trust those automatic driver updating programs, and I know the manual way is more reliable as well. Go to Device Manager (enter devmgmt.msc in the start menu), right-click on the hardware and select Properties. Note the driver date, and then go to the manufacturer's site and look at the Support or Downloads section. If you need help locating a driver, I can get you on your way.

    Drivers shouldn't be an issue though; driver verifier ran and failed to flag anything. That strongly suggests a hardware issue.
      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 17:24.
Find Us