I am having some Bsods while playing starcraft 2

[xsurfer808]

I have been having bsod crashes while playing starcraft 2 quite frequenlty I need help please.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002B04675
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\080810-24991-01.dmp
C:\Users\PanicX\AppData\Local\Temp\WER-87641-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
I attached the minidump file with it

 

[ttran]

Can you upload more DMP? You've said you got BSODs quite frequent, if so please upload the rest of them to us.
For this DMP, USBPORT.sys was blamed. One generic thing to try is go to device manager, under USB list, uninstall everything then restart your machine. You might want to update keyboard driver or mouse driver etc..

Run system files check:

Open an elevated command prompt and enter sfc /scannow.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.520\080810-24991-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Mon Aug  9 02:54:45.628 2010 (UTC + 7:00)
System Uptime: 1 days 0:08:03.408
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 1, fffff80002b04675}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8 )

Followup: MachineOwner
---------

 

[xsurfer808]

Thanks so much for getting back to me quickly. I unistalled everything then reinstalled the drivers again with updated versions. I recently have done a clean install of windows a few days ago I think the front usb ports might be damaged could this possibly attribute to the problem, I assume it would but am not a hundred percent sure. MightI just want to unplug the front ports from the board? Here is the other .dmp that I have had since the reinstall of windows

 

[ttran]

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:

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:

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: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[xsurfer808]

Thanks for the advice I have ran meemtest x86 for ten passes ram is stable and working fine I had some overheating cpu issues put on the crosair h50 no more overheating issues. I did run an sfc /scannow and everything checked out, I am not a computer illeterate person I did these things prior to coming here and again last night just to doubble check them. This is the reason i am here asking for help. because I have tried alot and cant seem to narrow down the problem. I do appriciate the time you have spent helping me thank you.

 

[xsurfer808]

Well I had another bsod while playing starcraft 2 no idea what caused it yet again, this time all drivers are updated some help again kind people. here is my minidump file.

Thanks for all the help so far!

 

[ttran]

Hi there,
Things looks better this time, dxgmms1.sys was blamed in the DMP. I would suggest you to download and install fresh copy of graphic card.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Also, please update directX as wells:
Download details: DirectX End-User Runtime

BUGCHECK SUMMARY:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.012\081410-16208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Sat Aug 14 15:46:17.685 2010 (UTC + 7:00)
System Uptime: 0 days 6:33:21.464
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa832741b030, 5, 0, fffff880109430d7}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+87 )

Followup: MachineOwner
---------

Regard,

Tuan

 

[xsurfer808]

Here is the latest this one happend while playing CoDMW2.
Thanks again for the help

 

[ttran]

It was caused by your graphic card, see if you can borrow a graphic card from friends to try on your system. Stop code 7E is potentially caused by graphic card and dxgmms1.sys was blamed.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED http://www.carrona.org/bsodindx.html#top

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

BUGCHECK SUMMARY:

BugCheck 1000007E, {ffffffffc0000005, fffff880109b87ac, fffff880035d0788, fffff880035cfff0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )

Followup: MachineOwner
---------
PROCESS_NAME:  System

Regard,

Tuan

 

[xsurfer808]

Got another one could this be a hardware problem?

 

[ttran]

Based on what we have discussed so far, if it is hardware problem, the first piece of hardware I suspect should be the graphic card. Have you done what I was trying to tell you to do about borrowing a graphic card? The new dmp didn't tell us much result except I just realize you have 2 out of date drivers and perhaps you might want to update them:

fffff880`02b2f000 fffff880`02b39000   CLBStor  CLBStor.sys  Wed Dec 31 17:02:34 2008 (495B433A)
fffff880`04455000 fffff880`044bd000   CLBUDF   CLBUDF.SYS   Wed Dec 31 17:02:30 2008 (495B4336)

They belong to UDF File System Driver - UDF File System Driver - CyberLink Corporation.

What third party firewall or av are you using? Stop code 3B are potentia;lly caused by that

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.528\081710-18314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Tue Aug 17 14:08:46.842 2010 (UTC + 7:00)
System Uptime: 0 days 10:41:42.247
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001ab650, fffff8800382c090, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

Regard,

Tuan

 

[xsurfer808]

I use microsoft security essentails. I have cyberlink powerdvd 8 to play my bluerays could that be what needs to be updated? I have onboard graphics on my mobo a 8800 nvidia card, I am running onboard as of right now. I have a 9600gt that I let my brother borrow that I am getting back in a week. I would just send mine of to get ia new one its a month and a half old so its still under warranty. I really am not satisfied with it anyway and was thinking of going with a dx11 card just havent decided on what to buy after having so many issues with the one I have right now.

 

[xsurfer808]

Should I possibly update my bios??? I think its out of date

 

[xsurfer808]

yet another bluescreen with different a different code I hate this computer now.

 

[ttran]

Hi,

The dump didn't tell us much. Please enable Driver Verifier:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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).

I have cyberlink powerdvd 8 to play my bluerays could that be what needs to be updated?

Definitely YES

Should I possibly update my bios??? I think its out of date

I think it's the right time to do that, go ahead and looks for newest version of BIOS update.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.692\081810-16754-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Wed Aug 18 14:15:20.500 2010 (UTC + 7:00)
System Uptime: 0 days 2:40:20.279
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002fe133e}

Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+25 )

Followup: MachineOwner
---------

 

[xsurfer808]

Just wanted to say thanks, It been a few days since any bsod and I have been playing games heavily. I updates the bios ran drver verifier my gts 250 is back in and working very well ran been monitoring with gpu-Z Updated the bios and got rid of the powerdvd software and got a power dvd 10 ultra copy verified all my drivers things definetly seem to be looking up. Hopefully everything will contiue to work properly thanks again for all the help.

 

[ttran]

Very nice! Hope never see you again...haha just kidding, just no more BSODs for you

 

[dranfu]

Just in case.

Have you checked this article: windows 7 64 bit BSOD - dxgmms1.sys ?