Solved Event 41, Kernel-Power

[Morgud]

I've installed Speccy, but in the summary it shows me "CPU 5C" whereas "Motherboard 20C". Thought the PC runs only like 5 minutes so far. Funny, even the HD's are shown with 23C.

Power Surge Protection, well in Europe i didn't need one. We had very few fluctuations in electricity, here i think every time the Air Conditioning outside jumps on, the power here fluctuates.

For the Voltages, i suppose the readings have to be in Volts, right? I did search the whole Bios menu, didn't find anything apart from
Core VID 1.4125V
Current Core VID 1.392V
Also, i still have the original manual, on the same page 24 it shows me the Cell Menu, as you said, but just like in the online Manual my Paper Manual shows me a picture of the Bios Cell Menu, and the three options:
CPU VDD Voltage (V)
CPU-NB VDD Voltage (V)
DRAM Voltage
All those three are set to "Auto" and greyed out.
But i will take a look again, lets see if i overlooked something.

BTW, how do i check, what did get damaged? I mean, if the CPU got damaged, how do i check it? I just hope, that not half the System got damaged.
The past few days i didn't experience the System to just Hard Hang.

 

[Dave76]

It's possible the monitoring programs can't read your CPU temps correctly.
After your computer is warmed up, re-boot into BIOS and check the CPU temp there, if it shows it.

Go to the voltage section in your BIOS and set them to 'Manual' this should allow you to see a voltage number, post them here.
CPU VDD Voltage
CPU-NB Voltage
DRAM Voltage

We'll go through the settings and testing process step by step, then we can determine if there is any damage.

 

[Morgud]

Hi Dave,
The PC was running the whole day, i played Farcry3 for quite some time. Just before i read in the Bios 25C, while before the reboot into Bios CoreTemp and Speccy told me 3C.

So for the Bios and Voltage. Do you mean Volts, or Hz? Earlier i searched for "Volts" in the whole Bios, but found none. The downloaded Manual is the same as the Booklet i have from the Mainboard. In the Picture that is in there about the "Cell Menu" you see 2 sections, one at the top and one at the bottom. The one at the top states:

Current CPU Frequency 3.60GHz (200x18)
Current DRam Frequency 1333MHz
Current CPU-NB Frequency 2000MHz

Is that what you meant buy Voltage? Would have helped if you told me you search for GHz/MHz values, i searched for Volt ~.~".

 

[Dave76]

Frequency is in MHz and voltage settings are in (v) volts.
We need the voltages settings, not the frequency MHz.
Page 24 of your manual, at the bottom of the picture.
Scroll down when you are in BIOS.
CPU VDD Voltage
CPU-NB Voltage
DRAM Voltage

View attachment 249645

 

[Morgud]

That's a problem. That where the place, i first thought of, when you said Volts. The problem is, that there is see only(like in your picture) "[Auto]".

Pressing Return does nothing, on the right where usually some explanation is i see no Volts, apart from DRam Voltage where it says "Auto = 1.50".
For the other two (CPU VDD & CPU-NB VDD)i can only speculate, as the only way to change those is through the + and - buttons. Pressing from [Auto] the - button shows a red "1.5500", and pressing the + from the [Auto] shows a white 1.1000, another + adds 0.0125 increments, so 1.1125 > 1.1250 > 1.1375 and so on.

 

[Dave76]

Can you confirm:
The CPU VDD is showing a red "1.5500" as the next choice?
The CPU-NB VDD is showing a white 1.1000 as the next choice?

I can't recommend any setting adjustments until I know what the current voltages are.

 

[Morgud]

I can confirm, that all three stand on [Auto]. Just like you can see on page 24. Both show if i push + (plus) it jumps to 1.1000, and if i push - (minus) from the [Auto] setting, it jumps to a red "1.5500". I suppose 1.5500 is the max value, you eventually get there if you press consistently long enough +, as it's going up in 0.0125 increments.

But, one more thing. I didn't have a lockup as before for quite some while. Also when i looked into the Event Viewer, all past Events of Kernel-Power where gone, erased, thought i didn't manually erase anything, nor did i clean up the Harddrive C: with any software or anything. That's very strange.

 

[Dave76]

Leave CPU VDD on 'Auto'.
Increase CPU-NB VDD to 1.150v.

Check for stability, let us know if it's stable.

 

[Morgud]

So you think if i set it to that Voltage, then the Ram will work correctly in Memtest as well?

 

[Dave76]

It's a good place to start, if it's not stable we can make another adjustment.
This has worked for many AMD motherboards.
When you have 8GB RAM most of the time you need to bump the IMC (CPU-NB VDD on your motherboard) voltage up a little, the more RAM you have will require more voltage.

 

[Morgud]

I set CPU-NB now to 1.150v, lets see.

 

[Dave76]

Run memtest86+ with all RAM cards installed, for 7 full passes, best to run overnight.
If you get any errors you can stop the test.

