Steam process can't be ended and system shutting down screen is slow

Every time I play 7 Days to Die and then put my laptop to sleep that's for sure it won't work anymore. There are weird problems beginning with connecting to servers and ending up with never ending processes (both Steam and the game that I can't always force end). Haven't checked other games but I already had some sleep mode BSOD.



In order to make Steam and 7dtd working properly I always have to reboot my laptop every single time I close the laptop lid. Sometimes it's BSOD, but mostly Steam and some errors related to memory. Or "Game Security Violation Detected" but that's more like EAC (Easy Anti Cheat) so the error is caused by the game not being able to shutdown properly when rebooting Windows.

I'm gonna tell you what I have been telling everyone using low power modes for the last 13 years now. Don't use sleep mode or hibernation. It can and will jack your system up. It may not happen to everyone, but I've read my fair share of threads just like yours all over the Internet about this issue. You're far better off just properly shutting down the computer. I'd be surprised if you don't already have data integrity problems.

You know, funny thing, cause I felt like it was totally opposite with my pc, bad condition hard drive and BSOD problems or any other errors. So I used to reboot and never used sleep mode. Either I didn't think about it or/and wasn't aware what exactly it does til i found out couple years ago.

Then since I had to like reboot my pc sometimes even 5 times 'til it won't show some 0x0000 error you just never knew when the system's gonna die tot hat point it won't work without format. So I started putting the pc to sleep since I didn't want to risk another cat & mouse play. It traumatized me so much I still tremble when I reboot the computer having a feeling it won't boot at 1st time or not at all.

What you say reminds me of quick saving in games which sounds about the same on potential data corruption consequences. So basically I think I'll be rebooting my new laptop while the potato pc doesn't like that in particular.

A BSOD is usually caused by hardware or a driver. If I ever get a BSOD (very rarely) I know to retrace my steps and see what hardware, drivers or software I just introduced to the system. Then I can deduce what the issue is. You can use a program called WhoCrashed which may help narrow down what the cause of the BSOD is.

Again, it may be hardware related, a driver or even an update to software like an anti-virus or what ever. Even a USB connected device could do it. Heat could do it as well since hardware doesn't like very high temps. Think video card.

Resplendence Software - WhoCrashed, automatic crash dump analyzer

Thx for mentioning the software, I'm gonna try it. As for heat I don't think there's any problem on that cause while this Asus Rog Laptop I own doesn't have the worst heating system I also use an external cooling usb pad so it's not bad at all. You're right on BSOD caused by drivers. I assume my worst BSOD at the moment could be "DRIVER_POWER_STATE_FAILURE".

A DRIVER_POWER_STATE_FAILURE leads me to believe the BSOD is directly related to the low power mode of sleep.

I'm not sure what that means but both my battery and psu modes are set to maximum performance.

What I'm saying is that the sleep mode that you were, are using can cause the driver or drivers responsible for power regulation to throw a fit, thus a BSOD. That's just a guess. You did indicate the BSODs happened prior to putting the computer in sleep mode.

Like I said, most BSODs are driver or hardware related. An updated piece of software for a program you use, be it a game, Steam, Epic Games, an anti-virus update or its functionality, a GPU driver, a newly attached USB device and its software, a new GPU, sound card, etc can cause a BSOD. I don't remember what the deal was with it, all I know is it's like a bad communication between the driver or hardware and OS that causes the BSOD. That's why you want WHQL signed drivers to help minimize that.

So, I would see what WhoCrashed says and I'd go into dxdiag and hit each tab looking for problem devices or a non-WHQL driver being reported. In dxdiag at the bottom there you should run in 64 bit afterwards to then check for 64 bit driver problems. The initial launching of dxdiag is for 32 bit, you want to check both.

To get into dxdiag, type dxdiag into search under the Windows start orb. Even if you find non-WHQL drivers, it may or may not be why this is the cause of this particular BSOD. WhoCrashed should be able to give you some better Info.. But it may be a little cryptic. WhoCrashed should give you a probable reason as to what it thinks it is. The other thing you can do is save the dump logs and upload those here to the BSOD subforum. I don't read dump logs though. They're absolutely massive and I have no idea what I'm looking for other than some very basic obvious things. And that's the other thing. If dump logs aren't on, then read here and make sure they are.

Thank you, I already did post a bsod thread but I have to fix my template or whatever is required there, cuz I pasted the log and apparently it's not enough. Somebody already shown me the rules link and I'll get into it soon.

But! "For best results, under write debugging information select full or complete memory dump." - I don't have it. I can select either Kernel memory dump (which is default) or Small Memory dump (256 kb).

Yeah, I just have none, small or kernel. Kernel would probably be the full since it's straight from the Kernel.


...and rumor has it "the Kernel" sits there in the OS making KFC all day long. Peter and CatDog - YouTube