Unity 3d crashes windows with BSOD

Toggle sidebar Toggle sidebar
C

Chris_32

Reputable
Sep 30, 2015
16
0
4,510
I've just built a new computer and while not top of the line, it is fairly decent. It serves as my gaming machine and also for my game development machine. I have been able to run several games on it in 4k without issues and many other programs such as Photoshop. Computer is working amazingly.

However, I have just recently encountered an odd situation. Unity 3D is crashing my computer and creating a BSOD with error "Whea uncorrectable error". The thing that is odd is it's only doing it if I start a new project in 3D mode or open an existing project that was started in 3D mode. If I choose 2D mode, I can create the project and it doesn't crash.

Unity will usually get booted up and I will see something about Ambient probes and "Failed to bake Ambient probe" or something close to that wording.

Once the computer reboots, I'll notice that everything looks darker. Rebooting doesn't seem to fix that, but reinstalling my graphic drivers does fix the dimness. I'm using the Asus 1080 TI graphics card and as I mentioned, it works great on all the games I've thrown at it.

I have run memory checks and cpu checks and even ran prime95 for some stress testing, but nothing shows problems or crashes Windows. So far, it's just something in Unity 3D when I try to access or create a project with 3D selected.

Any help is greatly appreciated. I'm still under the holiday return policy if it is a hardware issue, but it just doesn't feel like it is. Thanks.

i7-8700k
ASRock Fatal1ty Z370 Gaming K6
Asus 1080TI OC
Samsung evo 960 1 TB with Windows 10 installed.
16 GB Gskill ram (2 8GB sticks)
 
WHEA = Windows Hardware Error Architecture. Its an error called by CPU but not necessarily caused by it.
Remove any overclocks till we work out problem,

Could run Intel Processor Diagnostic Tool on CPU, just to back up Prime 95
Can be caused by Heat
Can be caused by overclocking software, so remove anything like MSI Afterburner, Asus GPU Tweak 2, Intel Extreme Tuning Utility

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 


Thank you.
I ran the intel processor diagnostic tool already and it passed, no issues reported.
I have been using the CAM software to monitor heat, and even when gaming it doesn't get hot. Running a new project in Unity is not creating any heat to be worried about.

The asus is the OC edition and it does have the GPU tweak. I can try removing that. Just odd that none of my games create issues, but Unity does.

I have looked at the BSOD minidump. It claimed the BSOD was because of genuine intel with error 124. I'll post it up somewhere.

I did have the CPU overclocked, so I turned that off and tried running Unity and it still gave me the BSOD.

 
GPU Tweak includes a sys file called ASio.sys that can play havoc with CPU commands, its the main reason I mention it by name. Its funny though as I use it myself and haven't had any problems so far (might be jinxing myself now) in over 2 years. Guess I don't play any games though

error 0124 = WHEA, its how i knew what you got... why is another story.
 


Removed GPU tweak and it still does the same thing.

I'm also asking on Unity's side as so far nothing else is causing the BSOD. And while I doubt Unity has any special drivers, if I can maybe get a better idea of what is going on at the start, perhaps that will help narrow it down.

As well as looking into the Unity Logs to see if it reports anything.

 
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/42uV.html

File: 122717-9828-01.dmp (Dec 27 2017 - 12:00:55)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 1 Day(s), 12 Hour(s), 07 Min(s), and 18 Sec(s)

The GPU tweaking driver "iomap64.sys" was found on your system. Remove all overclocks.

I can't help you with this. Wait for additional replies. Good luck.
 


Thanks for taking a look. I removed all overclocks and had no luck with it fixing the Unity issue, so I just put the gpu tweak back on. I guess I forgot about it when I did this dump, I should probably do another without it.

https://drive.google.com/open?id=1V76SMXvlkAdvis-6W73NSx0st1jK0tXh

Ok, this dump is with all overclocking off. the gpu tweak uninstalled, and the computer freshly rebooted. I went straight to trying to load up Unity for a 3D project and still got a BSOD.

I also just uninstalled CAM. I was using it to monitor stuff without using any of the tweaking features, but I saw in that report that it mentioned it created issues in Windows 10. Sadly, still no change.
 
I don't know if this helps. I created a 2D project in Unity and then tried to convert it to a 3D project by switching things over to match what a 3d project would be.

First test I started adding things to the scene, switching out of 2D mode, etc. Finally I got into the lighting. Unity includes a Default-Skybox material. I added that to the Skybox Material. Then, there is a Auto-Generate toggle, I hit that. Suddenly it froze and crashed. Second test I only added the Skybox material and turned on Auto Generate and it crashed again. Third test I tried it in the opposite order and it crashed.

