Multiple CPU (Intel) related BSOD's

ubuysa said:
That is the kernel dump that you have linked to. @axe0 may well see something in there that I have missed.

BTW. Disabling intelppm.sys will (should) cause your CPU to run at maximum power, which is what it will have been doing during the stress testing - which didn't BSOD. When you are using it normally the CPU, or at least some processors, will be switched to lower power states - and that may be the problem.

However, in my view, if disabling intelppm.sys does stop the BSODs it's only a workaround because your CPU should be stable across all power states.
Click to expand...

Thank you. About disabling intelppm function, just this? Or to disable both intelppm and Intel C-States? I noticed before that MHz jumping suddenly to 5.192, then back to 4.6, 4.7, to 4.9, & back to 5.2 (Turbo mode), and i suspect perhaps this is the culprit and the cause of crashes? By disabling intelppm it will make all cores to run on the same stable speed, correct? And, regarding ThrottleStop, is it safe to use it? I mean, a bit of undervolting, TPL1/2 limiting, and/or to cut down cores speed, i.e, to make all cores maxing out at 4.5, instead of 5.2, in order to reduce processor heat/power consumption? Sorry for asking such questions though, but i don't want to produce more problems to computer, due to extra temperatures/power consumption.
 
Demetrius said:
Hello there and many thanks for your response to my issue. I would be glad to submit a full kernel file, but as i said earlier, my Computer knowledge is limited to very basics. Full kernel dump is the "Memory.dmp" aka "complete crash dump"? If that is the correct file, i have submitted it few posts above, but i will here now again for any case. Sorry if this the wrong file. I'm bit lost with such technical terms.
Click to expand...
I understand it can be confusing.

A complete memory dump is basically a copy of everything stored in memory, both kernel mode and user mode stuff. The difference between them is basically that kernel mode operates with elevated 'permissions' as it has access to much more like controlling the hardware to make it operate. A full kernel dump is a copy of all kernel mode stuff in memory only. For an analyst, the practical difference is that much of the complete memory dump is user mode which is a problem for us. We can't easily debug user mode stuff as that's more like looking at code from third-party programs that the tools used can't easily interpret for us to make it more understandable, at least not without the tools getting help of how to interpret it which is private to the companies developing those programs.
 
DO NOT use Throttlestop. Not until you have the CPU fully stable. Personally I'd be very wary of it even then. And please also ensure that Afterburner is doing nothing either. It's really vital that the CPU is allowed to run at stock voltages/frequencies - excepting the Intel Speedstep adjustments of course. Overclocking/undervolting/tweaking any CPU are all potential BSOD triggers.

The thing with troubleshooting is to only ever change one thing at a time. If you'd feel more comfortable disabling the C-States then by all means try that first. Then let the PC run for a while to confirm whether the BSODs really have stopped. If it does still BSOD then disable intelppm.sys and see how it goes in that state.

You need to be systematic and disciplined when troubleshooting. One step at a time.
 
axe0 said:
I understand it can be confusing.

A complete memory dump is basically a copy of everything stored in memory, both kernel mode and user mode stuff. The difference between them is basically that kernel mode operates with elevated 'permissions' as it has access to much more like controlling the hardware to make it operate. A full kernel dump is a copy of all kernel mode stuff in memory only. For an analyst, the practical difference is that much of the complete memory dump is user mode which is a problem for us. We can't easily debug user mode stuff as that's more like looking at code from third-party programs that the tools used can't easily interpret for us to make it more understandable, at least not without the tools getting help of how to interpret it which is private to the companies developing those programs.
Click to expand...

Many thanks for the quick, but at the same time deeply explanation. For me, a mere mortal that just using a computer to spent some time with other family members by playing few online games with my son+nephews, it's confusing, yet very interesting stuff to read and learn. I will spent for sure a lot more time on sysnative site from now on. Already found a lot of interesting reads around.
 
ubuysa said:
DO NOT use Throttlestop. Not until you have the CPU fully stable. Personally I'd be very wary of it even then. And please also ensure that Afterburner is doing nothing either. It's really vital that the CPU is allowed to run at stock voltages/frequencies - excepting the Intel Speedstep adjustments of course. Overclocking/undervolting/tweaking any CPU are all potential BSOD triggers.

The thing with troubleshooting is to only ever change one thing at a time. If you'd feel more comfortable disabling the C-States then by all means try that first. Then let the PC run for a while to confirm whether the BSODs really have stopped. If it does still BSOD then disable intelppm.sys and see how it goes in that state.

You need to be systematic and disciplined when troubleshooting. One step at a time.
Click to expand...

Notice taken. I was just to make sure about the side-effects of such tweakers, and i couldn't find a better place to ask. So, ThrottleStop to avoid from now on. MSi Afterburner, son using it just to watch framerates into games, without touching voltages/clocks etc. Closing words: I see that many people going and asking for help (regarding such issues as mine), at various "overclocking" forums, and also son's school friend "adviced" us to go and ask at one well know such website. But i didn't. Me, i prefer to search and ask for help from people that have the true knowledge about this and that, instead of some fancy tweak kings or world records overclockers and such. And i'm glad i stumbled up sysnative.
 
One of my favourite phrases is "there is no such thing as a free lunch". Any kind of tweaking has a price, whether it's extra heat, extra power drawn, shorter component life, or an increased risk of BSOD. In my view you have to understand up front whether whatever gain you might make is worth the price. In addition, the law of diminishing returns comes into play eventually and the gain those last delicate tweaks (are claimed to) offer are often so small as to be not worth the effort.

IMO it's better to have a PC that meets 95% of your performance needs and which last 10 years than to have a PC that you've tweaked to meet 98% of your performance needs and which lasts only 5 years.
 
The Intel CPU Test failed and also revealed both 0x101 and 0x124 bugchecks. 0x124 = Machine Check Exception (Unknown Hardware Failure).

Part of the Intel CPU report to the 1st error:

Code: 
...#SSU#...
#Logs#System Messages#Included
-------------------------------------------------------------------
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000101 (0x000000000000000c, 0x0000000000000000, 0xffffd08038fe4180, 0x000000000000000a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b59e5aa9-cd7b-4f9a-bd78-fd63b239fe9a.
-------------------------------------------------------------------
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Dump file creation failed due to error during dump creation.
-------------------------------------------------------------------
Dump file creation failed due to error during dump creation.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The previous system shutdown at 8:50:35 PM on ‎5/‎8/‎2023 was unexpected.
-------------------------------------------------------------------
The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate.
-------------------------------------------------------------------

A 0x124 error:
Code: 
The previous system shutdown at 10:56:21 AM on ‎3/‎3/‎2023 was unexpected.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe78dec614028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 6eb2024f-f3d1-40e3-bc57-c889bc30f352.
-------------------------------------------------------------------
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
-------------------------------------------------------------------
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor APIC ID: 10

The details view of this entry contains further information.
-------------------------------------------------------------------

Also listed was file corruption on drives c: and d: The Intel report said to run chkdsk /r /f on each.

Bring up an Admin CMD prompt. Type/paste into the shell:
Code: 
chkdsk /f /r

Hit ENTER. Answer to reboot system.

Same as above for drive d: except type d: [ENTER] first. Then run chkdsk per above; reboot system.

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top