BSOD only when playing Dota 2

[wak0219]

System Specs:
Windows 7 64 bit

Mobo - ASUS M4A88T-M

GPU - GTX 960 - (here is the link to the exact card I have, looks like its already overclocked)
http://www.newegg.com/Product/Product.aspx?Item=N82E16814487091&Tpk=n82e16814487091

Processor - AMD Phenom II X6 1090T

Ram - 12gb - 8gb is Gskill, 4gb is Ballistix

Power Supply - Cougar A760w

I ran a Memcheck and it came back fine. I only blue screen when I play Dota 2. Just bought the GPU in February, drivers are up to date. I had an ATI card before this one and I started having this issue. I was hoping a new card would solve the issue. I have up to date drivers on my mouse/keyboard. I managed to get a couple pictures of the error messages. I just redownloaded Dota, haven't tried playing a game since I redownloaded.

Pictures of the BSOD errors: (quality isn't the greatest)

http://i.imgur.com/WNvwaVl.jpg?1 (error for this one is "system_service_exception")
http://i.imgur.com/TW19kL4.jpg?1
http://i.imgur.com/rtKErzf.jpg?1


Any help would be greatly appreciated.

Thanks

 

[johnbl]

second bugcheck was a bad address provided by/to a USB driver.
normally you would update the BIOS to get USB fixes, update the CPU chipset driver to get USB 2.0 updates, update any usb 3.0 chipset drivers for your motherboard if you have a special USB 3.0 support.

then you have to update the actual driver for the USB device that was making the bad call.

you can debug this but with only a kernel memory dump not a mini memory dump.
certain drivers USB drivers tend to cause this problem.

the other two bugcheck were most likely caused by memory corruption from the USB subsystem. (I can not tell with the info provided but it would be consistent with the named driver in bughceck 2)

 

[wak0219]

second bugcheck was a bad address provided by/to a USB driver.
normally you would update the BIOS to get USB fixes, update the CPU chipset driver to get USB 2.0 updates, update any usb 3.0 chipset drivers for your motherboard if you have a special USB 3.0 support.

then you have to update the actual driver for the USB device that was making the bad call.

you can debug this but with only a kernel memory dump not a mini memory dump.
certain drivers USB drivers tend to cause this problem.

the other two bugcheck were most likely caused by memory corruption from the USB subsystem. (I can not tell with the info provided but it would be consistent with the named driver in bughceck 2)

my bios are the most recent version. the only usb devices i have plugged in are my mouse and keyboard which have the most recent drivers. would uploading my dump file help figure this out?

 

[johnbl]

USB problems need to have a kernel memory dump to figure out. (rather than a minidump) With a minidump I can only look at the installed drivers and the current stack and make guesses as to the cause of the problem.

The kernel memory dump will save some debugging info for USB and some internal error logs.

The best way to figure these problems out would be a kernel memory dump while verify flags are enabled. Often it will name the actual driver causing the problem.

to turn on verifier: start cmd.exe as an admin, then run
verifier.exe /standard /all
reboot your system and use the system until the next bugcheck.

use verifier.exe /reset
to turn off veifier functions when you are done testing. (or your machine will run slower than normal)

you can look here to see how to change the memory dump type in windows: https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
or google for it.

second bugcheck was a bad address provided by/to a USB driver.
normally you would update the BIOS to get USB fixes, update the CPU chipset driver to get USB 2.0 updates, update any usb 3.0 chipset drivers for your motherboard if you have a special USB 3.0 support.

then you have to update the actual driver for the USB device that was making the bad call.

you can debug this but with only a kernel memory dump not a mini memory dump.
certain drivers USB drivers tend to cause this problem.

the other two bugcheck were most likely caused by memory corruption from the USB subsystem. (I can not tell with the info provided but it would be consistent with the named driver in bughceck 2)

my bios are the most recent version. the only usb devices i have plugged in are my mouse and keyboard which have the most recent drivers. would uploading my dump file help figure this out?

 

[wak0219]

I changed it to kernel memory dump and verifier is turned on. Let's see what this finds out. I'll be back with my findings!

 

[wak0219]

So I played a couple games over the course of the past couple days with verifier running and my computer set up to make kernel dump files. No BSOD's at all for these couple days. I re downloaded dota before I posted on here but hadn't played any games to test if that was an issue. Thought re downloading it may have fixed it until today; but of course I turned verifier off thinking my computer was fine. Got a new dump file from today's BSOD, but I didn't get a picture of the error message. How can I upload this dump file?

 

[johnbl]

kernel dumps are stored at c:\windows\memory.dmp
minidumps are in c:\windows\minidump directory

you can copy the .dmp file up to any server like microsoft onedrive or mediafire and post a link.

sometimes verifier actually masks certain kinds of bugs, useful debug info will still be in the kernel dump if you put it on a server.

So I played a couple games over the course of the past couple days with verifier running and my computer set up to make kernel dump files. No BSOD's at all for these couple days. I re downloaded dota before I posted on here but hadn't played any games to test if that was an issue. Thought re downloading it may have fixed it until today; but of course I turned verifier off thinking my computer was fine. Got a new dump file from today's BSOD, but I didn't get a picture of the error message. How can I upload this dump file?

 

[wak0219]

I have the kernel dump saved on desktop. I tried compressing it and it says File not found or no read permission. When I try to upload it to Microsoft One Drive it says I don't have permission to open this file. The file size is just over 1 gig, does that have anything to do with it?

 

[johnbl]

you only have read rights in the default directory that the file is stored in.
you would have to make a copy of the file to a new location if you wanted to modify it or open the it with write permissions.

I have the kernel dump saved on desktop. I tried compressing it and it says File not found or no read permission. When I try to upload it to Microsoft One Drive it says I don't have permission to open this file. The file size is just over 1 gig, does that have anything to do with it?