Random BSOD


  1. Posts : 2
    Windows 7 Ultimate x64
       #1

    Random BSOD


    Hi,

    I've been getting alot of Bsod latley. I'm using my computer mostly for
    music production, but it seems the system crashes completly at random.

    Sometimes I get a bsod and sometimes the system just frezes or the screen turns black and the only option is to shut off and restart.

    The problem began when I installed my new motherboard P5Q deluxe. I suspect somekind of bios corruption problem, becuse when I restart the cumputer after a crash I recive a "bad bios checksum" and it has to repare the bios. And don't think thats to healty for the computer.

    My spec are:

    Windows 7 Ultimate x64
    Asus P5Q deluxe
    Intel C2D E8500 @ 3,16 no oc.
    Avid Mbox Pro 3 soundcard
    Hardrives:
    1. SAMSUNG SP2504C ATA Device
    2. WDC WD7500AADS-00M2B0 ATA Device
    4 x Corsair Xms2 1 gigabyte

    I couldn't run the system health report it would not finish.

    Let me know if you need more information.
      My Computer


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

    Remove your Avid Technologies software. It was the cause of one of the crashes.

    Another crash was caused by your Avid Mbox. Download the latest drivers from here - Avid - Third Generation Mbox Pro Drivers

    Update your computer to SP1 - Learn how to install Windows 7 Service Pack 1 (SP1)

    Run a system file check - SFC /SCANNOW Command - System File Checker

    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: Thu Jun 23 11:56:32.362 2011 (UTC - 4:00)
    System Uptime: 0 days 1:11:05.000
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+409e5 )
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+409e5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Thu Jun 23 10:30:39.144 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:08.782
    Probably caused by : blbdrive.sys ( blbdrive!BlbDriveAddDevice+22d )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_blbdrive!BlbDriveAddDevice+22d
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Thu Jun 16 09:36:44.030 2011 (UTC - 4:00)
    System Uptime: 0 days 0:18:35.669
    Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+736 )
    PROCESS_NAME:  WerFault.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_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!NtfsFindPrefixHashEntry+736
    BiosReleaseDate = 06/25/2008
    SystemManufacturer = System manufacturer
    SystemProductName = P5Q DELUXE
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Thu Jun 16 09:09:01.401 2011 (UTC - 4:00)
    System Uptime: 0 days 1:35:13.040
    Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+173 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+173
    BiosReleaseDate = 06/25/2008
    SystemManufacturer = System manufacturer
    SystemProductName = P5Q DELUXE
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Thu Jun 16 07:32:55.486 2011 (UTC - 4:00)
    System Uptime: 0 days 1:31:05.000
    Probably caused by : ntkrnlmp.exe ( nt!SeQueryInformationToken+15a )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  services.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!SeQueryInformationToken+15a
    BiosReleaseDate = 06/25/2008
    SystemManufacturer = System manufacturer
    SystemProductName = P5Q DELUXE
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Mon Jun 13 09:53:46.491 2011 (UTC - 4:00)
    System Uptime: 0 days 0:02:04.130
    Probably caused by : ntkrnlmp.exe ( nt!NtCreateSection+17e )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!NtCreateSection+17e
    BiosReleaseDate = 06/25/2008
    SystemManufacturer = System manufacturer
    SystemProductName = P5Q DELUXE
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Debug session time: Thu Jun  9 15:03:27.043 2011 (UTC - 4:00)
    System Uptime: 0 days 0:05:34.682
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_nt!ExDeferredFreePool+233
    BiosReleaseDate = 07/10/2009
    SystemManufacturer = System manufacturer
    SystemProductName = P5Q DELUXE
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3166
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri May  6 23:31:36.882 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:35.724
    *** WARNING: Unable to verify timestamp for diginet.sys
    *** ERROR: Module load completed but symbols could not be loaded for diginet.sys
    Probably caused by : diginet.sys ( diginet+1525 )
    BUGCHECK_STR:  0xC1_24
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_diginet+1525
    BiosReleaseDate = 03/01/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3681
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri May  6 23:29:26.976 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:15.834
    *** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
    Probably caused by : 1394ohci.sys ( 1394ohci+c6de )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_VRF_1394ohci+c6de
    BiosReleaseDate = 03/01/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3681
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri May  6 23:14:38.544 2011 (UTC - 4:00)
    System Uptime: 0 days 0:49:33.448
    *** WARNING: Unable to verify timestamp for AvidMboxPro.sys
    *** ERROR: Module load completed but symbols could not be loaded for AvidMboxPro.sys
    Probably caused by : AvidMboxPro.sys ( AvidMboxPro+5b84 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  Live 8.1.1.exe
    FAILURE_BUCKET_ID:  X64_0xD1_AvidMboxPro+5b84
    BiosReleaseDate = 03/01/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz"
    MaxSpeed:     3160
    CurrentSpeed: 3681
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thank you!

    It appears to be working now.

    I have updated to Sp 1 and downloaded the latest mbox drive and I ran the Windows Resource Protection and it did not find any integrity violations.

    I haven't had any crashes since.

    Big thanks
      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 16:05.
Find Us