Slitherine

I've been getting this crash on a fairly regular basis since the .1 patch.

Unhandled Exception
ExpCode 0xC0000005
ExpFlags: 0
ExpAddress: 0x73515E37

can we have a Drx report as well, and any crash logs Could you please attach a DxDiag report file to your message / reply?

Please attach a DxDiag report fie.
How to get a DxDiag report file:

1. Click on "START" (on Windows 8/10 press “Windows key” and the “R” key at the same time)
2. Click "run" (skip this step on Windows 8/10)
3. Type in "dxdiag" and click "OK"
4. Check through the tabs and perform all tests
5. Click "Save all Information..." and save the text file to a location of your choice
6. Attach the file to your message

Here ya go

thanks, looking now

so the game worked fine before the first patch you say?

any error logs?

PIONEER DJM-850 is it internal or external device? and if external, what connection? USB?
i'm not saying this is the issue either, just trying to find that out, as the error code means little, if it's an external device, running the game without and if it works or doesn't rules it in or out etc.

as the only windows 10 error with your hardware, also both have the same SSD as well

Model: Samsung SSD 840 EVO 1TB
while the error codes aren't the same, the hardware is a match.

as with any conflict and error code, always try the basics first, eg

get up to date drivers installed, download any bios update for the effect devices etc, disable one and see if the error continues etc

Note that the error log is rewritten at each run, so you need to grab it immediately after the crash. Also, is this happening after you ALT+TAB? Have you tried running in windowed mode?

Cheers

Pip

I run the game in windowed mode and you are correct that this issue didn't occur in .0 RTM. I'll collect the dxdiag after the next crash, oops. I just updated the drivers for the Pioneer DJM-850 (it's a club mixer w/ a sound card)... Samsung Magician said everything was up to date. I changed the power settings to max perf and removed any sleep timers for the hardware which appears to be the fix in the TH article. Thank you Pip!

hope it all helps and works, if not pop back and we can and will try something else