If it fails, we can make another adjustment.
You need to set voltages as low as possible and still have a stable system, more voltage = more heat, the standard is to increase slowly until stable.
You need to be very careful with these voltages, too high a voltage and you can damage components.
Don't increase any voltage settings without checking with a member in this thread.

 

[Morgud]

I have set it to 1.1500, which should be the same thing; one more 0 doesn't matter as long as the dot is set correct, right?
I will let it run overnight today, both Ram Sticks.

BTW, after searching the internet for Memtest86+, i found allot forum threads where people said its not a failure free software, that made me worried.
So in order to check by myself, i checked my wife's PC with Memtest86+, her PC don't have any problem. Once 8 hours, Pass8 no Errors, and once 19 hours, Pass 17 no Error.

So, if my system runs stable, and every part in my PC is healthy (=not broke or faulty) then i should get no errors in Memtest86+ right? No matter how long i let it run.

 

[Dave76]

1.1500v is fine, 0 on the right side of the decimal point doesn't matter.

Actually there is no software that is 100% accurate or error proof, just the way things are. Memtest86+ is the most recommended RAM testing program and is the best in many opinions.

That's right, theoretically it could run forever with no errors on a solid machine.
Let us know the testing results.

 

[Morgud]

Now i didn't have any problem since January 1st, according to my Event Viewer, but now i got the same error again.
Didn't get yesterday to let Memtest86+ to run, but i suppose it's not necessary now.

 

[Dave76]

If everything is stable you can mark the thread 'Solved'.

 

[Morgud]

Well, i didn't run a Memtest as i said, but if you read closely, i got the same error again, 1.5 hours ago. So i still have that error, thought i didn't have had it for nearly 15 days. Last time was January 1st, and then today.

One other thing. I ran this system for like 10 months, with the same Bios setting and i didn't have any trouble with it. So it's kinda weird, that all of a sudden i get serious errors like that.

I should reinstall Windows 7 new from scratch, since i installed/deinstalled allot software over the past 10 months, plus i might did something bad by having Daemon Tools, Power ISO and Alcohol 120% installed at the same time. I not remember correctly, but i might had one emulated DvD drive from each of these three programs running, maybe i crashed something.
Reinstalling Windows could lead to the knowledge that it's either a Software thing, or indeed Hardware.

What i am going to do is, i go get me a new Mainboard and some new Ram. Then i first put the new Ram in the Old machine, and check it using Memtest. It's quite weird, that Ram#1 has the same failing address in both Slots, as well as Ram#2 has it's own failing address which is the same in both slots as well.

I'm thinking the Ram has a issue, and unless i can get exchange Ram physically i will probably keep poking in the dark. I know for sure, through stress tests, that my Graphic Card and CPU is fine, only the Ram fails Memtest, both Sticks or each one single.

So i will go get me some new hardware tomorrow, and then i first check New Ram in this Mainboard, and if that fails i exchange the Mainboard and check the Old Ram in the New board. After that, there is only the PSU left that could cause problems, and i probably let that one be checked when i buy new Hardware.

 

[Morgud]

Is it possible, that if a CPU got loose on its socket, it can influence the Ram Performance in Memtest86+?

As i tried to turn on my PC today, it booted into Windows7, and then froze with a Message Beep coming from the Mainboard.
I was already before suspecting that maybe the CPU got loose, but since i never moved my PC Case around i disregarded the idea. I however had once a PC where after about 2 years (and numerous moving) the CPU was loose, and after re-socketing it it ran like new.
So today i re-socketed the CPU after that error, and I'm thinking about to run a Memtest to check.

 

[Dave76]

I actually did read your post 'closely' and since you didn't mention the error, figured it must be minor.
Members here regularly work on several thread at a time, we can't memorize everyones issues, especially from two weeks ago.

Daemon Tools and Alcohol 120% have a driver that is known to cause problems and crashes, un-install them both. Use Power ISO.
Once they're removed, run the SPTD removal tool. DuplexSecure

Good plan, try the new RAM and test your motherboard.
Let us know the results.

 

[Morgud]

Dave76, I didn't want to sound rude, i hope that you not got offended through anything i wrote. But one post ahead of your post

If everything is stable you can mark the thread 'Solved'.

I wrote that "i did get the same error again".
Sorry for not being clear enough, but the same error means my PC froze up, no CapsLock/ScrolLock/NumLock turning on/off any lights on my keyboard, so a HardHang.

I can imagine, how many threads you guys need to work on at once, i belive allot people (including myself) are very grateful for that.

One of the First things i did, was uninstall Daemon Tools Lite, Power ISO, Alcohol 120% and using the SPDT deinstaller.

BTW, is it possible, that a not correctly socket-ed CPU can influence the Memtest? I know the Memtest's length depends on the CPU as well as the Ram's amount.