Windows 10: BSOD SYSTEM_SERVICE_EXCEPTION 3b caused by memory_corruption LARGE

I'm having a BSOD problem and Windbg reports that it is caused by memory corruption. Memory tests are passing, so I'm thinking it might be system file/driver corruption. Can you please check my MEMORY.DMP Crash Dump File and let me know where the problem is?


https://1drv.ms/u/s!AnY1EzPvF7CxgutKHgdQALkFAKCN8g?e=c3955e

:)

 

BSOD SYSTEM_SERVICE_EXCEPTION (3b)

I have just got Windows 10 on my PC. It is legitimate as are all of the software I have installed (first day so there are really only the most basic programs). Recently I have been having BSODs with SYSTEM_SERVICE_EXCEPTION (3b) like every 30 mins.

Here are the dumps (the last in the list is the latest one chronologically)

Dropbox - Link not found

Dropbox - Link not found

Dropbox - Link not found

Dropbox - Link not found

Dropbox - Link not found

Please advice, what can it be?

 

BSOD SYSTEM_SERVICE_EXCEPTION (3b)

Hi Alex,

Thank you for posting in Microsoft Community and being a part of Windows 10.

I understand the inconvenience you are facing in accessing the operating system with Blue screen errors. Do not worry we will help you with this issue.

Do provide us the additional information to assist you better with this issue:

• What is the make and model of your device?
• Is Windows 10 pre-installed on your computer/ upgraded from previous operating system?
• Are you able to boot the device to desktop with this error messages?
• Did you make any software/hardware changes to the computer prior to this issue?

SYSTEM_SERVICE_EXCEPTION:

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics driver’s crossing over and passing bad data to the kernel code.

As it mainly seems to be an issues with the drivers, I suggest you to update all the drivers and also the chipset drivers from the manufacturer's website and check if the blue screen occurs.

IRQL_NOT_LESS_OR_EQUAL:

This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process
internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software.

If you are able to boot the device to desktop, try the below troubleshooting steps and check if it helps.

Step 1: I suggest you to boot the system to Safe Mode with Networking wherein the computer starts with basic drivers and no third party programs. Check if you are still receiving the error message.

Refer: Start your PC in safe mode in Windows 10


Step 2: If the issue does not persists in Safe Mode then perform a
Clean boot to
check if any third party application is causing the issue, as clean boot helps in eliminating software conflicts.

Disclaimer: Putting your system in
Clean Boot state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.

How to perform a clean boot in Windows

(Applies to Windows 10 as well)

Note: After troubleshooting, refer to the section “How to reset the computer to start as usual after troubleshooting with clean boot” to return the computer to a
Normal startup mode.

Step 3: Follow the below steps to
place the computer in normal mode.

• Press Windows + R keys to open Run
  command.
• Type msconfig and press Enter.
• In the System Configuration window, click on
  General tab.
• Select Start-up selection as Normal startup, click on
  Apply and Ok.
• Follow onscreen instructions.

Hope it helps. Reply to the post with an updated status of this issue and required information for further assistance.

 

BSOD System_Service_Exception (3b)


Been getting this particular BSOD on a near constant basis when running high'ish memory dependent games.
After a fair amount of trying to fix it up with sfc, driver verifier and removing near anything I can think of that caused the bug, based on similar stories I finally managed to track it down to (3b), but past that I have no idea what actually causes the BSOD.

Any help'd be appreciated.

Attachment 53634