Windows 10: SYSTEM_SERVICE_EXCEPTION when searching in start menu

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[/quote] As this is a read operation, a driver requested data from the memory but received corrupted data.

 

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.

 

I'll add a space between the command and the actual parameter....*Smile

 

That is fine, it actually doesn't matter with sfc *Wink
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.

 

Does it really not contain more information? A file name? A process name or something like that?

 

Unfortunately I cannot find much in the dump, the active process was the search indexer FYI.

Moving over to drivers.


Warning I don't know exactly what driver you should update from your manufacturer as you didn't fill in your system specs although I requested so.
Please first check your manufacturer for driver updates BEFORE going to the site for driver updates
A list of outdated drivers, some links are for information about the drivers.

• TeeDriverx64
• NTIDrvr (update via your manufacturer)
• k57nd60a (update via your manufacturer)
• IntcDAud (Intel or manufacturer)
• btath_bus (update via your manufacturer)
• bScsiSDa
• bScsiMSa
• b57xdmp
• b57xdbd
• aPs2Kb2Hid

 

Do you have a process name of the search indexer?

As for the drivers: That is a list of all non-Microsoft drivers, right?

 

It is called searchindexer, from Microsoft most likely.

That is right yes.

 

SearchIndexer.exe is located in C:\Windows\system32. It is the Search Index Creation tool by Microsoft.

Is it that application, which actually caused the bluescreen? If so, does the dump contain any information to why this tool is crashing?

 

Have you updated the drivers?

I cannot answer your question as I doubt it a lot, but with Windows 10 it could be possible.

The why is for most causes explained in my previous post.
It is pretty general, but it is what in most cases happens.
If you want details, you'll need to ask an expert for it, because I cannot give you it.

 

If you see any updates, please tell me, but as far as I can tell, I am using the latest versions. *Smile

 

I am sorry, I have been quite busy so I have not checked for any updates *Sad