What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

DB back to crashing on game creation again

S

Syn-Ack

Member
Joined
Jun 15, 2012
Messages
849
Reaction score
5
So I thought I fixed this somehow by updating to latest beta and release versions, both worked. but inevitably they started crashing too every time a game is made(well about 75% of the time). I can even go back and run db .403 release and it works just fine, and will crash occasionally same time for no reason.

I have no AV running, No firewalls. I have done multiple installs(old DB work fine still, new one work fine still too but they all crash when making new game almost 75%+ of the time) attached are 2 logs of beta version. One shows where I made a game on my own, started a whimsy profile and it completed it. and upon creating new game D3 crashed and a error report came up asking if I Wanted to send into blizzard. I should mention about a week ago I was running .403 release with rift bot, and it had about 100 hours total logged on ONE character. One session went about 28 hours nonstop with no issues, Then out of no where about a couple of days ago this crash started happening. I can't find a link to whats causing it. I have literally NOTHING open but d3, firefox, notepad etc.

I have tried with it all closed to no avail. I have seen similar posts in this section of ppl getting the game creation crash, some people it gets fixed with no changes made what so ever it just happens on its own.
 

Attachments

Any and all profiles, doesn't matter which one. it happens on game creation, no matter if delay is set to 5-6 seconds or 30-60 seconds, diablo 3 itself crashes each time. I can make a T6 game myself, start the bot, and it runs fine no crashes no issues. profiles like rrix grift is proof cuz it doesn't leave game, itll run forever unless it hits a inactivity timer snag then exits game and if it tries to remake itll crash. Ive used rrix rift, yet another riftbot, whimsy profiles, staff of herding profiles, a1 and a4 bounty profiles. they ALL work, bounties too, I just have to make the game then set the recreate timer to something like 60 seconds so I got extra time to make the game myself then soon as i make game, bot takes over normally.
 
diablo 3 crashes on game creation, and db gracefully closes.
happens with WiN Act 1 bounties and also with rrrix rift profile when gold timer expires, leaves game and then creates new crash.
 
Syn-Ack said:
Any and all profiles, doesn't matter which one. it happens on game creation, no matter if delay is set to 5-6 seconds or 30-60 seconds, diablo 3 itself crashes each time. I can make a T6 game myself, start the bot, and it runs fine no crashes no issues. profiles like rrix grift is proof cuz it doesn't leave game, itll run forever unless it hits a inactivity timer snag then exits game and if it tries to remake itll crash. Ive used rrix rift, yet another riftbot, whimsy profiles, staff of herding profiles, a1 and a4 bounty profiles. they ALL work, bounties too, I just have to make the game then set the recreate timer to something like 60 seconds so I got extra time to make the game myself then soon as i make game, bot takes over normally.
Click to expand...

pm me your Skype and we will teamviewer it
 
I double checked my nvidia stuff, because it has shadowplay in it. But its been inactive and fine until recently. when I saw almost every post about people crashing upon making a game, they were USING a nvidia card which meant they had Nvidia Experience program that has shadowplay in it that can be enabled/disabled. Not sure why all of a sudden, or if shadowplay is the true cause of it. But Its the one thing I see in common with everything, I Never updated my nvidia drivers or anything during the period the crashes weren't happening then started happening.

I just shut down Nvidia experience all together, I am going to try it a few more times now that D3 is done with maintenance. If it still does not work which I think it won't. I will PM you my skype I just gotta make an account.


nvidia gtx card series
https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/215438-d3-crash-start-game.html

nvidia gtx card series
https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/215083-versions-d3-crash.html

another nvidia gtx series same crash issue
https://www.thebuddyforum.com/demon...rt/214309-diablo-3-consistently-crashing.html
 
Syn-Ack said:
I double checked my nvidia stuff, because it has shadowplay in it. But its been inactive and fine until recently. when I saw almost every post about people crashing upon making a game, they were USING a nvidia card which meant they had Nvidia Experience program that has shadowplay in it that can be enabled/disabled. Not sure why all of a sudden, or if shadowplay is the true cause of it. But Its the one thing I see in common with everything, I Never updated my nvidia drivers or anything during the period the crashes weren't happening then started happening.

I just shut down Nvidia experience all together, I am going to try it a few more times now that D3 is done with maintenance. If it still does not work which I think it won't. I will PM you my skype I just gotta make an account.


nvidia gtx card series
https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/215438-d3-crash-start-game.html

nvidia gtx card series
https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/215083-versions-d3-crash.html

another nvidia gtx series same crash issue
https://www.thebuddyforum.com/demon...rt/214309-diablo-3-consistently-crashing.html
Click to expand...

So, was Nvidia experience the problem?
 
Yes it appears nvidia is the common link to this. I noticed throughout all the things it just happened within the last few weeks. So I can only assume that these nvidia users like me, had some sort of 'forced' update for Nvidia Experience(I do not have auto updates for mine, I choose when I want to do it, but this must of been something else they did that required no request) Because before that, I ran DB/D3 with nvidia experience open all the time, in fact I used to have it OPEN while I was botting because it would suggest optimal changes for either performance or best game play and set them or tell me what to switch.

Now, as long as I exit the nvidia experience program each time it works fine. Though it does have some service setup that reboots it every 12 hours or so which you can disable if you wanted. Personally I am fine with keeping it exited out manually as I am now taking a liking to shadowplay and using it in another game to record video.

