Logging in to my desktop takes 5+ minutes... Same with shutting down (versus 5 seconds before). Not sure how to fix this or revert (referring to which service makes my pc speed normal). No Bsod but there was one black screen freeze.
Around 12.
Yes but I have no way of backing my files up.
Edit: that last one it wouldn't even shutdown, just went back to welcome and hung for 10 minutes.
Okay... I managed to enable my internet again, but it won't show the connectivity icon on the taskbar... not sure what I need to reenable for that.
So, with hardly no services running, I got the same error. Seems the logs just blame it on whatever though:
Attachment 141083
Attachment 141091
Last edited by 1212; 25 Jun 2017 at 08:12.
Its not sure that it could be the CPU, but here are a few things I found out:
This is the WHEA summary from the latest bsods, first one is from the full memory dump:
Code:0x124_GenuineIntel_PROCESSOR_CACHE - Cache error - ICACHEL0_IRD_ERR (Proc 2 Bank 0) memory_corruption - Cache error - ICACHEL0_IRD_ERR (Proc 3 Bank 0) memory_corruption - Cache error - ICACHEL0_IRD_ERR (Proc 3 Bank 0) memory_corruption - Cache error - ICACHEL0_IRD_ERR (Proc 3 Bank 0) memory_corruption - Cache error - ICACHEL0_IRD_ERR (Proc 2 Bank 0) memory_corruption - Cache error - ICACHEL0_IRD_ERR (Proc 2 Bank 0)
L0 cache pending between Proc 2 and 3.
Analysis of full memory dmp:
Code:0x00000124: WHEA_UNCORRECTABLE_ERROR (23.06.2017 16:27:01) [Windows 10] CAUSED BY: 0x124_GenuineIntel_PROCESSOR_CACHE [16.07.2016] WHEA Notify: Machine Check Exception Type: Cache error Error: ICACHEL0_IRD_ERR (Proc 2 Bank 0) PROCESS: chrome.exe
Code:2: kd> !tz 0 - ThermalZone @ 0xffffe70ff51d2680 Zone: \_TZ.TZ0 State: Read Flags: 0x00000002 Initialized Mode: Active PendingMode: Active ActivePoint: 0x00000000 PendingActivePoint: 0x00000000 Throttle: 0x00000064 PendingThrottle: 0x00000064 SampleRate: 0x00000000 ThrottleReasons: 0 OverThrottled: 0 ThermalStandby: 0 LastTime: 0x0000000000000000 LastTemp: 0x00000000 (0.0K) PassiveTimer: 0xffffe70ff51d26f0 PassiveDpc: 0xffffe70ff51d2730 Irp: 0xffffe70ff5017800 Device: 0xffffe70ff51efe40 Thermal Info: 0xffffe70ff51d2770Code:2: kd> !tzinfo 0xffffe70ff51d2770 ThermalInfo @ 0xffffe70ff51d2770 Stamp: 0x00000060 Constant1: 0x00000000 Constant2: 0x00000000 Period: 0x00000000 ActiveCnt: 0x00000000 MinThrottle: 0x00000000 OverThrottle: 0x00000000 Current Temperature: 0x00000db8 (351.2K) -> 78,05 °C Passive TripPoint Temperature: 0x00000000 (0.0K) ThermalStandby TripPoint Temperature: 0x00000000 (0.0K) Hibernate TripPoint Temperature: 0x00000000 (0.0K) Critical TripPoint Temperature: 0x00000f5c (393.2K)
The full memory dump show an relatively high temperature of 78 °C. This looks very high. Maybe another expert here can interpret this.
@BSODHunter, can you get a copy of the kernel dump online? The link provided by the OP seems to be expired.
Another 40 crashes later, probably going to be sending it back this week.
Attachment 141244
Whilst waiting for the download, I'm going to note a few things.
First thing, the reason why the BSOD was called
There are multiple similar errors, not all on the same core.
They all mean pretty much the same, the CPU was fetching instructions to execute when something went wrong.
I may be wrong, maybe the CPU is faulty and it was fetching improperly, but I do not think that the CPU is the cause.
IME it happens more often than not that whatever is giving instructions, after the CPU fetch request, is simply providing bad or improper instructions.
The issue with the 0x124 with a machine check exception, is that we cannot properly find out what gives the bad instructions. Not like with other crashes.
I've read some posts from experts about a year ago, they also say that the WHEA record is the most informative part and not even a kernel dump can provide all the information required to troubleshoot a WHEA at once.
Code:Error : ICACHEL0_IRD_ERR (Proc 3 Bank 0) Error : ICACHEL0_IRD_ERR (Proc 3 Bank 0) Error : ICACHEL0_IRD_ERR (Proc 3 Bank 0) Error : ICACHEL0_IRD_ERR (Proc 2 Bank 0)
@BSODHunter , what you point out about Chrome is a good catch.
Google Chrome has been known for causing 0x124 crashes in the past, with specific versions. Likely due to the hardware acceleration functionality which can simply be disabled in the settings. Chrome is the process that is the most active at the time of the crash, in 1 out of 13 crashes it is mentioned as the process name. I usually do not use the process name for analysis, because the process name is everytime different, but exceptions are there.
@zbook, your suggestion for stress testing the CPU is excellent. I do note you asked for the result, but if the test passed or not is not enough. Stress tests are not only there to identify if the part is capable of finishing it with success, it is also there to exploit things like temperature issues. With the CPU and GPU (and rarely drives) it is important to note as much information as possible. Intel has a good program which can find problems Prime95 can't, but Prime95 is IMHO better in finding temperature problems.
Temperature issues can have the result to a bad CPU, better prevent than resolve.
In this case, the temperature may be an issue. According to the specs of the i7-6700K the max temperature allowed is 64C, according to the kernel dump and as BSODHunter already pointed out it reaches nearly 80C.
This is the reason why you best request as much as possible information through photos and screenshots.
@1212 , we'll need to know all your system specs, mainly what cooling you're using.
It looks like your system is not being cooled well enough.
Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
Chrome has nothing to do with it. If it points to Chrome, it's because that was the only application open. Sometimes it'll say Opera, Firefox, whatever browser I'm using.
Attachment 141299
Specs:
Attachment 141300
PSU, per it being a laptop, is 100-240v & 19.5v output. Cooling system I don't know, but I've gotten frequent crashes even with it cool (though at rarer intervals).
Something I hadn't noticed before: while I pass Prim's torture tests with no issues, I did notice the CPU temps spike drastically, which is something I wasn't monitoring before.
Attachment 141266
Last edited by 1212; 26 Jun 2017 at 13:50.
I don't want to argue, but whether it is randomness or something that keeps occuring, if any pattern is there, like in your case Chrome, it has something to do with it.
I mentioned that Chrome is present in the dumps, because it is the process that was last active before the crash occured. If it may or may not be related, is yet to be proven.
Could you please provide the specs in the way it was requested, that way we could see it below every post of yours instead of a single post making troubleshooting a lot easier :)
Quote