Unity console showed Ambient Probes job failed with error code: 2 ("Failed to bake the ambient probe").

I just stressed tested my CPU again using intels extreme tuning Utility this time and it ran the CPU at full load, no temp issues and passed just fine. Not sure what else to check.
 
Try removing CAM 3 from PC as well. According to the one dump file Gardenman looked at, CAM 3 Advanced PC monitoring software by NZXT - WARNING: The 2008 version is known to cause problems with Windows 10. Uninstall. (Your version is from July 2008). I think newest version is 3.5 now.

Might want to update the realtek HD Audio drivers but they shouldn't cause WHEA errors.

normally whea only caused by Overclocking software or a Hardware problem. Given the NZXT programs is your case and likely linked to the motherboard (?), it could be cause

I can''t read the dmp files so i will wait and see if ASio.sys is still showing on your system
 
AsIO.sys - Asus Input Output driver is still on your PC, and from helping people try to remove it before, it can be a pain to remove. This can cause WHEA errors. Have you got any Asus programs on PC still?
 


Yeah, I already removed the CAM when I saw it mention it was outdated. There was no change.

I had removed the overclock software for the Asus card. That was the only thing I added from the graphics card CD. The drivers come from Nvidia through their experience software.

I'll double check if there is maybe something else that got installed with the overclock software, but I don't recall being prompted for additional stuff.
 
do you have anything called PC Probe 2 installed? the asIO.sys file can be part of 3 programs:
AI Suite (matches Asus motherboards)
GPU Tweak 2 (Matches Asus GPU
PC Probe 2

As you don't have an Asus motherboard, you shouldn't have AI Suite installed. It might be a left over from GPU Tweak 2 in which case I hate Asus as it should have removed the driver when you uninstalled it.

I was curious if it was also part of an Asrock program but they stopped being associated with Asus in 2010 and I would expect their software to be different by now.

one way to figure out what its attached to is search PC for it and see what file path it shows in.. probably drivers32 but worth a try.
 


I do not have PC probe 2 or AI Suite installed.
The only other asus I found was the registration thing, which I uninstalled just in case :)

When I searched for the file
asIO.sys is located in
c:\Windows\SysWOW64\drivers

 
okay, so its showing in the 32 bit drivers folder... syswow64 = system windows on windows, its how 32bit programs can run on 64bit windwws.

i was hoping it would be in another folder.

Shame we can't run that program that causes BSOD in safe mode, as then it would remove the ASio.sys file from running, and might tell me if I am chasing the wrong thing. WHEA errors can be any hardware, I am just fixated on this file and it might not be cause. If you BSOD in safe mode, its not a driver

this explains what an ambient Probe is: https://docs.unity3d.com/ScriptReference/RenderSettings-ambientProbe.html

I wonder if the TI has problems with Unity specifically, you might want to ask on here: https://forum.unity.com/threads/unity-editor-will-not-open-present-as-a-background-task.486216/
 


Yeah, I've been trying to look into the error and the light baking and such, but I haven't been able to get much out of it.

I do have a post over on Unity's forum, but the same results as the post you linked. It's hard to get an official response from Unity and since I couldn't find any case similar to mine, I'm not holding my breath for a response.

Should I just delete/rename/move the asio.sys file?

 
see if lets you rename it, i wouldn't delete it just in case it causes something else to break.

Could also try asking on Nvidia forums about Unity

maybe related: https://forum.unity.com/threads/crash-unity-with-windows-10-fall-creators-update-1709-and-nvidia-issue.505749/

 
I tried working with Nvidia, and they were very helpful, but no luck. I'm now not sure what to try. What piece might be bad if it were a hardware issue?

I should also add that I also have had a BSOD with the CLOCK_WATCHDOG_TIMEOUT, which when I look up, someone mentions is usually a driver error or the OS doesn't work with the processor well. They don't suggest it's hardware related, but could it be the cpu? I have the 8700k, which I know is a new chip, just wondering if it's bad or some flaw.
 
I started seeing some other odd behavior. The first is it froze on the battle.net login dialogue box. I'd open it and then it would freeze the computer before crashing (no bsod)

I then had another game that was working fine start crashing on me, though this one didn't freeze the computer. Game would crash with the error during loading. I tried to fix the game and reinstall it and still ran into the issue.

So I tried to reinstall windows fresh. I then updated only the graphic drivers and installed Unity. Unity still created a BSOD.

Still lost on what could be wrong.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom