BSOD when trying to stream or play arma 2


  1. Posts : 6
    Windows 7 Professional x64
       #1

    BSOD when trying to stream or play arma 2


    Please help! I have been getting this blue screen ever since I built computer. Always happens right when I am launching programs like games or stream.

    CPU: i7 2600k
    GPU: EVGA 570 GTX
    8gb gskil 1866 ram
    windows 7 pro x64


    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000041790
    BCP2: FFFFFA800192F240
    BCP3: 000000000000FFFF
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    OS Windows 7 Professional x64
    CPU i7 2600k
    Motherboard Asus P8Z68V-PRO
    Memory 8gb gskill 1866
    Graphics Card EVGA 570 GTX
    Screen Resolution 1920x1080

    Keyboard Steelseries 6gv2
    Mouse Logitech G400
    PSU Silverstone 800W
    Case Rosewill Challenger
    Cooling Corsair H60 High Performance Liquid Cooler
    Hard Drives Crucial M4 128GB SSD OCZ 60GB SSD Western Digital 500GB HDD
      My Computer


  2. Posts : 6
    Windows 7 Professional x64
    Thread Starter
       #2

    Accidental double post sorry, but thank you very much to anybody who can take the time to help me!
      My Computer


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

    Hello,

    Try running the three Prime95 tests, as well as Memtest86. It looks to me like there's a hardware problem showing its head.

    RAM - Test with Memtest86+

    Hardware - Stress Test With Prime95

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Jul 30 23:27:37.037 2012 (UTC - 4:00)
    System Uptime: 0 days 0:35:40.849
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  nvSCPAPISvr.ex
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Jul 29 17:47:02.497 2012 (UTC - 4:00)
    System Uptime: 1 days 5:23:32.309
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x24
    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteScb+108
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Jul 22 16:59:37.161 2012 (UTC - 4:00)
    System Uptime: 0 days 2:50:35.974
    Probably caused by : nvoclk64.sys ( nvoclk64+1ab7 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  NVMonitor.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nvoclk64+1ab7
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Aug  5 13:34:28.039 2012 (UTC - 4:00)
    System Uptime: 0 days 0:57:50.162
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Aug  5 13:38:08.475 2012 (UTC - 4:00)
    System Uptime: 0 days 0:02:57.287
    Probably caused by : win32k.sys ( win32k!bSpDwmValidateSurface+e68 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  XSplit.Core.ex
    FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!bSpDwmValidateSurface+e68
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Aug  5 13:51:06.554 2012 (UTC - 4:00)
    System Uptime: 0 days 0:12:15.366
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
    BiosReleaseDate = 09/16/2011
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


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

    Thank you very much Jonathan! After running both the tests, I found the culprit (one of the ram sticks) and I made sure to move them around and keep running the tests to verify that it wasn't the slot itself. Thanks again!
      My Computer


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

    You're welcome, glad to hear it!
      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 18:37.
Find Us