SYSTEM_SERVICE_EXCEPTION when searching in start menu

Looking at the usual causes, there is the memory option left.
Please test your memory

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

I was using Firefox and I had just clicked a tab when I got this error:

IRQL_NOT_LESS_OR_EQUAL

0x0000000a (0x0000000000080008, 0x0000000000000002, 0x0000000000000000, 0xfffff800bc2a3273).

According to the ocumentation, in this Stop error message, each parameter is a hexadecimal number that refers to a specific issue:

Parameter 1 - An address that was referenced incorrectly.
Parameter 2 - An IRQL that was required to access the memory.
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation.
Parameter 4 - The address of the instruction that referenced memory in parameter 1.

Please test your memory with the instructions earlier given.

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000080008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800bc2a3273, address which referenced memory

As this is a read operation, a driver requested data from the memory but received corrupted data.

Joergi said:

Thanks for analyzing this second bluescreen! As this is a different problem than the problem in the initial post of this thread, I had posted this new problem into a separate thread. I think it might well be that this second issue is not related to the first one.

Anyway, Memtest ran through without errors.

And now?

Doesn't matter, you get BSOD's, please keep it in 1 thread as long as you get them.

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Joergi said:

I'll add a space between the command and the actual parameter....:)

That is fine, it actually doesn't matter with sfc
With DISM, it does matter.

I finally had the time to run sfc /scannow. It finished without finding any violation.

So...what else?

Does the dump contain any information, on what exactly caused this read error in the IRQL_NOT_LESS_OR_EQUAL screen?

You know as much as I about the crash.

Please make sure the frequency of the RAM in the BIOS is supported by the motherboard.