[SOLVED] [BSOD] Memory_management / SYSTEM_SERVICE_EXCEPTION related to ntoskrnl.exe

[leorochaa]

Hello.

I'm having this problem since a long time (about 6 months). Every time I turn off my computer and turn it on again, some minutes later, I get a BSOD related to ntoskrnl.exe. I'm hybernating my windows so this happens less. The problem is that when my electricity turns off I'm "forced" to turn off my computer and it starts again.

First I was having this problem with windows 10. I've reinstalled it more than one time without success. After that I've tryed windows 11 (which I'm using now) but the problems still persists.

System informations:

• Intel Core i5-10400F
• GIGABYTE B460M-GAMING-HD
• NVIDIA GeForce GTX 1660 SUPER
• 1 x 16GB CRUCIAL DDR4 2666MHZ
• 1TB Samsung 980 NVME
• Colorful SL500 480GB

What i tried so far:

• Fresh reinstall of windows 11
• BIOS update
• Checked all drivers updates
• Running windows memory diagnostic check (had an error)
  • After I've done memtest86 without errors (it took 4 hours)

Minidump files: https://1drv.ms/u/s!Am-KRFGl-i84uyKozZ_LAsjqj_C2?e=hi37Ye

 

[white.a.drew]

Hello.

I'm having this problem since a long time (about 6 months). Every time I turn off my computer and turn it on again, some minutes later, I get a BSOD related to ntoskrnl.exe. I'm hybernating my windows so this happens less. The problem is that when my electricity turns off I'm "forced" to turn off my computer and it starts again.

First I was having this problem with windows 10. I've reinstalled it more than one time without success. After that I've tryed windows 11 (witch I'm using now) but the problems still persists.

System informations:

• Intel Core i5-10400F
• GIGABYTE B460M-GAMING-HD
• NVIDIA GeForce GTX 1660 SUPER
• 1 x 16GB CRUCIAL DDR4 2666MHZ
• 1TB Samsung 980 NVME
• Colorful SL500 480GB

What i tried so far:

• Fresh reinstall of windows 11
• BIOS update
• Checked all drivers updates
• Running windows memory diagnostic check (had an error)
  • After I've done memtest86 without errors (it took 4 hours)

Minidump files: https://1drv.ms/u/s!Am-KRFGl-i84uyKozZ_LAsjqj_C2?e=hi37Ye

The system diag maybe telling you the ram isn't compatible and force booting. Memtest86 test the modules themselves. Not compatible the system will. That maybe error one you are getting, two may just be you have the ram in the wrong slot,3 the dimm slot maybe shotty

 

[leorochaa]

Hello!

The motherboard has two slots of ram. I've tested in both and the problem still persists.

I'm thinking about buying another ram to test if the problem goes away. What do you think about it?

Regards

 

[Satan-IR]

Please verify if this is your motherboard here:
here : B460M GAMING HD (rev. 1.0)

As said above, have you tried the RAM stick in the other RAM slot?

Also the RAM part number seems to be BLS16G4D26BFSB.16FD which is not in the Gigabyte RAM QVL list for that motherboard here. It might not be compatible at all.

 

[leorochaa]

Please verify if this is your motherboard here:
here : B460M GAMING HD (rev. 1.0)

As said above, have you tried the RAM stick in the other RAM slot?

Also the RAM part number seems to be BLS16G4D26BFSB.16FD which is not in the Gigabyte RAM QVL list for that motherboard here. It might not be compatible at all.

I've already tried the RAM stick in the other RAM slot.

I'm going to buy another RAM stick to test it. I'm looking for a RAM which is compatible with the motherboard.

 

[johnbl]

you were running spotify, it was talking to microsoft streaming service on the machine then it got an error indicating the device went away. that led to the bugcheck.

it could be a bug in spotify, a bug in the driver or maybe the device did go away. I could not read the device list from a minidump but if it is a USB device sometimes the usb port goes to sleep and the device can not wake it back up. you might go into windows control panel, find device manager and right click on the usb ports and bring up properties. find the power management setting and tell windows not to let the ports to sleep. (if this is a usb device)

in general, if you can not find the device that has the bad device driver you would update the bios, the motherboard drivers and hope it fixes the problem. if that fails you should change the memory dump type to kernel and provide the next kernel dump.
c:\windows\memory.dmp file. This will have info on your plug and play system and usb subsystem.

you also have 3 drivers I have never seen:
C:\Windows\system32\drivers\wsddpp.sys Fri Feb 5 14:34:32 2021
C:\Windows\system32\drivers\wsddprm.sys Tue Feb 9 04:52:54 2021
C:\Program Files\Topaz OFD\Warsaw\wsddin64.sys Tue Feb 9 05:17:54 2021
by GAS Tecnologia
(i would not run it if I am the only one using the machine)

https://www.shouldiremoveit.com/warsaw-64-bits-174497-program.aspx

you should confirm if you need this or not. the description indicates it runs software when other people log onto your machine. Maybe for a hardware/software key for a shared machine? I do not know

 

[Satan-IR]

I've already tried the RAM stick in the other RAM slot.

I'm going to buy another RAM stick to test it. I'm looking for a RAM which is compatible with the motherboard.

I would do what @johnbl recommends before buying RAM.

I actually had a little time now to run the dumps quickly. In two of the dumps Discord.exe is the process named in the dump. In another one slack.exe is in the dump. In another one Spotify.exe is named. Not saying these cause the crash it's most probably drivers and these software are acutally 'victims'.

Another thing is you said you reinstalled Windows 10 few times (hopefully clean install?). Then Windows 11 and it's still there. This could either mean a hardware issue (less likely). Unless you remember adding some hardware and it's relevant driver and it all started? Or that it's a driver issue (more likely) caused by something you installed in all these OS installations. Maybe the software johnbl said?

 

[leorochaa]

you were running spotify, it was talking to microsoft streaming service on the machine then it got an error indicating the device went away. that led to the bugcheck.

it could be a bug in spotify, a bug in the driver or maybe the device did go away. I could not read the device list from a minidump but if it is a USB device sometimes the usb port goes to sleep and the device can not wake it back up. you might go into windows control panel, find device manager and right click on the usb ports and bring up properties. find the power management setting and tell windows not to let the ports to sleep. (if this is a usb device)

in general, if you can not find the device that has the bad device driver you would update the bios, the motherboard drivers and hope it fixes the problem. if that fails you should change the memory dump type to kernel and provide the next kernel dump.
c:\windows\memory.dmp file. This will have info on your plug and play system and usb subsystem.

you also have 3 drivers I have never seen:
C:\Windows\system32\drivers\wsddpp.sys Fri Feb 5 14:34:32 2021
C:\Windows\system32\drivers\wsddprm.sys Tue Feb 9 04:52:54 2021
C:\Program Files\Topaz OFD\Warsaw\wsddin64.sys Tue Feb 9 05:17:54 2021
by GAS Tecnologia
(i would not run it if I am the only one using the machine)

https://www.shouldiremoveit.com/warsaw-64-bits-174497-program.aspx

you should confirm if you need this or not. the description indicates it runs software when other people log onto your machine. Maybe for a hardware/software key for a shared machine? I do not know

Hello!

• I've turned of the settings to not let the ports sleep now.
• I'm going to change the memory dump type to kernel.
• About the drivers, they are used for my internet banking system here in Brazil. I use them in other computers and don't have problems about it.

Thanks!

 

[leorochaa]

I would do what @johnbl recommends before buying RAM.

I actually had a little time now to run the dumps quickly. In two of the dumps Discord.exe is the process named in the dump. In another one slack.exe is in the dump. In another one Spotify.exe is named. Not saying these cause the crash it's most probably drivers and these software are acutally 'victims'.

Another thing is you said you reinstalled Windows 10 few times (hopefully clean install?). Then Windows 11 and it's still there. This could either mean a hardware issue (less likely). Unless you remember adding some hardware and it's relevant driver and it all started? Or that it's a driver issue (more likely) caused by something you installed in all these OS installations. Maybe the software johnbl said?

About the windows 10 they were all clean install. The first times I got this BSOD I had only installed the NVIDIA graphic drivers, so I don't think is a driver issue. The hardware wasn't changed since I mounted my computer.

One of the things that is strange for me is that the windows memory diagnostic tools had errors. I don't know if any driver can influence on that test. That's why I'm thinking about a hardware problem.

On the other hand the memtest86 had no problems. 🤷‍♂️

 

[white.a.drew]

About the windows 10 they were all clean install. The first times I got this BSOD I had only installed the NVIDIA graphic drivers, so I don't think is a driver issue. The hardware wasn't changed since I mounted my computer.

One of the things that is strange for me is that the windows memory diagnostic tools had errors. I don't know if any driver can influence on that test. That's why I'm thinking about a hardware problem.

On the other hand the memtest86 had no problems. 🤷‍♂️

This is a ram issue at this point from everything you are saying and you have tried the only thing at this point is the not supported stick bugging the system cache

 

[Satan-IR]

About the windows 10 they were all clean install. The first times I got this BSOD I had only installed the NVIDIA graphic drivers, so I don't think is a driver issue. The hardware wasn't changed since I mounted my computer.

One of the things that is strange for me is that the windows memory diagnostic tools had errors. I don't know if any driver can influence on that test. That's why I'm thinking about a hardware problem.

On the other hand the memtest86 had no problems. 🤷‍♂️

From your post#1 I thought none of the tests showed errors, I missed that. If Windows Memory diagnostic shows errors there's something wrong with the RAM or the system (memory controller inside the CPU) doesn't like it or something.

I'm going to buy another RAM stick to test it. I'm looking for a RAM which is compatible with the motherboard.

Note that when some RAM is not on the motherboard QVL list for RAM it doesn't necessarily mean it's not compatible. The list is the RAM sticks the manufacturer actually tested on the board before releasig it into market and according to their test they work. Depending on very slight variations in chips in RAM production even identical sticks with all the same specs from save manufacturer made on same day are not 100% the same. I've seen one or two boards that didn't work with a RAM which WAS in the QVL list!

Can you perhaps borrow a stick of RAM from someone? I would check if the issue are resolved with another RAM module before buying RAM.

 

[leorochaa]

From your post#1 I thought none of the tests showed errors, I missed that. If Windows Memory diagnostic shows errors there's something wrong with the RAM or the system (memory controller inside the CPU) doesn't like it or something.

Note that when some RAM is not on the motherboard QVL list for RAM it doesn't necessarily mean it's not compatible. The list is the RAM sticks the manufacturer actually tested on the board before releasig it into market and according to their test they work. Depending on very slight variations in chips in RAM production even identical sticks with all the same specs from save manufacturer made on same day are not 100% the same. I've seen one or two boards that didn't work with a RAM which WAS in the QVL list!

Can you perhaps borrow a stick of RAM from someone? I would check if the issue are resolved with another RAM module before buying RAM.

I've tryed with one of my friends to borrow some ram but none of them have 2666mhz RAM. In some days the new RAM will arrive and we will have answers

Today I got new erros with IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA

 

[white.a.drew]

I've tryed with one of my friends to borrow some ram but none of them have 2666mhz RAM. In some days the new RAM will arrive and we will have answers

Today I got new erros with IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA

There's is a issue in the ram caching weather it's the ram not supported, or cpu cache decoder is dying, there's a issue somewhere in the cache logs

 

[leorochaa]

I installed the new memory today (I looked one of the memories supported by the motherboard) and seems like everything is ok now.

Thanks for you all.