Kernel Power 41

[Ben_Davis]

I understand this a very broad error, but it occurs every 5 mins or so into Assassins Creed: Odyssey (running at recommended settings) which makes it completely unbearable to play.
If it helps at all the psu was bought during october of 2017 from pccasegear

Event 41, Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

^This is printed in windows event viewer everytime this occurs, when it happens my screen and pc lights just turn off instantly and start to reboot.

Also as a side note help would be appreciated solving Event 10016, DistributedCOM which occurs multiple times at startup, it seems to be harmless but i’d still like to solve it if it wouldn’t be too much trouble.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-QS6DUO9\Ben Davis SID (S-1-5-21-1870275918-3780260749-4036643765-1002) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

^This is one of many printed in event viewer shortly after startup

Specs:
z270 Msi Gaming M3 motherboard
2x8gb ddr4 2400mhz apacer panther ram
intel i5-7500 cpu (stock cooler)
Asus rog strix 1060 6gb gpu
Corsair RM750x GOLD 750W psu
1080p 60hz 22" LG monitor

[veeg]

Hello

Please post those logs from your event viewer..

jmarket @phillpower2

[phillpower2]

Ben Davis has an ongoing thread here where they advised only yesterday that Windows has now been reinstalled on its own partition, continuing at that thread would have been more appropriate or alternatively closing that thread before starting this one.

[Ben_Davis]

Sorry, didn’t know if I needed to create a new thread for a different issue…
Here’s some log files >.>

Also xml and evtx files weren’t allowed to be uploaded for some reason? All I could them as was txt files.

Edit: Was lookin at my bios this morning and noticed my cpu was idling at 50 degrees C don’t feel like that’s normal, although i haven’t cleaned the dust from my pc in quite a while now.

