Irql_not_less_or_equal

Hi Guys.

I know there are loads of posts about this IRQL_NOT_LESS_OR_EQUAL problem. I've looked at

Blue Screen of Death (BSOD) Posting Instructions

I've downloaded and run DM Log Collector which saved txt files in SFdebugFiles folder. Even though the smallest file is 2kb the drivers.txt is 67kb but there is nothing in it.

I can upload any of the 6 txt files you want to see + 7 dmp files?

Its a Samsung NP350E7C-A04UK Laptop
Intel Pentium B970 processor (2MB L3 Cache) Intel HM70
2.3GHz processor speed
6GB DDR3 System Memory at 1333MHz (4GB x 1 + 2GB x 1) 2 SODIMM

I've run Windows Memory Diagnostic. I've looked at the event viewer at the results. The laptop won't keep running long enough to check things out.

I have a memory checker on CD but the original DVD drive doesn't open properly I have an external USB DVD drive which I use to install software.

This laptop has run I won't say perfectly for a few years as there are annoying bugs in Windows 7 but its generally pretty good.

Any suggestions would be appreciated.

Ok Roy I've added to files.

I will try sfc /scannow

As for chkdsk /r this process is a pain in the backside as it takes bleeding hours to do. I even left it running all night and it eventually finished in the morning.

Thanks Roy.

Update:

Event viewer:

Level Date and Time Source Event ID Task Category
Critical 20/03/2017 13:42:23 Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log Name: Microsoft-Windows-CodeIntegrity/Operational
Source: Microsoft-Windows-CodeIntegrity
Date: 20/03/2017 15:24:35
Event ID: 3001
Task Category: (1)
Level: Warning
Keywords:
User: SYSTEM
Computer: Samsung-Laptop
Description:
Code Integrity determined an unsigned kernel module \Device\HarddiskVolume1\Windows\System32\drivers\multikey.sys is loaded into the system. Check with the publisher to see if a signed version of the kernel module is available.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-CodeIntegrity" Guid="{4EE76BD8-3CF4-44A0-A0AC-3937643E37A3}" />
<EventID>3001</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>101</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2017-03-20T15:24:35.964421900Z" />
<EventRecordID>803</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="84" />
<Channel>Microsoft-Windows-CodeIntegrity/Operational</Channel>
<Computer>Samsung-Laptop</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FileNameLength">61</Data>
<Data Name="FileNameBuffer">\Device\HarddiskVolume1\Windows\System32\drivers\multikey.sys</Data>
</EventData>
</Event>


//./root/CIMV2
SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99
0x80041003

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 20/03/2017 16:01:19
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Samsung-Laptop
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
<EventID Qualifiers="49152">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-20T16:01:19.000000000Z" />
<EventRecordID>50233</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Samsung-Laptop</Computer>
<Security />
</System>
<EventData>
<Data>//./root/CIMV2</Data>
<Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage &gt; 99</Data>
<Data>0x80041003</Data>
</EventData>
</Event>

Ok I did run sfc /scannow but it still gets the BSOD after a few minutes. I open Computer and right-click on the hard drive for properties. I clicked check drive for errors. I did a restart and chkdsk started. I went out of the room for a minute when I can back Windows had started again.

I had to run cmd prompt and type in chkdsk /r /f /x, its said it would schedule on the next startup (I had to do that last time I did a chkdsk. I restarted and chkdsk started. It gets through stage 1, 2, 3 pretty quick. Stage 4 takes for ever it gets to 18% and doesn't go up even though the file count goes up slowly. I left it running and Windows restarted.

I looked at C:\Windows\Logs\CBS\CBS.log to see the results of sfc /scannow the file is quite bit at 2,516kb. Without deciphering what each line of code means that would take hours. I can post this file if its needed?

I looked for the chkdsk log file.

Location of chkdsk log file after scan

Wininit for yesterday and saved the log file.

Level Date and Time Source Event ID Task Category
Information 21/03/2017 01:58:09 Microsoft-Windows-Wininit 1001 None "
Checking file system on C:
The type of the file system is NTFS.
Volume label is Hard Drive.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
1891840 file records processed.
File verification completed.
5633 large file records processed.
0 bad file records processed.
6 EA records processed.
45 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
2116958 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
1891840 file SDs/SIDs processed.
Cleaning up 284 unused index entries from index $SII of file 0x9.
Cleaning up 284 unused index entries from index $SDH of file 0x9.
Cleaning up 284 unused security descriptors.
Security descriptor verification completed.
112560 data files processed.
CHKDSK is verifying Usn Journal...
36982056 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
1891824 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
84100398 free clusters processed.
Free space verification is complete.
Adding 7 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
976760535 KB total disk space.
637675812 KB in 1754518 files.
657068 KB in 112561 indexes.
28 KB in bad sectors.
2026059 KB in use by the system.
65536 KB occupied by the log file.
336401568 KB available on disk.
4096 bytes in each allocation unit.
244190133 total allocation units on disk.
84100392 allocation units available on disk.
Internal Info:
00 de 1c 00 4f 7d 1c 00 06 35 31 00 00 00 00 00 ....O}...51.....
01 0a 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 ....-...........
b0 8d 2f 00 50 01 2e 00 98 1c 2e 00 00 00 2e 00 ../.P...........
Windows has finished checking your disk.
Please wait while your computer restarts.

I only see 28 KB in bad sectors.

As I've said I ran Windows Memory Diagnostic. After it restarted I check the errors found it said:

Description
The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement
Problem signature
Problem Event Name: MemDiagV1
Range of memory size: 3072
Launch type: Manual
Schedule type: Immediate
Completion type: Pass
Test type: Standard
Failed tests: 0
Number of bad pages: 0
Test duration in seconds: 390
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Extra information about the problem
Bucket ID: 231860051

It strange it takes chkdsk 13 hours to complete.

Everything appears to be working normally. I will check it keeps that way for a day or two then mark this thread as Solved.

Thank you Roy.

Well its been working ok for the past week so problem Solved. Thanks again Roy.

I have another problem which has developed over the past week, so I will make a new thread in Microsoft Office.