Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This topic has been locked 
Discussions Rules and Guidelines
Report this post
post a cpuz validation link
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here
and psu brand/model/age
Most common, easiest cause for this is the PSU, but it's not always that. It can sometimes be the motherboard. Sometimes, it can be some combination of things.
This one can be a REAL pain to track down because unless you know what you're doing electrically, it's basically trial and error by changing parts out.
I ran into random restarts on my prior "system" (same as what I'm using now but different motherboard and CPU), but they only really happened under a certain BIOS version, and and even then only in certain circumstances (strangely, it's like dice was rolled half a minute after Windows loaded and there was a chance it would happen, and if not, it never happened). Went back to the prior BIOS and the issue went away, until later down the line started having other issues with getting it to POST (always failed POST on cold boot, always succeeded on second boot). Changed the PSU and it didn't change anything. Upgraded the CPU a while earlier and it happened there too, so not the CPU. Had to be motherboard (or RAM). Made a thread about here a while back and it was a real nightmare journey. Did an RMA with the motherboard (due to a separate issue with an improperly functioning bottom M2 port that was discovered later) and just bought a new, separate one (different model too) and haven't had issues with the rest of the hardware since.
PSU > Motherboard > CPU/RAM > Rest would my order of suspecting things.
Since it happens in games, I'd even more think it's the PSU. The GPU is under load then and it may be spiking at moments. PSU can't cope and it trips a restart?
As the above post states, give CPU-Z validation link (or otherwise list complete system hardware). If you go with CPU-Z, also list the PSU (CPU-Z won't show this).
What wattage is your gpu running at before the shutdowns? Is it high or near max wattage draw?
Can use msi afterburner on screen display to watch these things.
Cap the fps and see what happens? Or underclock the gpu and see what happens?
Can run a memory test or turn off xmp/docp if you want to try?
Sometimes I go months without it and sometimes it happens once per week or even almost everyday. Mine rarely happens when I'm playing something, though. It's usually on shutdown. The system hangs, I hard reset it then go to Event Viewer and E41 is there. Annoying af.
Given the amount of issues I also had with a particular RAM stick it could very much be the cause of my issue. Every tool says the RAM is fine, though.
But unfortunately, as stated by others, OP, it's trial and error.
Event ID 41 is nothing more than a logged entry Windows makes on start up when it detects the previous shutdown wasn't expected. Holding the power button and forcing the PC off will cause that event to be logged, because Windows itself wasn't responsible for the shutdown (even if it was in the process of doing so).
Have you done these things? if not can you try them?
update bios
use ddu to re-install gpu drivers
update chipset drivers
make sure Windows is up to date
look at drive health in CrystalDiskInfo
At least you know how to reproduce that problem. Can you try using one of those game booster programs to see if it still happens during that ending scene or whatever? I'd tell you to disable unnecessary programs but not sure if you'll get them, I want to see if that program will maybe do something to them.
Also try disabling antivirus during that piece?
I have a feeling it's like a single piece of software causing this maybe. If not your PSU like Illusion of Progress says.
But do you have anything running like motherboard software? you install anything around the same time this started? remove all usb connected hardware? you have multiple displays?
Well, I'll explain what I'm thinking. I'm not saying it's software like trying to say it's a random piece of software. I specifically meant (I don't think I've explained this so kind if understand the confusion) a piece of software that's much more tired directly to software that is funking up the operation of that hardware.
I'm thinking specifically something like motherboard software that's notorious for being buggy crashing systems or even 3rd party hardware that installs it's own system wide driver or something.
So, I do think hardware is likely somehow connected to the problem but I don't think it's hardware by itself. Or I mean it could be, but I wouldn't start troubleshooting hardware FIRST when we could look at the kind of software I'm talking about instead of having OP basically run out and buy a whole pc worth of parts so that this problem still follows and then he's like "well guys, problem is still here" when we could have just looked at software first and ended up in the same situation without having OP run out and get parts.
Or I mean he could troubleshoot hardware by resetting bios or re-installing drivers and stuff but at this point I don't think any of anything matters anymore since he's apparently not even here.
But yes, the running of certain software could be what is exposing the issue. But then it's still inherently a hardware issue.
If Event ID 41 (which means Windows prior shutdown was not expected/finalized by Windows itself) is getting logged, then it pretty much means one of two things...
1. Power was just unexpectedly lost. This means there is an electrical/stability issue somewhere.
2. The power button was held to force the PC off.
That's sort of it. Regarding the second, someone may force the PC off in response to another issue, so Event ID 41 showing up in that situation doesn't mean there's an electrical issue. But if you're not forcing the PC off and it's unexpectedly losing power itself, then it is an issue and of itself. It's not a software thing.
Good example was my own issue with this I had many months back; my issue ONLY happened (and not always!) after loading into Windows. If I sat in the BIOS, it never reset. If I made it passed the first few minutes after reaching the Windows desktop, it never reset. That can easily sound like something at startup, but problem is software will not cause a PC to reset; but it can expose an instability which will cause an electrical issue, which in turns results in power being lost. In my case, even in safe mode it happened, and on older BIOS it did not. Ergo, some firmware values/behavior was different and unstable for me, at least on that particular motherboard (which I suspect had electrical issues that were probably just skirting being exposed on the "good" BIOS).
Again, a PC is only stable until it is not.
But digging through drivers or doing userbenchmark runs isn't going to do anything here but waste time IMO. This error is (almost) always an electrical/stability issue involved. So yes I'd personally be looking at hardware first in this case.
Not all PC issues are the same. The symptoms should be used to narrow your initial efforts down, and then you go from there. That's how troubleshooting efficiently works. The first thing you check isn't always the cause, no. But you should still always try and make your troubleshooting efficient as opposed to guessing at random things.
PSU > Motherboard > RAM/CPU > Rest in order of likelihood IMO.
But these issues can be really niche and are a pain to troubleshoot, as I said. Unless you know how to look at a deeper (like on a component/electrical level, we're talking individual ICs/capacitors), you're best sort of swapping those things in these "power suddenly lost" situations. And 9/10 times (random number, yes), when it occurs involving games, as it does in OP's case, it's usually the PSU not coping with the draw the GPU is now adding to the power demand.
But like the very first reply was quick to correctly ask, the OP didn't even provide system specifications. So hopefully they do indeed come back and provide that (as well as other follow up); else we can only speculate and guess.
I'm not even worrying about kernel 41 error or shutdown problems really. I've seen those things mentioned and suppose I am considering them but as far as my troubleshooting is concerned those are worthless points.
I mean his issue or random reboots has nothing to with shutdown problem because he's not even shutting down the pc. It's not meant to shutdown, because it crashed/rebooted. Obviously it's going to have some shutdown problem logged when it hasn't even shutdown because it crashed and rebooted. So fixing the reboot problem is what I'm trying to fix first.
Power issues sure might be causing (I guess) but I still don't see it that way. I don't see a lack of power causing a crash/reboot or it might but I don't see it being that simple and in my experience a bad psu would look more distinctly as a bad psu issue and it doesn't look like that to me. Might be power related but it looks to me if it was, it's something random causing the power issue but not a single piece of hardware and looks more like something caused by software causing this hardware issue. I do see it as if you take that piece of software away the hardware will function fine without being sabotaged.
I know he's probably still around but I'm pretty much about to leave, so sorry if I sounded like a jerk. I'm not good at relaying that kind of message.
Sorry if that seems like a harsh way to put it, as ultimately everything is going down a list until something sticks, but what I mean is ignoring the symptoms just seem detrimental. The most efficient method of troubleshooting is to go after the most likely thing first (based on the symptoms), and then go from there, no? Who wants to spend more and time effort on things when these issues can already be time and effort intensive?
The logs are definitely not worthless. To the contrary, they are literally confirming the symptom (PC unexpectedly loses power). If those logs aren't accompanied by, and thus just the byproduct of, another log/issue, then it is the issue and we should tailor our troubleshooting priority based on that.
A PC suddenly restarting or powering off, especially under load, realllllly suggests an electrical or thermal issue to me.
I operate solely on the information I'm given. I try not to presume beyond that (and if I do, I tend to mention it is a presumption and will often pose it as a question for confirmation). I don't see the point of making presumptions on what "may be" unless it's stated. We'd be here all day and night.
The OP hasn't mentioned anything about the OS crashing or other issues. If they were mentioning BSODs and event ID 41 was just being created as a side effect, then sure there's some other issue (and in that case you'd be analyzing the BSOD itself to find it out), but right now the issue is presented by OP solely as a random restart with Event ID 41 being presented as the issue. So if I'm incorrectly approaching the problem here, it would be because I'm basing my approach on limited information. Information in, information out.
Based on what we know so far, I do believe there's likely some electrical (or thermal) issue somewhere. That could change if further information that wasn't presented up front paints a different picture, of course.
You may not see it that way, but electrical issues can 100% cause system instability, often times in the form of sudden restarts or shutdowns. Some motherboards/BIOS can even do this as a fail safe to protect from hardware damage from improper voltages or otherwise other electrical levels. Or the PSU just can't cope and the system turns off or restarts.
I guess we have different views here.
From where I sit, avoiding a known instability by limiting yourself from using software that itself probably isn't a problem just because it causes instability on your hardware means you have a hardware issue.
At that point, you're just avoiding the issue instead of fixing it.
You didn't come off that way (at least not to me). I was just curious as to why you seemed to presume that so "early" for lack of better words. I know in this social media era it's easy to think otherwise, but many people don't check online nonstop or as frequently.
If they ultimately don't reply, they don't and everyone moves on. If they do, we go from there.
...the problem is that my pc reboots randonmly after a while playing, sometimes after an hour, sometimes after and hour and half, sometimes after 5 minutes...
He posted this in the op though? Isn't random restarts a crash though? Or at least possibly when Windows is configured to reboot on a crash?
I suppose a good thing to do in my opinion is to disable the "automatically restart" thing and then see if the random restarts still happen.
https://www.drivereasy.com/knowledge/solved-computer-randomly-restarts/
But I suppose my point is from me to you that a random restart doesn't automatically mean it's NOT a crash. That's why I am going under the assumption it's a crash but I am open to any ideas anybody has.
I don't have anything against OP, I just wouldn't post anything at this point expecting any kind of response in a reasonable amount of time and I am impatient with these things unfortunately. Not sure why.
The reboots won't damage the hardware. Operating systems like Windows reboot or freeze on purpose to prevent damage. We do need to know your system specs and Windows version.
If you mean that the game always restarts in a specific place and you are certain (only after actually testing the PSU it's not that) it most likely means one of these issues:
A. Critical error in a component being used at the time (RAM, GPU, Storage)
i. Bad OC on a component -- can always temporarily remove the OC and see if freezes
ii. Component actually failing...but the issue usually wouldn't be intermittent.
iii. Drive in use is USB and power setting in BIOS disconnects it suddenly or XHCI is enabled
on certain USB3 controllers (Asmedia) with the latest version of Windows [known bug]
B. Critical software error by software that controls hardware (this includes things like RGB lighting software and mouse keybinding software). Any other driver or software that controls hardware can cause this issue, including overlays. You can try disabling these and see if it resolves, if it does it's that software that is faulty...
C. GPU driver issue, or issue relating to hardware-acceleration
D. Not enough RAM, but more specifically, not enough virtual memory (page memory) -- when set to "auto" this can sometimes result in "effective RAM" suddenly appearing to decrease and cause Windows to freeze because it looks like a RAM error.
E. Other special issue specific to your system, but some are not really unknown like Intel 12XXX and rebooting after you get a trillion WHEA errors in Windows 11. For that to find issue you will need special assistance because it varies board-by-board and on a CPU basis...
Unless you know where to start, first look at PERFMON
Instructions here: https://www.dell.com/support/kbdoc/en-us/000178177/how-to-use-windows-reliability-monitor-to-identify-software-issues
Since it is intermittent it can be caused by anything, even a unique interaction with the antivirus you use. Because of that it may be impossible to find the answer on your own and so...
If you can't find issue at all you can post to MSDN. There you can post a dump and it will be looked at, or use the "feedback" function in Windows. The feedback function will be slower.
General Microsoft Community Link: https://answers.microsoft.com/en-us/windows/forum
I'm not being obtuse; I'm aware of the issue. What I'm saying is that the issue, as presented, is one where the PC is suddenly losing power (and typically under load), and that is it. It's not being presented as an OS crash, and while it may be, until further information is provided that suggests it is, I am not going to presume it is.
Yes, my preference is to disable that too, but this is not needed to see if the restart is a BSOD or not. If there's nothing in event viewer about the BSOD and only stuff in event viewer about Event ID 41, then there is no OS crash. That means power is suddenly being lost and nothing more.
If OP does happen to follow up with information that these issues are indeed BSODs and not mere restarts from power loss, then we will go from there.
Of course it doesn't rule it out, and I never implied that it wasn't what was occuring. But see above; I also don't presume things and operate on the information that is presented.
:(
Well, if OP doesn't follow up, no big deal. Considering they stated "they need urgent help" and are "afraid of damaging hardware", they're mostly hurting themself if they don't. But yeah I get not liking your time wasted, but when spending your time helping people, I would be ready to accept over half of it (probably well over half) will be wasted. Just how it goes.