Edit 2: Did a full clean out of my pc, whole lotta dust, cpu currently running at 40 degrees C (only running a couple programs like chrome, youtube, steam and discord.

[Ben_Davis]

Just crashed with the same bsod error i was getting in my last post phill ‘unexpected_kernel_mode_trap’

[Ben_Davis]

Kernel41 again

[Ben_Davis]

‘Irql_not_less_or_equal’ @phillpower2

[phillpower2]

Download then run Speccy (free) and post the resultant url for us, details here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.

To publish a Speccy profile to the Web:

In Speccy, click File, and then click Publish Snapshot.

In the Publish Snapshot dialog box, click Yes to enable Speccy to proceed.

Speccy publishes the profile and displays a second Publish Snapshot. You can open the URL in your default browser, copy it to the clipboard, or close the dialog box.

Two different causes of both crashes, the first was caused by a problem with the CPU and possibly overheating which would explain the computer suddenly shutting down, hence the kernel event 41 info, the second crash is less clear as both memory and a couple of drivers are flagged up, will come back to them in a bit.

Debug session time: Mon Dec 31 18:00:06.665 2018 (UTC - 5:00)
System Uptime: 0 days 9:29:22.400

---

•                                                                         *

•                    Bugcheck Analysis                                    *

•                                                                         *

---

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000002bb0, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c5, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
[COLOR=rgb(226, 80, 65)]bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8030eb654cf, address which referenced memory [COLOR=rgb(41, 105, 176)]This suggests a memory problem but in the same dmp the driver below is flagged up.

[COLOR=rgb(226, 80, 65)]FAILURE_BUCKET_ID: X64_AV_nt!KiEndThreadAccountingPeriod+18f [COLOR=rgb(41, 105, 176)]This could be down to your GPU drivers.[/COLOR][/COLOR][/COLOR][/COLOR]

[Ben_Davis]

Speccy Snap: http://speccy.piriform.com/results/Z...h8FPqFHLXunXSX
Not sure if this correlates at all but in one of my threads, I posted about my cpu running past the base clock of 3.4ghz at times when there was little to no stress (it has an intel boost clock of 3.8ghz) could this be causing the excessive heat?

Edit: Had some spare time so I took the liberty of running the windows memory diagnostic, it showed no errors.

Edit 2: Just remembered something about a previous thread and the problems I was having, my cpu has an intel boost clock of 3.8ghz but it only ever goes to to 3.6ghz when stressed, would deeply appreciate some help with that, although I am considering buying a new cpu

[phillpower2]

Test the CPU with the Intel diagnostic tool which you can download from here

Edit: Had some spare time so I took the liberty of running the windows memory diagnostic, it showed no errors.

Only the most basic of tests and any reliable testing of the RAM needs to be done by running Memtest on each stick individually and for a minimum of 4 or 5 passes.

[COLOR=rgb(41, 105, 176)]NB: I note in Speccy that you still have the Iobit garbage on your computer.[/COLOR]

[Ben_Davis]

What’s wrong with Iobit? Typically I use it for driver booster so I dont have to worry about updating all my drivers… Is there a better alternative?

Also the cpu passed every test given by the diagnostic tool.

Edit: Is it normal for my cpu to run at an increased temperature compared to other pc parts? Only a couple degrees atm but it may have a been a greater difference earlier.

[phillpower2]

What’s wrong with Iobit?

More to the point what is right with it, driver updating explained below but take a look at the info here first and an explanation as to why you should not use their other wonderful software here the author of the article MIEKIEMOES has long been held in high regard and the same article referred to even after all these years.

Once Windows has been installed, you install the necessary drivers for the MB and other hardware and then leave well alone, drivers should not be allowed to auto update and you should never update any driver/s unless the new drivers are intended to resolve a specific issue that you are having, installing the new drivers can actually cause you the very issues that they are intended to resolve and uninstalling the new drivers may not resolve the problem/s.

[COLOR=rgb(41, 105, 176)]Did you manually install your motherboard drivers once Windows had been installed and starting with the chipset drivers first, if not, hardware that is in 100% working order will give you problems.

Edit: Is it normal for my cpu to run at an increased temperature compared to other pc parts? Only a couple degrees atm but it may have a been a greater difference earlier.

Completely normal and that is why you need to have thermal compound, a heatsink and CPU cooling fan atop of the HS, a CPU gets so hot in a nano second that it would take off your skin if you touched it.[/COLOR]

[Ben_Davis]

Alright I’ve removed all the iobit software and all my drivers should now be installed. I’m just gonna assume I just wait to see if it crashes again?

Edit: Crashed again

[phillpower2]

MBAM had a whole load of problems according to that crash dmp but its come to the point where we need to properly test your RAM and DIMM slots on the MB, this will take you a fair amount of time and Memtest is best left running overnight or if you are out for the day.

How to physically test you’re RAM.

For thorough testing, each stick should be individually tested using Memtest86 and for a minimum of four passes, Memtest86 free download and “how to” guide here

[COLOR=rgb(226, 80, 65)]The following checks require the computer case to be opened so take the following safety precautions first, disconnect the power cord from the wall socket, press the computer power on button for around 20 seconds to get rid of any residual charge in the system, remove the side of the case, take anti static precautions before touching anything inside, you can do this by touching a bare metal part of the case or the PSU.

Have a pencil and notepad to hand.

Remove each stick of RAM and blow out the memory slots.

Insert the first stick of RAM in memory slot one, reconnect the power and in the case of a desktop computer the video to screen cable.

Power up the computer and see how it goes.

Make a note of the results.

Repeat the procedure until the first stick of RAM has been tested in each memory slot and the results written down.

Remove the first stick of RAM and put it to one side on top of a piece of paper with the number one on it for identification purposes.

Repeat the procedure with all RAM until each stick has been tested in all slots, the results written down and the sticks identified numerically.[/COLOR]

[Ben_Davis]

Haven’t tested my ram just yet, probs doin it tomorrow but I did just get kernel power error again.
If it helps at all I’ve realised it only seems to happen when playing Ring Of Elysium or AC: Odyssey (could just be a coincidence tho)

Edit: Just realised how long this takes per stick per slot, may take me quite some time before I can get back to you with results.

Edit 2: About halfway thru testing, did recently however crash with a new error while playing a game. dmp 010919-8390-01 (something about kernel_security)