Random BSOD Usually playing Borderlands or just watching streams.


  1. Posts : 3
    Windows 7 Ultimate X64
       #1

    Random BSOD Usually playing Borderlands or just watching streams.


    Hi, I'm new to the forum and I'm putting up my first post with my BSOD error I get. I've gotten some in the past, but I decided to learn how to figure these things out this time.

    Details:

    I usually get a BSOD in a random situation either playing online games or just watching live streams (twitch.tv) or even Youtube videos on occasion. Much help is appreciated... It's amazing what people know on these forums.

    Thanks!

    Here is my SevenForums.zip file.

    Attachment 223673
      My Computer


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

    Hello,

    I'd suspect hardware is the problem; RAM is a likely culprit. Run the three Prime95 tests, as well as Memtest86; see if either of those turn of positives.

    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: Sat Jul 28 18:29:22.349 2012 (UTC - 4:00)
    System Uptime: 0 days 4:29:44.473
    Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Steam.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Thu Jul 26 00:55:05.607 2012 (UTC - 4:00)
    System Uptime: 0 days 4:16:35.731
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1e_0
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1e_0_nt!KiKernelCalloutExceptionHandler+e
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Jul 22 02:17:16.824 2012 (UTC - 4:00)
    System Uptime: 0 days 8:40:43.587
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : USBPORT.SYS ( USBPORT!MPf_PollEndpoint+77 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xBE
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xBE_USBPORT!MPf_PollEndpoint+77
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Jul 22 02:32:50.113 2012 (UTC - 4:00)
    System Uptime: 0 days 0:14:59.237
    Probably caused by : dxgmms1.sys ( dxgmms1!memset+80 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Borderlands.ex
    FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!memset+80
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sat Jul  7 19:41:10.171 2012 (UTC - 4:00)
    System Uptime: 0 days 7:23:41.295
    Probably caused by : win32k.sys ( win32k!ValidateHwnd+89 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  uTorrent.exe
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!ValidateHwnd+89
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Fri Jul  6 18:57:35.240 2012 (UTC - 4:00)
    System Uptime: 0 days 5:42:48.988
    Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Wed Jul  4 19:02:24.634 2012 (UTC - 4:00)
    System Uptime: 0 days 1:49:12.382
    *** WARNING: Unable to verify timestamp for cdd.dll
    *** ERROR: Module load completed but symbols could not be loaded for cdd.dll
    Probably caused by : cdd.dll ( cdd+95a5 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_cdd+95a5
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Tue Jun 19 23:20:11.548 2012 (UTC - 4:00)
    System Uptime: 0 days 14:21:26.672
    Probably caused by : aswTdi.SYS ( aswTdi+5039 )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  uTorrent.exe
    FAILURE_BUCKET_ID:  X64_0x3B_aswTdi+5039
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Thu Jun 14 00:26:51.145 2012 (UTC - 4:00)
    System Uptime: 0 days 4:49:11.269
    Probably caused by : atikmdag.sys ( atikmdag+44f63f )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Diablo III.exe
    FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+44f63f
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
    Debug session time: Sun Jun 10 21:48:19.722 2012 (UTC - 4:00)
    System Uptime: 0 days 3:08:37.846
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt+85f3c )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
    Debug session time: Wed May 23 20:45:55.130 2012 (UTC - 4:00)
    System Uptime: 0 days 1:34:31.894
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt+7f190 )
    BUGCHECK_STR:  0x1e_0
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BiosReleaseDate = 05/28/2010
    SystemProductName = GA-890GPA-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 3
    Windows 7 Ultimate X64
    Thread Starter
       #3

    I will test these out. Thanks
      My Computer


  4. Posts : 3
    Windows 7 Ultimate X64
    Thread Starter
       #4

    I results are clean. I also just found out that my SSD (OCZ Agility 3 120GB) had a firmware update from version 2.15 to 2.22. I updated the firmware and so far so good. I searched around and it seems that a lot of people were getting BSOD from this firmware problem.

    Is it possible for SSD firmware to cause such things? Apparently it does.
      My Computer


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

    Yes - bad firmware can certainly cause BSODs. The Vertex 3's were the bane of BSOD analysts until updated firmware for them was released. Hopefully the BSODs are gone for good!
      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 06:57.
Find Us