No Man's Sky

No Man's Sky

View Stats:
Rigid Tongue Aug 19, 2019 @ 10:47pm
When I exit NMS to desktop i get the bsod thing and my computer reboots.
I can play the game with no problems (apart from the stuttering now and then) but as soon as i exit to desktop i get the blue screen thingy and my computer reboots. Any info on this subject would be mostly apreciated. Thanks
Originally posted by The-Gizmo:
Lol, looks like I managed to figure out my case. It's using the classic theme (and possibly basic theme) in Windows 7. Basically any theme that disables the DWM will cause NVIDIA drivers (I assume it's NVIDIA related) to BSOD when closing a Vulkan based game, possibly in fullscreen as the game X4 doesn't have this issue for me and does use Vulkan.

I switched to the Aero theme so that DWM will be enabled, no more BSODs when exiting or changing resolution.
< >
Showing 1-15 of 25 comments
Reina Bunny Aug 20, 2019 @ 11:15pm 
This same thing happens to my friend. They can play the game just fine (we just played for 3-4 hours), and then when they exit to desktop, their computer blue screens.

Have you figured out a solution, OP?
Rigid Tongue Aug 20, 2019 @ 11:50pm 
no sorry. Done everything except clean reinstall of os. But not doin that since my others games plays fine.
Scynix Aug 20, 2019 @ 11:54pm 
What error pops up on the blue screen? Do you recall? You should take a picture with your phone if you can. Usually BSOD's will give some kind of indicator to what caused them, like a memory fault. Though it's usually only helpful part of the time, it might help figure out why your game crashes. Maybe it's failing to unload the memory NMS grabbed?
Kazongas Aug 21, 2019 @ 12:02am 
My steam used to crash when i exited NMS. Maybe your steam crashing is creating the BSOD. Just a thought. I configured my controller properly and it fixed it.
Rigid Tongue Aug 21, 2019 @ 1:00am 
Originally posted by Scynix:
What error pops up on the blue screen? Do you recall? You should take a picture with your phone if you can. Usually BSOD's will give some kind of indicator to what caused them, like a memory fault. Though it's usually only helpful part of the time, it might help figure out why your game crashes. Maybe it's failing to unload the memory NMS grabbed?

its says event 41 task 63, which says this "When the Kernel-Power EventID 41 Task 63 is analyzed in such a manner, it's found that it's often one of the drivers on your computer". But i have checked many, many times. Everything is fine. Got me buggered. lol
Scynix Aug 21, 2019 @ 1:21am 
Not sure if it helps, but I know what event 41 is. It means the system didn't shut down properly previously, which can actually lead to corrupted windows files. Sometimes a failing OS can cause this, sometimes a failing CPU. Unfortunately, it can encompass everything from just a file being corrupted to your system failing. It's an irritating error to fix.

Do you have any other games that are experiencing the same thing? I was crashing with Beyond until I updated to the newest geforce drivers for my card.

I can suggest a few things to check, but you won't be happy with them.
The primary causes are all power related: Overclocking causing a kernal error, Memory failing,
Power supply failing, CPU overheating, or Windows kernal corrupted.
This error is most commonly associated with hardware failure, but if you only started experiencing this with NMS, maybe when NMS crashed your system it corrupted one of the more important windows libraries.

You could try running windows recovery, but ... yeah, this is a rough one. It'll take a lot of trial and error to figure out whats causing it. I'd suggest starting with reinstalling NMS, Uninstalling any drivers used by NMS and reinstalling them fresh, then running the windows recovery... if you still crash, you might have to consider doing some hardware testing.

I unfortunately had this happen a few years ago, exact same error, but it was being caused by the dust on my CPU overheating and crashing. Exact same power failure error, too.

My source: I work for a major data center in vegas. I work on servers every day. Unfortunately, this kind of error is most often the single most irritating thing to try to troubleshoot.

I hope something in this helps you.
Rigid Tongue Aug 21, 2019 @ 1:32am 
Originally posted by Scynix:
Not sure if it helps, but I know what event 41 is. It means the system didn't shut down properly previously, which can actually lead to corrupted windows files. Sometimes a failing OS can cause this, sometimes a failing CPU. Unfortunately, it can encompass everything from just a file being corrupted to your system failing. It's an irritating error to fix.

Do you have any other games that are experiencing the same thing? I was crashing with Beyond until I updated to the newest geforce drivers for my card.

I can suggest a few things to check, but you won't be happy with them.
The primary causes are all power related: Overclocking causing a kernal error, Memory failing,
Power supply failing, CPU overheating, or Windows kernal corrupted.
This error is most commonly associated with hardware failure, but if you only started experiencing this with NMS, maybe when NMS crashed your system it corrupted one of the more important windows libraries.

You could try running windows recovery, but ... yeah, this is a rough one. It'll take a lot of trial and error to figure out whats causing it. I'd suggest starting with reinstalling NMS, Uninstalling any drivers used by NMS and reinstalling them fresh, then running the windows recovery... if you still crash, you might have to consider doing some hardware testing.

