|
So for several weeks I've had issues with DOTA 2 crashing without an error message. It happened after I:
-Updated Windows
-Updated graphics driver
-Updated DOTA 2
So any of those could be the issue. I've done a fresh reinstall of Dota 2, reupdated my graphics drivers, but DOTA 2 still crashes.
My autoexec at some point was deleted automatically by DOTA 2, and the format of autoexecs is now different. I'm on a 64 BIT Windows 7, and DOTA 2 currently only runs in 32 bit mode. My autoexec had a line that forced DOTA 2 to run only on 2 processors.
A fix I found that works most of the time is opening DOTA 2, opening the Task Manager, then telling the Task Manager to only run DOTA 2 on the first 2 cores of my 4-core processor. Twice now, however, when I've applied that fix, I get the following BSOD.
![[image loading]](http://i.imgur.com/wMmHESr.jpg)
I'm running Windows 7 Home Premium x64 SP 1.
PC is a custom build, i5-3570K processor.
I would REALLY like to get this figured out. It's making me quite frustrated. Any help would be great!
EDIT: I've also crashed twice while playing Heroes of the Storm, not sure if a connected issue.
|
Is it always the same type of BSOD (it's 0x9c in your example picture), or is it sometimes a different code?
This is a tool that can sometimes help to find a misbehaving driver: http://www.nirsoft.net/utils/blue_screen_view.html
Using it works by looking at the lines with colorful background in the lower half of its window. You google for the file names that are mentioned. If you are lucky it's a device driver and then you'll know what to update.
|
United Kingdom20285 Posts
|
On March 21 2015 18:53 Ropid wrote:Is it always the same type of BSOD (it's 0x9c in your example picture), or is it sometimes a different code? This is a tool that can sometimes help to find a misbehaving driver: http://www.nirsoft.net/utils/blue_screen_view.htmlUsing it works by looking at the lines with colorful background in the lower half of its window. You google for the file names that are mentioned. If you are lucky it's a device driver and then you'll know what to update.
I'm downloading, will run it later. I've had the same BSOD twice (it's only happened twice, but both times after I've applied the fix).
And yes, my CPU is stock. I haven't OC'd it (yet). The build is about 18 months old with no other irregularities, though.
|
United Kingdom20285 Posts
Hm check your CPU temps. Could be a hardware or a software issue. Probably software(?) if you're at stock
|
It's not processor temperature. According to the BSOD tool I've only received that specific BSOD once. That BSOD was caused by hal.dll, an earlier BSOD caused by ntoskrnl.exe.
Today I played Elder Scrolls Online for the first time since I've had issues, and it also crashed. Diablo 3 has not crashed for me with extensive play during this time.
|
United Kingdom20285 Posts
What's the other code/s that you got? (that one would be 9c)
idk, still looks like cpu/memory instability i think
|
The second BSOD, the older one, is 1e. I've only received the 9c once in all my BSOD history.
EDIT: If the issue is hardware, what would it be? I haven't cleaned the inside of my PC for a while and I have a dog with long hair. Or should I check for anything loose? Or look for something physically broken?
|
United Kingdom20285 Posts
EDIT: If the issue is hardware, what would it be? I haven't cleaned the inside of my PC for a while and I have a dog with long hair. Or should I check for anything loose? Or look for something physically broken?
Probably a bios setting for RAM (could try keeping the same timings but setting it down 1 speed bump, like 1600mhz to 1333mhz for example) though that's pretty wild guessing, i'm not good @ troubleshooting
|
A driver with a bug can also produce memory corruption. It will look exactly like a hardware issue, you'll see random BSODs. Do you remember if you changed something about drivers a few weeks ago when your issues began? It might also be something else that's low-level like an antivirus or backup software)?
For a hardware issue, you should just try to see what happens after you clean everything. You could also take out the RAM sticks and the graphics card and plug them back in. Same with cables, you could re-plug them all. This feels stupid, but you never know with computers. 
|
Northern Ireland22208 Posts
i can vouch for the open it up, clean, re-seat components approach for fixing random problems in computers
|
|
|
|
|
|
EPT
