Windows 10: Power Kernel 41 Error, During Gaming, Possibly Software?

Well I have overclocked the GPU after the problem started, but it made no difference.

 

If you are able to I would try to pay to get the problem professionally diagnosed. When I was having issues, the diagnostics test would turn up no issues but once I sent it in to be repaired, the problem was discovered very quickly during their own diagnostics testing as a bad motherboard. This specific issue seems to be caused by different components for different people, so theres really no sense in buying a new psu or ram or motherboard unless you know for sure which one is the problem. I almost went out and bought new ram and psu for mine and was briefly convinced I had shitty power in my condo wall outlets from reading this forum until it was finally discovered to be the mb, and it's run 100% perfect since.

 

Yeah I have taken it back to the store where I bought it, because they also do repairs and they have said there is no problem with the components.

 

I dont think its the components.
I tried everything also.After having no problem what so ever on win 7.After i upgraded to win 10 hell starts.
update bios/ memtest /prime95 /reinstall/fastboot off etc/ format 6-8 times/ adjust voltage./timing ram/driver verifier.List goes on.
Still crash!
But if you try using live cd Ubunto , it do not crash at all.
I tried running it all weekend no crash.
Back to win 10 crash after 30 minuts

There is something generally wrong with win 10 itself.

Also anyone compared win 7 vs win 10 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\
ref
WER Settings (Windows)
Almost all that have the mystic crash with no dump files, almost all have some kind of write permissionm error.Mostlly runtimebroker.
Maybe microsoft screwed something again.and we with these crashes have som block that do so we simply cant dump correctly.

 

The thing is I had the same issue on windows 7. Is it possible that the voltage from the mains in my house is not stable and causing the reboot?

 

I got a update on this mystery crash that produce no mystery dump.


After i updated to AMD latest 16.3.2

changelog.

So they apperentlly knew this with out telling anyone.So i hope 1000 of people have not buy a new psu if it was AMD fault

I had 1 crash the next day, insteed of 10 a day.
Then i turned of superfetch, cause i have ssd.

Have not have crash for 3 days now. *Wink

 

@storm shadow, I already explained that in post 7

There are 3 different crashes

• A freeze crash
• A sudden shutdown/restart crash
• A bluescreen crash

A memory dump will only be created when a bluescreen crash occurs.
A kernel event id 41 only means an unexpected power problem has occured what happens with both a shutdown/restart and bluescreen crashes.

 

yeah i know.
But if you did a read on the matter there have been 10 000 users having this power problem on win 10.

Even when everybody knew it wasent the PSU, since like 9000 of those having this crash updated from a fully funcionally win 7 and never had a kernel 41 crash on win 7.
Problems started only after they updated to win 10.

At least problems are fixed from my part, with the answer in my latest post.

 

Kernel Power 41 event is just an abnormal shutdown. Even if the user switches the computer off before shutting it down, this event will be recorded in the log. A particular OS has nothing to do with it, specially when the event comes without a bugcheck code, it is mostly a hardware related issue. (Scenario 3 as stated in https://support.microsoft.com/en-in/kb/2028504)

Windows 7 also had a great great lot of kernel power 41 issues.

 

Your not reading a word what i am saying.You just refaring to microsoft who do not know anything on this matter either.
That why its "abnormal".

yes i get its a abnormal shut down.But as i stated many times for the 10 000 users that never ever had problem on win 7 , but when upgraded to win 10 , they have kernel 41 crash with no bugcode

Why on earth should they change PSU.
New build sure it can be anything.
A logic person that had no problem on win 7 but have abnormal crash on win 10.Would be very stupid just buy new hardware, and wait for another crash.

Also even AMD stated in there changelog fix that there last driver produced exactlly such a crash.
After i changes to the AMD latest i havent had any kernel 41 crash.First time in almost a year since i upgraded
But i guess you gonna tell me again now there are 3 kind of crashes for the 5 time.

 

You say you know, but you keep referring shutdowns/restart crashes as BSODs which they are NOT.

I don't, because I have no interest in it due to the fact that I have no problem with it.

 

Hi David. Be cool, mate.

This is a newly built computer, so you cannot say that you have got the issue only after upgrading to windows 10. If another system is/was stable, that is another story.

I think you know that DOTA2 is the most problematic game. Every third gamer complain about that game. It causes a lot of various different issue.

As it is your first self-built system, you might have done some little mistakes there as well. May be a board pin is not having a proper standoff? May be the peripherals are not properly seated? May be the thermal paste is not properly applied? May be the power connections are not properly configured? May be the CPU cooler is not functioning properly? May be the system is overheating? Many a problems may occur in the first built. It happens for everybody. Moreover, new hardware are not beyond suspect; I myself got a bad board out of the pack. Nobody can nullify this possibility. Have a double check. Dismantle the system, re-seat it perfectly, taking adequate time and cautions at every step.

@axe0 is saying what is the core, basic logic of troubleshooting. You are not getting him because the issue is very frustrating to you. That's right. But that guy is volunteering for you. Please dont be rude on him. He is having the real expertise in this field. Just browse over this subsection of this forum .... you will see how many members are benefited by his insights. Dont wast it, use it for good.

Hope you will be able be able to get to the root of the issue. Just throw the frustration away, just stop thinking that Windows 10 is causing it, and use axe0 for your good guide, not as a person having different opinion.

 

Hi all, sorry to butt in, but I found this thread while searching for answers to my own problem. Games used to work fine for me, but then I upgraded to Win10 (from 8.1), and I would get a black screen + reboot when I'd try to run a game. Some games would last a few seconds, or a minute or two before black screen + reboot. I've tried various driver updates, a clean reinstall of Win10, and now a reset to factory settings (putting me back on 8.1), but the problem persists. I haven't checked the PSU yet.

I tried running IntelBurn as suggested a few pages back, and my computer shut down within seconds of starting the program. Like maybe 2-3 seconds? I'm just wondering if that points to anything specific.

 

I understand this is an older thread but I had the exact same issue as the OP and had the same error codes and everything. I went through the thread and tried just about everything but nothing had worked.

I had recently had a PSU die on me and needed to replace it, and that is when the problems started to happen. I double checked every wire but they were all securely fastened.

What I had neglected to do is change out the power cable. I had just used the same power cable I had with my previous PSU. My computer was unable to properly shutdown and would just crash and reboot. As soon as I switched out the power cable to the one that came with the new PSU, everything ran smoothly and I was successfully able to shut my computer down without it crashing.

Problem was simply solved by swapping out my power cable to use the one that came with the new PSU.