DB BSODing me off :(

[werkerguy]

Hi guys,

I have just purchased the db, and it is amazeballs. I am however, experiencing an issue whereby db will crash after an hour or two. I love waking up in the mornings to see my stash filled with unid legs, and horadric caches, but alas this bug keeps spoiling my daily christmas mornings.

PC Specs:

i7-2700k
14GB Ram
R9 x270
Win 7 x64 (I previously was on Win 8.1 but downgraded after a few reformats did not resolve the issue)
DB version: 1.1.1759.349

I have zipped the logs from the last crash, as well as the minidump logs from windows. Please can someone help to resolve this, as I would love to be able to do an 8 hour session!

If I have neglected to add anything further that can be of value please let me know and I will gladly assist.

PS: Diablo is down for scheduled maintenance so you chaps that were also experiencing this problem had better hit the reply/pm button and help a brother out! No excuses hehe

Regards,
Werkerguy

View attachment db.zip

 

[jaksemurf]

Hi guys,

I have just purchased the db, and it is amazeballs. I am however, experiencing an issue whereby db will crash after an hour or two. I love waking up in the mornings to see my stash filled with unid legs, and horadric caches, but alas this bug keeps spoiling my daily christmas mornings.

PC Specs:

i7-2700k
14GB Ram
R9 x270
Win 7 x64 (I previously was on Win 8.1 but downgraded after a few reformats did not resolve the issue)
DB version: 1.1.1759.349

I have zipped the logs from the last crash, as well as the minidump logs from windows. Please can someone help to resolve this, as I would love to be able to do an 8 hour session!

If I have neglected to add anything further that can be of value please let me know and I will gladly assist.

PS: Diablo is down for scheduled maintenance so you chaps that were also experiencing this problem had better hit the reply/pm button and help a brother out! No excuses hehe

Regards,
Werkerguy

View attachment 124267

Just get R-YAR. If DB crashes, D3, or your internet crashes, it will log you back in/restart programs or whatever it needs to do to get the bot running again.

Honestly, you'll have much better success with this than anything.

I didn't notice the BSOD part. The fact that you have windows 8, which my laptop has, and which crashes for me CONSTANTLY, makes me think that it's just the fact that Windows 8 sucks and is incredibly unstable at times

 

[werkerguy]

Just get R-YAR. If DB crashes, D3, or your internet crashes, it will log you back in/restart programs or whatever it needs to do to get the bot running again.

Honestly, you'll have much better success with this than anything.

I didn't notice the BSOD part. The fact that you have windows 8, which my laptop has, and which crashes for me CONSTANTLY, makes me think that it's just the fact that Windows 8 sucks and is incredibly unstable at times

Hi Jaksemurf,

Thanks for taking the time to help me out, I am also experiencing the problem on windows 7, which I downgraded to, as I too thought it was just Win8.1 being sh!t. But alas it is still happening.

With regards to using YAR, I think that you may be on to something, as although it does BSOD, it does reboot after generating the dump file. My issue with this however, is that if I add YAR to the startup directory, it does indeed startup, but the start button within YAR needs to be pressed in order to initiate the procedure of opening diablo and DB etc. How would I get around that?

Cheers!

 

[Tony]

tried to check windows event viewer log files?

 

[werkerguy]

tried to check windows event viewer log files?

Hi Tony,

There are the DB application errors which cause the reboot:

Application: Demonbuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
Stack:
at Demonbuddy.App.Application_DispatcherUnhandledException(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.DispatcherUnhandledExceptionEventHandler.Invoke(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.Dispatcher.CatchException(System.Exception)
at System.Windows.Threading.Dispatcher.CatchExceptionStatic(System.Object, System.Exception)
at System.Windows.Threading.ExceptionWrapper.CatchException(System.Object, System.Exception, System.Delegate)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at System.Windows.Application.Run()
at Demonbuddy.App.Main()

Application: Demonbuddy.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Exception Stack: at Demonbuddy.App.Application_DispatcherUnhandledException(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs) at System.Windows.Threading.DispatcherUnhandledExceptionEventHandler.Invoke(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs) at System.Windows.Threading.Dispatcher.CatchException(System.Exception) at System.Windows.Threading.Dispatcher.CatchExceptionStatic(System.Object, System.Exception) at System.Windows.Threading.ExceptionWrapper.CatchException(System.Object, System.Exception, System.Delegate) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.Run() at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at System.Windows.Application.Run() at Demonbuddy.App.Main()

Demonbuddy.exe
1.1.1788.355
53471352
KERNELBASE.dll
6.1.7600.16385
4a5bdbdf
e0434352
0000b727
12dc
01cf55432380d0d1
C:\Users\xf\Documents\Demonbuddy\Demonbuddy.exe
C:\Windows\syswow64\KERNELBASE.dll
6852e674-c136-11e3-80c4-448a5b21b61c

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff80002e50964, 0xfffff88006ebf080, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041114-31668-01.

041114-31668-01.dmp 2014/04/11 06:59:00 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c000001d fffff800`02e50964 fffff880`06ebf080 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+71f00 C:\Windows\Minidump\041114-31668-01.dmp 8 15 7600 276*392 2014/04/11 07:00:48 AM

I hope we can isolate the problem which is causing the reboots as I lose out on bountys

Thanks

 

[Tony]

remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable
- microsoft visual c++ 2012 x86 redistributable


restart your pc,
download the installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart


let me know if that makes any difference


are you on a legit OS copy?

 

[werkerguy]

remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable
- microsoft visual c++ 2012 x86 redistributable


restart your pc,
download the installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart


let me know if that makes any difference


are you on a legit OS copy?

Hi Tony,

I will try that when I get back home today. I was initially on a legit copy of win 8.1, thought the problem was with the OS, so currently running an unregistered win 7 ultimate version, which still reboots, albeit much less frequently. I will post an update as to whether the problem has been resolved later today.

Thanks

 

[Tony]

alright,on Win8.1 skip the
remove
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended


part

 

[werkerguy]

Turns out the new motherboard I had purchased was faulty, as I swapped it out with another board from the shop and it works flawlessly!

 

[Viz]

Turns out the new motherboard I had purchased was faulty, as I swapped it out with another board from the shop and it works flawlessly!

I have the same error as you did you notice on DB prior to the crash a "out of sync error"..? I'm tired of not being able to use DB.

 

[Tony]

Turns out the new motherboard I had purchased was faulty, as I swapped it out with another board from the shop and it works flawlessly!

great