I unfortunately had this happen a few years ago, exact same error, but it was being caused by the dust on my CPU overheating and crashing. Exact same power failure error, too.

My source: I work for a major data center in vegas. I work on servers every day. Unfortunately, this kind of error is most often the single most irritating thing to try to troubleshoot.

I hope something in this helps you.

Yeah i have checked everything there and is fine. My hardware has been tested and all is good too. Have no problems when any other game i play so thats why i dont know. I will try the recoverey thing and get back to you. Thanks.
The-Gizmo Aug 21, 2019 @ 9:23am 
FWIW I have the exact same issue. The game plays 100% fine, then when I exit, BSOD. Also, if I change resolutions, that will also trigger it, every single time 100% reproducible. I've encountered this with DOOM when run in Vulkan, but OpenGL worked just fine no issues. Seems to be related to NVIDIA and Vulkan in my experience.

I did a crash dump analysis, and it BSODs in NMS in roughly the same spot DOOM running Vulkan did for me: "Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+7e )"

I'm going to try to see if the game runs in Linux under Proton, if so, then problem solved most likely.
The author of this thread has indicated that this post answers the original topic.
The-Gizmo Aug 21, 2019 @ 9:57am 
Lol, looks like I managed to figure out my case. It's using the classic theme (and possibly basic theme) in Windows 7. Basically any theme that disables the DWM will cause NVIDIA drivers (I assume it's NVIDIA related) to BSOD when closing a Vulkan based game, possibly in fullscreen as the game X4 doesn't have this issue for me and does use Vulkan.

I switched to the Aero theme so that DWM will be enabled, no more BSODs when exiting or changing resolution.
Reina Bunny Aug 21, 2019 @ 3:42pm 
Originally posted by The-Gizmo:
Lol, looks like I managed to figure out my case. It's using the classic theme (and possibly basic theme) in Windows 7. Basically any theme that disables the DWM will cause NVIDIA drivers (I assume it's NVIDIA related) to BSOD when closing a Vulkan based game, possibly in fullscreen as the game X4 doesn't have this issue for me and does use Vulkan.

I switched to the Aero theme so that DWM will be enabled, no more BSODs when exiting or changing resolution.

I'll have my friend try this when they get home from work. Here's to hoping!
Sans Aug 21, 2019 @ 3:47pm 
Latest experimental fix log states:

Fixed a crash that could occur when quitting the game.

Should go live by tomorrow at the latest.
Sorry your having issues. Just a bit of education BSOD 99% of the time means a system issue if it's driver, os, or hardware. Sadly NMS might be triggering something while crashing / closing down to trigger the BSOD. For example when I was younger I OC my CPU and this back when no 64bit games existed. I used a 64bit OS and no issues. But as soon as I played a 64bit game I kept getting these BSOD... Till I found out was some error happening because I had slightly OC the PC. Even the software to do stress testes never triggered it lol.
Rigid Tongue Aug 21, 2019 @ 10:30pm 
Originally posted by The-Gizmo:
Lol, looks like I managed to figure out my case. It's using the classic theme (and possibly basic theme) in Windows 7. Basically any theme that disables the DWM will cause NVIDIA drivers (I assume it's NVIDIA related) to BSOD when closing a Vulkan based game, possibly in fullscreen as the game X4 doesn't have this issue for me and does use Vulkan.

I switched to the Aero theme so that DWM will be enabled, no more BSODs when exiting or changing resolution.

Man u r a god. Change it to Aero and no bsod. Thankyou my friend. Still its bloody stupid i have to done this tho, but thanks again.
󠀡󠀡 Aug 21, 2019 @ 10:49pm 
Originally posted by The-Gizmo:
Lol, looks like I managed to figure out my case. It's using the classic theme (and possibly basic theme) in Windows 7. Basically any theme that disables the DWM will cause NVIDIA drivers (I assume it's NVIDIA related) to BSOD when closing a Vulkan based game, possibly in fullscreen as the game X4 doesn't have this issue for me and does use Vulkan.

I switched to the Aero theme so that DWM will be enabled, no more BSODs when exiting or changing resolution.

I use Win 7 too. How do I change to the Aero theme? I don't have any updates on my Windows 7 though. I just use the basic version.
Mr.Unknown Aug 21, 2019 @ 11:03pm 
Once i had this problem on my old PC and it was Ram issue, mqny games using max 8Gb memory but Star Citizen start using 12 - 14Gb Ram and there start BSOD, cuz no one game using Ram too much. So try some HW test for all components, some Ram work normaly but when it aproching full memory it can have damaged last memory chip and can causing BSOD.. mqny BSOD is HW issue..so try HW full test...
< >
Showing 1-15 of 25 comments
Per page: 1530 50

Date Posted: Aug 19, 2019 @ 10:47pm
Posts: 25