BSOD while playing Starcraft 2


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD while playing Starcraft 2


    Hi all,

    recently i've been suffering from BOSD while i am playing starcraft2
    i've tried to analyse minidump but not sure what exactly to look for
    please help me out here, i've attached my recent minidump in the post

    system details
    OS Windows 7 Ultimate x64
    CPU i7 930 @4GHz (21 x 190)
    Motherboard Asus P6X58D-E
    Memory Corsair CMP6GX3M3A1600C8 6GB (3x XMS3 2GB)
    Graphics Card(s) Gigabyte GeForce GTX 460 1GB
    Sound Card x-fi xtreme music
    Monitor(s) Displays Del 2407WFP-HC
    Hard Drives Intel X25-M 80GB (System)
    PSU Corsair HX620

    cheers
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    13 memory dumps from 13 Sep to 30 Oct (about 6 weeks)
    4 different BSOD errors
    4 different causes blamed
    Still not enough to see if this is a hardware pattern or not.

    As such, please run these free diagnostics. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    Please uninstall Daemon Tools as it has been known to cause BSOD's on some Win7 installations.

    Also, please run Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP
    In the event that this post does not solve your issues, please post back with the information in this topic: https://www.sevenforums.com/crashes-d...tructions.html

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 30 04:34:33.678 2010 (UTC - 4:00)
    System Uptime: 0 days 0:56:06.693
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 24 12:00:26.511 2010 (UTC - 4:00)
    System Uptime: 0 days 8:33:35.525
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 24 03:23:55.216 2010 (UTC - 4:00)
    System Uptime: 0 days 1:16:19.231
    BugCheck D1, {f4c, d, 8, f4c}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    Bugcheck code 000000D1
    Arguments 00000000`00000f4c 00000000`0000000d 00000000`00000008 00000000`00000f4c
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 21 08:38:19.688 2010 (UTC - 4:00)
    System Uptime: 0 days 0:30:08.703
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 16 04:35:06.697 2010 (UTC - 4:00)
    System Uptime: 0 days 2:17:19.601
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    BugCheck D1, {f4b, d, 8, f4b}
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    Bugcheck code 000000D1
    Arguments 00000000`00000f4b 00000000`0000000d 00000000`00000008 00000000`00000f4b
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 10 14:25:14.408 2010 (UTC - 4:00)
    System Uptime: 0 days 9:31:24.423
    Probably caused by : hardware ( nt!KiTimerWaitTest+6f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    Bugcheck code 0000000A
    Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`032c418f
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct  8 09:16:53.194 2010 (UTC - 4:00)
    System Uptime: 0 days 5:52:57.208
    Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+411 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    Bugcheck code 0000000A
    Arguments 00000000`37800000 00000000`0000000d 00000000`00000001 fffff800`032c2661
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Oct  5 16:44:23.206 2010 (UTC - 4:00)
    System Uptime: 0 days 2:55:52.221
    BugCheck D1, {6cc, d, 8, 6cc}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    Bugcheck code 000000D1
    Arguments 00000000`000006cc 00000000`0000000d 00000000`00000008 00000000`000006cc
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct  3 09:23:54.573 2010 (UTC - 4:00)
    System Uptime: 0 days 4:54:57.588
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    Bugcheck code 0000000A
    Arguments 00000000`00004471 00000000`0000000d 00000000`00000001 fffff800`03284630
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 27 16:57:08.086 2010 (UTC - 4:00)
    System Uptime: 0 days 5:43:06.990
    BugCheck D1, {f428, d, 8, f428}
    Probably caused by : ndis.sys ( ndis! ?? ::FNODOBFM::`string'+636e )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    Bugcheck code 000000D1
    Arguments 00000000`0000f428 00000000`0000000d 00000000`00000008 00000000`0000f428
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 20 07:48:51.866 2010 (UTC - 4:00)
    System Uptime: 0 days 2:35:31.881
    BugCheck D1, {f33, d, 8, f33}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    Bugcheck code 000000D1
    Arguments 00000000`00000f33 00000000`0000000d 00000000`00000008 00000000`00000f33
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep 16 13:14:19.865 2010 (UTC - 4:00)
    System Uptime: 0 days 8:13:11.769
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 12 10:28:27.104 2010 (UTC - 4:00)
    System Uptime: 0 days 7:37:51.119
    *** WARNING: Unable to verify timestamp for ser2pl64.sys
    *** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys
    Probably caused by : ser2pl64.sys ( ser2pl64+7d61 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x44
    PROCESS_NAME:  System
    Bugcheck code 00000044
    Arguments fffffa80`0a111010 00000000`00000eae 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      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 09:27.
Find Us