Bsod - driver_irql_not_less_or_equal

zbook said:

1) update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
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.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)


2) When were the RAM modules installed?

3) Were the RAM modules seen on the Qualified Vendor List (QVL) ?

4) Post a share link using one drive, drop box, or google drive for: C:\windows\memory.dmp

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
14/02/2020 19:42:21    795,57 C:\WINDOWS\MEMORY.DMP

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /scanhealth
8) dism /online /cleanup-image /restorehealth
9) sfc /scannow
10) chkdsk /scan
11) wmic recoveros set autoreboot = false
12) wmic recoveros set DebugInfoType = 7
13) wmic recoveros get autoreboot
14) wmic recoveros get DebugInfoType
15) bcdedit /enum {badmemory}

16) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

17) Make sure that there is no over clocking while troubleshooting

18) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

19) Remove this RAM module:
Kingston 99U5471-054.A00LF

20) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.

a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool

The testing is done not by time but by passes.
The more passes the better the testing conditions.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer after removal of the Kingston RAM module.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM

21) Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean

22) Malwarebytes can be reinstalled one week after the last BSOD or unexpected shutdown or restart

The 8 passes are gonna take a while for me to post here. I left it overnight and it only completed 3 passes after 7 hours. But I can provide 5-16 right now. And I'll upload the memory dump to Google Drive later today.

Microsoft Windows [Version 10.0.18362.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.592

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.592

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is 8D.

Stage 1: Examining basic file system structure ...
1737216 file records processed.
File verification completed.
7403 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
461 reparse records processed.
1954222 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
461 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
108504 data files processed.
CHKDSK is verifying Usn Journal...
37079632 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

219059445 KB total disk space.
121566916 KB in 555432 files.
322252 KB in 108505 indexes.
0 KB in bad sectors.
1859937 KB in use by the system.
65536 KB occupied by the log file.
95310340 KB available on disk.

4096 bytes in each allocation unit.
54764861 total allocation units on disk.
23827585 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-IOCS7GP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-IOCS7GP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

PS.: I did remove the Kingston stick and uninstalled Malwarebytes for the time being. I'm thinking about jumping straight to test each RAM on each DIMM as that looks like it's going to be faster than testing the 16GB together.

Testing 2 RAM modules simultaneously allows testing the dual channel capability of the motherboard.
So this is a useful testing method.

zbook said:

Testing 2 RAM modules simultaneously allows testing the dual channel capability of the motherboard.
So this is a useful testing method.

I see. That being the case, here's the test for the 2 modules. The tests for each DIMM with a single module will take a bit of time.

Memtest 86+ version 5.01: 16 GB (2 x 8 GB) ,9 passes, 0 errors = test pass

There are problems that cannot be tested.
For example all DIMM and all RAM can be tested one at a time and pass.
The computer can still have unexpected shutdowns and restarts.
This is typically caused by mismatched RAM.
The RAM testing is not capable of testing good RAM that is mismatched and reporting problems.

The computer or motherboard manufacturer tests RAM modules and often publish Qualified Vendor Lists (QVL)

Only use RAM that is matched (same SKU) and is on the QVL.

So now test the computer for one week without the Kingston RAM module.

Report into the thread any unexpected shutdowns or restarts including BSOD>