Multiple BSODs

Page 1 of 2 12 LastLast

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

    Multiple BSODs - Solved?


    Hi,
    Sysytem spec:
    Windows 7 Home Premium x64 OEm
    System age 16 months
    OS last reinstalled about 2 months ago.

    I've attached a zip file with the Windows_NT6_BSOD_jcgriff2folder & the PERFMON HTML file as described in the posting instructions thread.

    I have been having BSODs randomly for the last few months (prior to and after reinstalling the OS). SOmetimes it goes weeks with no crashes, othertimes I get multiple crashes a day.

    Any help in identifying the causes and solving the problem will be greatly appreciated.


    Last edited by zzchess; 06 Jun 2011 at 12:06.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    zzchess said:
    Hi,
    Sysytem spec:
    Windows 7 Home Premium x64 OEm
    System age 16 months
    OS last reinstalled about 2 months ago.

    I've attached a zip file with the Windows_NT6_BSOD_jcgriff2folder & the PERFMON HTML file as described in the posting instructions thread.

    I have been having BSODs randomly for the last few months (prior to and after reinstalling the OS). SOmetimes it goes weeks with no crashes, othertimes I get multiple crashes a day.

    Any help in identifying the causes and solving the problem will be greatly appreciated.


    You uploaded the app instead of the results

    try this method


    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



    To ensure minidumps are enabled:

    Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    Under the Advanced tab, click on the Startup and Recovery Settings... button.
    Ensure that Automatically restart is unchecked.
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    OK your way out.
    Reboot if changes have been made.
      My Computer


  3. Posts : 908
    Vista Home Premium x86 SP2
       #3

    Hello zzchess, and welcome to the Seven Forums!

    You have done very well, and you have zipped the files correctly, but you have unfortunately zipped one of the wrong files.

    You have zipped up the .exe which you have downloaded. I assume that you have run the .exe.

    Can you please try one more time, and then zip up the folder, Windows_NT6_BSOD_jcgriff2, in your Documents folder.

    Thanks a lot, and the very best of luck!

    Richard
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    niemiro said:
    Hello zzchess, and welcome to the Seven Forums!

    You have done very well, and you have zipped the files correctly, but you have unfortunately zipped one of the wrong files.

    You have zipped up the .exe which you have downloaded. I assume that you have run the .exe.

    Can you please try one more time, and then zip up the folder, Windows_NT6_BSOD_jcgriff2, in your Documents folder.

    Thanks a lot, and the very best of luck!

    Richard
    Richard I believe your sig is missing. See attached.
      My Computer


  5. Posts : 908
    Vista Home Premium x86 SP2
       #5

    zigzag3143 said:
    niemiro said:
    Hello zzchess, and welcome to the Seven Forums!

    You have done very well, and you have zipped the files correctly, but you have unfortunately zipped one of the wrong files.

    You have zipped up the .exe which you have downloaded. I assume that you have run the .exe.

    Can you please try one more time, and then zip up the folder, Windows_NT6_BSOD_jcgriff2, in your Documents folder.

    Thanks a lot, and the very best of luck!

    Richard
    Richard I believe your sig is missing. See attached.
    Thanks a lot! It was actually an irresponsible joke: Rate signature of person above you

    However, I think that it is time for a change! I shall go on the hunt for a new, more sensible one! (you are not the first person to notice, it really is time for a change!)

    And it is not something I can stick with forever!

    Thanks again, and sorry!

    Richard
      My Computer


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

    Correct files uploaded now sorry.
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    zzchess said:
    Correct files uploaded now sorry.
    No DMP's included in upload.
      My Computer


  8. Posts : 908
    Vista Home Premium x86 SP2
       #8

    zigzag3143 said:
    zzchess said:
    Correct files uploaded now sorry.
    No DMP's included in upload.
    I get 12 dump files...

    Edit: Look at the Hosts file also
      My Computer


  9. Posts : 1,782
    Windows 7 Home Premium 64bit
       #9

    Code:
    sptd.sys     Tue Nov 23 06:47:37 2010 (4CEBA9D9)
    Uninstall Daemon Tools. Its driver, SPTD, is a known BSOD maker in Windows 7. It caused one of your crashes. Once DT is removed run the SPTD removal tool. DuplexSecure

    Please run these tests and report back the results
    1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
    2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
    3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests



    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Sat May 28 03:33:55.582 2011 (UTC - 4:00)
    System Uptime: 0 days 0:11:52.252
    Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  CurseClient.ex
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
    BiosReleaseDate = 06/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Wed May 25 10:13:12.289 2011 (UTC - 4:00)
    System Uptime: 0 days 0:13:40.959
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b16 )
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b16
    BiosReleaseDate = 06/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Apr 30 03:45:21.209 2011 (UTC - 4:00)
    System Uptime: 0 days 0:06:11.505
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    BUGCHECK_STR:  0x1a_41790
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!PoIdle+53a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Apr 17 06:26:05.651 2011 (UTC - 4:00)
    System Uptime: 0 days 0:06:44.337
    Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1c5 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  CurseClient.ex
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyWorkingSet+1c5
    BiosReleaseDate = 06/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Apr 17 06:15:32.042 2011 (UTC - 4:00)
    System Uptime: 0 days 0:02:35.727
    Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+8c )
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x24
    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsUninitializeNtfsMcb+8c
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Apr 11 10:38:40.654 2011 (UTC - 4:00)
    System Uptime: 0 days 0:15:25.339
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    BUGCHECK_STR:  0x1a_41284
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!PoIdle+53a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Apr 11 08:39:38.442 2011 (UTC - 4:00)
    System Uptime: 0 days 0:13:23.738
    Probably caused by : memory_corruption ( nt!MmZeroPageThread+823 )
    BUGCHECK_STR:  0x50
    FAILURE_BUCKET_ID:  X64_0x50_nt!MmZeroPageThread+823
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Tue Mar 15 13:44:05.608 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:11.278
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Wed Mar  9 23:21:41.467 2011 (UTC - 4:00)
    System Uptime: 0 days 11:44:40.843
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : CLFS.SYS ( CLFS!CClfsContainer::IoAsyncWriteCompletion+70 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_CLFS!CClfsContainer::IoAsyncWriteCompletion+70
    BiosReleaseDate = 11/25/2009
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Mar  7 11:08:33.127 2011 (UTC - 4:00)
    System Uptime: 0 days 0:10:30.797
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_nt!PoIdle+53a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Mar  6 07:41:08.732 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:12.402
    Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )
    BUGCHECK_STR:  0x74
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


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

    Interim update. I ran the memory and HD checks a while back at the suggestion of my PC manufacturer and had no errors. I'll check them again soon though.

    I ran two of the Prime 95 tests yesterday, the small FFT for 10 hours and the blend for 4 hours with no errors or warnings. I'm running the in-place large FFT test at the moment.
      My Computer


 
Page 1 of 2 12 LastLast

  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 00:53.
Find Us