Question Periodic system crashes and BSODs ?

[Samuelff]

Good afternoon, I have this problem. I have the Windows 10 operating system and I periodically get a blue screen of death due to an ntoskrnl.exe error.
SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED or IRQL_NOT_LESS_OR_EQUAL

Periodic system crashes and blue screens due to:
KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_SERVICE_EXCEPTION, or IRQL_NOT_LESS_OR_EQUAL errors.

There are 5 minidump files:
https://www.dropbox.com/t/2sgrfO4EY4E6kJ2v
If anyone knows how to fix this, I would be very grateful.

 

[Bob.B]

Good afternoon, I have this problem. I have the Windows 10 operating system and I periodically get a blue screen of death due to an ntoskrnl.exe error (SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED or IRQL_NOT_LESS_OR_EQUAL) Periodic system crashes and blue screens due to KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_SERVICE_EXCEPTION, or IRQL_NOT_LESS_OR_EQUAL errors.

There is 5 minidump files
https://www.dropbox.com/t/2sgrfO4EY4E6kJ2v
If anyone knows how to fix this, I would be very grateful.

Until someone comes along that knows how to read dumps put a copy of memtest86 on a flash stick.

Boot the stick and let it run.....no errors allowed.

 

[ubuysa]

Taking the dumps as a whole the most likely cause here is bad RAM and you're running with mismatched RAM. You have one stick of 4GB Samsung M471A5244CB0-CWE RAM - quite possible soldered in, since this looks like the RAM the laptop originally came with - and one stick of 16GB Kingston KF3200C20S4/16G RAM. The might look the same and run at the same speed but their internal timings are unlikely to match. Mismatched RAM causes a huge number of problems, which it's why it's always the first thing we look for.

You might well tell me that it's been working fine for years, but components age at different rates, and whilst they may have tolerated each other they may not be doing so now.

If you can remove the 4GB RAM (which I doubt) then please remove that and run on just the 16GB stick. If you cannot remove the 4GB then you'll need to remove the 16GB RAM that you added and see whether it's stable on just the 4GB.

 

[Samuelff]

Good afternoon, I did as you said. I hope it works or I'll wait until the next crash.

 

[ubuysa]

If you get another BSOD please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

BTW if it does turn out to be that the 16GB of RAM is not compatible I can help you find RAM that is.

 

[Samuelff]

If you get another BSOD please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need and will make diagnosing your problem easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

BTW if it does turn out to be that the 16GB of RAM is not compatible I can help you find RAM that is.

Just got a blue screen twice in a row after rebooting the system. Here is the info https://www.dropbox.com/t/Do0cJbU00gENWqAB

 

[Samuelff]

A few more crashes with a blue screen. https://www.dropbox.com/t/maZX2Rg0zkUHt60p

 

[ubuysa]

Ah, I see you did remove the 4GB RAM. Since you're still getting BSODs you now need to replace the 4GB RAM and remove the 16GB RAM.

If it still BSODs on just the 4GB RAM stick run the Sysnative data collection app again and upload the new output file. It is absolutely vital that we ensure bad RAM is not the cause because all these dumps could easily be down to bad RAM.

 

[Samuelff]

Ah, I see you did remove the 4GB RAM. Since you're still getting BSODs you now need to replace the 4GB RAM and remove the 16GB RAM.

If it still BSODs on just the 4GB RAM stick run the Sysnative data collection app again and upload the new output file. It is absolutely vital that we ensure bad RAM is not the cause because all these dumps could easily be down to bad RAM.

After reinstalling Windows, there were constant reboots and blue screens. I put back 2х 4GB cards that the laptop was purchased with. Here is information about the crash https://www.dropbox.com/t/FXGqyDtwPZPQiStl

 

[ubuysa]

Do these BSODs only happen when playing a game, or do they happen at other times?

I ask because on of the dumps shows that the BSOD was caused by a module called NEPp78one4, which I've never seen before. More worrying is that it's being loaded from your Temp folder...

  Image path: \??\C:\Temp\NEPp78one4

That suggests that it's not entirely kosher since it's not in a recognised installation folder.

The best I can find is that this model may be associated with an anti-cheat tool from NetEase. NEP modules seem to be related to NetEase. That's why I asked whether these BSODs only happen in-game. Anti-cheat tools are known to cause BSODs.

The other dump also has an NEP module loaded (NEPf6dn8rw) also being fetched from your Temp folder.

Of course, the fact that they are in a Temp folder might indicate that they are malware, so if you don't know what they are I would run a couple of good malware scans.

 

[Samuelff]

Do these BSODs only happen when playing a game, or do they happen at other times?

I ask because on of the dumps shows that the BSOD was caused by a module called NEPp78one4, which I've never seen before. More worrying is that it's being loaded from your Temp folder...

  Image path: \??\C:\Temp\NEPp78one4

That suggests that it's not entirely kosher since it's not in a recognised installation folder.

The best I can find is that this model may be associated with an anti-cheat tool from NetEase. NEP modules seem to be related to NetEase. That's why I asked whether these BSODs only happen in-game. Anti-cheat tools are known to cause BSODs.

The other dump also has an NEP module loaded (NEPf6dn8rw) also being fetched from your Temp folder.

Of course, the fact that they are in a Temp folder might indicate that they are malware, so if you don't know what they are I would run a couple of good malware scans.

So recently I launched the game Marvel Rivals about three times but every time I launched it a blue screen appeared. But the problem with blue screens appeared in me 2 years ago, but they weren't that often.

 

[ubuysa]

Yes, but do they only happen in games?

 

[Samuelff]

Yes, but do they only happen in games?

No, they started appearing periodically starting Thursday, no matter what I did, whether it was searching the Internet, diagnosing memory, checking the disk for malfunctions, even when I was installing Windows. Approximate time of system crash every 10-15 minutes, and maybe 3 times in a row.

 

[ubuysa]

If it BSODs during Windows install then it's a hardware problem for certain. To be sure, I'd like you to try starting Windows in Safe Mode. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. On the other hand, if it's stable in Safe Mode then your problem is with a third-party driver or service that wasn't loaded in Safe Mode. There is another technique we can use in that case to locate the problem service or driver.