So if your going to close this link, For future reference Tony I am pretty much 100% positive that if you come across any other people where D3 crashes on game creation, and you see in their log file that they run an nvidia card. You can use this as a reference that even if they DONT use shadowplay or the nvidia app, it will effect the game crashing in the background due to latest forced update anyway. All they have to do is exit the program, and it should stay out for 12+ hours or longer until services restarts it.
 
I uninstalled Nvidia Experience, it worked for a while but D3 started crashing again...
 
Check your processes that are running, Look for nvidia related ones. such as something like nvidiastreamer and its labeled as a capture service, I force kill that along with all the other nvidia ones I can(2 are denied access because they are essential to your video card running) You shouldn't need to kill them all, but a simple uninstall of the experience wouldn't fix it I don't think. As I mentioned something restarts the service every 12 hours or something, not JUST the nvidia experience, but whatever is the actual process causing the crash.

Just in case, Double check that it IS because of nvidia and not another reason. to test this theory, do this:

open d3, open db, start your bot. if diablo 3 crashes upon demonbuddy opening the game THEN TRY THIS

open d3, open db again, THIS TIME make your own game t1-t6 whatever you wish to bot on. THEN START YOUR BOT. If the bot CRASHES then it is something else, if the bot DOES NOT crash then it is in fact nvidia related.

The reason why I will confirm 100% this works is because to avoid getting around crashes, and being able to bot before I figured this out I was starting my own T6 games, then clicking Start on demonbuddy and it worked fine although if it tripped inactivity it would crash obviously on next game remake. But if your running rrix profile which almost never remakes, its good, and you can manually pause the bot, make a new game on your own every few hours to 'change the loot pool' up(this main reason most of profiles don't stay in the same game, blizz has confirmed that loot servers exists where you can probably not get a certain item if you spend 20hrs+ in a game, it just won't drop period. But if it drops in your game, you are more likely to see it again. Hence people who used to find furnaces, witching hours and such would keep those games alive for people who hunted them with rifts/gambles.
 
Syn-Ack said:
Check your processes that are running, Look for nvidia related ones. such as something like nvidiastreamer and its labeled as a capture service, I force kill that along with all the other nvidia ones I can(2 are denied access because they are essential to your video card running) You shouldn't need to kill them all, but a simple uninstall of the experience wouldn't fix it I don't think. As I mentioned something restarts the service every 12 hours or something, not JUST the nvidia experience, but whatever is the actual process causing the crash.

Just in case, Double check that it IS because of nvidia and not another reason. to test this theory, do this:

open d3, open db, start your bot. if diablo 3 crashes upon demonbuddy opening the game THEN TRY THIS

open d3, open db again, THIS TIME make your own game t1-t6 whatever you wish to bot on. THEN START YOUR BOT. If the bot CRASHES then it is something else, if the bot DOES NOT crash then it is in fact nvidia related.

The reason why I will confirm 100% this works is because to avoid getting around crashes, and being able to bot before I figured this out I was starting my own T6 games, then clicking Start on demonbuddy and it worked fine although if it tripped inactivity it would crash obviously on next game remake. But if your running rrix profile which almost never remakes, its good, and you can manually pause the bot, make a new game on your own every few hours to 'change the loot pool' up(this main reason most of profiles don't stay in the same game, blizz has confirmed that loot servers exists where you can probably not get a certain item if you spend 20hrs+ in a game, it just won't drop period. But if it drops in your game, you are more likely to see it again. Hence people who used to find furnaces, witching hours and such would keep those games alive for people who hunted them with rifts/gambles.
Click to expand...

I opened my own thread.

I can confirm that it only crashes on game creation. I've been using your strategy with R-RIFT profile, and it's working just fine.
 
I'm using ATI card and have the same problem, game crashed everytime ..
 
I know ATI has a similar program to nvidia experience, But I have not used an ATI card or the software for the video card(catalyst control center iirc) in a very long time. You may wish to look into the CCC.exe if i remember correctly, pull it up, check the processes against the link to ones that don't work. try and exit the control center completely. but before you do any of that, try the thing I mentioned. about creating a game yourself then starting the bot, as opposed to starting the bot at character screen and making a game via bot.

As Thatsme described, he is able to bot via making his own games but it crashes on game creation. So best suggestion is to try that, then follow up with the CC.
 
im new to this, obviously, this is my 2nd post. I've had db for like 4-5 days I think and it has been temperamental since day 1. I've had the same issues, that's how I ended up on this post. but 2 days ago I ran it before I left for work at 5:30 am and it was still running when I got home. I decided to leave it on since it was actually working without me needing to tend to it every few games, and left it on all night. it was working for more than 24 hours flawlessly. I stopped it because 24+ hours straight is too much in my book and did nothing else on the computer or diablo, didn't restart, shutdown, suspend, sleep; I literally did nothing. start diablo and db up again the next day, and its back to the same random crashing.
 
Thats why i mentioned services, you could have done nothing at all. but your computer could have automatically opened a program in the background via services or other automated stuff causing it to crash. however without seeing a log file of your own I don't even know where to begin, or if yours is even related to nvidia experience game creation crash only etc. this thread was originally made and then found out to be specifically for nvidia cards with diablo 3 crashing on DB game creation --- however working just fine if bot is started after you make the game yourself its a surefire way to tell if you have the nvidia experience issue
 
You must log in or register to reply here.
Back
Top