Windows 10: Random IRQL_NOT_LESS_OR_EQUAL twice or three times in a week

Previously my VAIO laptop with Win 8.1 worked well for some years. Then two months ago I upgraded it to Win 10 but it caused random BSOD, happened twice or three times in a week. The BSOD mentioned "IRQL_NOT_LESS_OR_EQUAL". So I formatted the harddisk (using "clean" command in diskpart) and reinstalled Win 10. Then Windows Update installed some programs automatically. I added just Chrome and Steam (to play Team Fortress) but there is still the same random BSOD.

Eventviewer gives too little information. Blue Screen View mentions it caused by ntoskrnl.exe. I'm unable to find which driver causes the BSOD. So here I attach a zip file that is generated by dm_log_collector.exe and hope someone can pinpoint the driver that causes the BSOD.


Thanks

Attachment 93194

:)

 

Intermittant (three times a week) slowdown in Windows 10 requiring restart

Hello Petitor,

Apology for delayed response.

I would suggest you to follow the suggestions provided by Sachin Venkatesh replied on November 12, 2015 from the link given below and check.

Refer:

DistributedCOM Error event ID 10016

Hope this information is helpful. Do let us know if you need any further assistance, we'll be glad to assist you.

 

Intermittant (three times a week) slowdown in Windows 10 requiring restart

Thanks for both your reply. My question is that, although it may be fixable, is it likely to cause the entire system to become unresponsive in the way described in the original post?

 

There is only one dump file, presumably because you have only has the one BSOD since you clean installed.

If you have any more BSOD's the extra data could be useful. For now all I can pick out is a reference to an Intel Graphics Driver misbehaving.
Code: ffffd000`23fe69c8 fffff800`c4e16935Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys igdkmd64+0x16935[/quote] Code: 2: kd> lmvm igdkmd64 Browse full module list start end module name fffff800`c4e00000 fffff800`c51b8000 igdkmd64 (deferred) Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys Image name: igdkmd64.sys Timestamp: Mon Dec 21 19:46:50 2015 (5678572A) CheckSum: 003A4051 ImageSize: 003B8000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
Are you able to roll back the Intel Graphics Driver or find an alternative from Sony?

 

Thanks for analyzing my dump file. You‘re right, there is only one dump file because I recently clean-installed. Actually the laptop has experienced two crashes (in different days) ==> one this BSOD and one frozen/hang which I think it was unable to generate any dump file.

Yes I'm able to rollback the Intel Graphics Driver but the frozen/hang has happened before the Windows-Update updated the driver yet, so that Win10 Pro was still fresh and I think rolling back the driver would not fix the problem.

Sony website provides Intel Graphics Driver only for Win7 Ultimate, Win8 Pro and Win8.1 Pro, not for Win10 Pro.
Sony Asia Pacific

If the laptop experiences the BSOD again, I will post more dump file here


Thanks

 

The SONY driver for W8.1 will probably work fine with W10 and would be worth trying if you are still getting BSODs

 

I have tried to install the Sony driver for Win8.1 Pro but it got error message: “Unable to conform the current system environment”. That driver doesn’t work on Win10 Pro.

So I downloaded the newer driver from Intel website to replace the driver that was installed by Windows Update.

Hope the replacement solves the problem. If it's still getting BSOD, I will post the new dump file here.


Thanks

 

Hi

I just got second BSOD.

I attached the dump file below and hope it gives a clue to faulty driver.

Thanks *Smile

Attachment 95077

 

Hello Bozhart *Smile

The crash happened because of a processor problem - one core attempted to get the attention of another core, in order to synchronise their activites with respect to an operation that requires coordination of the processor cores. Here is the code:
Code: CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffd001d1681180, The PRCB address of the hung processor. Arg4: 0000000000000003, The index of the hung processor.[/quote] The problem is more likely to be a driver rather than the CPU hardware being faulty. I found reference to a driver not loading properly:
Code: ffffd001`d1f58338 fffff801`ffb3b330Unable to load image \SystemRoot\System32\drivers\amdkmpfd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amdkmpfd.sys *** ERROR: Module load completed but symbols could not be loaded for amdkmpfd.sys amdkmpfd+0xb330[/quote] This would tie in with the crash and suggests you need to try and update or reinstall this driver: AMD PCI Root Bus Lower Filter. It was most likely installed along with your graphics drivers. As they are all dated 2015 there is most likely an update you can use.

 

I have just replaced AMD Catalyst package that came from Windows Update with newer AMD Crimson package (16.2.1 beta - 3/1/2016).

It changed the version of amdkmpfd.sys from 8.14.1.6028 (12/16/2015) to 8.14.1.6032 (2/10/2016).

I'll update if it's still getting BSOD.


Thanks

 

Hi

In last two weeks the laptop got some "frozens" (lock ups) and only one new dump file, see the attachment below. Thanks

By the way, Windows Anniversary Update (version 1607) has been released to public on August 2, 2016. Will it be worth clean-reinstalling this new version into the laptop to see if it’s still getting crash?

Attachment 97703

 

There was a problem identified in the crash dump thread:
Code: ffffd000`261b6700 fffff961`127ecf40Unable to load image \SystemRoot\System32\win32kbase.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32kbase.sys *** ERROR: Module load completed but symbols could not be loaded for win32kbase.sys win32kbase+0x5cf40[/quote] This driver is part of the windows operating system, and so your suggestion to try the W10 update is worth trying. There is no need to clean install, just let the system update - it will be a full update taking up to 2 hours to complete. You can force the update to start by visiting: https://support.microsoft.com/en-gb/help/12387/windows-10-update-history?ocid=update_setting_client

 

Hi

This attachment is fourth dump file. Hope this will give more clues.

I haven't upgraded yet Windows 10 to version 1607 because my internet is too slow.
I will ask my friend to download the newer WIndows 10 ISO to DVD.


Thanks

Attachment 99151